Search options

LMAO!  Now that I re-read this, it makes me laugh the way you worded it.  Hehe.  That may be true, but to a n00b like me, I didn't see anything that tells me that GUIRunOnce runs after RunOnceEx.  I was just basically trying to say that it might save other n00bs like me a lot of time if the tutorials warned about what would happen if you reboot at the end of RunOnceEx.  I forget which forum I got the shutdown in cleanup.cmd from, but I mostly used DP Finisher in GUIRunOnce because the tutorial didn't say anything about the pros and cons and GUIRunOnce was the default, so I figured it must be the safest option.  Yeah, I should know what happens when I assume something. 

I gotta say that I'm so thankful that this unattended community is a very helpful bunch.  Everyone seems to help as much as they can and I hope I can give back by helping others.  Oh, speaking of which, when I researched the desktop.ini error, I did not see anything that states that rebooting before DP Finisher finishes could be the cause of the desktop.ini error, but that is exactly what caused it for me.  Also, I saw a lot of messages of people making cleanup routines to cleanup DP files in their root folder instead of trying to figure out why DP Finisher did not finish.  I'm not sure but am wondering if at least some were because of the same reason as me.  After all, I did get the shutdown found in cleanup.cmd, run at the end of RunOnceEx from one of the forums in this unattended install community.  I hope this helps someone. 

Ed

Ahh, thank you.  Thank you for both changing the title and for answering my question.  I will try that in next test.

Although I see the extra info in that tutorial, I still don't see anything that talks about how the DP cleanup/KTD is started or more importantly, how I can do a reboot after it is done.

Yes, I did run DP as my last stage (thanks to tutorials). 

I'm afraid I didn't keep the logs.  Its very reproducable tho... Just enable KTD and have RunOnceEX reboot.  Hmm, I'm not sure if this matters, but I have RunOnceEx run a CleanUp.cmd that has:

   cmdow @ /HID
   shutdown.exe -r -f -t 60 -c "Windows XP will now restart in 1 minute..."
   DEL ***some stuff here for cleanup***
   EXIT

This at the very least will leave stuff in C:\D\ and not finish copying KTD to C:\Windows\DriverPacks\ and sometimes give a desktop.ini error.

Sorry, but I'm a bit too busy ATM to mess with it more.  Maybe in a week or 2.  Removing the reboot in cleanup.cmd eliminates all these problems.  I watched the install and saw the DriverPacks starting to do things right after the RunOnceEx ended (which was during the shutdown.exe countdown timer. 

I hope this helps someone.
Ed

I posted tooooo soooooon.  I just tested with DP Finisher set to RunOnceEx and it still happens.  KTD runs after all the RunOnceEx is done, but I haven't read anything about how to run things after that point.  I don't see how KTD is set to start.

Hmm, I need to reboot after KTD is done, but I don't see how to do that.  Any ideas?

Yeah, I had  the same problem.  I got around it by re-installing WinXP.  I thought it ironic that I had to re-install Windows to download the files I needed to make the install disk I'm working on.  <grin>

Well, anyway, now I'm getting the leech warning again.  It must be a conflict with some program I installed since I downloaded the files a couple of weeks ago.  This should be fun tracking down.  I'll let you know if I figure out which program it is.

Yes, I tried IE v6 and FireFox v2.  I got around this problem by installing windows on another drive and it worked there.  I must have something corrupt, but I doubted that since I haven't had problems on any other website.

Kinda ironic... I had to re-install Windows in order to download the drivers I needed for the Windows install disk I'm working on. 

I did try to replace the GDIPLUS.MAN as per instructions from google searches.  It didn't help.  And yes, was using ISO's, which only confused me since most explainations for that problem were blaming CD or CD-ROM problems.  Also, I can open the problem files with a notepad and it looked fine.  And, the same ISO's worked fine with VMware.  Another interesting thing is that of the 3 or 4 different files (different file in different ISO's), some were compressed and some were not.

Ed