RE: Getting serial port driver which worked on NT4 to wor k on XP

The standard serial driver from Microsoft does not work with the device
unfortunately. Can we just create an inf file? Or will we have to support
plug and play as suggested? If so any pointers as to how to get started?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: 15 October 2007 16:27
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to work
on XP

Do the standard XP serial drivers not work for your hardware?

If you really need to replace the inbox drivers then you need to write a
PnP driver for your hardware. You should consider using KMDF. You should
also evaluate if you need a hardware driver at all. (See the question
above.)

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@cubic.com
Sent: Monday, October 15, 2007 11:15 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Getting serial port driver which worked on NT4 to work
on XP

Hello

I am looking at the code for a multidrop driver we developed for NT4
(not me). It was compiled using ntddk.h. It works fine for NT4 but we
are struggling to get it to work on XP.

On our embedded systems running embedded XP, COM ports 3 to 6 are
multidrop devices. But in XP Device Manager the drivers associated with
these ports are the standard Windows drivers - serial.sys and
serenum.sys. If I try to change the driver I am prompted for an inf
file which we don’t have. Can I just create an inf file and still use
the NT4 created multidrop.sys file?

How do I go about creating the inf file? any resources?

Or are we going to have to re-write the driver for XP?

Angus


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

**********************************************************************
This document is intended for, and should only be read by,
those persons to whom it is addressed. Its contents are
confidential and if you have received this message in error,
please delete it. Any form of reproduction, dissemination,
copying, disclosure, modification, distribution and / or
publication of this message without our prior written
consent is strictly prohibited.

Any views expressed in this message are those of the
individual sender, and do not necessarily represent the
position of CTSL. Furthermore CTSL does not authorise
or use e-mail for official contractual correspondence.
Nothing received in e-mail has any contractual validity.

CTSL and each legal entity in Cubic Corporation reserve
the right to monitor all e-mail communications through
its networks.

Registered Office:
Cubic Transportation Systems Ltd
AFC House
Honeycrock Lane
Salfords
Surrey
RH1 5LA
United Kingdom

Registered in England under number 01381707
**********************************************************************

If the serial driver is being loaded then you are reporting a hardware ID that says you are an RS232 device. Are your reporting some variation of pnp0501?

You can write an INF to prevent serial.sys from loading and still retain your NT4 driver, but it will be !'ed out in device manager. Furthermore, there is no guarantee that your hardware resources will be powered on. Why? Because if the pnp device is not started and powered on, the bus which enumerated the device is allowed to turn off the device.

If you want an INF to install serial based driver (like yours) which is pnp, look at the INF in the KMDF serial sample. If you want an INF to make pnp pick no driver for the device, look at %windir%\inf\machine.inf at the NO_DRV installation section (this is called a NULL service install, you can also search the WDK for this term)

Another side effect of your NT4 driver’s presence is that power management (like standby, hibernate) may not work on the machine due to the presence of an NT4 legacy driver using legacy HAL APIs to claim resources). I think in the end you will be pleasantly surprised by KMDF and that your port will be rather easy.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Comber Angus
Sent: Monday, October 15, 2007 10:02 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to wor k on XP

The standard serial driver from Microsoft does not work with the device
unfortunately. Can we just create an inf file? Or will we have to support
plug and play as suggested? If so any pointers as to how to get started?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: 15 October 2007 16:27
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to work
on XP

Do the standard XP serial drivers not work for your hardware?

If you really need to replace the inbox drivers then you need to write a
PnP driver for your hardware. You should consider using KMDF. You should
also evaluate if you need a hardware driver at all. (See the question
above.)

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@cubic.com
Sent: Monday, October 15, 2007 11:15 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Getting serial port driver which worked on NT4 to work
on XP

Hello

I am looking at the code for a multidrop driver we developed for NT4
(not me). It was compiled using ntddk.h. It works fine for NT4 but we
are struggling to get it to work on XP.

On our embedded systems running embedded XP, COM ports 3 to 6 are
multidrop devices. But in XP Device Manager the drivers associated with
these ports are the standard Windows drivers - serial.sys and
serenum.sys. If I try to change the driver I am prompted for an inf
file which we don’t have. Can I just create an inf file and still use
the NT4 created multidrop.sys file?

