RE: SPAM-LOW: RE: Symlinks and device co-installers

Ok, I already had the subclass set, but I had to manually include the
EnumPropPages32 field. Is this necessary, or am I missing something else
from the INF file? Device Manager does show the standard “Port Settings”
dialog, and I’m already picking the “PortName” property out of the registry
during AddDevice.

You’re right, I do have a symbolic link pointed to another symbolic link. I
just tried changing the code so that the target of the \DosDevices\COMn link
is the PDO object name, but the same problem occurs.

However, no matter what I do, I cannot open the device by the
\DosDevices\COMn link, even when the link points to the PDO name. Do I need
to pass a device name to IoCreateDevice, rather than NULL?

The most confounding thing is that the driver calls IoCreateSymbolicLink,
which returns STATUS_SUCCESS, but it doesn’t seem as though the link works.
I cannot find the link, using home-grown tools that call
NtQueryDirectoryObject. Enumerating ??, \GLOBAL??, etc. has no effects.
I’ve tried creating my link with the names \DosDevices\COMn, ??\COMn, and
\GLOBAL??\COMn, and ??\GLOBAL\COMn, all of which have had no effect.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, August 03, 2005 3:38 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: RE: [ntdev] Symlinks and device co-installers

There is no serial class driver. Serial.sys handles 16550 devices and is a
template for the serial interface, but it does not handle all classes of
that device.

To get a COM port number assigned to your device, you need to install under
the ports class and set the subclass correctly (so that the ports class
installer knows if it is a LPT or COM port being installed). This will get
the serial class installer DLL to run on your device. the Ports CI will
give you a com name under “PortName” in the device node.
It will be present during AddDevice if you want to create the symlink there.

As for creating the \DosDevices\Comx link to another symbolic link (device
interfaces are really a symbolic link themselves), I don’t think that works.
you can create a symbolic link against the name of your PDO though
(IoGetDeviceProperty will retrieve the name for you). That
definitely works.

The device interface and ComX names are 2 separate names representing the
same thing. One is an old style NT4 fixed name whiel the other is more
compatible with PNP and is not fixed. Implementing one does not advertise
the other, you need to create both.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Wednesday, August 03, 2005 12:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Symlinks and device co-installers

I’m working on a serial port device driver. Currently, the driver handles
setting up several symbolic links, during IRP_MN_START_DEVICE. Is this the
best place for this? Should my driver just attach to the PDO, and should I
use a user-mode app to handle wiring up all of the symbolic links?
(Serial.sys appears to handle all of its own symbolic link logic.)

If user mode, is a co-installer the right place to do this?

I’m rather disappointed that the serial port class driver doesn’t handle all
of this. I had expected / hoped that exposing a device interface with the
proper GUID, combined with installing the right class driver would handle
all of this. But alas, no.

I’m also seeing some strange behavior with the NT Object Manager. My device
driver creates a symbolic link, \DosDevices\COM, which points to the
device interface path returned by IoRegisterDeviceInterface. The call to
IoCreateSymbolicLink return STATUS_SUCCESS. However, user-mode apps cannot
open the device (ERROR_FILE_NOT_FOUND).

The weirdest part is that sysinternal’s WINOBJ utility shows the symbolic
link, but cannot query the link for its target! It shows up in the
\GLOBAL?? object directory, but the “SymLink” column shows “link>”. I’ve stepped through WINOBJ’s call to NtOpenSymbolicLinkObject,
and
it returns STATUS_OBJECT_NAME_NOT_FOUND. What am I doing wrong?

– arlie


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

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

Ahhhhh, if only email had a recall button. I found the bug seconds after I
sent this. My function that queried the PortName value from the registry
was not setting up a UNICODE_STRING.Length properly; it included the NUL
terminator.

Problem solved.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Wednesday, August 03, 2005 7:12 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: RE: SPAM-LOW: RE: [ntdev] Symlinks and device
co-installers

Ok, I already had the subclass set, but I had to manually include the
EnumPropPages32 field. Is this necessary, or am I missing something else
from the INF file? Device Manager does show the standard “Port Settings”
dialog, and I’m already picking the “PortName” property out of the registry
during AddDevice.

You’re right, I do have a symbolic link pointed to another symbolic link. I
just tried changing the code so that the target of the \DosDevices\COMn link
is the PDO object name, but the same problem occurs.

