After several days of stress, trying to figure out why my RIS server (win2003, standard, deploying win2003, standard) stops and gives the famous "The selected image does not contain the required drivers".

I have read all the previous posts and still cannot get it to work.

my current configuration is:
[Unattended] section
modify
OemPreinstall = Yes
add
OemPnPDriversPath="Drivers\ws03xp32"
DriverSigningPolicy=Ignore

created $oem$\$1\drivers\ws03xp32 at the same level as i386 and under i386

downloladed the ris inf file from intel

ws03xp32 contains
e100b325.sys
e100b325.din
e100b325.dll
intelnic.dll
prounstl.exe

started and stopped binlsvc

what am i missing?

Hi,

The files themselves go into the i386 folder directly. You will need the inf file too to get them working (you do not list it). For text mode setup you ONLY need the inf and sys files as far as I know (and possibly the din file too?). The rest of the driver files are not used during text mode setup and should not be copied into i386. If you do not do this then the Pro/100 drivers will not be available during text mode setup, which is where you need them. Remember to keep the $OEM$... folders and files too as these are used during GUI mode setup and will be the drivers used by Windows proper. I always put all of the driver files, just as you have done, into the $OEM$... folder and not just the inf, sys and din.

You seem to be doing everything else correctly.

You do not need the $OEM$ folder nested within i386. You only need the $OEM$ folder alongside i386.

Cheers,

Andy

andy thanks for your input, but it still does not work

ws03xp32 now contains
e100b325.cat
e100b325.din
e100b325.inf
e100b325.sys
e100msg.dll
intelnic.dll

looked at these files on the orginal system
e100b325.din, e100msg.dll and intelnic.dll in windows\system32
e100b325.sys in windows\system32\drivers

verified that these files were present in the rip folder

also copied e100b325.din, e100msg.dll, intelnic.dll and e100b325.sys to flat files

got it

when the instructions mentioned i386 I thought they were talking about the i386 folder in the ris image not the one in the "flat-file"

Pls remember to restart your "Boot Information Negotiation Layer" service after you have copied the lan driver into i386.

Final resolution:

Download thes drivers from Intel: Download

And place the following files into this directory on the RIS-server:

the new file (from the download) e100b325.inf in the i386 directory.
And the e100b325.sys (from your normal driver) also in the i386 directory.

go to the RIS server and type:

net stop binlsvc
net start binlsvc

Now it should work!

For use in Windows i used these drivers.

Hi all,
I've been trying to get this to work for days and still having no joy.

I have winServer2003 and I'm trying to RIS XP with SP1.
Also have SP1 installed on server.
(MS hotfix article suggested SP1 might fix the problem but no joy)

I am using the following PXE NIC
Intel® pro/100 VM
And get the "no NIC Driver" error message during text setup.

I have modified ristndrd.sif
[Unattended]
OemPreinstall = yes
OemPnPDriversPath = "Drivers\ws03xp32"
DriverSigningPolicy = Ignore

I have copied the following into i386:
e100b325.inf
e100b325.sys
e100b325.din

I have also created $oem$\$1\Drivers\ws03xp32 in the same directory as i386
into this I have placed:
e100b325.cat
e100b325.din
e100b325.inf
e100b325.sys
e100bmsg.dll
NicCo.dll
NicInst.dll

Deleted all of the .PNF in the i386 directory

Then stopped and started the Boot Information Negotiation Layer

But still no joy.




If I copy .inf and .sys files from a 2003 RIS Image then it gets past the "No Nic Drivers" error and then starts to copy files but then I get a blue screen of death.



I'm now at my witt's end, so any help would be much appreciated.

Sorted

Replaced the 10mb hub with a 100mb adsl router and worked straight away