Jbenke

Could be a simple problem but I call a %reboot% 3 and when it hits the reboot command, instead of haulting until after the reboot it skips to the next installation and then reboots. So when the comp comes back up, it in sense skipped an installation all together. Something simple, like needing two digits in reboot? %reboot% 03?

If you are running Vista and have Nero 7 installed thats probably the problem. There was a thread about it quite a while back. Couldn't find on a quick look but I'm sure it's there. Something about a change that Nero 7 makes causes that to crash the Application Host. Happens on my vista machine with Nero 7. I believe the developer mentioned having no clue as to why it was happening and the only resolution he could offer was a rebuild and leave nero 7 off of it.

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?

I didn't know it was really that hard to run it from the network. I have the exact same versions on cd and the network. I just copyied it up there with the directory strucure, Unattended, which contains the wpi.ico and autorun, (truthfully this directory name doesn't matter) then wpi\all the normal stuff. Then when I want to use it I just map a local drive letter to \\server\unattended and the autorun in the unattended directory kicks off and the wpi behaves as if it were on a cd. If the autorun doesn't kick I just go hit the wpi.hta and it goes. Have yet to notice any issues.

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.*

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!

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

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.

Is there a file that I can look at or a quick ref that someone can give the that spells out all of the registry changes, as in new keys or existing keys that the wpi uses?

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!

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.

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

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

I am curious to know how the file paths are handled once the installer starts. Do they resolve to the direct paths and save those for execution later? EI d:\blahh\setup.exe or do they maintain their %WPI%\blahh\setup.exe untill it actually gets to their turn to install. The reason I am asking is I am running the WPI from a network drive and I have to have a few reboots, When the machine comes back up I will need to remap to share and then call the installer.hta. The main question is do I need to make sure it's the same drive letter for the mapping or does it not matter?

Ok this is a wierd one but I am hoping someone might have a solution. I have a piece of software I am trying to install (Aspect WinSet 3.1) and I use AutoIt to script the install process. The Script works fine if I execute it manually but if WPI excutes it, it blocks a command prompt that opens as part of the programs installation and the who thing frags up. Alll I can figure is there's a process or something that WPI has a hold of that is blocking things. My solution is probably the hard way but as long as it works. If I call a reboot before it starts the script, load the script into the startup directory, kill the RunOnceEx of WPI so it dosn't restart on reboot the script goes through fine and then I just call the installer and things continue fine. What I am wondering is if there is a command I can call or a list of processes or such that I can kill to basically stop the WPI in it's tracks and free up everything it had ahold of, then once the script finished I can call the installer again. Trying to avoid the reboot here is I can. Any thoughts? I tried just killing mshta.exe but when I call the installer again it reports errors and won't continue with the script. Thanks for any help you can offer.