Help repackage a legacy app! (newbie)
Hi people,
I am very new to AdminStudio and packaging in general. My company uses SCCM to deploy software. I am trying to package an old piece of software call Webster's Unabridged Dictionary 3.0. The software uses a setup.exe to install, but does not appear to support any of the normal InstallShield switches, like /s for silent.
So I tried using the AdminStudio repackaging wizard in Installation Monitoring mode to capture the installation. The capture goes OK and creates the MSI. I am then able to install the program using the MSI, but when I try to launch it, I get an error "Failed to load the engine DLL!".
It appears to me that the MSI is not registering some DLL or copying it to the correct place.
Can anybody offer any advice? AdminStudio tips? Or maybe some other way to make the setup.exe run silent?
Thanks!
I am very new to AdminStudio and packaging in general. My company uses SCCM to deploy software. I am trying to package an old piece of software call Webster's Unabridged Dictionary 3.0. The software uses a setup.exe to install, but does not appear to support any of the normal InstallShield switches, like /s for silent.
So I tried using the AdminStudio repackaging wizard in Installation Monitoring mode to capture the installation. The capture goes OK and creates the MSI. I am then able to install the program using the MSI, but when I try to launch it, I get an error "Failed to load the engine DLL!".
It appears to me that the MSI is not registering some DLL or copying it to the correct place.
Can anybody offer any advice? AdminStudio tips? Or maybe some other way to make the setup.exe run silent?
Thanks!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
pjgeutjens
13 years ago
Chris,
you might want to try a snapshot capture (snapshot before - install -snapshot after). This might well contain alot more (dll's) than your InstallMonitor capure, and if give you a clue as to what's missing.
What you can also do is try including your application's first startup in your capture to include any on-first-startup operations.
A final thing you can do is run ProcMon in the background when you start your (packaged) app, this should point you to what's missing.
PJ
you might want to try a snapshot capture (snapshot before - install -snapshot after). This might well contain alot more (dll's) than your InstallMonitor capure, and if give you a clue as to what's missing.
What you can also do is try including your application's first startup in your capture to include any on-first-startup operations.
A final thing you can do is run ProcMon in the background when you start your (packaged) app, this should point you to what's missing.
PJ
Posted by:
aogilmor
13 years ago
sometimes those old apps will have a setup.lst and if you're lucky even a cab file with all the app files, that way you can just add files to a blank project/MSI and not worry about all that setup capture and snapshot cruft.
Posted by:
turbokitty
13 years ago
You could also try "multiple snapshot" mode. I don't find "installation monitoring" mode works very well, especially on old or obscure installers.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