How do I go about creating the inf file? any resources?

Or are we going to have to re-write the driver for XP?

Angus


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

**********************************************************************
This document is intended for, and should only be read by,
those persons to whom it is addressed. Its contents are
confidential and if you have received this message in error,
please delete it. Any form of reproduction, dissemination,
copying, disclosure, modification, distribution and / or
publication of this message without our prior written
consent is strictly prohibited.

Any views expressed in this message are those of the
individual sender, and do not necessarily represent the
position of CTSL. Furthermore CTSL does not authorise
or use e-mail for official contractual correspondence.
Nothing received in e-mail has any contractual validity.

CTSL and each legal entity in Cubic Corporation reserve
the right to monitor all e-mail communications through
its networks.

Registered Office:
Cubic Transportation Systems Ltd
AFC House
Honeycrock Lane
Salfords
Surrey
RH1 5LA
United Kingdom

Registered in England under number 01381707
**********************************************************************


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

OK it looks like we might have to re-write.

One final question, would it be possible to write a driver, possibly using
WDF, which could run on Windows NT4 AND Windows XP? (Ideally also Windows
2000). Or would we need a driver for Windows NT and another driver for XP
(I presume a driver which would run on XP would also run on Windows 2000?).

Angus

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: 15 October 2007 18:16
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to wor k
on XP

If the serial driver is being loaded then you are reporting a hardware ID
that says you are an RS232 device. Are your reporting some variation of
pnp0501?

You can write an INF to prevent serial.sys from loading and still retain
your NT4 driver, but it will be !'ed out in device manager. Furthermore,
there is no guarantee that your hardware resources will be powered on. Why?
Because if the pnp device is not started and powered on, the bus which
enumerated the device is allowed to turn off the device.

If you want an INF to install serial based driver (like yours) which is pnp,
look at the INF in the KMDF serial sample. If you want an INF to make pnp
pick no driver for the device, look at %windir%\inf\machine.inf at the
NO_DRV installation section (this is called a NULL service install, you can
also search the WDK for this term)

Another side effect of your NT4 driver’s presence is that power management
(like standby, hibernate) may not work on the machine due to the presence of
an NT4 legacy driver using legacy HAL APIs to claim resources). I think in
the end you will be pleasantly surprised by KMDF and that your port will be
rather easy.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Comber Angus
Sent: Monday, October 15, 2007 10:02 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to wor k
on XP

The standard serial driver from Microsoft does not work with the device
unfortunately. Can we just create an inf file? Or will we have to support
plug and play as suggested? If so any pointers as to how to get started?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: 15 October 2007 16:27
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to work
on XP

Do the standard XP serial drivers not work for your hardware?

If you really need to replace the inbox drivers then you need to write a
PnP driver for your hardware. You should consider using KMDF. You should
also evaluate if you need a hardware driver at all. (See the question
above.)

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@cubic.com
Sent: Monday, October 15, 2007 11:15 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Getting serial port driver which worked on NT4 to work
on XP

Hello

I am looking at the code for a multidrop driver we developed for NT4
(not me). It was compiled using ntddk.h. It works fine for NT4 but we
are struggling to get it to work on XP.

On our embedded systems running embedded XP, COM ports 3 to 6 are
multidrop devices. But in XP Device Manager the drivers associated with
these ports are the standard Windows drivers - serial.sys and
serenum.sys. If I try to change the driver I am prompted for an inf
file which we don’t have. Can I just create an inf file and still use
the NT4 created multidrop.sys file?

How do I go about creating the inf file? any resources?

Or are we going to have to re-write the driver for XP?

Angus


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

**********************************************************************
This document is intended for, and should only be read by,
those persons to whom it is addressed. Its contents are
confidential and if you have received this message in error,
please delete it. Any form of reproduction, dissemination,
copying, disclosure, modification, distribution and / or
publication of this message without our prior written
consent is strictly prohibited.

Any views expressed in this message are those of the
individual sender, and do not necessarily represent the
position of CTSL. Furthermore CTSL does not authorise
or use e-mail for official contractual correspondence.
Nothing received in e-mail has any contractual validity.

