I don’t understand why C:\path was fine under the 64 bit OS but refused
under the 32 bit OS, when the call to ZwOpenFile was always made during
DriverEntry. That has echoes of a buggable differnce between the two
platforms. Anyway, thanks for the heads up. It sounds like my pre-pending
??\Global\ to the path and file name requested by the user will resovle the
issue.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill Wandel
Sent: Wednesday, February 10, 2010 10:37 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] ZwOpenFile
Gary,
I know that you got this working by using Global but I am trying to
understand why that was necessary. ??\Gobal\ should always work so maybe
the rule becomes that we should always use it just to be safe. I think that
it is valid starting with XP.
FWIW I have completed two fairly simple WFP drivers, one of which is in a
shipping product and the other for a company that went out of business last
week.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com]
On Behalf Of Gary G. Little
Sent: Wednesday, February 10, 2010 10:08 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] ZwOpenFile
I currently open the file from DriverEntry which makes reading the file only
during driver load/initialization. That will need to change to do dynamic
updates of the loaded file without having to start/stop it.
Thanks for the information. Looks like you, David, and are about the only
folks working on WFP drivers.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill Wandel
Sent: Tuesday, February 09, 2010 7:54 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] ZwOpenFile
Gary,
I ran a x86 WIN7 test with my driver that uses ZwCreateFile to open a
configuration file. The path used is ??\c:\some path. The file was opened
from DriverEntry and it opened successfully. The file also opened
successfully from a work item.
In a somewhat related issue, I know that if you use NtCreateFile from a user
app you will get session 1 instead of the global directory if you use ??\
instead of ??\Global. I ran into this last week.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com]
On Behalf Of Gary G. Little
Sent: Tuesday, February 09, 2010 4:10 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] ZwOpenFile
Thanks Max, that appears to be the offering for which the OS gods were
looking. Did that come from documentation, or like me, trying everything you
could think of until you hit the right combination, better known as the
shotgun approach to programming? If you have documentation I would love to
have the link. So far everywhere I have looked, even in the WDK, goes
traipsing off into .Net and C#.
So then the question becomes why didn’t the 64bit OS fail in the same
manner? Is the global name space different between the two OS’s?
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Tuesday, February 09, 2010 12:11 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] ZwOpenFile
\??\C:\Temp\DomainNames.csv
Try ??\Global\C:\Temp\DomainNames.csv
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
__________ Information from ESET Smart Security, version of virus signature
database 4851 (20100209) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus signature
database 4852 (20100209) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus signature
database 4852 (20100209) __________
The message was checked by ESET Smart Security.
http://www.eset.com
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
__________ Information from ESET Smart Security, version of virus signature
database 4852 (20100209) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus signature
database 4854 (20100210) __________
The message was checked by ESET Smart Security.
http://www.eset.com
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
__________ Information from ESET Smart Security, version of virus signature
database 4854 (20100210) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus signature
database 4854 (20100210) __________
The message was checked by ESET Smart Security.
http://www.eset.com