However, no matter what I do, I cannot open the device by the
\DosDevices\COMn link, even when the link points to the PDO name. Do I need
to pass a device name to IoCreateDevice, rather than NULL?

The most confounding thing is that the driver calls IoCreateSymbolicLink,
which returns STATUS_SUCCESS, but it doesn’t seem as though the link works.
I cannot find the link, using home-grown tools that call
NtQueryDirectoryObject. Enumerating ??, \GLOBAL??, etc. has no effects.
I’ve tried creating my link with the names \DosDevices\COMn, ??\COMn, and
\GLOBAL??\COMn, and ??\GLOBAL\COMn, all of which have had no effect.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, August 03, 2005 3:38 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: RE: [ntdev] Symlinks and device co-installers

There is no serial class driver. Serial.sys handles 16550 devices and is a
template for the serial interface, but it does not handle all classes of
that device.

To get a COM port number assigned to your device, you need to install under
the ports class and set the subclass correctly (so that the ports class
installer knows if it is a LPT or COM port being installed). This will get
the serial class installer DLL to run on your device. the Ports CI will
give you a com name under “PortName” in the device node.
It will be present during AddDevice if you want to create the symlink there.

As for creating the \DosDevices\Comx link to another symbolic link (device
interfaces are really a symbolic link themselves), I don’t think that works.
you can create a symbolic link against the name of your PDO though
(IoGetDeviceProperty will retrieve the name for you). That
definitely works.

The device interface and ComX names are 2 separate names representing the
same thing. One is an old style NT4 fixed name whiel the other is more
compatible with PNP and is not fixed. Implementing one does not advertise
the other, you need to create both.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Wednesday, August 03, 2005 12:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Symlinks and device co-installers

I’m working on a serial port device driver. Currently, the driver handles
setting up several symbolic links, during IRP_MN_START_DEVICE. Is this the
best place for this? Should my driver just attach to the PDO, and should I
use a user-mode app to handle wiring up all of the symbolic links?
(Serial.sys appears to handle all of its own symbolic link logic.)

If user mode, is a co-installer the right place to do this?

I’m rather disappointed that the serial port class driver doesn’t handle all
of this. I had expected / hoped that exposing a device interface with the
proper GUID, combined with installing the right class driver would handle
all of this. But alas, no.

I’m also seeing some strange behavior with the NT Object Manager. My device
driver creates a symbolic link, \DosDevices\COM, which points to the
device interface path returned by IoRegisterDeviceInterface. The call to
IoCreateSymbolicLink return STATUS_SUCCESS. However, user-mode apps cannot
open the device (ERROR_FILE_NOT_FOUND).

The weirdest part is that sysinternal’s WINOBJ utility shows the symbolic
link, but cannot query the link for its target! It shows up in the
\GLOBAL?? object directory, but the “SymLink” column shows “link>”. I’ve stepped through WINOBJ’s call to NtOpenSymbolicLinkObject,
and
it returns STATUS_OBJECT_NAME_NOT_FOUND. What am I doing wrong?

– arlie


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

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: xxxxx@stonestreetone.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

Did you clear DO_DEVICE_INITIALIZING from DeviceObject->Flags? Does
QueryDosDevices return your com port? Is your com port number greater
then 9? If so, you need to open it as \.\comx (which works for <=9 as
well).

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Wednesday, August 03, 2005 4:12 PM
To: Windows System Software Devs Interest List
Subject: RE: SPAM-LOW: RE: [ntdev] Symlinks and device co-installers

Ok, I already had the subclass set, but I had to manually include the
EnumPropPages32 field. Is this necessary, or am I missing something
else
from the INF file? Device Manager does show the standard “Port
Settings”
dialog, and I’m already picking the “PortName” property out of the
registry
during AddDevice.

You’re right, I do have a symbolic link pointed to another symbolic
link. I
just tried changing the code so that the target of the \DosDevices\COMn
link
is the PDO object name, but the same problem occurs.

However, no matter what I do, I cannot open the device by the
\DosDevices\COMn link, even when the link points to the PDO name. Do I
need
to pass a device name to IoCreateDevice, rather than NULL?

The most confounding thing is that the driver calls
IoCreateSymbolicLink,
which returns STATUS_SUCCESS, but it doesn’t seem as though the link
works.
I cannot find the link, using home-grown tools that call
NtQueryDirectoryObject. Enumerating ??, \GLOBAL??, etc. has no
effects.
I’ve tried creating my link with the names \DosDevices\COMn, ??\COMn,
and
\GLOBAL??\COMn, and ??\GLOBAL\COMn, all of which have had no effect.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, August 03, 2005 3:38 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: RE: [ntdev] Symlinks and device co-installers

