If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Can not run at start
Hi All,
I have a program which need to run at start when user login. The vender, who develop the program, save a value in registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run But for some reason, the program did not run at start. In Task Manager, under Processes tag, I could not find out the program. Any body knows why it happened? How to fix the problem? Thanks in advance. |
Ads |
#2
|
|||
|
|||
Can not run at start
"qq" wrote in message
news I have a program which need to run at start when user login. The vender, who develop the program, save a value in registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run But for some reason, the program did not run at start. The usual reason for this is internal, i.e. the app must itself be configured to start at boot or login. In Task Manager, under Processes tag, I could not find out the program. Does not Task Manager allow you either to / Add an app or to / Browse to any .EXE on the hard drive? -- Don Phillipson Carlsbad Springs (Ottawa, Canada) |
#3
|
|||
|
|||
Can not run at start
"qq" wrote in message news I have a program which need to run at start when user login. The vender, who develop the program, save a value in registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run But for some reason, the program did not run at start. The usual reason for this is internal, i.e. the app must itself be configured to start at boot or login. In Task Manager, under Processes tag, I could not find out the program. Does not Task Manager allow you either to / Add an app or to / Browse to any .EXE on the hard drive? -- Don Phillipson Carlsbad Springs (Ottawa, Canada) |
#4
|
|||
|
|||
Can not run at start
Try putting the program in the startup folder.
"qq" wrote in message news Hi All, I have a program which need to run at start when user login. The vender, who develop the program, save a value in registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run But for some reason, the program did not run at start. In Task Manager, under Processes tag, I could not find out the program. Any body knows why it happened? How to fix the problem? Thanks in advance. |
#5
|
|||
|
|||
Can not run at start
Try putting the program in the startup folder.
"qq" wrote in message news Hi All, I have a program which need to run at start when user login. The vender, who develop the program, save a value in registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run But for some reason, the program did not run at start. In Task Manager, under Processes tag, I could not find out the program. Any body knows why it happened? How to fix the problem? Thanks in advance. |
#6
|
|||
|
|||
Can not run at start
The usual reason for this is internal, i.e. the app must itself be
configured to start at boot or login. I will ask the vendor who develop the program about it. In Task Manager, under Processes tag, I could not find out the program. Does not Task Manager allow you either to / Add an app or to / Browse to any .EXE on the hard drive? I don't understand what you are saying? Can you explain it more? thanks. |
#7
|
|||
|
|||
Can not run at start
The usual reason for this is internal, i.e. the app must itself be
configured to start at boot or login. I will ask the vendor who develop the program about it. In Task Manager, under Processes tag, I could not find out the program. Does not Task Manager allow you either to / Add an app or to / Browse to any .EXE on the hard drive? I don't understand what you are saying? Can you explain it more? thanks. |
#8
|
|||
|
|||
Can not run at start
Try putting the program in the startup folder.
Yes, I tried put the program in the startup folder. But the program just run, then end at all. The program is a server program, it should run all the time, then, client computer can access the server computer for using scanner. |
#9
|
|||
|
|||
Can not run at start
Try putting the program in the startup folder. Yes, I tried put the program in the startup folder. But the program just run, then end at all. The program is a server program, it should run all the time, then, client computer can access the server computer for using scanner. |
#10
|
|||
|
|||
Can not run at start
qq wrote:
Hi All, I have a program which need to run at start when user login. The vender, who develop the program, save a value in registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run But for some reason, the program did not run at start. In Task Manager, under Processes tag, I could not find out the program. Any body knows why it happened? How to fix the problem? Thanks in advance. And what happens when you take the EXACT command string shown under the Run key and then try to execute it at a command prompt? If the program won't run from a command prompt, it certainly won't run from a command line specified under the Run key. Services are NOT specified by the Run key. Those are commands to load [background] programs and use the same syntax as what you yourself can enter at a command prompt. |
#11
|
|||
|
|||
Can not run at start
qq wrote:
Hi All, I have a program which need to run at start when user login. The vender, who develop the program, save a value in registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run But for some reason, the program did not run at start. In Task Manager, under Processes tag, I could not find out the program. Any body knows why it happened? How to fix the problem? Thanks in advance. And what happens when you take the EXACT command string shown under the Run key and then try to execute it at a command prompt? If the program won't run from a command prompt, it certainly won't run from a command line specified under the Run key. Services are NOT specified by the Run key. Those are commands to load [background] programs and use the same syntax as what you yourself can enter at a command prompt. |
#12
|
|||
|
|||
Can not run at start
And what happens when you take the EXACT command string shown under the
Run key and then try to execute it at a command prompt? If the program won't run from a command prompt, it certainly won't run from a command line specified under the Run key. Services are NOT specified by the Run key. Those are commands to load [background] programs and use the same syntax as what you yourself can enter at a command prompt. . Yes, I tried it. It works when I execute it at a command prompt. And the program run all the time when I run it at a command prompt and run it from Start Run. Any suggestion? |
#13
|
|||
|
|||
Can not run at start
And what happens when you take the EXACT command string shown under the
Run key and then try to execute it at a command prompt? If the program won't run from a command prompt, it certainly won't run from a command line specified under the Run key. Services are NOT specified by the Run key. Those are commands to load [background] programs and use the same syntax as what you yourself can enter at a command prompt. . Yes, I tried it. It works when I execute it at a command prompt. And the program run all the time when I run it at a command prompt and run it from Start Run. Any suggestion? |
#14
|
|||
|
|||
Can not run at start
qq wrote:
And what happens when you take the EXACT command string shown under the Run key and then try to execute it at a command prompt? If the program won't run from a command prompt, it certainly won't run from a command line specified under the Run key. Services are NOT specified by the Run key. Those are commands to load [background] programs and use the same syntax as what you yourself can enter at a command prompt. . Yes, I tried it. It works when I execute it at a command prompt. And the program run all the time when I run it at a command prompt and run it from Start Run. Any suggestion? You could alter the command to have any stdout generated by the program saved in a logfile, like: progfile progpath\loadlog.txt where progfile is the name of the program's executable file (and should include its absolute path to ensure it gets found) and progpath is the folder of wherever program got installed (so the log file gets saved in the same place although you can pick some other location if you want). The "" will append the stdout from the program into the logfile so this file will continue to increase in size. If you don't want to see a log of all loads of this program then use "" which overwrites the file when new content is captured. If the program doesn't generate any standard output for when it errors on attempting to load, this trick won't help as the log file will always be empty. Have you look in the Event Viewer to see if there is an entry showing an error for this program? Clear out all events in the Event Viewer for all categories, reboot, and then check the Event Viewer to see if there was an error recorded. With other programs getting loads, like security software (anti-virus, firewall, anti-spam, etc), it may be possible that there is too long a lag of when a program loads so that a subsequent program can no longer find the first program or whatever it might've created. Have you tried copying the command from the Run registry key, delete that registry key, and create a shortcut in your Startup folder? You can put the shortcut in either your own Startup folder or the one under All Users if you want every Windows account to load that program when the user logs in. If you don't want to pollute your Start folder with another startup program, you can schedule an event in Task Scheduler that loads the program on login. Using either the Startup folder or a scheduled task has the program load later to accomodate any dependency it may have on some other service, process, or data created by some prior program. Could be a timing issue where you have to automatically load the program but do it a bit later. Server programs that run as an NT service are NOT listed in the Run registry key or in your Startup folder. More likely this is a user-level program that runs as a background job and which listens for connections on a port. Yes, that is a server program but it is not a service in Windows. Also, many times when a program is listed in the Run registry key (and sometimes even when added as a shortcut in the Startup folder or added as a scheduled event to run on login), there is supposed to be a command-line parameter to specify that this instance is a special load of the program rather than a load of its GUI for use by the end user. Perhaps the command in the Run registry key got corrupted and a command-line parameter is missing. The manual or documentation for the program should detail if it has any command-line parameters when calling the program's executable file; however, too often developers don't tell to doc folks about parameters or they don't want their users to know about them (that is, there are some command-line parameters that may not be documented). |
#15
|
|||
|
|||
Can not run at start
qq wrote:
And what happens when you take the EXACT command string shown under the Run key and then try to execute it at a command prompt? If the program won't run from a command prompt, it certainly won't run from a command line specified under the Run key. Services are NOT specified by the Run key. Those are commands to load [background] programs and use the same syntax as what you yourself can enter at a command prompt. . Yes, I tried it. It works when I execute it at a command prompt. And the program run all the time when I run it at a command prompt and run it from Start Run. Any suggestion? You could alter the command to have any stdout generated by the program saved in a logfile, like: progfile progpath\loadlog.txt where progfile is the name of the program's executable file (and should include its absolute path to ensure it gets found) and progpath is the folder of wherever program got installed (so the log file gets saved in the same place although you can pick some other location if you want). The "" will append the stdout from the program into the logfile so this file will continue to increase in size. If you don't want to see a log of all loads of this program then use "" which overwrites the file when new content is captured. If the program doesn't generate any standard output for when it errors on attempting to load, this trick won't help as the log file will always be empty. Have you look in the Event Viewer to see if there is an entry showing an error for this program? Clear out all events in the Event Viewer for all categories, reboot, and then check the Event Viewer to see if there was an error recorded. With other programs getting loads, like security software (anti-virus, firewall, anti-spam, etc), it may be possible that there is too long a lag of when a program loads so that a subsequent program can no longer find the first program or whatever it might've created. Have you tried copying the command from the Run registry key, delete that registry key, and create a shortcut in your Startup folder? You can put the shortcut in either your own Startup folder or the one under All Users if you want every Windows account to load that program when the user logs in. If you don't want to pollute your Start folder with another startup program, you can schedule an event in Task Scheduler that loads the program on login. Using either the Startup folder or a scheduled task has the program load later to accomodate any dependency it may have on some other service, process, or data created by some prior program. Could be a timing issue where you have to automatically load the program but do it a bit later. Server programs that run as an NT service are NOT listed in the Run registry key or in your Startup folder. More likely this is a user-level program that runs as a background job and which listens for connections on a port. Yes, that is a server program but it is not a service in Windows. Also, many times when a program is listed in the Run registry key (and sometimes even when added as a shortcut in the Startup folder or added as a scheduled event to run on login), there is supposed to be a command-line parameter to specify that this instance is a special load of the program rather than a load of its GUI for use by the end user. Perhaps the command in the Run registry key got corrupted and a command-line parameter is missing. The manual or documentation for the program should detail if it has any command-line parameters when calling the program's executable file; however, too often developers don't tell to doc folks about parameters or they don't want their users to know about them (that is, there are some command-line parameters that may not be documented). |
Thread Tools | |
Display Modes | |
|
|