Hopefully this'll be a fairly easy question for someone to answer, but I've looked all over the interent and can't find an answer...
Using InstallShield ver5 repackager, does anyone know what happens in the background once a snapshot is done? I know that doesn't really make sense, but once the first snapshot has been taken, the app installed and configured the machine rebooted and you run repackager again, what does it reference so that it knows it's already done a snapshot?
I'm assuming something's written on the client machine somewhere, maybe a registry key, maybe a file, but I just can't find out what or where...
Any help would be much appreciated as this is really bugging me.

0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I believe the initial snapshot is stored in folder C:\Config.Repackager. If it exists, and contains data, then it knows an initial shot has been taken. Could be wrong, but that's what it looks like to me.
Answered 07/23/2004 by: rogebil
Senior Yellow Belt

Please log in to comment
I have just started using Installshield for snapshots and don't know alot about it yet. But have used other tools. I always try to supress the reboot when using snapshot style tools to record an install. You might be able to do your install via command line. I have used this parameter for msi installs before, REBOOT=ReallySuppress.
Answered 07/24/2004 by: gscotte
Senior Yellow Belt

Please log in to comment
Wise's SetupCapture kicks ass (in my humble opinion).

If you get a chance, check out Wise Package Studio or the Wise Installation System.

Again, in my opinion, MUCH easier to use than InstallShield.
Answered 08/02/2004 by: sean_c_roberts
Senior Purple Belt

Please log in to comment