can serial.sys create a PDO when a nonPNP serial device is insered?

in win 2000,a nonPNP device,such as a serial printer ,is inserted,can the
serial bus create a PDO for the serial port?
if I want to develop a driver for the printer(nonPNP),then this may be a
layered driver.the lower one is serial.sys,the higher one is printer.sys.
what does the serial bus do in this course?
what does serial.sys do ?Is serial bus equal to serial.sys??
I know the pdo created by usb .sys( I am not sure of the name) is passed as
a parametre to Adddevice() in a WDM driver.
however,I have no idea about whether the serial.sys can create a pdo and
pass it to
AddDevice(),does serial.sys create a pdo and pass it to AddDevice()????
HELP!!!!!!!!!!!!!!!!!!!!!!!!!

 

No, serial.sys wouldn't create a PDO if you plug in non-enumerable serial
device. In fact, serial.sys is not a bus driver and it doesn't enumerate any
devices. That job is done by an upper device filter of serial.sys called
serenum.sys. If you have non-enumerable serial device then the only option
you have is to manually install the driver (root-enumerate) and have the
driver open the com port in kernel-mode and talk to it. They are some PNP
rules to be followed when you talk to a device in kernel-mode. Take a look
at the src\general\toaster\toastmon sample.

Read:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/serial/hh/serial/sseovr_5icn.asp
http://www.microsoft.com/whdc/hwdev/tech/IO/superio/serddvr.mspx
http://www.wd-3.com/archive/SerialFilter.htm

 

Also check out http://www.wd-3.com/archive/SerialAttachedDevices.htm,
which explains how to write drivers for PnP or non-PnP devices attached
to a serial port.

 

IIRC the standard print monitor allows serial-attached printers.
So, white only the graphics driver for your printer. Then install it to
"COM1", and the Windows spooler will write the stream generated by your
graphics driver directly to your serial wire.

 

devices. That job is done by an upper device filter of serial.sys called

Suggestion for MS:

- maybe advance SerEnum to use the "default PnP ID" from the registry. If the
device is attached but not PnP-capable - then SerEnum will enumerate this
registry ID and create a PDO.

Is it a bad idea?

 

I did what you told,and progressed much.But I got a new problem after Getdiviceobjectpointer() ,IOAttachdevicetodevicestack(),the IRP_MJ_CREATE is sent,but while opening the serial port ,a nonpage error happened.
what is the reason? I wrote a function called SerialOpen() to open the port.
and also ,do I have to open a serial port in order to communicate with the serial device by serial port?
This is what Walter Wony says:
"The root enumerator acts as the bus driver for your device. The PnP Manager loads your driver and calls DriverEntry and AddDevice in the normal way for a WDM driver. In your StartDevice function, you would normally read the registry to get the name of the attachment port, and then you'd call IoGetDeviceObjectPointer to open a handle to SERIAL.SYS and to obtain a DEVICE_OBJECT pointer to which you can submit IRPs. < Thereafter, you send IRP_MJ_READ, IRP_MJ_WRITE, and IRP_MJ_DEVICE_CONTROL requests to SERIAL. > You use these requests to control the RS-232 signal lines and and to send and receive data from your widget."

the words between <> confused me a little.I shall first open a serial port in order to communicate. Am I right?

Also ,when is IRP_MJ_CREATE sent by IOManager?