Hi,
I am currently working on Epson APD 4.7.The source is an exe calling msi.Since the msi couldnt be packaged we are going with the exe installation.When we install the app with /s it is going for force reboot.I tried REBOOT=R,Reallysuppress,No,/norestart,/noreboot options.Nothing is working out.So could anyone help me to suppress the forced reboot.

Thanks,
snkchn.
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
have you tried using setup.exe /v to suppress the reboot
Answered 10/07/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
Since the msi couldnt be packaged Why not? I've yet to encounter such a thing.
Answered 10/07/2009 by: VBScab
Red Belt

Please log in to comment
0
Thanks./v is not working.The command i used is setup.exe /s /v /f1file.ini
Answered 10/07/2009 by: snkchn
Senior Yellow Belt

Please log in to comment
0
can you not create an mst instead if you have an msi already
Answered 10/07/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
The problem is that this exe calls the msi only finally and the msi which is available in Installer folder is not the exact one i need.So no other way i have to use this exe only.
Answered 10/07/2009 by: snkchn
Senior Yellow Belt

Please log in to comment
0
in that case extract the msi first

install msi on a clean worksation

run your setup.exe capture it

then create mst for the extracted msi

run your first captured msi as a pre req

then install base msi and mst
Answered 10/07/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
the extracted msi doesnot installs
Answered 10/07/2009 by: snkchn
Senior Yellow Belt

Please log in to comment
0
the extracted msi doesnot installs

Does it start installing and stop with an error, or does it not start at all?

You could perhaps check the MSI for Install Conditions or Custom Actions that force it to be called through a setup.exe. You could then try disabling these in an MST and see if you have more luck. also look into the ISSETUPDRIVEN property

PJ
Answered 10/07/2009 by: pjgeutjens
Red Belt

Please log in to comment
0
You may want to give us some links for DL of that driver so we can actually test it if its available.

YOu may want to check out this Installshield parameters to pass some arguments from setup.exe to Windows Installer. http://itninja.com/blog/view/installshield-setup-parameters

For me you can try this.. setup.exe /s /v"REBOOT=\"ReallySuppress\" REBOOTYESNO=NO REBOOTPROMPT=S /NORESTART"
Looks like an overkill but always works for me.
Answered 10/08/2009 by: dj_xest
Fifth Degree Black Belt

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