BenjaminKalytta Posted July 19, 2004 Posted July 19, 2004 Did you load your test.ini for example?May I get access to your system with "Windows Remote Desktop"? I can't imagine why this could happen. Are there 2 debug windows opened or did you start wihu twice?It should show something like this:
Alanoll Posted July 19, 2004 Posted July 19, 2004 I'm about to head home, so in a bit sure, you can have access to the machine.Never done it before, just PM me.When I get home, I'll try it again.And now, there weren't two WIHU, just two screencaptures. Took the first one right when started, and then again after.Yes i loaded test.ini.usedwihu.exe /SkipSettigns /SkipRestart /ini-test.ini
BenjaminKalytta Posted July 19, 2004 Posted July 19, 2004 wihu.exe /SkipSettigns /SkipRestart /ini-test.inishould bewihu.exe /SkipSettigns /verbose /SkipRestart /ini=test.iniTo test it. And if /SkipSettigns is used, I found out that environment isn't loaded.(because settings is skiped ... but I changed this because it is confusing)Please just redownload this exe and test it again ... don't forget /verbose switch.benjamin
Alanoll Posted July 19, 2004 Posted July 19, 2004 i used /verbose switch before, forgot to type it....it now works properly, with using /SkipSettings....i guess you didn't use that switch your tests while I did in mine still want the debug window?
BenjaminKalytta Posted July 19, 2004 Posted July 19, 2004 still want the debug window?No, thx it now works properly, with using /SkipSettings....i guess you didn't use that switch your tests while I did in mineNext time just show entire command line But hey, great to find this bug. The less the better. I've learned from this bug not to add global things into local window procedure ... I said this /SkipXxx switches are critical benjamin
Alanoll Posted July 19, 2004 Posted July 19, 2004 hehe....all these posts ("requests") for 3 little bugs. lol.What about the one remaing request of mine? The restart thing?EDIT:: Wait....you fixed that too. /Restartwait=X /AutoInstall
BenjaminKalytta Posted July 19, 2004 Posted July 19, 2004 EDIT:: Wait....you fixed that too. /Restartwait=X /AutoInstallYes, but don't forget to specify elapse time otherwise it won't work./autoinstall=<time>Benjamin
Alanoll Posted July 20, 2004 Posted July 20, 2004 Hmmm....Shouldn't this screen go to the progress bar thing?I don't think it did....If it's not meant to, perhaps a feature to see what it's doing? (still using that test version you had me use too) The feature being, in a normal Windows Installer install, it tells you the component being installed, so perhaps the description.x line to e displayed with the progress bar going across?mmkay...never mind about the feature request I believe it's a bug again.When I remove the /AutoInstall=0 switch it works fine, so does /AutoInstall=1.Also, what is..."Terminated error code 7. The storage blocks were destroyed"?
BenjaminKalytta Posted July 20, 2004 Posted July 20, 2004 Shouldn't this screen go to the progress bar thing?Yes it's a bug ... I think I should rename it back to beta 2 ... It's fixed now.(Btw. don't know why this din't work ... according to Windows API it should work as it was ... but as always documentation arent always perfect )Also, what is..."Terminated error code 7. The storage blocks were destroyedI don't kown ... seems to be just a return code from an application ... needn't say much.Benjamin
Alanoll Posted July 20, 2004 Posted July 20, 2004 the fiels were where they were supposed to be....meh...Also, when I added it to my Unattend Install, I had a WIHU instance run for my hotfixes (guess why I made that INI file ) but at the end it stayed at the Finish screen. When I boot up my laptop with the test install going, I'll take the VMware screenshot and show you.
BenjaminKalytta Posted July 20, 2004 Posted July 20, 2004 I think I know what you mean ... it should be already fixed. (Some day I'll remove Autoinstall and SkipXxx things if there are so many bugs inside. )Benjamin
Alanoll Posted July 20, 2004 Posted July 20, 2004 well, I like the skip settings switch, as I run it three different times (simpler smaller INI's) and yeah...no need for it three times....AutoInstall it good as well, for Unattended obviosly...Any plans on replacements?
Osmosis Jones Posted July 20, 2004 Posted July 20, 2004 a stupid question again, how and when do you call wihu durning installation?
Alanoll Posted July 20, 2004 Posted July 20, 2004 mmkay, bug 4 gone (the progress bar thing) but bug 5 remains.....and I assume user error before program error Bug 5 being that it doesn't get past the Finish screen."..\Unattend\wihu.exe /SkipSettings /AutoInstall=1 /SkipRestart /Ini=hotfixes.ini /Log=%systemdrive%\wihu-hotfixes.log" INI file attached.Anyway to changing the logging so when using /verbose it doesn't open the debug window, but instead outputs to the log file?HOTFIXES.INI
Recommended Posts