Express Posted February 6, 2006 Share Posted February 6, 2006 Hi All,Can someone shed some light here on where I can check or what may be wrong. Everytime UA DVD get to T-39 it reboots. What can be the cause of this??Thanks Link to comment Share on other sites More sharing options...
Shark007 Posted February 6, 2006 Share Posted February 6, 2006 (edited) Extracted from WINNT.SIF[GuiUnattended]DetachedProgram=%systemroot%\filename.exethe above executes @T-39 , possibly, if you're using this,there is an error in your command / path / filename / file itself etc.shark Edited February 6, 2006 by Shark007 Link to comment Share on other sites More sharing options...
Express Posted February 6, 2006 Author Share Posted February 6, 2006 Here is part of my winnt.sif:;SetupMgrTag[Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" AutomaticUpdates=No[unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes TargetPath=\WINDOWS OemPnPDriversPath="Drivers\000_chipset_dc5000_d530_evo;\Drivers\010_broadcom_nic;\Drivers\011_intel_pro100;\Drivers\012_intel_pro1000;\Drivers\020_intel_graphics;Drivers\021_nvidia_graphics;\Drivers\022_ati_graphics;\Drivers\023_color_grapics;\Drivers\030_ADI_audio;Drivers\031_SoundMax" DriverSigningPolicy=Ignore UnattendSwitch = Yes Repartition = Yes FileSystem = convertNTFS ExtendOemPartition = 1, NoWait[GuiUnattended] AdminPassword=*********************** EncryptedAdminPassword=Yes AutoLogon=Yes AutoLogonCount=1 OEMSkipRegional=1 TimeZone=35 OemSkipWelcome=1 Link to comment Share on other sites More sharing options...
Shark007 Posted February 6, 2006 Share Posted February 6, 2006 My next suggestion would be to eliminate OemPnPDriversPath from winnt.sifto see if its caused by a driver file, or a bad inf.also, i have seen this caused by a corrupt file on the harddrive within the installation source files.An easy way to eliminate this possibilty is to COPY (not move)the entire compilation elsewhere (hopefully a diff hdd) and create the ISO from there.shark Link to comment Share on other sites More sharing options...
Express Posted February 6, 2006 Author Share Posted February 6, 2006 Hey Shark,Ok after sitting infront of the machine and watching evey freaking movement it looks as it restarts at T-32 once it is doing the network drivers installs.....AHHHHHHH I am going nutssss Link to comment Share on other sites More sharing options...
Shark007 Posted February 6, 2006 Share Posted February 6, 2006 Its a driver conflict/error of some sort.Again, take out the OemPnPDriversPath.shark Link to comment Share on other sites More sharing options...
VCC Posted February 6, 2006 Share Posted February 6, 2006 (edited) Maybe this will help you troubleshoot what is going on. It is Micro$oft's info on things you can use to troubleshoot Windows Setup.Description of Windows Setup Function KeysGood luck, I've run into something similar, but the T- spot was a bit further and was due to drivers not being defined in txtsetup properly.+++Also, do some searches on M$'s support site, you should find some useful commands they have to run in the command window that shows up using Shift+F10.+++++For more help: Setup stops responding with 34 minutes remaining Edited February 6, 2006 by VCC Link to comment Share on other sites More sharing options...
VCC Posted February 6, 2006 Share Posted February 6, 2006 (edited) Here is a site that shows the control panel tools by command (which may be run using Shift-F10 during GUI Mode Setup):How to run Control Panel tools by typing a commandWell, time for me to scram, hope this info will aide you in your problem. Edited February 6, 2006 by VCC Link to comment Share on other sites More sharing options...
VCC Posted February 6, 2006 Share Posted February 6, 2006 (edited) I would also like to suggest the use of Bashrat T.S.'s DriverPacks. There has been much work put into these and they are worth using them. Unless of course you enjoy doing it yourself. But, they are worth mentioning. For the link to the DriverPack site, I have updated my signature to include it or you can find the forum in the Member Contributed Projects area. Edited February 6, 2006 by VCC Link to comment Share on other sites More sharing options...
Express Posted February 7, 2006 Author Share Posted February 7, 2006 Shark & VCC Thanks for your help I really do appreciate I will try first thing in the morning, I have the machine at work. Also I should mentioned the last thing I installed on that machine was "XPIZE". Could that have damaged the files?VCC I will take a look at Bashrat T.S.'s DriverPacks. Thanks again, Link to comment Share on other sites More sharing options...
Express Posted February 7, 2006 Author Share Posted February 7, 2006 Shark007 Posted Yesterday, 03:12 PMMy next suggestion would be to eliminate OemPnPDriversPath from winnt.sifto see if its caused by a driver file, or a bad inf.I am in the process of running the ua install now without the OemPnPDriversPath, lets see what happens. I also uninstalled XPIZE from my machine as well, I don't need to take unnecessary chances on my pc which I have too much lose...I will get back to you and let you know if that worked. If that is the case then what do you suggest may be the issue? The drivers got corrupted? Link to comment Share on other sites More sharing options...
Express Posted February 7, 2006 Author Share Posted February 7, 2006 Guess what Shark, you are a "Genius". Took out the OemPnPDriversPath and it worked. Now the question is why did that happen, and if it's corrupted how do I uncorrupt and which file do I need to replace.THANKS.... Link to comment Share on other sites More sharing options...
Shark007 Posted February 7, 2006 Share Posted February 7, 2006 you're welcome.the handholding is just about done.You mention network drivers, which do install around T-32These would be my 1st suspect. Replace the OemPnPDriversPath in winnt.sifbut remove the network drivers from the source files.Remove the entire 010_broadcom_nic folder and any other nic drivers you have.Possibly, your drivers arent for your exact nic or something like that.Have fun troubleshooting and enjoy the forums, see yashark Link to comment Share on other sites More sharing options...
Express Posted February 7, 2006 Author Share Posted February 7, 2006 Thanks Shark,nuff said, I'll check those drivers.Thanks again, I appreciate your time and knowledge.Express Link to comment Share on other sites More sharing options...
Express Posted February 9, 2006 Author Share Posted February 9, 2006 Hey VCC, I can use your help.http://www.msfn.org/board/index.php?showforum=108See above post I am having some trouble gettng the driver pak to install driver.Thanks 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