>>Ok, I now have a major problem. User tries to install the application and she receives error messages. I suggested her to copy installation directory to her local drive and run the setup.exe, but it gives her the error...
>>
>>I'm going to try to run the installation from disks myself (I tried to run it from the distribution directory before and it worked fine). Can I use files from another directory while building Setup? May be it was the problem?
>
>I placed all the necessary file is what's called the Images directory. Never really had a problem with getting errors during installation.
>
>Try to test the setup on a "virgin" machine. IOW, one that's never had VFP installed. Without knowing what the error was, I can't possibly give any sort of answer.
>

All machines here have VFP installed. Anyway, I placed icon and makeshortcut.exe files into "Image" directory, then tried diskettes on two machines (with VFP installed), they both worked fine.

I changed MakeShortCut to put "" around the work dir, but it still uses short name. I didn't notice any immediate consequences in my quick tests.

>>>>George,
>>>>
>>>>Sorry to bother you again. I created MakeShortcut.exe using the following code:
>>>< snip >
>>>>It does its job fine, however I noticed, that Start In directory is shown as C:\DATAEN~1
>>>>
>>>>Do you know, why is what? It works anyway...
>>>
>>>It's simply using the short path name. If the original path is an LFN, and it isn't surrounded by quotes, I'm guessing that Windows is making the translation. This isn't an area that I've tested with the DLL, however. Using the short path isn't all that bad. I know that in the case of some versions of IIS, you can't use an LFN.