Strange behavior...
So, I'm running into an issue I've never seen before. I've re-packaged a vendor's application installation media (as I have on hundreds of previous occasions), but, for whatever reason, after installation, when I attempt to launch the program, it launches a completely different program. For example, if the program installed itself at "C:\Program Files\Microsoft\Notepad.exe," when I attempt to launch that "notepad.exe," the "C:\Program Files\Other Program\Other File.exe" runs in it's place. Any ideas of the cuff? Thank you.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
mahendraKumar
12 years ago
check your application shortcut target exe and arguments... whether it tries to invoke other applications...
Posted by:
stmasi
12 years ago
The application shortcut points to the correct executable in the correct folder. What I was trying to explain is when I double-click the executable "c:\program files\program one\app1.exe" it actually launches the executable "c:\program files\program two\app2.exe." Now, if that's not strange, I don't know what is! I've never before encountered this behavior so I don't know where to go from here. The two executables are separate and not at all related (two entirely different products), so I can't understand how this could happen. Thanks.
Posted by:
mahendraKumar
12 years ago
ok ... dont launch the exe from the shortcut created ... launch it directly from the pfiles by double clicking it ...
open task manager to find what is the exe launched ... if the exe name that you have launched is found in the taskmanger then the exe might be internally code to launch the other application.. you have to ask your vendor ...(you may also kill the process of your application exe check if application B gets closed....)
also you can use promon ,filemon to dig into the issue more....
if you want to find whether application exe A and B are dependent ... use dependency walker to find out the relations...
i hope this tips may help....
open task manager to find what is the exe launched ... if the exe name that you have launched is found in the taskmanger then the exe might be internally code to launch the other application.. you have to ask your vendor ...(you may also kill the process of your application exe check if application B gets closed....)
also you can use promon ,filemon to dig into the issue more....
if you want to find whether application exe A and B are dependent ... use dependency walker to find out the relations...
i hope this tips may help....
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.