Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Upcoming OSR Seminars | ||
---|---|---|
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
Kernel Debugging | 30 January 2023 | Live, Online |
Developing Minifilters | 20 March 2023 | Live, Online |
Internals & Software Drivers | 17 April 2023 | Live, Online |
Writing WDF Drivers | 22 May 2023 | Live, Online |
Comments
Thanks for the help.
As far as I understand, when a driver is installed, the inf has been copied
to winnt\inf directory as oem*.inf. Also, my inf file directs the system to
copy *.sys to winnt\system32\drivers directory. When another adapter is
inserted, the sytem would check this inf and then search the *.sys files in
winnt\system32\drivers.
If the system really needs signature or something, why is it not consistent?
Yes, API is an option. But does that mean the app should be run before the
driver is installed? If yes, it is painful.
Regards
James
-----Original Message-----
From: Keith Garner [mailto:[email protected]]
Sent: Thursday, April 13, 2000 11:31 AM
To: NT Developers Interest List
Cc: 'NT Developers Interest List'
Subject: [ntdev] RE: [ntdev]Ask for device driver again in Win2k
Yes,
From what I understand when you plug a USB ( or serial, etc.. ) device into
a new port, Windows 2000 considers this a new device. As such, it will try
to conduct a full installation.
The exception to this is if you have a Signed Driver ( WHQL Certified ).
You may want to look into the Windows API function: SetupCopyOEMInf, as
documented in the Platform SDK.
It allows you to copy your driver to a location on the Hard Disk, and force
the OS to load the driver files from that location, not the A:.
KeithGa
-----Original Message-----
From: Zhou, James [mailto:[email protected]]
Sent: Wednesday, April 12, 2000 7:20 PM
To: NT Developers Interest List
Subject: [ntdev] [ntdev]Ask for device driver again in Win2k
Hi,
I am developing a win2k driver for a USB product.
After the first time my USB adapter is inserted and driver is installed form
a floppy disk successfully, if this adapter is removed and another adapter
with a different serial number is inserted, most of the time, the system
just displays some information about finding a new device and loads the
driver automatically. But sometimes, the system asks for the floppy
installation disk again. Does any body know why?
Thanks in advance.
James
---
You are currently subscribed to ntdev as: [email protected]
To unsubscribe send a blank email to $subst('Email.Unsub')
---
You are currently subscribed to ntdev as: [email protected]
To unsubscribe send a blank email to $subst('Email.Unsub')