Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Problems with Post-Setup Executable DCom98.EXE in Setup
Message
De
14/12/1998 11:20:46
Koos Veel
Gamma Research
Aruba
 
 
À
11/12/1998 19:21:29
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00166630
Message ID:
00167217
Vues:
16
Hello Ed,

>>Well we use the setupwizard of VFP 6.0. Since InstallShield cost to much time
>> to research we decided to keep to VFP 6.0. We decided to just include the
>> DCOM98.EXE file in the setup filelist. So it get's copied to the executable
>> directory of the application.
>
>That's fine. What do you do when you discover NT running SP1 or SP2? And,
> more importantly, what if you have something to run post-setup besides
> DCOM?

Well our customers (at the moment) don't use Windows NT. But they will eventually I guess. And we never (thus far) used the post-setup. But we decided not to use the post-setup for executing DCOM98. We will do it in the executable of the application.

>You have to open a registry key before reading a value - EnableDCOM is a\
>registry value of the key "Software\Microsoft\OLE". Using the VFP reigstry
>class, you'd do something like:

Thanks. We will experiment with it!

>>Because we want to execute the DCOM98.EXE file if the return code isnt't equal
>> to 0. We use RUN /N SETUP\DCOM98.EXE /Q to execute it.
>
> This is dangerous, since the DCOM98 may force a reboot during install, and you
> definitely will have some shred .DLLs loaded at the poiunt that DCOM is
> invoked.

Correct. So having DCOM98.EXE executed in the executable isn't an option I guess.

>>Do you have another elegant solution to our problem?
>
> You don't have to write in InstallShield (I do, because I have it and know it
> pretty well, and it does a lot of setup-related things well); the Windows
> Scripting Host would be a good choice (it's free, has support for JSCRIPT and
> VBSCRIPT, and oiffers a whole lot of stuff that's useful to your VFP
> environment as well in terms of additional automation objects), or even
> something like WinBatch

Hmm that might me an option. I'll do some research for Windows Scripting Host (never heard of it before) and I'm downloading WinBatch at the moment. How would we use WinBatch and the WSH then? Call it from the executable application or?

Thanks in advance!

Christian
Using the account of Koos Veel
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform