>>>I would like to distribute my application on CD and enable the Autorun feature. I did this numerous times in VFP5 successfully, but I'm getting an error in VFP6. As per Article Q172078, I renamed the setup.exe to autorun.exe. But when I run the autorun.exe, after a few steps I get a message saying that the file 'setup.exe' cannot be opened. Of course it can't, it no longer exists, but why is the installation looking for it? I tried this with both the 'netsetup' option and the 'websetup' option and had the same problem. I've already upgraded my Setup Wizard. Anyone else do this successfully?
>>>
>>>Thanks!
>>
>>Looking at a typical AUTORUN.INF file the following lines should suffice:

>>[AutoRun]
>>open=setup.exe

>>Assuming SETUP.EXE is in the root directory of the CD. The AUTORUN.INF file also needs to be in the root directory of the CD.
>>
>>If you put all your install files in a directory on the CD, change the lines to:
>>

>>[AutoRun]
>>open=relative_directory_path_here\setup.exe

>>Just do not precede the directory path with a drive letter.
>
>
>According to the KB article, I should rename setup.exe to autorun.exe, setup.lst to autorun.lst and create a file called autorun.inf with the lines:
>
>[autorun]
>OPEN=AUTORUN.EXE
>
>This is how I did it in VFP5 and it worked great. Now I'm getting an error that it's looking for the setup.exe file. The path is correct, but the file doesn't exist because I renamed it. Why is it specifically looking for setup.exe? According to the KB article, this should work for VFP6, too.

I am not sure about the info in the KB, but I would not rename SETUP.EXE to AUTORUN.EXE. I woudl try it just as you always have. Looking through the SETUP.INF file, I see references to SETUP.EXE and not AUTORUN.EXE.