Setup Tosses to Desktop after half second

[cduckett]

We have had a lot of success running our installation program built with Setup Factory, but recently have run across some strange behavior. On a Dell Dimension L600r with Windows 98 (ver 4.10.2222, upgraded from Windows95) the app runs for 1/2 a second then terminates, tossing the user back to the desktop. We've installed both DCOM95, DCOM98, as well as MDAC, turned off other programs (even virus-scan), but still no go. Because we haven't seen (or heard) of this behavior on other systems we're rather stumped. Do you have an idea what might be causing the setup program to bail to the desktop after half a second, and what we might do to fix it? All in all, we have been extremely satisified with the product. This is more a developer's curiosity (and tenacity) working here than any real concern.

[Mark]

Hi,

This definitely sounds like there is an incorrect version of RICHED32.DLL installed on the Windows 98 system.

Please see: http://support.microsoft.com/support.../Q218/8/38.ASP for more information on this problem. The Microsoft Knowledge Base article has information on how users should solve this problem; it involves extracting riched32.dll from the CAB files on the original WIN CD.

If you are distributing RICHED32.DLL please see: http://support.microsoft.com/support.../Q197/5/80.asp for more information on distributing this dll.

mark.

[xFX]

We have had this same problem with several of the products we develop.

It can happen under Windows 2000, Me, 9x... and I don't think it has anything to do with the files we're distributing as the setup bearly makes it to the "welcome" screen and then shutsdown itself.

Any ideas Mark?

[This message has been edited by xFX (edited 07-23-2001).]

[Mark]

Hi,

Those are the exact symptoms of an incorrect version of riched32.dll being installed on the system. Are you distributing riched32.dll? Or have you in the past?

I would read the two Microsoft articles and see if they shed any light on your problems.

mark.

[xFX]

Actually I have finally found the problem.

It has nothing to do with the Rich Edit Control.

The program I'm installing is an application that sits in the tray area… so, since you cannot detect if a program is running with SF and my program must be closed when running the setup I added an option to my program that when launched with the /close command line it started a new instance of the program, detected any previous instances and closed them all.

The program (with the /close parameter) was being launched when the setup created with SF was launched.

Well, it happens that under Windows 9x/Me (not always though) this would crash SF.

So, I had to remove the shell operation of running my program and change it by an ugly screen at the startup of the setup alerting the user that they must close the program before installing a new version.