Jump to content

Factory error 1231?


Recommended Posts

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.log

Logging = Yes

LogLevel = 2

LogPerf = Yes

UserName = administrator

Password = <removed>

WinBOMType=Factory

Reseal=Reboot

ResealMode = Mini

[PnPDriverUpdate]

TargetRoot=%SYSTEMROOT%\drivers

UpdateInstalledDrivers = Yes

WaitForPNP=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

  • 2 weeks later...

  • 2 weeks later...

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 factory

process was generating the 1231 error. Actually it's a combination of

factors. The systems we are talking about are Dell dimensions 8250.

Among things, they include an Intel 100 Pro network adapter and a ATI

radeon 9700 128 video adapter. Now that last was actually the cause of

all the problems.

I did a series of tests starting with the Windows XP gold edition. In

this particular version of XP there's no driver for the ATI video

adapter. So I was quite surprised that this version worked with the

winbom.ini file you so kindly provided. After the first test I

installed SP1 on the machine, ran the process and noticed that the

factory mode generated the error once more. I compared the drivers

that where included in SP1 but not available in the gold edition of

XP. Among things, the USB and Video drivers where added. So that left

me to the conclusion that these drivers had something to do with

generating the error. I installed XP gold again and updated the video

drivers to the version from the Windows Update site and started the

factory mode again. After the reboot the error was immediately

generated. So we had a winner! Now to get the whole thing working. I

concluded that the video driver was interfering with the initial

network card detection and initialization process at the start of the

factory process, but I still wondered why. Well, remember the error

that was generated, #1231? It must have something to do with the

network. I looked at my Winbom file again and suddenly I noticed the

computer name change just before getting the drivers from the network

location. Remembering a section form the winbom chm file that would

reboot the pc just after the computer name change, I added this to the

original winbom file. Eg:

[Factory]

RebootAfterComputerName = Yes

The factory process was started again and I was right on my conclusion

The reboot did the trick. I'm making an assumption that the process

first detects an available network card in the machine, assigns a new

name to the pc and in that process the video adapter would interfere

in some way, generating the 1231 error. Funny thing is that it was a

combination of hardware that was the cause of all this misery. The

dell machines with an identical configuration except for the nic

worked perfectly without the reboot setting. From now on I will

include 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 this

knowledge.

With kind regards,

Michael Waterman

Link to comment
Share on other sites

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...