STATUS_OBJECT_PATH_NOT_FOUND being returned from WdfDeviceCreate....

NTDEV
1

…why?

Based on searching Google for “STATUS_OBJECT_PATH_NOT_FOUND
WdfDeviceCreate” it looks like I am the first person to ever encounter
this error (not likely, but it is always interesting when a Google
search turns up zilch).

I have a software only driver that creates a “controller device” in my
device entry. Later my user mode app sends an IOCTL to my driver
requesting that it create a new virtual disk device. When I call
WdfDeviceCreate, I get back STATUS_OBJECT_PATH_NOT_FOUND. This seems
strange to me given that I’m trying to create the object- of course it
isn’t found.

my device init functions look like (this is suedo code- I replaced some
variables with the appropriate constant that they represent in this
particular case):

WdfDeviceInitSetExclusive(deviceInit, FALSE);
WdfDeviceInitSetIoType(deviceInit, WdfDeviceIoBuffered);
WdfDeviceInitSetDeviceType(deviceInit, FILE_DEVICE_CD_ROM);
WdfDeviceInitAssignName(deviceInit, “\Device\MyDevice\MyDeviceDvd1”);

Any ideas?

Thanks,
–Jeremy

2

Does the directory “MyDevice” exist?

In the debugger, what happens if you type “!object \Device\MyDevice”. I
suspect you’ll find there is no such directory, which is what’s causing
your problem. Either create the directory manually (WDF isn’t doing it
for you) or don’t put your device object in a non-existent directory.

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jeremy Chaney
Sent: Wednesday, September 06, 2006 5:36 PM
To: ntdev redirect
Subject: [ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

…why?

Based on searching Google for “STATUS_OBJECT_PATH_NOT_FOUND
WdfDeviceCreate” it looks like I am the first person to ever encounter
this error (not likely, but it is always interesting when a Google
search turns up zilch).

I have a software only driver that creates a “controller device” in my
device entry. Later my user mode app sends an IOCTL to my driver
requesting that it create a new virtual disk device. When I call
WdfDeviceCreate, I get back STATUS_OBJECT_PATH_NOT_FOUND. This seems
strange to me given that I’m trying to create the object- of course it
isn’t found.

my device init functions look like (this is suedo code- I replaced some
variables with the appropriate constant that they represent in this
particular case):

WdfDeviceInitSetExclusive(deviceInit, FALSE);
WdfDeviceInitSetIoType(deviceInit, WdfDeviceIoBuffered);
WdfDeviceInitSetDeviceType(deviceInit, FILE_DEVICE_CD_ROM);
WdfDeviceInitAssignName(deviceInit, “\Device\MyDevice\MyDeviceDvd1”);

Any ideas?

Thanks,
–Jeremy

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

Or more succinctly, why do you need a deeper object path then
\Device\MyDeviceDvd1? If you want to distinguish different interfaces
on the same device by using different symbolic links, you can use the
symbolic path to point to a deeper path, see
http://blogs.msdn.com/doronh/archive/2006/08/23/715612.aspx

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, September 06, 2006 6:30 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

Does the directory “MyDevice” exist?

In the debugger, what happens if you type “!object \Device\MyDevice”. I
suspect you’ll find there is no such directory, which is what’s causing
your problem. Either create the directory manually (WDF isn’t doing it
for you) or don’t put your device object in a non-existent directory.

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jeremy Chaney
Sent: Wednesday, September 06, 2006 5:36 PM
To: ntdev redirect
Subject: [ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

…why?

Based on searching Google for “STATUS_OBJECT_PATH_NOT_FOUND
WdfDeviceCreate” it looks like I am the first person to ever encounter
this error (not likely, but it is always interesting when a Google
search turns up zilch).

I have a software only driver that creates a “controller device” in my
device entry. Later my user mode app sends an IOCTL to my driver
requesting that it create a new virtual disk device. When I call
WdfDeviceCreate, I get back STATUS_OBJECT_PATH_NOT_FOUND. This seems
strange to me given that I’m trying to create the object- of course it
isn’t found.

my device init functions look like (this is suedo code- I replaced some
variables with the appropriate constant that they represent in this
particular case):

WdfDeviceInitSetExclusive(deviceInit, FALSE);
WdfDeviceInitSetIoType(deviceInit, WdfDeviceIoBuffered);
WdfDeviceInitSetDeviceType(deviceInit, FILE_DEVICE_CD_ROM);
WdfDeviceInitAssignName(deviceInit, “\Device\MyDevice\MyDeviceDvd1”);

Any ideas?

Thanks,
–Jeremy

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

4

I’m porting this code from a WDM driver, where for whatever reason (I’ve
been pulling source from many, many different samples) the path that I
had been using (and was working) was three levels deep. I changed it to
two levels as you suggested and now WdfDeviceCreate succeeds, but that
leads to a new problem- in my user mode app DefineDosDevice succeeds,
but CreateFile does not. I had this problem before in my WDM driver and
I fixed it by removing DO_DEVICE_INITIALIZING from my device object
flags. Is there an equivalent operation I need to perform in WDF? I
looked through the WdfDeviceInit methods and couldn’t find anything that
looked relevant.

Another interesting detail: I thought that if DefineDosDevice succeeds,
then using WinObj I should see my device under the Sessions/0/DosDevices
key, but it isn’t there.

Thanks,
–Jeremy

Doron Holan wrote:

Or more succinctly, why do you need a deeper object path then
\Device\MyDeviceDvd1? If you want to distinguish different interfaces
on the same device by using different symbolic links, you can use the
symbolic path to point to a deeper path, see
http://blogs.msdn.com/doronh/archive/2006/08/23/715612.aspx

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, September 06, 2006 6:30 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

Does the directory “MyDevice” exist?

In the debugger, what happens if you type “!object \Device\MyDevice”. I
suspect you’ll find there is no such directory, which is what’s causing
your problem. Either create the directory manually (WDF isn’t doing it
for you) or don’t put your device object in a non-existent directory.

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jeremy Chaney
Sent: Wednesday, September 06, 2006 5:36 PM
To: ntdev redirect
Subject: [ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

…why?

Based on searching Google for “STATUS_OBJECT_PATH_NOT_FOUND
WdfDeviceCreate” it looks like I am the first person to ever encounter
this error (not likely, but it is always interesting when a Google
search turns up zilch).

I have a software only driver that creates a “controller device” in my
device entry. Later my user mode app sends an IOCTL to my driver
requesting that it create a new virtual disk device. When I call
WdfDeviceCreate, I get back STATUS_OBJECT_PATH_NOT_FOUND. This seems
strange to me given that I’m trying to create the object- of course it
isn’t found.

my device init functions look like (this is suedo code- I replaced some
variables with the appropriate constant that they represent in this
particular case):

WdfDeviceInitSetExclusive(deviceInit, FALSE);
WdfDeviceInitSetIoType(deviceInit, WdfDeviceIoBuffered);
WdfDeviceInitSetDeviceType(deviceInit, FILE_DEVICE_CD_ROM);
WdfDeviceInitAssignName(deviceInit, “\Device\MyDevice\MyDeviceDvd1”);

Any ideas?

Thanks,
–Jeremy

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

5

You said that this is a controller device right? You need to call
WdfControlFinishInitializing

Beverly

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jeremy Chaney
Sent: Thursday, September 07, 2006 2:02 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

I’m porting this code from a WDM driver, where for whatever reason (I’ve
been pulling source from many, many different samples) the path that I
had been using (and was working) was three levels deep. I changed it to
two levels as you suggested and now WdfDeviceCreate succeeds, but that
leads to a new problem- in my user mode app DefineDosDevice succeeds,
but CreateFile does not. I had this problem before in my WDM driver and
I fixed it by removing DO_DEVICE_INITIALIZING from my device object
flags. Is there an equivalent operation I need to perform in WDF? I
looked through the WdfDeviceInit methods and couldn’t find anything that
looked relevant.

Another interesting detail: I thought that if DefineDosDevice succeeds,
then using WinObj I should see my device under the Sessions/0/DosDevices
key, but it isn’t there.

Thanks,
–Jeremy

Doron Holan wrote:

Or more succinctly, why do you need a deeper object path then
\Device\MyDeviceDvd1? If you want to distinguish different interfaces

on the same device by using different symbolic links, you can use the
symbolic path to point to a deeper path, see
http://blogs.msdn.com/doronh/archive/2006/08/23/715612.aspx

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, September 06, 2006 6:30 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

Does the directory “MyDevice” exist?

In the debugger, what happens if you type “!object \Device\MyDevice”.

I suspect you’ll find there is no such directory, which is what’s
causing your problem. Either create the directory manually (WDF isn’t

doing it for you) or don’t put your device object in a non-existent
directory.

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jeremy Chaney
Sent: Wednesday, September 06, 2006 5:36 PM
To: ntdev redirect
Subject: [ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

…why?

Based on searching Google for “STATUS_OBJECT_PATH_NOT_FOUND
WdfDeviceCreate” it looks like I am the first person to ever encounter

this error (not likely, but it is always interesting when a Google
search turns up zilch).

I have a software only driver that creates a “controller device” in my

device entry. Later my user mode app sends an IOCTL to my driver
requesting that it create a new virtual disk device. When I call
WdfDeviceCreate, I get back STATUS_OBJECT_PATH_NOT_FOUND. This seems
strange to me given that I’m trying to create the object- of course it

isn’t found.

my device init functions look like (this is suedo code- I replaced
some variables with the appropriate constant that they represent in
this particular case):

WdfDeviceInitSetExclusive(deviceInit, FALSE);
WdfDeviceInitSetIoType(deviceInit, WdfDeviceIoBuffered);
WdfDeviceInitSetDeviceType(deviceInit, FILE_DEVICE_CD_ROM);
WdfDeviceInitAssignName(deviceInit, “\Device\MyDevice\MyDeviceDvd1”);

Any ideas?

Thanks,
–Jeremy

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

6

KMDF does nothing with the name other then pass it to IoCreateDeviceSecurity. Perhaps IoCreateDeviceSecure has some additional checks in it that cause this error to occur.

are you creating the symbolic link in your driver or in UM?

d

7

In my driver. By following Beverly’s advice and calling
WdfControlFinishInitializing CreateFile now succeeds.

It may be premature to ask this question (I still have a few more things
to look at before I can honestly declare that I’ve checked everything)
but as long as I’m already submitting a post, I might as well…

In my user mode app, I call DefineDosDevice to map my device to ‘f:’ and
it succeeds. I then call CreateFile on ‘\.\f:’ and that succeeds.
Nothing shows up in explorer, though, and if I try to switch to the ‘f:’
drive at the command prompt I get a “The system cannot find the drive
specified” error. I thought that once I successfully called
DefineDosDevice, my virtual drive would show up?

Thanks,
–Jeremy

xxxxx@Microsoft.com wrote:

KMDF does nothing with the name other then pass it to IoCreateDeviceSecurity. Perhaps IoCreateDeviceSecure has some additional checks in it that cause this error to occur.

are you creating the symbolic link in your driver or in UM?

d

8

JEREMY:

I can’t say that I really know the answer to this question. However,
as it is late and you might not hear from anyone else tonight, I think
that the basic problem is that their is both a local and global DOS
namespace. If you create define a dos device, whether in user or kernel
mode, in the context of the LocalSystem account/System process, then it
will be a member of the global namespace, and otherwise will end up in
the local. In user mode, unless you go out of your way, there is no
chance that you will happen to be running under LocalSystem; in the
kernel this is also the case if you define in response to an IOCTL. If,
however, you do the definition in DriverEntry or somewhere else that
runs in the System context, it will be global. In the kernel, you can
also specify explicitly by using “\DosDevices\Global” as the path.

I realize that this is not much of an answer, but I thought it might be
worth at least looking at until you can get some better ideas from
others. Although my work is entirely kernel mode, I pretty much never
get involved with actual devices, so I can’t be of much help here.

MM

>> xxxxx@telestream.net 2006-09-07 20:02 >>>
In my driver. By following Beverly’s advice and calling
WdfControlFinishInitializing CreateFile now succeeds.

It may be premature to ask this question (I still have a few more
things
to look at before I can honestly declare that I’ve checked everything)

but as long as I’m already submitting a post, I might as well…

In my user mode app, I call DefineDosDevice to map my device to ‘f:’
and
it succeeds. I then call CreateFile on ‘\.\f:’ and that succeeds.
Nothing shows up in explorer, though, and if I try to switch to the
‘f:’
drive at the command prompt I get a “The system cannot find the drive
specified” error. I thought that once I successfully called
DefineDosDevice, my virtual drive would show up?

Thanks,
–Jeremy

xxxxx@Microsoft.com wrote:

KMDF does nothing with the name other then pass it to
IoCreateDeviceSecurity. Perhaps IoCreateDeviceSecure has some
additional checks in it that cause this error to occur.

are you creating the symbolic link in your driver or in UM?

d

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

9

The other issue is that this is cached information; the usual fix is to
send a WM_DEVICECHANGE message (have fun finding an example - the easy
to find examples are what to do when you RECEIVE one, not when you send
one.) That message tells the recipient the drive map has changed so it
will refresh it.

We’ve had this problem for years over in file systems (where we
sometimes make drive letter just magically appear for pseudo file
systems.)

In general, this is one reason why folks recommend that you play with
the mount manager - it’s all tied into this sort of plumbing and it
“just happens” without any special interaction.

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Thursday, September 07, 2006 7:33 PM
To: ntdev redirect
Subject: Re:[ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

JEREMY:

I can’t say that I really know the answer to this question. However,
as it is late and you might not hear from anyone else tonight, I think
that the basic problem is that their is both a local and global DOS
namespace. If you create define a dos device, whether in user or kernel
mode, in the context of the LocalSystem account/System process, then it
will be a member of the global namespace, and otherwise will end up in
the local. In user mode, unless you go out of your way, there is no
chance that you will happen to be running under LocalSystem; in the
kernel this is also the case if you define in response to an IOCTL. If,
however, you do the definition in DriverEntry or somewhere else that
runs in the System context, it will be global. In the kernel, you can
also specify explicitly by using “\DosDevices\Global” as the path.

I realize that this is not much of an answer, but I thought it might be
worth at least looking at until you can get some better ideas from
others. Although my work is entirely kernel mode, I pretty much never
get involved with actual devices, so I can’t be of much help here.

MM

>> xxxxx@telestream.net 2006-09-07 20:02 >>>
In my driver. By following Beverly’s advice and calling
WdfControlFinishInitializing CreateFile now succeeds.

It may be premature to ask this question (I still have a few more
things
to look at before I can honestly declare that I’ve checked everything)

but as long as I’m already submitting a post, I might as well…

In my user mode app, I call DefineDosDevice to map my device to ‘f:’
and
it succeeds. I then call CreateFile on ‘\.\f:’ and that succeeds.
Nothing shows up in explorer, though, and if I try to switch to the
‘f:’
drive at the command prompt I get a “The system cannot find the drive
specified” error. I thought that once I successfully called
DefineDosDevice, my virtual drive would show up?

Thanks,
–Jeremy

xxxxx@Microsoft.com wrote:

KMDF does nothing with the name other then pass it to
IoCreateDeviceSecurity. Perhaps IoCreateDeviceSecure has some
additional checks in it that cause this error to occur.

are you creating the symbolic link in your driver or in UM?

d

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

10

I can see the WM_DEVICECHANGE message affecting the driver icon showing
up in Explorer, but does that explain why the f: drive isn’t found even
at a command prompt? I’ll play around with my device path like Martin
said and see if that does anything. If I don’t get anywhere, should I
change the subject line and repost my question? I’ve kind of taken us
off topic.
–Jeremy

Tony Mason wrote:

The other issue is that this is cached information; the usual fix is to
send a WM_DEVICECHANGE message (have fun finding an example - the easy
to find examples are what to do when you RECEIVE one, not when you send
one.) That message tells the recipient the drive map has changed so it
will refresh it.

We’ve had this problem for years over in file systems (where we
sometimes make drive letter just magically appear for pseudo file
systems.)

In general, this is one reason why folks recommend that you play with
the mount manager - it’s all tied into this sort of plumbing and it
“just happens” without any special interaction.

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Thursday, September 07, 2006 7:33 PM
To: ntdev redirect
Subject: Re:[ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

JEREMY:

I can’t say that I really know the answer to this question. However,
as it is late and you might not hear from anyone else tonight, I think
that the basic problem is that their is both a local and global DOS
namespace. If you create define a dos device, whether in user or kernel
mode, in the context of the LocalSystem account/System process, then it
will be a member of the global namespace, and otherwise will end up in
the local. In user mode, unless you go out of your way, there is no
chance that you will happen to be running under LocalSystem; in the
kernel this is also the case if you define in response to an IOCTL. If,
however, you do the definition in DriverEntry or somewhere else that
runs in the System context, it will be global. In the kernel, you can
also specify explicitly by using “\DosDevices\Global” as the path.

I realize that this is not much of an answer, but I thought it might be
worth at least looking at until you can get some better ideas from
others. Although my work is entirely kernel mode, I pretty much never
get involved with actual devices, so I can’t be of much help here.

MM

>>> xxxxx@telestream.net 2006-09-07 20:02 >>>
In my driver. By following Beverly’s advice and calling
WdfControlFinishInitializing CreateFile now succeeds.

It may be premature to ask this question (I still have a few more
things
to look at before I can honestly declare that I’ve checked everything)

but as long as I’m already submitting a post, I might as well…

In my user mode app, I call DefineDosDevice to map my device to ‘f:’
and
it succeeds. I then call CreateFile on ‘\.\f:’ and that succeeds.
Nothing shows up in explorer, though, and if I try to switch to the
‘f:’
drive at the command prompt I get a “The system cannot find the drive
specified” error. I thought that once I successfully called
DefineDosDevice, my virtual drive would show up?

Thanks,
–Jeremy

xxxxx@Microsoft.com wrote:
> KMDF does nothing with the name other then pass it to
IoCreateDeviceSecurity. Perhaps IoCreateDeviceSecure has some
additional checks in it that cause this error to occur.
> are you creating the symbolic link in your driver or in UM?
>
> d
>

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

11

Btw, I tried created a deeply named device object (\Device\Root1\Root2) using both IoCreateDevice and IoCreateDeviceSecure on Vista. Both calls failed. I have not tried a previous OS release…are you sure this naming scheme was successful? Or were the symlinks pointing to the deep name?

d

12

This is sucessful if the \Device\Root1 is previously created as object
directory. We use this in our product.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From:
To: “Windows System Software Devs Interest List”
Sent: Wednesday, September 13, 2006 1:51 AM
Subject: RE:[ntdev] STATUS_OBJECT_PATH_NOT_FOUND being returned from
WdfDeviceCreate…

> Btw, I tried created a deeply named device object (\Device\Root1\Root2) using
both IoCreateDevice and IoCreateDeviceSecure on Vista. Both calls failed. I
have not tried a previous OS release…are you sure this naming scheme was
successful? Or were the symlinks pointing to the deep name?
>
> d
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer