 |
|
|
|
Next: display memory?
|
| Author |
Message |
External
Since: Mar 18, 2006
Posts: 3
|
(Msg. 1) Posted: Sun Oct 22, 2006 5:55 am
Post subject: Client mode device driver: how to make system recognize it?
Archived from groups: microsoft>public>windowsxp>device_driver>dev (more info?)
|
|
|
Hello.
I wrote a user-mode (as opposed to kernel-mode) device driver
which control my network devices through TCP/winsock, and which actually
is an exe-task (as MSDN teach us).
How to make system (WinXP) recognize it as a driver?
i.e. how to manage it (XP) include the driver in the device manager's list
of devices?
What is the next (or first) step: just inf-file/install?
Or some specific issues about exe/dll/proxy exist too (this is a DCOM
driver)?
Tried, but failed. Any ideas (links, samples) are appreciated.
Thanks. |
|
| Back to top |
|
 | |
External
Since: Aug 02, 2006
Posts: 3
|
(Msg. 2) Posted: Sun Oct 22, 2006 5:55 am
Post subject: Re: Client mode device driver: how to make system recognize it? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Sergei,
> I wrote a user-mode (as opposed to kernel-mode) device driver
> which control my network devices through TCP/winsock,
AFAIK, network drivers cannot operate in the user mode. The excerpt
below is taken from MSDN:
////////////////
The UMDF supports the development of drivers for protocol-based or
serial bus-based devices, such as USB devices and network-connected
devices. For example, you can write drivers for the following types of
devices by using the UMDF:
Portable storage devices, such as PDAs and cell phones
Portable media players
USB bulk transfer devices
Auxiliary display and video devices
These devices can be directly connected, connected on the network, or
connected through a wireless protocol such as Bluetooth.
///////////
As you can see, network devices are not on the list, are they???? The
only thing MSDN says is that target devices for user-mode driver may be
connected on the network, but this is not the same thing as network
device
In fact, I don't know what you are trying to do, but if you need a
network driver in a true meaning of this term, you have to write a
kernel-mode one
Anton Bassov
Sergei Vlasov wrote:
> Hello.
> I wrote a user-mode (as opposed to kernel-mode) device driver
> which control my network devices through TCP/winsock, and which actually
> is an exe-task (as MSDN teach us).
>
> How to make system (WinXP) recognize it as a driver?
> i.e. how to manage it (XP) include the driver in the device manager's list
> of devices?
> What is the next (or first) step: just inf-file/install?
> Or some specific issues about exe/dll/proxy exist too (this is a DCOM
> driver)?
> Tried, but failed. Any ideas (links, samples) are appreciated.
> Thanks. |
|
| Back to top |
|
| |
External
Since: Aug 17, 2006
Posts: 5
|
(Msg. 3) Posted: Mon Oct 23, 2006 9:55 am
Post subject: Re: Client mode device driver: how to make system recognize it? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Nope, Anton (thank you for the reply, however) you did not catch the
idea.
I'm talking about device (say, like traffic lights controller): no more,
no less, and its driver.
Not a network driver, but device driver.
This device (unlike most regular PC devices) is attached not to
PCI, USB, or COM/IRDA/BT, but to Ethernet and is controlled with
regular TCP/winsock (client mode) methods/packets.
I try to find a way to see this (these - them are many) devices
in the Device Manager's list, as well as the driver itself, with all
standard
controls.
Because the driver is an exe-file and is a client mode task (not a -sys)
there is
no regular installation procedure. (But should be, I guess. And I try
to find
the starting point for me to manage it work)
Sergei.
> Sergei,
>
>> I wrote a user-mode (as opposed to kernel-mode) device driver
>> which control my network devices through TCP/winsock,
> AFAIK, network drivers cannot operate in the user mode. The excerpt
> below is taken from MSDN:
>
>
> The UMDF supports the development of drivers for protocol-based or
> serial bus-based devices, such as USB devices and network-connected
> devices. For example, you can write drivers for the following types of
> devices by using the UMDF:
>
> These devices can be directly connected, connected on the network, or
> connected through a wireless protocol such as Bluetooth.
>
> As you can see, network devices are not on the list, are they???? The
> only thing MSDN says is that target devices for user-mode driver may
> be
> connected on the network, but this is not the same thing as network
> device
>
> In fact, I don't know what you are trying to do, but if you need a
> network driver in a true meaning of this term, you have to write a
> kernel-mode one
>
> Anton Bassov
>
>
>
> Sergei Vlasov wrote:
>> Hello.
>> I wrote a user-mode (as opposed to kernel-mode) device driver
>> which control my network devices through TCP/winsock, and which
>> actually
>> is an exe-task (as MSDN teach us).
>>
>> How to make system (WinXP) recognize it as a driver?
>> i.e. how to manage it (XP) include the driver in the device manager's
>> list
>> of devices?
>> What is the next (or first) step: just inf-file/install?
>> Or some specific issues about exe/dll/proxy exist too (this is a DCOM
>> driver)?
>> Tried, but failed. Any ideas (links, samples) are appreciated.
>> Thanks.
> >> Stay informed about: Client mode device driver: how to make system recognize it? |
|
| Back to top |
|
| |
External
Since: Oct 22, 2006
Posts: 2
|
(Msg. 4) Posted: Mon Oct 23, 2006 9:55 am
Post subject: Re: Client mode device driver: how to make system recognize it? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
"SergeV" <s_no_spam_v DeleteThis @a_ca.de_m.org> wrote in message
news:OwcJMDq9GHA.1252@TK2MSFTNGP04.phx.gbl...
>
> Nope, Anton (thank you for the reply, however) you did not catch the idea.
> I'm talking about device (say, like traffic lights controller): no more,
> no less, and its driver.
> Not a network driver, but device driver.
> This device (unlike most regular PC devices) is attached not to
> PCI, USB, or COM/IRDA/BT, but to Ethernet and is controlled with
> regular TCP/winsock (client mode) methods/packets.
That is interesting. Under which platform? Linux?
I have never heard of such thing under Windows Environment.
> I try to find a way to see this (these - them are many) devices
> in the Device Manager's list, as well as the driver itself, with all
> standard
> controls.
You already mentionned that your device controller is an EXE, not a .sys
driver, therefore you will not see them listed under Device manager, because
device manager are for actual device drivers and WDM drivers. >> Stay informed about: Client mode device driver: how to make system recognize it? |
|
| Back to top |
|
| |
|
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Profile
Private Messages
Log in