There is no serial class driver. Serial.sys handles 16550 devices and
is a
template for the serial interface, but it does not handle all classes of
that device.

To get a COM port number assigned to your device, you need to install
under
the ports class and set the subclass correctly (so that the ports class
installer knows if it is a LPT or COM port being installed). This will
get
the serial class installer DLL to run on your device. the Ports CI will
give you a com name under “PortName” in the device node.
It will be present during AddDevice if you want to create the symlink
there.

As for creating the \DosDevices\Comx link to another symbolic link
(device
interfaces are really a symbolic link themselves), I don’t think that
works.
you can create a symbolic link against the name of your PDO though
(IoGetDeviceProperty will retrieve the name for you). That
definitely works.

The device interface and ComX names are 2 separate names representing
the
same thing. One is an old style NT4 fixed name whiel the other is more
compatible with PNP and is not fixed. Implementing one does not
advertise
the other, you need to create both.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Wednesday, August 03, 2005 12:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Symlinks and device co-installers

I’m working on a serial port device driver. Currently, the driver
handles
setting up several symbolic links, during IRP_MN_START_DEVICE. Is this
the
best place for this? Should my driver just attach to the PDO, and
should I
use a user-mode app to handle wiring up all of the symbolic links?
(Serial.sys appears to handle all of its own symbolic link logic.)

If user mode, is a co-installer the right place to do this?

I’m rather disappointed that the serial port class driver doesn’t handle
all
of this. I had expected / hoped that exposing a device interface with
the
proper GUID, combined with installing the right class driver would
handle
all of this. But alas, no.

I’m also seeing some strange behavior with the NT Object Manager. My
device
driver creates a symbolic link, \DosDevices\COM, which points to the
device interface path returned by IoRegisterDeviceInterface. The call
to
IoCreateSymbolicLink return STATUS_SUCCESS. However, user-mode apps
cannot
open the device (ERROR_FILE_NOT_FOUND).

The weirdest part is that sysinternal’s WINOBJ utility shows the
symbolic
link, but cannot query the link for its target! It shows up in the
\GLOBAL?? object directory, but the “SymLink” column shows “querying
link>”. I’ve stepped through WINOBJ’s call to NtOpenSymbolicLinkObject,
and
it returns STATUS_OBJECT_NAME_NOT_FOUND. What am I doing wrong?

– arlie


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

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To
unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

> I’m rather disappointed that the serial port class driver doesn’t handle all

There is no serial port class driver. The serial.sys is a classic PC UART
hardware driver, not splitted to class-minidriver halves.

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

Allow me to rephrase. I’m disappointed that such a common, important class
of devices has rather poor, non-uniform support, both in kernel mode (no
class driver) and in user mode (no uniform handling of symlinks, legacy
names, etc.). Especially when you consider all of the functionality
specific to serial ports, but not to any particular physical implementation,
such as flow control, support for SERIAL_TIMEOUTS, etc.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Thursday, August 04, 2005 9:33 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: Re: [ntdev] Symlinks and device co-installers

I’m rather disappointed that the serial port class driver doesn’t
handle all

There is no serial port class driver. The serial.sys is a classic PC UART
hardware driver, not splitted to class-minidriver halves.

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


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

You are currently subscribed to ntdev as: xxxxx@stonestreetone.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

A class driver would involve a port/miniport solution using current
development methods. We polled the industry and they didn’t want it,
they wanted their own drivers for their own custom non UART based HW.
The ports class installer handles the symlink and legacy naming issues,
arbitrating COM port numbers and trying to make sure that only one
device on the machine has a particular number.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Friday, August 05, 2005 8:02 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Symlinks and device co-installers

Allow me to rephrase. I’m disappointed that such a common, important
class
of devices has rather poor, non-uniform support, both in kernel mode (no
class driver) and in user mode (no uniform handling of symlinks, legacy
names, etc.). Especially when you consider all of the functionality
specific to serial ports, but not to any particular physical
implementation,
such as flow control, support for SERIAL_TIMEOUTS, etc.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S.
Shatskih
Sent: Thursday, August 04, 2005 9:33 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: Re: [ntdev] Symlinks and device co-installers

I’m rather disappointed that the serial port class driver doesn’t
handle all

