Hi!

Does anyone have any idea where I can find a Monitoring Tools, such FileMon from SysInternals.com, where I can see what parameters a exe-file is launched with. When I install the the program without the "launch.exe" it just says "Use launch.exe to install this application."

I guess the application is lauched with some parameters, but I can´t find anything in the MSI-file.

Thanks!

/Jonas
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
why not try filemon and/or regmon?
launch the EXE and let them capture.
save the log file, open in excel. Data, sort, sort on result column. Look for Access denied, file not found, no such path, etc. and see if you can get the file it's looking for.

Also, try admin options, i.e. launch.exe /a or setup.exe /a will sometimes extract the files you need to a directory of your choice so you can look at and control the files.
Answered 12/22/2004 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Thanks for your reply.
The thing is that I don´t get any results like that in FileMon.
I can see that it starts the applications, but I can´t see what parameters that are used. I wanna know the parameters so I can make individual packages for each part of the applications, instead of making a huge package containing all of them.
The individual applications are already in MSI-format, but says it needs to be launched from "launch.exe".
/Jonas
Answered 12/22/2004 by: jonasm
Blue Belt

Please log in to comment
0
Well, filemon probably wouldn't give you the argument directly, you'd probably get some other type of error. but I see what you're saying.

Look for the property ISSETUPDRIVEN within the MSI itself. Changing that will sometimes work.

Sometimes installshield packages require installshield already on the machine. in that case you can probably resolve it by running isscript.msi (or some similar name, usually included with the installation)

BTW, I think using separate Features and Conditions, rather than building separate packages, is the way to go on something like this.

More details might help: what MSI tool are you using, what app is it, etc. Maybe somebody has already done this app - look on this site for the Packages section.


ORIGINAL: jonasm

Thanks for your reply.
The thing is that I don´t get any results like that in FileMon.
I can see that it starts the applications, but I can´t see what parameters that are used. I wanna know the parameters so I can make individual packages for each part of the applications, instead of making a huge package containing all of them.
The individual applications are already in MSI-format, but says it needs to be launched from "launch.exe".
/Jonas
Answered 12/22/2004 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
2
Hi Jonasm,

Just use another of Sysinternals tools, procexp - Process Explorer. Simply launch Process Explorer, Run whatever process you want to find the command line for, then double click it in Process Explorer and it'll tell you.

Simple really. I did ask them for a tool that queried an executable to show all available command line options but they said this was impossible *sigh*

Hope that helps

Paul
Answered 12/22/2004 by: plangton
Second Degree Blue Belt

Please log in to comment
0
Thank you Paul!

That was exactly what I was looking for!

My problem is solved!

Merry X-mas to all of you!

/Jonas

ORIGINAL: plangton

Hi Jonasm,

Just use another of Sysinternals tools, procexp - Process Explorer. Simply launch Process Explorer, Run whatever process you want to find the command line for, then double click it in Process Explorer and it'll tell you.

Simple really. I did ask them for a tool that queried an executable to show all available command line options but they said this was impossible *sigh*

Hope that helps

Paul
Answered 12/23/2004 by: jonasm
Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity