Magtek ImageSafe

[scizzat]

Hey there, all. It’s been a while since I have posted. Have sort of a weird scenario. I’m helping someone put an application together. Everything is good for the most part except the setup.exe for Magtek ImageSafe. The installer can be found at Device Drivers and Agent Installers - InstaMed Developer Portal (MagTek ImageSafe (v112)).

You’ll end up downloading an exe which is a self-extractor and then you’re presented with more files and folders. You eventually end up with a setup.exe and and MSI file. If you try running the MSI separately, it tells you to run the setup.exe file first. If we run a setup.exe /? against the installer, we get the following parameters.

I’ve tried seeing if I could mess with the MSI in Orca with no luck. I ended up stumbling upon this by mistake I suppose. I started to create a new PSADT file and put the appropriate files in the ‘Files’ folder. For the heck of it, I ran the PSADT script and I noticed in the logs it detected a Zero-Config MSI (the one that will not run without running setup.exe first), and it installed with no issues. When attempting to run the other script (the complete one with the other apps that need to be installed), the Magtek ImageSafe application doesn’t get detected and will not install.

I’ve exhausted multiple command lines to try and get the setup.exe to install silently but it just won’t (unless you do the scenario where you just leave the PSADT script untouched). My coworker is about to tell the requestor they’ll just have to have one part of the install that requires interaction but I’m trying to prevent that.

Any ideas would be greatly appreciated! Thanks in advance!

[bohnanza22]

Have you tried:

Start-ADTProcess -FilePath "$($adtSession.DirFiles)\setup.exe" -ArgumentList '/S /v/qn' -WindowStyle 'Hidden'

in the install section of Invoke-AppDeployToolkit.ps1?

Placing the .exe and any other associated files, in the the Files folder of your PSADT package?

No space between /v and /qn. the .exe looks like it passes anything past the /v in the command to the .MSI. Some InstallShield executables do this.

Depending on the InstallShield deployment you may need to create an answer (.iss) file. Do a search on how to create an InstallShield answer file you will find some instructions.

[scizzat]

@bohnanza22

how to create an InstallShield answer file

Hey Willis,

Thanks for the response. Yes, I tried the same command line that you provided, except in the 3.10 version of PSADT, not 4+. Tried multiple variations and just wouldn’t work. Did you happen to download the file yourself and try it on your machine? I’ll look into the answer file after I hit reply on this post.

[scizzat]

Thank you very much. Creating the iss file solved my issue!

[bohnanza22]

No I didn’t get a chance to download the file. But… I have packaged a bunch of InstallShield based installers here. I’m not a fan of InstallShield but it’s the things we hate that we remember the most

I’m glad it worked for you.

[scizzat]

We’re gluttons for punishment. Remember the bad more than the good, lol. Thanks again!