Thank you very much.
That looks like exactly what I need.
I’ll try it out and let you know what happens.
Thanks again.
Evan.
-----Original Message-----
From: Anne Philip [mailto:xxxxx@tdksys.com]
Sent: 12 April 2001 16:47
To: NT Developers Interest List
Subject: [ntdev] RE: How do I force a driver to unload?
UpdateDriverForPlugAndPlayDevices ?
I am not sure about this though, I have not used it myself, you see for the
driver I was working with the inital approcah worked as it invovled a stack
of drivers and an install shield program which will in turn call the
SetOem… API. Does this help in any way?
-----Original Message-----
From: Evan Lloyd [mailto:xxxxx@eicon.com]
Sent: 12 April 2001 15:38
To: NT Developers Interest List
Subject: [ntdev] RE: How do I force a driver to unload?
Thanks Anne.
The problem here is that if the user has plugged the card in
before my install runs (as one would, you don’t
need a driver if you haven’t got the hardware) then
2k will already have loaded the generic driver, before I
get a chance to copy the .inf file.
Another approach that may have potential is if there is an
API that will allow me to invoke update driver for the card.
Any thoughts?
Evan.
-----Original Message-----
From: Anne Philip [mailto:xxxxx@tdksys.com]
Sent: 12 April 2001 13:16
To: NT Developers Interest List
Subject: [ntdev] RE: How do I force a driver to unload?
Hi,
I think by copying the inf file of your driver into the inf directry as
against the inf/other dir, your driver will be loaded and not the generic
one. But copying the inf files to the inf dir directly is not permissible.
So either in your co installer you can use the foll API SetupCopyOEMInf
which will rename your inf into oemx.inf and then copy into the inf dir.
Then the generic driver will not be installed. Hope this should solve your
problem by installing the correct driver in the first place.
Regds,
Anne
-----Original Message-----
From: xxxxx@eicon.com [mailto:xxxxx@eicon.com]
Sent: 11 April 2001 01:00
To: NT Developers Interest List
Subject: [ntdev] How do I force a driver to unload?
I have a problem where win2k sees my PCCard (PCMCIA) device,
and helpfully loads a generic driver without seeking permission
and without allowing intervention or looking for other drivers.
The proper long term solution for this is to change the CIS to
be multi-function so that other drivers can load against their
functions.
In the short term however I would like to be able to coerce the
generic driver out of memory, so that my other drivers can be
loaded. Has anyone any advice on how this can be done?
I assume I will need a co-installer, but I have not yet found
any documentation on how to identify the driver I want to eject,
nor any API that enables this.
Anyone have any thoughts, please?
TIA,
Evan.
You are currently subscribed to ntdev as: xxxxx@tdksys.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@eicon.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@tdksys.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@eicon.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com