Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

windows xp run key started program does not start 1

Status
Not open for further replies.

SirWillie

Technical User
Sep 22, 2002
19
US
Is there a timing issue in Widows XP (SP2) when starting a program with:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run?

The only unique thing about the program is resides on a server, not the local workstation. The program runs just fine from a command prompt after the system has booted. Also, it ran with no problem on WIN2K.
 
XP attempts to optomize its bootup, a process roughly addressed in this FAQ: faq779-4518

Cannot you create a local filestore for this program? It would help a great deal at boot.
 
The program needs to run on the server. It calls USMT and saves the data on the server before a migration. Is there a way to turn off the Optomization?
 
The only way to turn off boot time optomization is with a Group Policy/registry entry. See the last paragraph of faq779-4017

But it really should not be a factor.
 
What is the value (path) in the Run key that is not working?

This thread explains what I am thinking about.

Reg File to Create System DSN
thread779-1128697
 
The path is "\\server\scripts\migrate.cmd options" so I shoud try "\\\\server\\scripts\migrate.cmd options"?
 
You could try it, maybe even \\ before migrate.cmd too?

At least you wont die wondering.
 
The solution was to turn off boot optimization with MMC. This worked good. Adding the additional "\" did not seem to make any difference. The "Always wait till network....." local policy setting is retained after sysprep.

"Autostarting USMT is the bomb", Upgrades and installs are almost hands-off. I can remote into a customer's server, enter the name of the workstation(s) I want to rebuild and hit go. Then 30-45 minutes later a local tech goes to the workstation, calibrates the touchscreen and verifies serial communications. Done.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top