Michael_W Posted September 25, 2004 Share Posted September 25, 2004 Hi Everyone,I'm using sysprep in factory mode. After the 1st reboot factory.exe starts but winbom.log reports a #1231 error:ERROR: Failed to establish a connection to remote location "\\DPSRV\Drivers", error #1231.when copying updated drivers from a remote location. The winbom.ini looks like the following :[Factory]FactoryComputerName = *Logfile = c:\Winbom.logLogging = YesLogLevel = 2LogPerf = YesUserName = administratorPassword = <removed>WinBOMType=FactoryReseal=RebootResealMode = Mini[PnPDriverUpdate]TargetRoot=%SYSTEMROOT%\driversUpdateInstalledDrivers = YesWaitForPNP=Yes[PnPDrivers]\\DPsrv\Drivers\DELL8250\Sound = Sound[OEMrun][NetCards][updateInis][FactoryRunOnce][branding][AppPreInstall][ComputerSettings]After the autologon, the network is up and running, and factory continues. The weird thing is that this only happens with the "Intel pro 100 M" nic. The same wimbom file works perfectly on other machines with a different nic. I've tried all kind of intel drivers, but for now I'm stuck :-(. I've seen a previous post about this, but no solution there. Is there anyone that can point me in the right direction?Thanks Michael Link to comment Share on other sites More sharing options...
Michael_W Posted October 4, 2004 Author Share Posted October 4, 2004 Well, I finally figured out what the problem was. If anyone has the same problem and wants to know the solution, then just send an email.Mike Link to comment Share on other sites More sharing options...
Michael_W Posted October 15, 2004 Author Share Posted October 15, 2004 On many request, this is the mail I send to Microsoft Support. Hope it helps if you encounter the problem.Hello Again,I'm happy to report that I discovered the reason why the factoryprocess was generating the 1231 error. Actually it's a combination offactors. The systems we are talking about are Dell dimensions 8250.Among things, they include an Intel 100 Pro network adapter and a ATIradeon 9700 128 video adapter. Now that last was actually the cause ofall the problems. I did a series of tests starting with the Windows XP gold edition. Inthis particular version of XP there's no driver for the ATI videoadapter. So I was quite surprised that this version worked with thewinbom.ini file you so kindly provided. After the first test Iinstalled SP1 on the machine, ran the process and noticed that thefactory mode generated the error once more. I compared the driversthat where included in SP1 but not available in the gold edition ofXP. Among things, the USB and Video drivers where added. So that leftme to the conclusion that these drivers had something to do withgenerating the error. I installed XP gold again and updated the videodrivers to the version from the Windows Update site and started thefactory mode again. After the reboot the error was immediatelygenerated. So we had a winner! Now to get the whole thing working. Iconcluded that the video driver was interfering with the initialnetwork card detection and initialization process at the start of thefactory process, but I still wondered why. Well, remember the errorthat was generated, #1231? It must have something to do with thenetwork. I looked at my Winbom file again and suddenly I noticed thecomputer name change just before getting the drivers from the networklocation. Remembering a section form the winbom chm file that wouldreboot the pc just after the computer name change, I added this to theoriginal winbom file. Eg:[Factory]RebootAfterComputerName = YesThe factory process was started again and I was right on my conclusionThe reboot did the trick. I'm making an assumption that the processfirst detects an available network card in the machine, assigns a newname to the pc and in that process the video adapter would interferein some way, generating the 1231 error. Funny thing is that it was acombination of hardware that was the cause of all this misery. Thedell machines with an identical configuration except for the nicworked perfectly without the reboot setting. From now on I willinclude the reboot option in my winbom file(s), just in case. Anyway,I'm glad the problem is solved. Hope you can make use of thisknowledge.With kind regards,Michael Waterman 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