pbooms Posted December 23, 2005 Share Posted December 23, 2005 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 modifyOemPreinstall = Yesadd OemPnPDriversPath="Drivers\ws03xp32"DriverSigningPolicy=Ignorecreated $oem$\$1\drivers\ws03xp32 at the same level as i386 and under i386downloladed the ris inf file from intelws03xp32 containse100b325.syse100b325.dine100b325.dllintelnic.dllprounstl.exestarted and stopped binlsvcwhat am i missing? Link to comment Share on other sites More sharing options...
Fencer128 Posted December 24, 2005 Share Posted December 24, 2005 (edited) 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 Edited December 24, 2005 by Fencer128 Link to comment Share on other sites More sharing options...
pbooms Posted December 27, 2005 Author Share Posted December 27, 2005 andy thanks for your input, but it still does not workws03xp32 now containse100b325.cate100b325.dine100b325.infe100b325.syse100msg.dllintelnic.dlllooked at these files on the orginal systeme100b325.din, e100msg.dll and intelnic.dll in windows\system32e100b325.sys in windows\system32\driversverified that these files were present in the rip folderalso copied e100b325.din, e100msg.dll, intelnic.dll and e100b325.sys to flat files Link to comment Share on other sites More sharing options...
pbooms Posted December 28, 2005 Author Share Posted December 28, 2005 got itwhen the instructions mentioned i386 I thought they were talking about the i386 folder in the ris image not the one in the "flat-file" Link to comment Share on other sites More sharing options...
wing_bbs Posted December 30, 2005 Share Posted December 30, 2005 Pls remember to restart your "Boot Information Negotiation Layer" service after you have copied the lan driver into i386. Link to comment Share on other sites More sharing options...
djseppie Posted June 28, 2006 Share Posted June 28, 2006 (edited) Final resolution:Download thes drivers from Intel: DownloadAnd 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 binlsvcnet start binlsvcNow it should work! For use in Windows i used these drivers. Edited June 29, 2006 by djseppie Link to comment Share on other sites More sharing options...
glyph Posted July 17, 2006 Share Posted July 17, 2006 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 VMAnd get the "no NIC Driver" error message during text setup.I have modified ristndrd.sif[unattended]OemPreinstall = yesOemPnPDriversPath = "Drivers\ws03xp32"DriverSigningPolicy = IgnoreI have copied the following into i386:e100b325.infe100b325.syse100b325.dinI have also created $oem$\$1\Drivers\ws03xp32 in the same directory as i386into this I have placed:e100b325.cate100b325.dine100b325.infe100b325.syse100bmsg.dllNicCo.dllNicInst.dllDeleted all of the .PNF in the i386 directoryThen stopped and started the Boot Information Negotiation LayerBut 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. Link to comment Share on other sites More sharing options...
glyph Posted July 17, 2006 Share Posted July 17, 2006 Sorted Replaced the 10mb hub with a 100mb adsl router and worked straight away Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now