subaqua2004 Posted November 4, 2004 Share Posted November 4, 2004 I can't find any precise info about the problem I'm having.I've built an unattended install (originally coming off a Ghost image, but nowworking using WinPE).I've got drivers in $OEM$\$1\Drivers and I've added them to the OemPnPDriversPath.Setup appears to work fine, but when it gets to installing the network (T-30),setup appears to exit (goes back to a plain blue screen), then the PC rebootsand when it comes back up I get "Setup is restarting...." and the whole processstarts again (from T-39).The weird thing is, it doesn't do it /every/ time (perhaps 8/10 times). I've usedvarious different hardware, including VirtualPC and the same thing happens.When I comment out the drivers path, it goes through 100% no problems (but no drivers either!)Any clues? Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted November 4, 2004 Share Posted November 4, 2004 Did you add the necessary entries to the dosnet.inf file? (in case you're adding MassStorage drivers) Link to comment Share on other sites More sharing options...
subaqua2004 Posted November 4, 2004 Author Share Posted November 4, 2004 No. I'm only trying to add network, video and audio drivers at this stage. All our PCs (well, the ones I want to install unattended) have plain vanilla IDE HDDs. Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted November 4, 2004 Share Posted November 4, 2004 Did you set any network preferences in your winnt.sif? Link to comment Share on other sites More sharing options...
SiMoNsAyS Posted November 4, 2004 Share Posted November 4, 2004 for me it sounds like a problem with your network added drivers, you can first, be sure to have the latest drivers for your hardware. second, be sure that you have properly configured your network on winnt.sif. finally to locate the problem you can start removing drivers until the problem fixes so you know what caused it. Link to comment Share on other sites More sharing options...
kalavera Posted November 7, 2004 Share Posted November 7, 2004 I HAVE FOUND THE BUG!The problem is in txtsetup.sif. If you notice there is a "end" character at the end of txtsetup.sif (before modification). Then after running the driverpack script it adds the entries at the really end of the file, this way not leaving the "end" character at the end of the file.SOLUTION:Just cut and paste the character to the end of the file. Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted November 7, 2004 Share Posted November 7, 2004 I HAVE FOUND THE BUG!The problem is in txtsetup.sif. If you notice there is a "end" character at the end of txtsetup.sif (before modification). Then after running the driverpack script it adds the entries at the really end of the file, this way not leaving the "end" character at the end of the file.SOLUTION:Just cut and paste the character to the end of the file.I'm sorry to disappoint you, but I'm afraid you weren't the one to see this as the first one...This character is known as the :EOF character and indeed marks the end of the txtsetup.sif file. The strange thing about all this is: there hasn't been any trouble with this for months, untill now... RyanVM didn't add this character at the end of the txtsetup.sif file and he never had any troubles with this. It must be something of SP2 or something... And not everybody is getting this error, which makes this bug even stranger...But, you are right, that when you get errors, you might want to cut/paste it to the end of the txtsetup.sif file! Link to comment Share on other sites More sharing options...
Timorad Posted November 7, 2004 Share Posted November 7, 2004 Try replacing, in your presetup.cmd this:reg add "HKCU\Software\Microsoft\Driver Signing" /v Policy /t REG_DWORD /d 1 reg add "HKCU\Software\Policies\Microsoft\Windows NT\Driver Signing" /v BehaviorOnFailedVerify /t REG_DWORD /d 1 reg add "HKLM\Software\Microsoft\Driver Signing" /v Policy /t REG_BINARY /d 01by this:reg add "HKCU\Software\Microsoft\Driver Signing" /v Policy /t REG_DWORD /d 1 /freg add "HKCU\Software\Policies\Microsoft\Windows NT\Driver Signing" /v BehaviorOnFailedVerify /t REG_DWORD /d 1 /freg add "HKLM\Software\Microsoft\Driver Signing" /v Policy /t REG_BINARY /d 01 /fWorked for me, and I had the same symptoms. Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted November 7, 2004 Share Posted November 7, 2004 **** Already forgot that! I really have to update it with this!Thanks again, Timorad! Link to comment Share on other sites More sharing options...
esp Posted November 8, 2004 Share Posted November 8, 2004 Can anybody type the :EOF character?I mean, what does it look like? I don't think I've ever seen anything like that, not in notepad anyway. Is it the square shape that was used in prehistoric computing times? Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted November 8, 2004 Share Posted November 8, 2004 Can anybody type the :EOF character?I mean, what does it look like? I don't think I've ever seen anything like that, not in notepad anyway. Is it the square shape that was used in prehistoric computing times?Yes, it's the rectangular shape Link to comment Share on other sites More sharing options...
RogueSpear Posted November 8, 2004 Share Posted November 8, 2004 I've noticed some anomalies with the EOF character. It would appear, in my case anyway, the it is required to have at least one CR before and at least one CR after.Also when I make changes to my ISO and then save the ISO, something happens to that file everytime. I have to go back and insert the txtfiles.sif again, overwriting the one in the ISO, then save, then I'm all set. I don't know if this is some kind of bug in UltraISO or not. But its all rather annoying. Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted November 8, 2004 Share Posted November 8, 2004 Also when I make changes to my ISO and then save the ISO, something happens to that file everytime. I have to go back and insert the txtfiles.sif again, overwriting the one in the ISO, then save, then I'm all set. I don't know if this is some kind of bug in UltraISO or not. But its all rather annoying.Why don't you use CDimage to create the image? OK, it rebuilds the ISO every time, but who cares, it only takes about one minute... Link to comment Share on other sites More sharing options...
subaqua2004 Posted November 10, 2004 Author Share Posted November 10, 2004 I HAVE FOUND THE BUG!The problem is in txtsetup.sif. If you notice there is a "end" character at the end of txtsetup.sif (before modification). Then after running the driverpack script it adds the entries at the really end of the file, this way not leaving the "end" character at the end of the file.SOLUTION:Just cut and paste the character to the end of the file.Umm...nope. The EOF character appears to be there.I did recreate the i386 directory from my original XP CD and that worked...for a time. Now its back to how it was before. I'm going to try Pyron's method.I'll report back later...Subaqua Link to comment Share on other sites More sharing options...
subaqua2004 Posted November 11, 2004 Author Share Posted November 11, 2004 Pyron's method didn't change the result (as I suspected). However, it is pretty cool, so I'll stick with it.Strangely, removing cmdlines.txt seems to let it run through...but the only thing I've got in there is a call to RunOnceEx.cmd!?!?! 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