>>>>George,
>>>>
>>>>What do you put in Post-Setup executable? I'm using Setup Wizard and can not yet figure out, how to create a Shortcut link. User can change the default location of my exe during installation...
>>>>
>>>>Could you please give me instructions?
>>>>
>>>>Thanks in advance.
>>>
>>>Nadya,
>>>
>>>A post-setup executable in 6.0 and before is just like any other executable. FWIW, here's how I did mine.
>>>
>>>In order to check where the user installed the executable, I used SYS(16, 1), in the post-setup and wrote a configuration file. I used the registry class to check to make sure that DCOM95 was installed, from the information Ed Rauh provided in his FAQ. If it wasn't (we were running a lot of Win95B boxes at the time), that was installed. I also used to to check if the WSH was installed (via oReg.IsKey('vbscript.regexp')) if not, it installed that too. I also used my lnkfiles.dll to create the shortcuts. Finally, I used something similar to the download that John Koziol and I put together to create a VBScript file to start the program, and the dll to point to the proper icon.
>>>
>>>I'd say that 90%+ of the work that was done, was from existing code or methodology that I've either posted here, or at VFUG.
>>
>>Could post-setup executable be a prg or it should be exe? Could it be VFP exe?
>
>It's a VFP exe.
>
>>I've downloaded your class already, so I'm going to try tomorrow...
>>
>>This
GenLoader - a WSH Loader Script Wizard File #
9889 also should help a lot.
>
>That's the one John and I worked on.
Thanks, George. I made a MakeShortcut exe (post-executable) using your DLL and everything is fine now.
Thanks again.
If it's not broken, fix it until it is.
My Blog