>>The Setup Wizard probably did not get it right, especially if you had to send a shared .dll to \windows\system.
>
>That might explain why the user has to close Explorer in order for the setup to copy the MSVCRT.DLL file.
Bingo. There are other files, as well.
>
>>I have no idea how InstallShield Express would handle this. I am using Professional, and there's a simple function call that handles this. I do not either like or trust automated systems - I want to write the code myself - more control, you know :).
>
>The express version is 3 times less than the professional version. I am just trying to see if I really need the professional version or not.
You need the additional power. Don't try to save the money.
>>The following file has two versions - one for 95, one for NT.
>>\windows\system\ctl3d32.dll
>
>This is where it gets complicated. :) Can you tell me in InstallShield you specify which file goes for Windows '95 and which one goes for NT? I will check to see if in the express version, I can do that as well.
>
InstallShield uses code files that look remarkably like C (a real language, folks...). It is in that code you call the function that returns the operating system version, and the you act based on that information.
>>Add to this any files needed by your .ocx files. Some of these files are considered shared. Some are self-registering.
>
>This was also another concern. I have an OCX that I have found that I only have to check ActiveX in the setup wizard and it was ok for the application to be able to use the OCX. It is possible VFP setup wizard auto register when we check ActiveX? I remember having had problem with that with InstallShield because I wasn't sure if it was doing that automacially or not when it sees an OCX extension. In the express version, I haven't found any place to specify that that file was an ActiveX file.
There is a specific function in InstallShield that copies and registers self-registering files.
>Are those what you mentioned yesterday? If I don't do anything for this part, this mean after the setup, the user won't be able to start the EXE. Do I really need to modify the registry? If yes, what is the minimum I have to do?
>
>That part is really the one which make me afraid. I know of few people which uses InstallShield for their setup and never heard of that. That's why I am wondering if modifying the registry to make VFP EXE runs is really a must.
To be complete, you *must* modify the Registry. It is central to a proper 32-bit environment installation. That said, it also opens the doors to all sorts of fun you can have in the application later.
You take shortcuts at your own risks.
----------------
David M. Stowell
D. M. Stowell Consulting
