XP expert help needed to autostart program

[Guest]

System=XP SP2

I have a program that refuses to automatically start and complete when XP
starts. I have tried the obvious and some not-so-obvious solutions and now I
am in need of some expert help.

Here's the scenario:

When I click on the desktop icon, the program starts and runs just fine. If
I go to the program folder and click on the program.exe file, it starts and
runs just fine. If I put a shortcut to the Start->Programs->Startup folder
and reboot, the program will start and hang. I have made sure that all folder
permissions are correct, but still no help.

The problem is not having the program start, as it does that, it is having
the programs that this one calls start up. At least, that is what I think is
happening.

It is almost like an old shell problem that wouldn't execute more than x
number of levels down the tree unless it was called directly.

Bottom line is that this software is worthless to me if I can't get it to
run when XP boots.

Any ideas?

 

[Guest]

Try going to run,type:services.msc In msc,scroll to the service(s),double
click,
select "auto-start" or manual,edit the other tabs/services.....

 

[Guest]

Try going to run,type:services.msc In msc,scroll to the service(s),double
click,
select "auto-start" or manual,edit the other tabs/services.....

That might work if this program was a system service and showed up on that
list, which it doesn't. I went so far as to put the shortcut back into the
Startup folder and reboot, then services.msc, etc but still nothing. The
program starts, then various subsystems start, then the last module hangs.

I just don't understand why Windows cannot cause the program to complete its
startup sequence but the admin user (me) can.

Thanks for the help,
Fred

 

[Malke]

That might work if this program was a system service and showed up on that
list, which it doesn't. I went so far as to put the shortcut back into the
Startup folder and reboot, then services.msc, etc but still nothing. The
program starts, then various subsystems start, then the last module hangs.

I just don't understand why Windows cannot cause the program to complete its
startup sequence but the admin user (me) can.

Thanks for the help,
Fred

Andrew E. is one of our resident trolls and you can ignore anything he
says. Obviously this is a permissions issue. The most efficient way to
solve it is to contact the program's tech support for workarounds,
patches, updates, etc. If for some reason you can't do this, then run
Regmon and Filemon from Sysinternals (free) to see where the program is
trying to write. Change permissions on those specific locations/registry
keys accordingly. Another way to deal with this is to create a Scheduled
Task to run the program and set the task to run as Administrator.

http://www.microsoft.com/technet/sysinternals/default.mspx


Malke

 

[Ron Martell]

Try going to run,type:services.msc In msc,scroll to the service(s),double
click,
select "auto-start" or manual,edit the other tabs/services.....

:

Andrew, please go away. Your nonsensical drivel not funny and
certainly not helpful.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."