rgoff Posted August 31, 2006 Posted August 31, 2006 I tried to use my HFSLIPed WinXP sp2 disk to do a repair of an existing installation. It never stopped to display options; instead it started the installation on my second partition. There was a reference in another topic to winnt.sif? I used the "fixed" version; is that the culprit? Log files attached.hfsliplogs.zip
Tomcat76 Posted August 31, 2006 Posted August 31, 2006 I'd bet it's the winnt.sif file. I can't think of anything else that would cause Windows setup to not display any installation options...BTW... It looks to me that that WU.TXT file is a result of a scan on the C: drive. I thought the installation of Windows you're having problems with is located on your second partition.
rgoff Posted August 31, 2006 Author Posted August 31, 2006 BTW... It looks to me that that WU.TXT file is a result of a scan on the C: drive. I thought the installation of Windows you're having problems with is located on your second partition.The install I wanted to repair is on C:. D: is where it went to install a new OS. I stopped it as it started because I didn't really know what it was doing and was hoping it wasn't eating my C: drive.Here's winnt.sf:[Data]AutoPartition=1;AutoPartition=0MsDosInitiated=0UnattendedInstall=Yes[unattended]UnattendMode=ReadOnly ; a little less automated (Windows asks more questions);UnattendMode=ProvideDefaults ; a little more automated (Windows asks fewer questions)ExtendOemPartition=0FileSystem=LeaveAloneOemSkipEula=YesOemPreinstall=YesDriverSigningPolicy=Ignore;NonDriverSigningPolicy=Ignore ; This setting has NOTHING to do with how WFP treats system filesRepartition=NoTargetPath=\WINNT[GuiUnattended]; asterisk means admin password is BLANK!AdminPassword=*OEMSkipRegional=1OemSkipWelcome=1;TimeZone=35 ; United States - East Coast;TimeZone=145 ; Russia - Moscow[systemFileProtection]; these no longer work post sp-1, here for illustration of how this used to work;SFCDisable=ffffff9d;SFCShowProgress=1;SFCQuota=1[setupparams]; found these two below in SETUPLOG.TXT at "SpSetupLoadParameter", some appear to be undocumented?;optionaldirs=skipmissingfiles=yes;UserExecute = ; It is generally unwise to use this, esp. with registry tweaks, as Windows is FAR from done with setup;UserExecute = %systemroot%\System32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %systemroot%\Inf\YOURINF.inf[TapiLocation];; United States - East Coast;CountryCode=1Dialing=Tone;; Russia - Moscow;;CountryCode=7;Dialing=Pulse[RegionalSettings];; United States - East Coast;LanguageGroup=1Language=00000409;; Russia - Moscow;;LanguageGroup=5,1 ;SystemLocale=0419 ;UserLocale=0419 ;UserLocale_DefaultUser=0419 ;InputLocale=0409:00000409,0419:00000419 ;InputLocale_DefaultUser=0409:00000409,0419:00000419[Networking]InstallDefaultComponents=Yes[GuiRunOnce]; An application that requires the Windows Explorer shell to install, or that reboots, will not work here.; To run an EXE file:; start /wait %systemdrive%\myfile.exe; To run an INF file:;"%systemroot%\System32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %systemroot%\Inf\myfile.inf"
Super-Magician Posted August 31, 2006 Posted August 31, 2006 @rgoff, your WINNT.SIF file is definitely the culprit! It appears you are using the file provided by FDV on his site.Remove it from your FIX folder and everything should be fine . Good luck !
rgoff Posted September 5, 2006 Author Posted September 5, 2006 Thanks. Reverting to the original winnt.sif file made the new disk go through the prompts as I expected. (The repair didn't fix the problem that I was hoping it would, a glitch in launching applications that's apparently due to some malware I've picked up.)
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