[tolasar]

Hello all,

This is my first time trying to do an unattended install of XP Pro. I have successfully slipstramed my SATA drivers into it. I am trying to integrate my drivers as well.

When simulating the installation with VMWare, the setup runs until the "Installing Network" phase. At this point the system reboots. There is no error message. Is there a way I can find the culprit or can someone point me in the right direction?

The network driver is a RealTek 8110 Gigabit Ethernet. Below is my Winnt.sif file:


[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
WaitForReboot="No"

TargetPath=\WINDOWS
DriverSigningPolicy=Ignore
OemPnPDriversPath="\drivers\SATA;\drivers\Video;\drivers\Ethernet;\drivers\GART;\drivers\MemCtl;\drivers\SMBus;\drivers\Audio"

[GuiUnattended]
AdminPassword=
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=35
OemSkipWelcome=1

[UserData]
ProductID=XXXX-XXXX-XXXX-XXXX-XXXX
FullName="John Doe"
OrgName="Doe Enterprises"
ComputerName="DEERDOE"

[TapiLocation]
CountryCode=1
Dialing=Tone
AreaCode=978

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=Yes

This is a full retail copy of XP Pro. Any suggestions would be appreciated. If more info is needed, let me know (I think I gave it all?)

[benners]

This happens when there are two machines with the same name on the network, alter the sif file while testing or change the name of the machine you are running VMWare on

[tolasar]

benners, on Jan 11 2005, 08:10 PM, said:

This happens when there are two machines with the same name on the network, alter the sif file while testing or change the name of the machine you are running VMWare on

The machine name is unique. Normally I am in a domain but just wanted to set it up as a workgroup PC and join the domain after setup is complete.

[tolasar]

Does anyone else know what might be causing this?

[tguy]

When testing in VMware, try commenting out the OEMPnpDriversPath statement in the WINNT.SIF file.

VMware uses an AMD PCNET NIC driver. If you don't have that in your Drivers\NIC directory you may have found your cause. Just let Windows install the default NIC it picks during the installation and then install VMware Tools after the OS boots.

I have done this succesfully many times.

[tolasar]

Thanks for that suggestion, I'll try it. Is there a way to have it install the driver for my NIC? I really don't want to try this on a CD until I'm sure all the "kinks" are worked out.