Jump to content

First time trying to include drivers...


Recommended Posts

Posted

This is the first time that I have tried to include additional drivers in my unattended install and the first test of it failed.

I double checked everyting in the guide here and nada.

Here is what I have right now:

Unattended section of answer file:

[Unattended]
   UnattendMode=FullUnattended
   UnattendSwitch=yes
   OemSkipEula=Yes
   OemPreinstall=No
   TargetPath=\WINDOWS
   Hibernation=1
   DriverSigningPolicy=ignore
   WaitForReboot=no
   OemPnPDriversPath=\drivers\000_mobo;\drivers\001_network;\drivers\002_audio;\drivers\003_video

Do I NEED quotes around the OemPnPDriversPath= variable?

Here is the dir structure:

$oem$
             $1
                Drivers
                   000_Mobo
                   001_network
                   002_Audio
                   003_Video

Thanks in advance!

Jason.


Posted

I am assuming that is a yes to the quotation marks...

Also, I am at work right now looking at the corporately built W2K unattended install and the thing that catches my eye with it is that they put the $oem$ folder structure in the i386 folder.

What would be the benefit to this? And how would one reference the directory structure from the answer file?

OR

Is this just something that is unique to W2K?

Anyhow, on a side note, the unattended install build by my higher-ups is SWEET!!!! Been using it for a few years. It even spans across 3 disks. I wish that I could share the secrets of it but most of the automation is actually achieved wiht custom written .exe's. Even the answer file is generated anew each time the process is started. It is made by an interactive EXE that asks for certain pieces of information.

Thanks,

Jason.

Posted
...

[Unattended]
OemPnPDriversPath=\drivers\000_mobo;\drivers\001_network;\drivers\002_audio;\drivers\003_video

...

Remove those backslashes (\) :

[Unattended]
OemPnPDriversPath="drivers\000_mobo;drivers\001_network;drivers\002_audio;drivers\003_video"

And indeed add quotations ("...")

Posted

Well I tried it and a few other things and I think that my problem has more to do with the fact that I am trying to get Nforce2 drivers to work.

I have read a ton of threads on the subject, tried some of the suggestions, but so far, no go.

What is the absolute most fool proof way to get the NForce2 drivers integrated into an unattended install?

Thanks,

Jason.

Posted
I was hoping that I could get it integrated at the earliest point in the install.

Any suggestions?

try xpcreate.... i am not sure if it could slipstream Nforce2 drivers but u can give a look or a try.....

Posted

CODE

[unattended]

UnattendMode=FullUnattended

UnattendSwitch=yes

OemSkipEula=Yes

OemPreinstall=No

TargetPath=\WINDOWS

Hibernation=1

DriverSigningPolicy=ignore

WaitForReboot=no

OemPnPDriversPath=\drivers\000_mobo;\drivers\001_network;\drivers\002_audio;\drivers\003_video

I think "OemPreinstall"=No is not good => "OemPreinstall=Yes"

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...