Getting Random Runtime errors when Resuming WPI after Reboot.

[Jbenke]

Curious if someone could take a look at this and let me know if I did something stupid. I am getting random Runtime errors when calling the common\installer.hta after a reboot. Mostly happens after the default user entry you see in my config file. Let me know if there are any others files I need to post.

Thanks!

config.js

useroptions.js

[zorphnog]

Is the Default User entry the only one that reboots? Post your WPI_log.txt and rbconfig.js. Both should be on the root of you system drive (C:\).

[Jbenke]

Is the Default User entry the only one that reboots? Post your WPI_log.txt and rbconfig.js. Both should be on the root of you system drive (C:\).

No I have a total of two reboots but the "Default User" is the first reboot. I have attached the files you requested. Thanks for the help, much appreciated!

rb_config.js

WPI_Log.txt

[Jbenke]

Perhaps this is creating the problem? I noticed when the WPI resumes itself it calls the installer.hta proceeded by the mshta command. When mine resumes, I have been killing that reg entry (Before Reboot) and calling the installer.hta file directly with a script and I have not been proceeding it with the mshta command. Could this possibly be the problem?

Even if I just go back and run wpi.hta and say resume on previous install I still get the runtime error if I have received it before. Nothing but canceling the install will allow me to use the wpi again.

Edited September 5, 2007 by Jbenke

[Jbenke]

Anyone have any clues on this one? Still getting it randomly, claims there is an invalid character on line 1. I assume this is suppose to be in the rb_config.js I don't see anythign that looks like an invalid character, does anyone else? The js file is attached to the third post in this thread. Any clue what would be causeing the change if there is an error?

Appreciate any help I can get, I am done with what I need this for for the most part if I can solve this issue.

Thanks!

Edited September 7, 2007 by Jbenke

[Jbenke]

Ok I've narrowed it down a bit more here. Hopefully someone with respond to this with a thought. It happens on a total of two of my installs and both reboot in the same way.

1. I call a number of scripts, seems at this point that what they are doesn't matter.

2. I delete the RunOnceEx so that the wpi won't continue on the next reboot untill I am ready for it.

3. I call a reboot.

4. PC Reboots, auto logs in, runs some scripts in startup, then calls a reboot. (NOTE: I do not let the WPI resume during this. Explained below.)

5. The machine reboots and runs another script in startup, which does a few things and then calls INstaller.hta so the WPI can continue where it left off.

I think that the reboot in between without calling the WPI is the problem, perhaps something else after the reboot is being called besides installer.hta and when it checks for installer.hta and it's not their it freaks???

Simple solution, make the WPI come back up in the middle reboot, assuming that is the problem. Problem is that I am changing users so I can copy the admin profile to the default profile with copyprofile.exe and the wpi looks as if all it's reg entries are located in the current user and if I were to call it would I be risking more errors than I already have?

Also I don't believe the problem to be the copying of the profiles it's self as another install has the same reboot pattern (Mostly because I did it before I was using the WPI and havne;t changed it yet) and it has nothing to do with the profiles and even comes back up in the admin user vs swapping around a bit.

Any thoughts???? Anyone?????????????????????? Please?! *Groveling on hands and knees*

Will provide any files that you think may help.

[zorphnog]

Check to see if these registry entries exist once you are ready to resume WPI in the admin account:

HKCU\Software\WPI\ResumeInstall

HKCU\Software\WPI\Theme

HKCU\Software\WPI\PlayAudioInInstaller

HKCU\Software\WPI\CurrentInstall

HKCU\Software\WPI\LastExec

HKCU\Software\WPI\LastTopLine

HKCU\Software\WPI\Language

HKCU\Software\WPI\LogPath

[Jbenke]

Yes they do, are their any other registry entries that matter?

[zorphnog]

Ok. I think I figured it out. Try using this installer.js file. Place it in your WPIScripts folder.

installer.js

[Jbenke]

Cool I will give that a try. Should this fix the problem with starting the wpi in a differant profile? Or the original script error after booting up into a profile and not running the wpi?

Thanks again!

[zorphnog]

Just the original error with it not running WPI. The registry keys would have to be saved to HKLM to work in any profile.

[Jbenke]

I thought it had fixed it as I ran it a ton of times without an issue. Previously it would error every or every other time. However the very last run error. 1 out of 15 or so isn't to bad though. Perhaps theirs just one more thing to be changes and you got most of it?

Here's hoping. *Crosses Fingers*

*Extremely appreciating the time and effort you are putting in to fixing this.*

[Jbenke]

Ok still getting the error randomly, anyone else think why I would be getting this? I am killing the start command in the regex and later for all intents and purposes just calling the installer.hta from the startup directory. Could this in someway be a bad thing?