/build/static/layout/Breadcrumb_cap_w.png

Anyone having problem with driver installation in RIS

I'm ecperiencing problem with driver installation in my RIS images.

I'm doiing the $oem$ procedure but whitout success...

any hints ?

thanks

Francis

0 Comments   [ + ] Show comments

Answers (6)

Posted by: bkelly 20 years ago
Red Belt
1
This has always worked for me, one good source of "how to" on this can be found here:
http://support.microsoft.com/support/kb/articles/q254/0/78.asp

If you are still having problems, post as much specific information as possible including a copy of your inf file and perhaps someone can locate an error. The inf file is very unforgiving if any mistakes are included.

Good luck!
Posted by: Francoisracine 20 years ago
Third Degree Blue Belt
1
Can you give more informations about what you are doing and which drivers?
Posted by: francisg 19 years ago
Purple Belt
1
Hi bob,

Here's my inf created with setupe manager:

;SetupMgrTag
[Unattended]
OemSkipEula=Yes
OemPnPDriversPath=C:\drivers\modem;C:\drivers\audio;C:\drivers\video;C:\drivers\network;
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
AdminPassword=
OEMSkipRegional=1
TimeZone=35
OemSkipWelcome=1

[UserData]
FullName="Agence Spatiale Canadienne"
OrgName="Canadian Space Agency"
ComputerName=

[Display]
BitsPerPel=16
Xresolution=1024
YResolution=768
Vrefresh=60

[TapiLocation]
CountryCode=107
Dialing=Tone
AreaCode=450

[RegionalSettings]
LanguageGroup=1
SystemLocale=00001009
UserLocale=00001009
InputLocale=1009:00000409

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=win2000dist

[Identification]
JoinDomain=csa


[Networking]
InstallDefaultComponents=Yes

thanks

Frank
Posted by: ST170SP1 19 years ago
Senior Yellow Belt
1
Hi Francisg,

You problem is most likly to do with the driver path string for the OemPnPDriversPath. The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.

The entry should be something like:
[Unattended]
OemPnPDriversPath = "Drivers\network adapter;Drivers\Modem;Drivers\Video"

JamesT
Posted by: violin 19 years ago
Yellow Belt
1
Agree with JamesT, just use "Drivers\path" I would get rid of the space in network adapter, just call it NIC (DOS roots showing)
Posted by: shepherdblake 19 years ago
Yellow Belt
1
I've solved this problem by getting the "RIS" version of the INF. I know that both Broadcom and Intel provide a special RIS version of the INF file.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