Installing INF & driver files for PnP device

I know this is the NT list, but maybe someone here will know the answer for
98/ME anyway.

If I have a PnP (USB) device on NT, I can “preinstall” the driver before the
device is plugged in by using SetupCopyOEMInf to copy the INF file in, and
get it set up so that it properly shows where I’ve stored the drivers. Then
the first time the device is plugged in, hardware install automatically
copies the drivers and does everything necessary without user intervention.

I’d like to accomplish the same thing on Win98/ME, but I haven’t figured out
how. I can copy the INF and drivers directly to where they should live.
But as soon as I plug the device in, the INF file gets found, and then it
asks the user where the drivers are. It doesn’t seem to notice that they
are already in the right place, and I haven’t found any way to tell 98 which
directory I’ve stored the files in, in case it does insist on copying. So
the user has to know where I put those files, which is a pain.

Anyone know how to train 98/ME to believe that everything is already in the
right place, or alternately to tell it in advance where to find the drivers
for the INF file?

Thanks,

Loren

> Hi Loren,

I tried this INF file in Win-Me for the same problem.
/*

[Version]
Signature=“$CHICAGO$”
Class=USB
provider=%MSFT%
LayoutFile=layout.inf

[SourceDisksNames]
1=“XYZ USB device”,“”,1

[SourceDisksFiles]
ufd.sys=1

[Manufacturer]
%MfgName%=XYZ

[XYZ]
%USB\VID_1234&PID_0001.DeviceDesc%=UFD.Dev, USB\VID_0637&PID_0001
[PreCopySection]
HKR,NoSetupUI,1

[DestinationDirs]
UFD.Files.Ext = 10,System32\Drivers
UFD.Files.Inf = 10,INF

[UFD.Dev]
CopyFiles=UFD.Files.Ext, UFD.Files.Inf
AddReg=UFD.AddReg

[UFD.Dev.NT]
CopyFiles=UFD.Files.Ext, UFD.Files.Inf
AddReg=UFD.AddReg

[UFD.Dev.NT.Services]
Addservice = UFD, 0x00000002, UFD.AddService

[UFD.AddService]
DisplayName = %UFD.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 2 ; SERVICE_AUTO_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\ufd.sys
LoadOrderGroup = Base

[UFD.AddReg]
HKR,DevLoader,*ntkern
HKR,NTMPDriver,ufd.sys
HKLM,“System\Currentcontrolset\Services\UFD\Parameters”,"MaximumTransferSize
",0x10001,4096
HKLM,“System\Currentcontrolset\Services\UFD\Parameters”,“DebugLevel”,0x10001
,2

[UFD.Files.Ext]
ufd.sys

[UFD.Files.Inf]
ufd.Inf

;---------------------------------------------------------------;

[Strings]
MSFT=“XYZ”
MfgName=“XYZ”
USB\VID_1234&PID_0001.DeviceDesc="UFD.Sys ---- "
UFD.SvcDesc=“UFD.Sys ----- driver”

*/

Rgds
-Manju


From: Loren Wilton[SMTP:xxxxx@earthlink.net]
Reply To: NT Developers Interest List
Sent: Wednesday, May 21, 2003 11:36 AM
To: NT Developers Interest List
Subject: [ntdev] Installing INF & driver files for PnP device

I know this is the NT list, but maybe someone here will know the
answer for
98/ME anyway.

If I have a PnP (USB) device on NT, I can “preinstall” the driver
before the
device is plugged in by using SetupCopyOEMInf to copy the INF file
in, and
get it set up so that it properly shows where I’ve stored the
drivers. Then
the first time the device is plugged in, hardware install
automatically
copies the drivers and does everything necessary without user
intervention.

I’d like to accomplish the same thing on Win98/ME, but I haven’t
figured out
how. I can copy the INF and drivers directly to where they should
live.
But as soon as I plug the device in, the INF file gets found, and
then it
asks the user where the drivers are. It doesn’t seem to notice that
they
are already in the right place, and I haven’t found any way to tell
98 which
directory I’ve stored the files in, in case it does insist on
copying. So
the user has to know where I put those files, which is a pain.

Anyone know how to train 98/ME to believe that everything is already
in the
right place, or alternately to tell it in advance where to find the
drivers
for the INF file?

Thanks,

Loren


You are currently subscribed to ntdev as: xxxxx@satyam.com
To unsubscribe send a blank email to
xxxxx@lists.osr.com

**************************************************************************
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**************************************************************************