Error: File e100bnt.sys caused an unexpected error...

[Phoenix_Remind]

Hey all -

I am running RIS on a 2000 Windows Server and am deploying Windows XP.

Recieved the above-mentioned error after attempting several times with several variations to drop Intel Pro

100 VM drivers on RIS server. I have been working on this for a week and am making snail-like progress. This e100bnt.sys file error is not really recorded anywhere - at least I haven't found it.

I basically make it to the screen where it starts installing the setup files and then shortly after it abruptly stops with the Error: File e100bnt.sys caused an unexpected error.. in D:\xpsprtm\base\boot\setup\setup.c

Please help.

On another note I have another question below:

Now I have noticed that there are two ristndrd files - one in templates folder and the other in the i386 folder. Are both these necessary? It's getting annoying to constantly edit both.

One last thing in the ristndrd file or .sif file when describing a path -

such as: OEMPnPDriversPath = drivers\broadcom

are quotation marks around the folders and sub-folders needed?

such that it would be : OEMPnPDriversPath = "drivers\broadcom"

Edited February 15, 2006 by Phoenix_Remind

[Phoenix_Remind]

Ok still same problem with Intel PRO 100 VM.

However, I have discovered that the .SIF file in I386 is not used - only the one in I386\templates folder is applied. I also noticed that only the drivers in the I386 folder are applied to the client computer - NOT the drivers that I placed in the I386\$oem$\$1\nic folder. Little confusing even though I write the OEMPnP Drivers path in the template .SIF file.

I am very much new to RIS deployment so its a learning process for me. So please excuse my ineptitude. Thanks for any advice\help.

Edited February 15, 2006 by Phoenix_Remind

[Fencer128]

Hi,

To get support for 3rd party NIC drivers during text mode setup (which is what you want to do) then copy the *.inf and *.sys driver files for the NIC into the i386 folder of your RIS image. In the case of Intel you may want to make sure that you've removed any existing e100...sys, etc. driver files that relate to Intel NICs first.

You also want to make sure that you're using the RIS specific driver files supplied with the Intel 10.2 drivers, and not merely the Windows XP driver files.

Finally you will need to restart the BINLSVC on the RIS server. To do this type the following at a cmd prompt:

NET STOP BINLSVC
NET START BINLSVC

Everything should now work.

You will still need the Windows XP drivers located within the $OEM$\$1\NIC... folder and the "OEMPnPDriverPath=" ristndrd.sif file entry as these are used by Windows during GUI mode setup.

BTW - You should have really posted this in the Unattended RIS Installation sub-forum.

Good luck

Andy

Edited February 15, 2006 by Fencer128