CTSL and each legal entity in Cubic Corporation reserve
the right to monitor all e-mail communications through
its networks.

Registered Office:
Cubic Transportation Systems Ltd
AFC House
Honeycrock Lane
Salfords
Surrey
RH1 5LA
United Kingdom

Registered in England under number 01381707
**********************************************************************


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

Kmdf is supported on windows 2000 and all subsequent releases, nt4 is not supported.

d

Sent using my smartphone, apologies forany typos

-----Original Message-----
From: “Comber Angus”
To: “Windows System Software Devs Interest List”
Sent: 10/16/07 6:21 AM
Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to wor k on XP

OK it looks like we might have to re-write.

One final question, would it be possible to write a driver, possibly using
WDF, which could run on Windows NT4 AND Windows XP? (Ideally also Windows
2000). Or would we need a driver for Windows NT and another driver for XP
(I presume a driver which would run on XP would also run on Windows 2000?).

Angus

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: 15 October 2007 18:16
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to wor k
on XP

If the serial driver is being loaded then you are reporting a hardware ID
that says you are an RS232 device. Are your reporting some variation of
pnp0501?

You can write an INF to prevent serial.sys from loading and still retain
your NT4 driver, but it will be !'ed out in device manager. Furthermore,
there is no guarantee that your hardware resources will be powered on. Why?
Because if the pnp device is not started and powered on, the bus which
enumerated the device is allowed to turn off the device.

If you want an INF to install serial based driver (like yours) which is pnp,
look at the INF in the KMDF serial sample. If you want an INF to make pnp
pick no driver for the device, look at %windir%\inf\machine.inf at the
NO_DRV installation section (this is called a NULL service install, you can
also search the WDK for this term)

Another side effect of your NT4 driver’s presence is that power management
(like standby, hibernate) may not work on the machine due to the presence of
an NT4 legacy driver using legacy HAL APIs to claim resources). I think in
the end you will be pleasantly surprised by KMDF and that your port will be
rather easy.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Comber Angus
Sent: Monday, October 15, 2007 10:02 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to wor k
on XP

The standard serial driver from Microsoft does not work with the device
unfortunately. Can we just create an inf file? Or will we have to support
plug and play as suggested? If so any pointers as to how to get started?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: 15 October 2007 16:27
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to work
on XP

Do the standard XP serial drivers not work for your hardware?

If you really need to replace the inbox drivers then you need to write a
PnP driver for your hardware. You should consider using KMDF. You should
also evaluate if you need a hardware driver at all. (See the question
above.)

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@cubic.com
Sent: Monday, October 15, 2007 11:15 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Getting serial port driver which worked on NT4 to work
on XP

Hello

I am looking at the code for a multidrop driver we developed for NT4
(not me). It was compiled using ntddk.h. It works fine for NT4 but we
are struggling to get it to work on XP.

On our embedded systems running embedded XP, COM ports 3 to 6 are
multidrop devices. But in XP Device Manager the drivers associated with
these ports are the standard Windows drivers - serial.sys and
serenum.sys. If I try to change the driver I am prompted for an inf
file which we don’t have. Can I just create an inf file and still use
the NT4 created multidrop.sys file?

How do I go about creating the inf file? any resources?

Or are we going to have to re-write the driver for XP?

Angus


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


This document is intended for, and should only be read by,
those persons to whom it is addressed. Its contents are
confidential and if you have received this message in error,
please delete it. Any form of reproduction, dissemination,
copying, disclosure, modification, distribution and / or
publication of this message without our prior written
consent is strictly prohibited.

Any views expressed in this message are those of the
individual sender, and do not necessarily represent the
position of CTSL. Furthermore CTSL does not authorise
or use e-mail for official contractual correspondence.
Nothing received in e-mail has any contractual validity.

CTSL and each legal entity in Cubic Corporation reserve
the right to monitor all e-mail communications through
its networks.

Registered Office:
Cubic Transportation Systems Ltd
AFC House
Honeycrock Lane
Salfords
Surrey
RH1 5LA
United Kingdom

Registered in England under number 01381707



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


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

No KMDF for NT4.

