setup corrupting registry?

[SpaceStationAlpha]

I have a client who believes that a setup that I built with SUF 5.0.1.5 may have corrupted his Windows 2000 registry. He says that the setup hung while displaying "Updating System". The registry apparently was corrupted, but I'm not sure how to determine whether the setup caused the corruption. The same setup has been used successfully on several other client systems. Has anyone ever experienced anything like this?

[Mark]

Re: setup corrupting registry?

Hi,

There is a newer version of Setup Factory 5.0 available: ( http://www.indigorose.com/setup5/update.html )

I do not think that your installation corrupted your user's registry; perhaps his registry was already corrupted? I have never heard of this happening to anyone else.

mark.

[SpaceStationAlpha]

Re: setup corrupting registry?

Thanks for your reply. It seems to me that the existence of a new version is irrelevant to my situation. I do have 5.0.1.6 as well as SUF 6. 5.0.1.5 was the latest release of SUF 5, in which I originally developed the setup, at the time I sent the setup to the client. What am I going to tell him, you're wrong, the setup can't have had anything to do with your problem, but here, try this new version anyway?

[Brett]

Re: setup corrupting registry?

The Setup Factory install runtime does absolutely nothing to the Registry on its own except to create the regsitry entry to register the uninstall program for your software (if you told it to create an uninstall). The only way other that Setup Factory touches the Registry is if you explicitly tell it to through actions, etc.

In all of our years selling Setup Factory, we have never had a valid case of the Setup Factory runtime itself doing any damage to a user's system, unless of course the maker of the setup told it to (i.e. Delete C:\*.*)

So unless you did something to the setup to make it adversely affect the Registry, you can be confident that the corruption was coincidental.

- Brett

[SpaceStationAlpha]

Re: setup corrupting registry?

Thank you, that is great to hear, and fits with what I believed. Is it reasonable to expect that if the setup writes only one or two simple registry values, using registry keys for my firm's product defined in the usual manner, and the same or very similar setup has caused no difficulty in hundreds of other installations, that the setup did not adversely affect the registry? What if the CD-ROM were somehow damaged slightly, causing the setup to hang while atttempting these normally innocuous registry writes -- is that by some stretch of imagination a potential cause?