G
George
Guest
I am building a series of scripts (basically batch files) to automate
certain tasks in Windows XP. There are several scripts I need to
run,and often multiple reboots are needed. So in order to continue
after each reboot, I simply use the RunOnce command (HKLM/Software/
Microsoft/Windows/CurrentVersion/RunOnce) to run the next script after
a reboot has occurred.
I do this by having a command in each script that just imports a reg
file into the registry which is the command for the RunOnce command.
Sounds simply enough.
The problem is when I install the Cisco VPN client (our company
requires us to use version 4.8.01.0300) at the end of the install
(right before the client install forces a reboot) it actually executes
the script in the RunOnce command in the registry!
Why does it do this?
This is a real problem for me, because it causes the next script
(which was supposed to run AFTER the reboot) to run now, and this
messes a lot of things up.
I even tried to put the next script into the Start Menu / Startup
folder instead, and it launches that too!
I found what I thought would be a solution, where I edited the file
OEM.INI (inside the the install folder for the VPN Client) and if you
edit the line that says "Reboot=2" and change it to "Reboot=1" it
suppresses the reboot. By doing this, it doesn't launch stuff in
RunOnce or the Startup folder, but now the stupid program about
halfway thru the install stops responding! So now I have to manually
pull up task manager, perform an END TASK and then I can reboot the
computer. This kind of defeats the purpose of an automatic script
I can replicate this problem on over 20 different computers (laptops,
desktops, different brands, models, etc...) So I know the problem
isn't a certain driver from a certain computer.
Does anybody have an idea what I can do?
Is there a way to get this app to install and not reboot (and not
crash)? If I could get that to work, then I could just initiate my
own reboot (via the shutdown.exe command), and that should work. Or
if the client wants to reboot itself, thats OK too, as long as it
stops launching what it finds in RunOnce and Startup!
certain tasks in Windows XP. There are several scripts I need to
run,and often multiple reboots are needed. So in order to continue
after each reboot, I simply use the RunOnce command (HKLM/Software/
Microsoft/Windows/CurrentVersion/RunOnce) to run the next script after
a reboot has occurred.
I do this by having a command in each script that just imports a reg
file into the registry which is the command for the RunOnce command.
Sounds simply enough.
The problem is when I install the Cisco VPN client (our company
requires us to use version 4.8.01.0300) at the end of the install
(right before the client install forces a reboot) it actually executes
the script in the RunOnce command in the registry!
Why does it do this?
This is a real problem for me, because it causes the next script
(which was supposed to run AFTER the reboot) to run now, and this
messes a lot of things up.
I even tried to put the next script into the Start Menu / Startup
folder instead, and it launches that too!
I found what I thought would be a solution, where I edited the file
OEM.INI (inside the the install folder for the VPN Client) and if you
edit the line that says "Reboot=2" and change it to "Reboot=1" it
suppresses the reboot. By doing this, it doesn't launch stuff in
RunOnce or the Startup folder, but now the stupid program about
halfway thru the install stops responding! So now I have to manually
pull up task manager, perform an END TASK and then I can reboot the
computer. This kind of defeats the purpose of an automatic script
I can replicate this problem on over 20 different computers (laptops,
desktops, different brands, models, etc...) So I know the problem
isn't a certain driver from a certain computer.
Does anybody have an idea what I can do?
Is there a way to get this app to install and not reboot (and not
crash)? If I could get that to work, then I could just initiate my
own reboot (via the shutdown.exe command), and that should work. Or
if the client wants to reboot itself, thats OK too, as long as it
stops launching what it finds in RunOnce and Startup!
