/build/static/layout/Breadcrumb_cap_w.png

Epson Advanced Printer Driver 4.0 Reboot Isuue

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.
Asked 14 years ago 2969 views
0 Comments   [ + ] Show comments

Answers (9)

Posted by: cygan 14 years ago
Fifth Degree Brown Belt
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
Posted by: snkchn 14 years ago
Senior Yellow Belt
0
the extracted msi doesnot installs
Posted by: pjgeutjens 14 years ago
Red Belt
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
Posted by: dj_xest 14 years ago
5th Degree Black Belt
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.
Posted by: cygan 14 years ago
Fifth Degree Brown Belt
0
have you tried using setup.exe /v to suppress the reboot
Posted by: anonymous_9363 14 years ago
Red Belt
0
Since the msi couldnt be packaged Why not? I've yet to encounter such a thing.
Posted by: snkchn 14 years ago
Senior Yellow Belt
0
Thanks./v is not working.The command i used is setup.exe /s /v /f1file.ini
Posted by: cygan 14 years ago
Fifth Degree Brown Belt
0
can you not create an mst instead if you have an msi already
Posted by: snkchn 14 years ago
Senior Yellow Belt
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