Forums

by Silver Springs ... >> Wed, 1 Sep 1999 1:24:00 GMT

Hi
I have bundled my run-time JADE application into a self-extracting SETUP routine using InstallShield Express and it all works a treat except for the following.

I create all the files and then write them to a CD. Then when I install from the CD InstallShield throws up this dialogue stating :

The following files failed to self-register : MFC42D.DLL"

You can press OK to this and everything seems to work OK -- but how does one get passed this conflict InstallShield has in trying to register MFC42D.DLL (which is a required DLL in the BIN directory) ??


SilverSprings ............................... silversprings@easyliving.com

by Geoff McIlraith >> Tue, 7 Sep 1999 1:19:11 GMT

I create all the files and then write them to a CD. Then when I install from the CD InstallShield throws up this dialogue stating :

The following files failed to self-register : MFC42D.DLL"

I haven't used InstallShield Express (just InstallShield Pro), but a couple of possibilities occur....

1) MFC42D relies on MSVCRTD.DLL. Have you installed this?
2) Is the file already in use, and hence the copy is not able to complete? In InstallShield there is a "batch mode" that handles this situation by insisting on a reboot of the machine, and copying the DLL's in as the system boots up. I think that this forces you to do the registration yourself once the system has rebooted (presumably by putting a call to you install program in the RunOnce entry on the registry).

One thing that wasn't clear to me in you e-mail, was whether installing from HardDisk behaves differently to CD. If this is the case, then it would be worth making sure the read-only settings of the DLLs isn't making a difference.

You can press OK to this and everything seems to work OK -- but how does one get passed this conflict InstallShield has in trying to register MFC42D.DLL (which is a required DLL in the BIN directory) ??

I think in 5.0 this isn't required any more (just MFC42.DLL)

Just a thought. We put MFC42.DLL in the bin directory, to allow people to propagate JADE systems by copying the bin directory. Strictly speaking, this DLL should be in the system32 directory. Because of this, it may be in use from the system32 directory, and not allowing you to register the one in the JADE directory.
I don't think you SHOULD register the one in the JADE bin directory, because then other applications will look for it here.

Hope these wild stabs in the dark help,

Geoff

by Silver Springs ... >> Thu, 9 Sep 1999 23:33:42 GMT

Thanxx Geoff (of North & South magazine fame),

I got the problem both installing from hard disk and CD-ROM. However, I discovered an option in IS Express that allowed me to specify whether or not I wanted IS Express to register the DLL or not -- so I unchecked the box on this one.

I then found the error dialogue disappeared and it seems to have no ill effect on the installed run-time application -- so all's well on that front.

I must investigate IS Pro -- and the added advantages that gives you (which must be substantial given the fact that it's three times the price). IS Express suits my needs right now for producing demo CD's of JADE applications.

Cheers
Alan_________________