There is no serial port class driver. The serial.sys is a classic PC
UART
hardware driver, not splitted to class-minidriver halves.

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


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

You are currently subscribed to ntdev as: xxxxx@stonestreetone.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Arlie Davis wrote:

Allow me to rephrase. I’m disappointed that such a common, important class
of devices has rather poor, non-uniform support, both in kernel mode (no
class driver) and in user mode (no uniform handling of symlinks, legacy
names, etc.).

The key word to keep in mind here is “legacy”. Serial ports are have
been around a very long time. There were vast numbers of serial port
apps for standalone DOS. When Windows came along, Microsoft tried to
make things so that those DOS apps wouldn’t have to be completely
redesigned, leading to a large number of serial port apps for Windows
using a somewhat convoluted architecture. When NT came along, I imagine
the design goal was not to break all of those old apps, so a lot of that
architecture carried forward.

USB has a relatively well-thought out driver design, because it was cut
from whole cloth with WDM in mind. Serial ports were not. And today,
serial ports are on their last legs; no one is going to redesign the
serial port driver model at this point.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Fair enough. Could you provide a link to better documentation on this?
Specifically, how to have the class installer manage the legacy COM symbolic
links. The DDK info on serial ports is not terrible, but it’s not great,
either.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Friday, August 05, 2005 12:11 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: RE: [ntdev] Symlinks and device co-installers

A class driver would involve a port/miniport solution using current
development methods. We polled the industry and they didn’t want it, they
wanted their own drivers for their own custom non UART based HW.
The ports class installer handles the symlink and legacy naming issues,
arbitrating COM port numbers and trying to make sure that only one device on
the machine has a particular number.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Friday, August 05, 2005 8:02 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Symlinks and device co-installers

Allow me to rephrase. I’m disappointed that such a common, important class
of devices has rather poor, non-uniform support, both in kernel mode (no
class driver) and in user mode (no uniform handling of symlinks, legacy
names, etc.). Especially when you consider all of the functionality
specific to serial ports, but not to any particular physical implementation,
such as flow control, support for SERIAL_TIMEOUTS, etc.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S.
Shatskih
Sent: Thursday, August 04, 2005 9:33 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: Re: [ntdev] Symlinks and device co-installers

I’m rather disappointed that the serial port class driver doesn’t
handle all

There is no serial port class driver. The serial.sys is a classic PC UART
hardware driver, not splitted to class-minidriver halves.

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


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

You are currently subscribed to ntdev as: xxxxx@stonestreetone.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

The maintains a bitmap of claimed com port names under a registry key.
Everytime you install a port, it claims a new bit, every time you
uinstall a device it clears the bit. This is exported from msports.dll
as well, ComDBXxx functions. The ports class installer sample in the
DDK shows this IIRC.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Friday, August 05, 2005 9:41 AM
To: Windows System Software Devs Interest List
Subject: RE: SPAM-LOW: RE: [ntdev] Symlinks and device co-installers

Fair enough. Could you provide a link to better documentation on this?
Specifically, how to have the class installer manage the legacy COM
symbolic
links. The DDK info on serial ports is not terrible, but it’s not
great,
either.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Friday, August 05, 2005 12:11 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: RE: [ntdev] Symlinks and device co-installers

A class driver would involve a port/miniport solution using current
development methods. We polled the industry and they didn’t want it,
they
wanted their own drivers for their own custom non UART based HW.
The ports class installer handles the symlink and legacy naming issues,
arbitrating COM port numbers and trying to make sure that only one
device on
the machine has a particular number.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Friday, August 05, 2005 8:02 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Symlinks and device co-installers

Allow me to rephrase. I’m disappointed that such a common, important
class
of devices has rather poor, non-uniform support, both in kernel mode (no
class driver) and in user mode (no uniform handling of symlinks, legacy
names, etc.). Especially when you consider all of the functionality
specific to serial ports, but not to any particular physical
implementation,
such as flow control, support for SERIAL_TIMEOUTS, etc.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S.
Shatskih
Sent: Thursday, August 04, 2005 9:33 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: Re: [ntdev] Symlinks and device co-installers

I’m rather disappointed that the serial port class driver doesn’t
handle all

There is no serial port class driver. The serial.sys is a classic PC
UART
hardware driver, not splitted to class-minidriver halves.

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


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

You are currently subscribed to ntdev as: xxxxx@stonestreetone.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To
unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


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

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com