zzzz Posted May 5, 2005 Posted May 5, 2005 I have this weird problem. The setup automatically reboots when it finishes installing network (about T-30). And when setup restarts, it keeps rebooting at that point.I don't use nLite, no Reg Tweaks.I integrate hot fixes manually from Ryan's pack, use Pyron's method to install drivers, and BTS's WMP10 slipstreamer.I change the billboard screen by the one I found here.My Winnt.SIF: (still use $OEM$ folder to copy some files to harddrive);SetupMgrTag[Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" AutomaticUpdates=1[Unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes UnattendSwitch="yes" TargetPath=\WINDOWS FileSystem=* UnattendSwitch="yes" WaitForReboot="No" KeyboardLayout="US" OemPnPDriversPath="Drivers" DriverSigningPolicy=Ignore NonDriverSigningPolicy=Ignore[GuiUnattended] AdminPassword=********* EncryptedAdminPassword=Yes OEMSkipRegional=1 TimeZone=20 OemSkipWelcome=1[Display] AutoConfirm=1[UserData] ProductKey=************ FullName="*******" OrgName="******" ComputerName=*******[TapiLocation] CountryCode=1 AreaCode=*** LongDistanceAccess="*"[RegionalSettings] LanguageGroup=1[Identification] JoinWorkgroup=******[Networking] InstallDefaultComponents=Yes[Components] msmsgs=off msnexplr=off zonegames=off[Shell] DefaultStartPanelOff = Yes
Bâshrat the Sneaky Posted May 5, 2005 Posted May 5, 2005 I'm afraid you'll have to leave out one part at the time to see what's causing it. So first add nothing, test, add RyanVM's updatepack, test, my DPs, test, WMP10, test. (however WMP10 would be VERY unlikely )
benners Posted May 5, 2005 Posted May 5, 2005 Check on the network to see if the computername you are using in the sif file is already in use when you are installing windows.
oioldman Posted May 5, 2005 Posted May 5, 2005 Is this[Identification] JoinWorkgroup=******actually allowed? or have you removed it from an accepted name for display purposes?If not enter one and see what happens.
zzzz Posted May 5, 2005 Author Posted May 5, 2005 All the **** is normal characters that I replaced.Computer name is unique and not similar to anything (username...).I guess I have to check each part then
benners Posted May 5, 2005 Posted May 5, 2005 The next time it reboots, if you have an old Win98 boot disk, boot from that and navigate to the windows folder, then type edit setuperr.log I think that is right, you may need to have edit.com on the disk I can't remember if it is an internal or external dos command, then you should be able to see the reason for the reboot.Another suggestion is copy the setuperr.log file from the machine and open it on another with windows installed, just makes it easier reading.
zzzz Posted May 5, 2005 Author Posted May 5, 2005 The next time it reboots, if you have an old Win98 boot disk, boot from that and navigate to the windows folder, then type edit setuperr.log I think that is right, you may need to have edit.com on the disk I can't remember if it is an internal or external dos command, then you should be able to see the reason for the reboot.Another suggestion is copy the setuperr.log file from the machine and open it on another with windows installed, just makes it easier reading.<{POST_SNAPBACK}>Thanks for the tip. I used WinPE and was able to see the log. Turns out that it's the duplicate computer name that causes the problem. Sorry benners, you were right , didn't check the network .It seems that in these installations, setup reads winnt.sif on the harddrive? Cause it doesn't help when I replace the winnt.sif on the cd.
benners Posted May 5, 2005 Posted May 5, 2005 Sorry benners, you were rightLord take me now for my genius has become my curse Seriously though, glad you sorted it
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