I have a custom device - which is to be managed through the application I
am tasked with. This interface is otherwise not for use by the system and
hence the usual issues of concurrent access would be moot.
It is again not resident on the PCI bus & hence should not interfere with
the Win PnP. What would be the best way to implement this - a user mode
driver / service?
Thanks.
Whether the device is on the PCI bus or not has really nothing to do with
whether or not the driver for the device participates in the PnP model in
Windows. If your hardware has any resources memory/ports/dma
channels/interrupts then the driver for that device should be a WDM driver
with full PnP and power support. And, this would be a kernel-mode driver.
It would be helpful to know more about what kind of device this is and how
it connects to the PC though.
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
wrote in message news:xxxxx@ntdev…
>
> I have a custom device - which is to be managed through the application I
> am tasked with. This interface is otherwise not for use by the system and
> hence the usual issues of concurrent access would be moot.
>
> It is again not resident on the PCI bus & hence should not interfere with
> the Win PnP. What would be the best way to implement this - a user mode
> driver / service?
>
> Thanks.
>
>
If you dont care about PnP ( seems like the case) then U can ignore Windows
driver model ( WDM)…
If you need accessing the HW of the device then for Windows NT family
(including XP home ) you will have to write some kernelmode software …
If you happen to have the application software already written and was
interfacing say for 16 bits family of Microsoft’s OS then for NT you can use
a VDD
Otherwise for NT you can write a driver, and a specialized usr to krnl
interface… using windows ddk
-prokash
----- Original Message -----
From:
To: “Windows System Software Devs Interest List”
Sent: Tuesday, October 14, 2003 12:46 AM
Subject: [ntdev] Phoenix rises - hardware access from application
> I have a custom device - which is to be managed through the application I
> am tasked with. This interface is otherwise not for use by the system and
> hence the usual issues of concurrent access would be moot.
>
> It is again not resident on the PCI bus & hence should not interfere with
> the Win PnP. What would be the best way to implement this - a user mode
> driver / service?
>
> Thanks.
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
Well, as I said for a driver that controls hardware, that is a driver for a
device requiring resouces, the driver *should* be a WDM driver of some type.
It is possible to use an NT4 style, or legacy, driver to control hardware,
but it isn’t a good idea for a production driver. There are several reasons
why this is so, chief among them is if your legacy style driver controls
hardware, it will disable power management on every system on which it runs.
This is not a good way to make end users happy.
If you are just running this in the lab and could care less about power
management then by all means avoid the pain of WDM.
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Prokash Sinha” wrote in message news:xxxxx@ntdev…
>
> If you dont care about PnP ( seems like the case) then U can ignore
Windows
> driver model ( WDM)…
>
> If you need accessing the HW of the device then for Windows NT family
> (including XP home ) you will have to write some kernelmode software …
>
> If you happen to have the application software already written and was
> interfacing say for 16 bits family of Microsoft’s OS then for NT you can
use
> a VDD
>
> Otherwise for NT you can write a driver, and a specialized usr to krnl
> interface… using windows ddk
>
> -prokash
> ----- Original Message -----
> From:
> To: “Windows System Software Devs Interest List”
> Sent: Tuesday, October 14, 2003 12:46 AM
> Subject: [ntdev] Phoenix rises - hardware access from application
>
>
> > I have a custom device - which is to be managed through the application
I
> > am tasked with. This interface is otherwise not for use by the system
and
> > hence the usual issues of concurrent access would be moot.
> >
> > It is again not resident on the PCI bus & hence should not interfere
with
> > the Win PnP. What would be the best way to implement this - a user mode
> > driver / service?
> >
> > Thanks.
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@garlic.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
>
>
>
>
Your point is well taken !
He mentioned that it is not a PCI device. Also I’m not sure if he is talking
about ACPI, and how if any power mgmt is possible under ISA … I am not a
bus driver guy, though I like to learn despite my bad driving of a stick
shift up around the san francisco hills, almost buring the cluch 
-prokash
----- Original Message -----
From: “Bill McKenzie”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Wednesday, October 15, 2003 9:47 AM
Subject: [ntdev] Re: Phoenix rises - hardware access from application
> Well, as I said for a driver that controls hardware, that is a driver for
a
> device requiring resouces, the driver should be a WDM driver of some
type.
> It is possible to use an NT4 style, or legacy, driver to control hardware,
> but it isn’t a good idea for a production driver. There are several
reasons
> why this is so, chief among them is if your legacy style driver controls
> hardware, it will disable power management on every system on which it
runs.
> This is not a good way to make end users happy.
>
> If you are just running this in the lab and could care less about power
> management then by all means avoid the pain of WDM.
>
> –
> Bill McKenzie
> Compuware Corporation
> Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
> http://frontline.compuware.com/nashua/patches/utility.htm
>
>
> “Prokash Sinha” wrote in message news:xxxxx@ntdev…
> >
> > If you dont care about PnP ( seems like the case) then U can ignore
> Windows
> > driver model ( WDM)…
> >
> > If you need accessing the HW of the device then for Windows NT family
> > (including XP home ) you will have to write some kernelmode software …
> >
> > If you happen to have the application software already written and was
> > interfacing say for 16 bits family of Microsoft’s OS then for NT you can
> use
> > a VDD
> >
> > Otherwise for NT you can write a driver, and a specialized usr to krnl
> > interface… using windows ddk
> >
> > -prokash
> > ----- Original Message -----
> > From:
> > To: “Windows System Software Devs Interest List”
> > Sent: Tuesday, October 14, 2003 12:46 AM
> > Subject: [ntdev] Phoenix rises - hardware access from application
> >
> >
> > > I have a custom device - which is to be managed through the
application
> I
> > > am tasked with. This interface is otherwise not for use by the system
> and
> > > hence the usual issues of concurrent access would be moot.
> > >
> > > It is again not resident on the PCI bus & hence should not interfere
> with
> > > the Win PnP. What would be the best way to implement this - a user
mode
> > > driver / service?
> > >
> > > Thanks.
> > >
> > > —
> > > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> > >
> > > You are currently subscribed to ntdev as: xxxxx@garlic.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@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
Power management is handled for ISA from the driver’s perspective in a very
similar fashion to PCI. The only difference being that the hardware for PCI
actually might get powered down at some point Whether or not the
hardware is capable of power management is pretty much irrelevant. The
driver, if it is going out to the public, still needs to handle power
management as documented in the DDK. Again, if the driver doesn’t control
hardware, then use an NT4 style driver and simplify your life.
Interesting discussion Eliyas had on this a while back:
http://groups.google.com/groups?q=Eliyas+power+resources+NT&hl=en&lr=&ie=UTF
-8&oe=UTF-8&selm=3b02eb37%241%40news.microsoft.com&rnum=3
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Prokash Sinha” wrote in message news:xxxxx@ntdev…
>
> Your point is well taken !
> He mentioned that it is not a PCI device. Also I’m not sure if he is
talking
> about ACPI, and how if any power mgmt is possible under ISA … I am not a
> bus driver guy, though I like to learn despite my bad driving of a stick
> shift up around the san francisco hills, almost buring the cluch
>
> -prokash
>
> ----- Original Message -----
> From: “Bill McKenzie”
> Newsgroups: ntdev
> To: “Windows System Software Devs Interest List”
> Sent: Wednesday, October 15, 2003 9:47 AM
> Subject: [ntdev] Re: Phoenix rises - hardware access from application
>
>
> > Well, as I said for a driver that controls hardware, that is a driver
for
> a
> > device requiring resouces, the driver should be a WDM driver of some
> type.
> > It is possible to use an NT4 style, or legacy, driver to control
hardware,
> > but it isn’t a good idea for a production driver. There are several
> reasons
> > why this is so, chief among them is if your legacy style driver controls
> > hardware, it will disable power management on every system on which it
> runs.
> > This is not a good way to make end users happy.
> >
> > If you are just running this in the lab and could care less about power
> > management then by all means avoid the pain of WDM.
> >
> > –
> > Bill McKenzie
> > Compuware Corporation
> > Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
> > http://frontline.compuware.com/nashua/patches/utility.htm
> >
> >
> > “Prokash Sinha” wrote in message
news:xxxxx@ntdev…
> > >
> > > If you dont care about PnP ( seems like the case) then U can ignore
> > Windows
> > > driver model ( WDM)…
> > >
> > > If you need accessing the HW of the device then for Windows NT family
> > > (including XP home ) you will have to write some kernelmode software
…
> > >
> > > If you happen to have the application software already written and was
> > > interfacing say for 16 bits family of Microsoft’s OS then for NT you
can
> > use
> > > a VDD
> > >
> > > Otherwise for NT you can write a driver, and a specialized usr to krnl
> > > interface… using windows ddk
> > >
> > > -prokash
> > > ----- Original Message -----
> > > From:
> > > To: “Windows System Software Devs Interest List”
> > > Sent: Tuesday, October 14, 2003 12:46 AM
> > > Subject: [ntdev] Phoenix rises - hardware access from application
> > >
> > >
> > > > I have a custom device - which is to be managed through the
> application
> > I
> > > > am tasked with. This interface is otherwise not for use by the
system
> > and
> > > > hence the usual issues of concurrent access would be moot.
> > > >
> > > > It is again not resident on the PCI bus & hence should not interfere
> > with
> > > > the Win PnP. What would be the best way to implement this - a user
> mode
> > > > driver / service?
> > > >
> > > > Thanks.
> > > >
> > > > —
> > > > Questions? First check the Kernel Driver FAQ at
> > > http://www.osronline.com/article.cfm?id=256
> > > >
> > > > You are currently subscribed to ntdev as: xxxxx@garlic.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@garlic.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
>
>
>
>
Thanx for the pointer !
-prokash
----- Original Message -----
From: “Bill McKenzie”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Wednesday, October 15, 2003 10:59 AM
Subject: [ntdev] Re: Phoenix rises - hardware access from application
> Power management is handled for ISA from the driver’s perspective in a
very
> similar fashion to PCI. The only difference being that the hardware for
PCI
> actually might get powered down at some point Whether or not the
> hardware is capable of power management is pretty much irrelevant. The
> driver, if it is going out to the public, still needs to handle power
> management as documented in the DDK. Again, if the driver doesn’t control
> hardware, then use an NT4 style driver and simplify your life.
>
> Interesting discussion Eliyas had on this a while back:
>
>
http://groups.google.com/groups?q=Eliyas+power+resources+NT&hl=en&lr=&ie=UTF
> -8&oe=UTF-8&selm=3b02eb37%241%40news.microsoft.com&rnum=3
>
> –
> Bill McKenzie
> Compuware Corporation
> Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
> http://frontline.compuware.com/nashua/patches/utility.htm
>
>
> “Prokash Sinha” wrote in message news:xxxxx@ntdev…
> >
> > Your point is well taken !
> > He mentioned that it is not a PCI device. Also I’m not sure if he is
> talking
> > about ACPI, and how if any power mgmt is possible under ISA … I am not
a
> > bus driver guy, though I like to learn despite my bad driving of a stick
> > shift up around the san francisco hills, almost buring the cluch
> >
> > -prokash
> >
> > ----- Original Message -----
> > From: “Bill McKenzie”
> > Newsgroups: ntdev
> > To: “Windows System Software Devs Interest List”
> > Sent: Wednesday, October 15, 2003 9:47 AM
> > Subject: [ntdev] Re: Phoenix rises - hardware access from application
> >
> >
> > > Well, as I said for a driver that controls hardware, that is a driver
> for
> > a
> > > device requiring resouces, the driver should be a WDM driver of some
> > type.
> > > It is possible to use an NT4 style, or legacy, driver to control
> hardware,
> > > but it isn’t a good idea for a production driver. There are several
> > reasons
> > > why this is so, chief among them is if your legacy style driver
controls
> > > hardware, it will disable power management on every system on which it
> > runs.
> > > This is not a good way to make end users happy.
> > >
> > > If you are just running this in the lab and could care less about
power
> > > management then by all means avoid the pain of WDM.
> > >
> > > –
> > > Bill McKenzie
> > > Compuware Corporation
> > > Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer
tool:
> > > http://frontline.compuware.com/nashua/patches/utility.htm
> > >
> > >
> > > “Prokash Sinha” wrote in message
> news:xxxxx@ntdev…
> > > >
> > > > If you dont care about PnP ( seems like the case) then U can ignore
> > > Windows
> > > > driver model ( WDM)…
> > > >
> > > > If you need accessing the HW of the device then for Windows NT
family
> > > > (including XP home ) you will have to write some kernelmode software
> …
> > > >
> > > > If you happen to have the application software already written and
was
> > > > interfacing say for 16 bits family of Microsoft’s OS then for NT you
> can
> > > use
> > > > a VDD
> > > >
> > > > Otherwise for NT you can write a driver, and a specialized usr to
krnl
> > > > interface… using windows ddk
> > > >
> > > > -prokash
> > > > ----- Original Message -----
> > > > From:
> > > > To: “Windows System Software Devs Interest List”
> > > > Sent: Tuesday, October 14, 2003 12:46 AM
> > > > Subject: [ntdev] Phoenix rises - hardware access from application
> > > >
> > > >
> > > > > I have a custom device - which is to be managed through the
> > application
> > > I
> > > > > am tasked with. This interface is otherwise not for use by the
> system
> > > and
> > > > > hence the usual issues of concurrent access would be moot.
> > > > >
> > > > > It is again not resident on the PCI bus & hence should not
interfere
> > > with
> > > > > the Win PnP. What would be the best way to implement this - a user
> > mode
> > > > > driver / service?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > —
> > > > > Questions? First check the Kernel Driver FAQ at
> > > > http://www.osronline.com/article.cfm?id=256
> > > > >
> > > > > You are currently subscribed to ntdev as: xxxxx@garlic.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@garlic.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@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
Actually, it’s entirely possible that ISA hardware will be powered down,
too. Your hardware could be plugged into a laptop docking station, which
will turn off power when docking and undocking, as well as across sleep
states. Alternatively, it could be embedded on a motherboard and the BIOS
might provide ACPI control methods that allow the device to be powered off
at run time, while the system is using other devices.
–
Jake Oshins
Windows Base Kernel Team
This posting is provided “AS IS” with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add “Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm”
“Bill McKenzie” wrote in message
news:xxxxx@ntdev…
>
> Power management is handled for ISA from the driver’s perspective in a
very
> similar fashion to PCI. The only difference being that the hardware for
PCI
> actually might get powered down at some point Whether or not the
> hardware is capable of power management is pretty much irrelevant. The
> driver, if it is going out to the public, still needs to handle power
> management as documented in the DDK. Again, if the driver doesn’t control
> hardware, then use an NT4 style driver and simplify your life.
>
> Interesting discussion Eliyas had on this a while back:
>
>
http://groups.google.com/groups?q=Eliyas+power+resources+NT&hl=en&lr=&ie=UTF
> -8&oe=UTF-8&selm=3b02eb37%241%40news.microsoft.com&rnum=3
>
> –
> Bill McKenzie
> Compuware Corporation
> Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
> http://frontline.compuware.com/nashua/patches/utility.htm
>
>
> “Prokash Sinha” wrote in message news:xxxxx@ntdev…
> >
> > Your point is well taken !
> > He mentioned that it is not a PCI device. Also I’m not sure if he is
> talking
> > about ACPI, and how if any power mgmt is possible under ISA … I am not
a
> > bus driver guy, though I like to learn despite my bad driving of a stick
> > shift up around the san francisco hills, almost buring the cluch
> >
> > -prokash
> >
> > ----- Original Message -----
> > From: “Bill McKenzie”
> > Newsgroups: ntdev
> > To: “Windows System Software Devs Interest List”
> > Sent: Wednesday, October 15, 2003 9:47 AM
> > Subject: [ntdev] Re: Phoenix rises - hardware access from application
> >
> >
> > > Well, as I said for a driver that controls hardware, that is a driver
> for
> > a
> > > device requiring resouces, the driver should be a WDM driver of some
> > type.
> > > It is possible to use an NT4 style, or legacy, driver to control
> hardware,
> > > but it isn’t a good idea for a production driver. There are several
> > reasons
> > > why this is so, chief among them is if your legacy style driver
controls
> > > hardware, it will disable power management on every system on which it
> > runs.
> > > This is not a good way to make end users happy.
> > >
> > > If you are just running this in the lab and could care less about
power
> > > management then by all means avoid the pain of WDM.
> > >
> > > –
> > > Bill McKenzie
> > > Compuware Corporation
> > > Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer
tool:
> > > http://frontline.compuware.com/nashua/patches/utility.htm
> > >
> > >
> > > “Prokash Sinha” wrote in message
> news:xxxxx@ntdev…
> > > >
> > > > If you dont care about PnP ( seems like the case) then U can ignore
> > > Windows
> > > > driver model ( WDM)…
> > > >
> > > > If you need accessing the HW of the device then for Windows NT
family
> > > > (including XP home ) you will have to write some kernelmode software
> …
> > > >
> > > > If you happen to have the application software already written and
was
> > > > interfacing say for 16 bits family of Microsoft’s OS then for NT you
> can
> > > use
> > > > a VDD
> > > >
> > > > Otherwise for NT you can write a driver, and a specialized usr to
krnl
> > > > interface… using windows ddk
> > > >
> > > > -prokash
> > > > ----- Original Message -----
> > > > From:
> > > > To: “Windows System Software Devs Interest List”
> > > > Sent: Tuesday, October 14, 2003 12:46 AM
> > > > Subject: [ntdev] Phoenix rises - hardware access from application
> > > >
> > > >
> > > > > I have a custom device - which is to be managed through the
> > application
> > > I
> > > > > am tasked with. This interface is otherwise not for use by the
> system
> > > and
> > > > > hence the usual issues of concurrent access would be moot.
> > > > >
> > > > > It is again not resident on the PCI bus & hence should not
interfere
> > > with
> > > > > the Win PnP. What would be the best way to implement this - a user
> > mode
> > > > > driver / service?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > —
> > > > > Questions? First check the Kernel Driver FAQ at
> > > > http://www.osronline.com/article.cfm?id=256
> > > > >
> > > > > You are currently subscribed to ntdev as: xxxxx@garlic.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@garlic.com
> > > To unsubscribe send a blank email to xxxxx@lists.osr.com
> > >
> > >
> >
> >
> >
> >
>
>
>
>
Thanx a bunch Jake, Bill … for the insight …
Hope the OP has the rador on …
-prokash
----- Original Message -----
From: “Jake Oshins”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Friday, October 17, 2003 10:31 AM
Subject: [ntdev] Re: Phoenix rises - hardware access from application
> Actually, it’s entirely possible that ISA hardware will be powered down,
> too. Your hardware could be plugged into a laptop docking station, which
> will turn off power when docking and undocking, as well as across sleep
> states. Alternatively, it could be embedded on a motherboard and the BIOS
> might provide ACPI control methods that allow the device to be powered off
> at run time, while the system is using other devices.
>
> –
> Jake Oshins
> Windows Base Kernel Team
>
> This posting is provided “AS IS” with no warranties, and confers no
rights.
> OR if you wish to include a script sample in your post please add “Use of
> included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm”
>
> “Bill McKenzie” wrote in message
> news:xxxxx@ntdev…
> >
> > Power management is handled for ISA from the driver’s perspective in a
> very
> > similar fashion to PCI. The only difference being that the hardware for
> PCI
> > actually might get powered down at some point Whether or not the
> > hardware is capable of power management is pretty much irrelevant. The
> > driver, if it is going out to the public, still needs to handle power
> > management as documented in the DDK. Again, if the driver doesn’t
control
> > hardware, then use an NT4 style driver and simplify your life.
> >
> > Interesting discussion Eliyas had on this a while back:
> >
> >
>
http://groups.google.com/groups?q=Eliyas+power+resources+NT&hl=en&lr=&ie=UTF
> > -8&oe=UTF-8&selm=3b02eb37%241%40news.microsoft.com&rnum=3
> >
> > –
> > Bill McKenzie
> > Compuware Corporation
> > Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
> > http://frontline.compuware.com/nashua/patches/utility.htm
> >
> >
> > “Prokash Sinha” wrote in message
news:xxxxx@ntdev…
> > >
> > > Your point is well taken !
> > > He mentioned that it is not a PCI device. Also I’m not sure if he is
> > talking
> > > about ACPI, and how if any power mgmt is possible under ISA … I am
not
> a
> > > bus driver guy, though I like to learn despite my bad driving of a
stick
> > > shift up around the san francisco hills, almost buring the cluch
>
> > >
> > > -prokash
> > >
> > > ----- Original Message -----
> > > From: “Bill McKenzie”
> > > Newsgroups: ntdev
> > > To: “Windows System Software Devs Interest List”
> > > Sent: Wednesday, October 15, 2003 9:47 AM
> > > Subject: [ntdev] Re: Phoenix rises - hardware access from application
> > >
> > >
> > > > Well, as I said for a driver that controls hardware, that is a
driver
> > for
> > > a
> > > > device requiring resouces, the driver should be a WDM driver of
some
> > > type.
> > > > It is possible to use an NT4 style, or legacy, driver to control
> > hardware,
> > > > but it isn’t a good idea for a production driver. There are several
> > > reasons
> > > > why this is so, chief among them is if your legacy style driver
> controls
> > > > hardware, it will disable power management on every system on which
it
> > > runs.
> > > > This is not a good way to make end users happy.
> > > >
> > > > If you are just running this in the lab and could care less about
> power
> > > > management then by all means avoid the pain of WDM.
> > > >
> > > > –
> > > > Bill McKenzie
> > > > Compuware Corporation
> > > > Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer
> tool:
> > > > http://frontline.compuware.com/nashua/patches/utility.htm
> > > >
> > > >
> > > > “Prokash Sinha” wrote in message
> > news:xxxxx@ntdev…
> > > > >
> > > > > If you dont care about PnP ( seems like the case) then U can
ignore
> > > > Windows
> > > > > driver model ( WDM)…
> > > > >
> > > > > If you need accessing the HW of the device then for Windows NT
> family
> > > > > (including XP home ) you will have to write some kernelmode
software
> > …
> > > > >
> > > > > If you happen to have the application software already written and
> was
> > > > > interfacing say for 16 bits family of Microsoft’s OS then for NT
you
> > can
> > > > use
> > > > > a VDD
> > > > >
> > > > > Otherwise for NT you can write a driver, and a specialized usr to
> krnl
> > > > > interface… using windows ddk
> > > > >
> > > > > -prokash
> > > > > ----- Original Message -----
> > > > > From:
> > > > > To: “Windows System Software Devs Interest List”
>
> > > > > Sent: Tuesday, October 14, 2003 12:46 AM
> > > > > Subject: [ntdev] Phoenix rises - hardware access from application
> > > > >
> > > > >
> > > > > > I have a custom device - which is to be managed through the
> > > application
> > > > I
> > > > > > am tasked with. This interface is otherwise not for use by the
> > system
> > > > and
> > > > > > hence the usual issues of concurrent access would be moot.
> > > > > >
> > > > > > It is again not resident on the PCI bus & hence should not
> interfere
> > > > with
> > > > > > the Win PnP. What would be the best way to implement this - a
user
> > > mode
> > > > > > driver / service?
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > —
> > > > > > Questions? First check the Kernel Driver FAQ at
> > > > > http://www.osronline.com/article.cfm?id=256
> > > > > >
> > > > > > You are currently subscribed to ntdev as: xxxxx@garlic.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@garlic.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@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
Thanks for your responses. The driver is essentially meant for a custom
board & so far I learnt that it is a serial-type interface. There is
another windows service developed for this board & I was hoping to have
the new device managed as well by this service. May have more specifics
later.
Regards.