Since this is a hardware driver, I would suggest to drop NT4 and write the
KMDF driver. Supporting NT4 will require writing and maintaining 1 more
binary - major time/man*hours investment, and the OS is nearly dead.


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

“Comber Angus” wrote in message news:xxxxx@ntdev…
> OK it looks like we might have to re-write.
>
> One final question, would it be possible to write a driver, possibly using
> WDF, which could run on Windows NT4 AND Windows XP? (Ideally also Windows
> 2000). Or would we need a driver for Windows NT and another driver for XP
> (I presume a driver which would run on XP would also run on Windows 2000?).
>
> Angus
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
> Sent: 15 October 2007 18:16
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to wor k
> on XP
>
> If the serial driver is being loaded then you are reporting a hardware ID
> that says you are an RS232 device. Are your reporting some variation of
> pnp0501?
>
> You can write an INF to prevent serial.sys from loading and still retain
> your NT4 driver, but it will be !'ed out in device manager. Furthermore,
> there is no guarantee that your hardware resources will be powered on. Why?
> Because if the pnp device is not started and powered on, the bus which
> enumerated the device is allowed to turn off the device.
>
> If you want an INF to install serial based driver (like yours) which is pnp,
> look at the INF in the KMDF serial sample. If you want an INF to make pnp
> pick no driver for the device, look at %windir%\inf\machine.inf at the
> NO_DRV installation section (this is called a NULL service install, you can
> also search the WDK for this term)
>
> Another side effect of your NT4 driver’s presence is that power management
> (like standby, hibernate) may not work on the machine due to the presence of
> an NT4 legacy driver using legacy HAL APIs to claim resources). I think in
> the end you will be pleasantly surprised by KMDF and that your port will be
> rather easy.
>
> d
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Comber Angus
> Sent: Monday, October 15, 2007 10:02 AM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to wor k
> on XP
>
> The standard serial driver from Microsoft does not work with the device
> unfortunately. Can we just create an inf file? Or will we have to support
> plug and play as suggested? If so any pointers as to how to get started?
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
> Sent: 15 October 2007 16:27
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] Getting serial port driver which worked on NT4 to work
> on XP
>
> Do the standard XP serial drivers not work for your hardware?
>
> If you really need to replace the inbox drivers then you need to write a
> PnP driver for your hardware. You should consider using KMDF. You should
> also evaluate if you need a hardware driver at all. (See the question
> above.)
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@cubic.com
> Sent: Monday, October 15, 2007 11:15 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Getting serial port driver which worked on NT4 to work
> on XP
>
> Hello
>
> I am looking at the code for a multidrop driver we developed for NT4
> (not me). It was compiled using ntddk.h. It works fine for NT4 but we
> are struggling to get it to work on XP.
>
> On our embedded systems running embedded XP, COM ports 3 to 6 are
> multidrop devices. But in XP Device Manager the drivers associated with
> these ports are the standard Windows drivers - serial.sys and
> serenum.sys. If I try to change the driver I am prompted for an inf
> file which we don’t have. Can I just create an inf file and still use
> the NT4 created multidrop.sys file?
>
> How do I go about creating the inf file? any resources?
>
> Or are we going to have to re-write the driver for XP?
>
> Angus
>
> —
> 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
>
>
>
> This document is intended for, and should only be read by,
> those persons to whom it is addressed. Its contents are
> confidential and if you have received this message in error,
> please delete it. Any form of reproduction, dissemination,
> copying, disclosure, modification, distribution and / or
> publication of this message without our prior written
> consent is strictly prohibited.
>
> Any views expressed in this message are those of the
> individual sender, and do not necessarily represent the
> position of CTSL. Furthermore CTSL does not authorise
> or use e-mail for official contractual correspondence.
> Nothing received in e-mail has any contractual validity.
>
> CTSL and each legal entity in Cubic Corporation reserve
> the right to monitor all e-mail communications through
> its networks.
>
> Registered Office:
> Cubic Transportation Systems Ltd
> AFC House
> Honeycrock Lane
> Salfords
> Surrey
> RH1 5LA
> United Kingdom
>
> Registered in England under number 01381707
>

>
> —
> 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
>