>Sorry, Ed, correction to the above - I got confused with the VFP version we run simultaneously on the same machines.
>
>The actual shortcut command line is
>
>NetPath1\FOXPROX.EXE NetPath2\StartPrg.prg -CNetPath3\Config.FP
>
>I can't say for absolute certain, but I believe the Starts In folder is what it defaults to when you set up the shortcut using the wizard, i.e. NetPath1.
>

I'd bet on it not being set, and therfore defaulting to the desktop. I'd also guess that the config designator is not being processed, either, especially if the paths are stored as relative paths.

My preference for FPDOS is to use the environment variable FOXPROCFG to point to the station's correct CONFIG file. The file does noy havr to be named CONFIG.FP.

Typpically, I have the following in each workstation's AUTOEXEC.BAT:

SET FOXPROCFG = C:\FOXDOS\CONFIG.identifier

Which points to the config for that and only that workstation; a FPDOS executable or app launched with the runtime will take the value from th file named in the environment variable in preference to anything except a file named CONFIG.FP in the Starts In directory.

>>Hi Ed,
>>
>>The Starts In folder is a folder on C: directly off the root - C:\LABT_VFP.
>>
>>>>The .EXE (actually an .FXP run using actual FPDOS) is started with a desktop shortcut. The actual programs and data, and FPD itself are all on separate remote server folders.
>>>>
>>>
>>>What's the Starts In directory of the shortcut?
>>>
>>>>I understand how the desktop works; its folder most definitely is NOT the root of C:, hence my question...
>>>>
>>>>>My first thought is...
>>>>>
>>>>>Did you copy the shortcut to the EXE onto the desktop or did you copy the EXE onto the desktop? The desktop is really just a folder in the file system.
>>>>>
>>>>>>A client site is running an FPD2.6 app under 95 & NT. The app is started with a -CPath\Config.FP command line switch. The specified CONFIG.FP includes the line TMPFILES=C:\. For some reason, these temp files appear on the desktop while the app is running. They disappear after a normal shutdown but are left there if the app crashes. Can quickly lead to a very messy desktop.
>>>>>>
>>>>>>Any ideas why these files are showing up on the desktop, and on how to prevent this from happening?