>Hi, Ed!
>
>>>
>It's too late to check for once VFP starts; you need a non-VFP component, such as a launcher, to check for and if necessary create the TMPFILES directory - VFP will attempt to use the TMPFILES directory immediately on startup.
><<
>
>But you can do this job due to a small VFP application which has a special config.fpw file without any TEMPFILES entry <vbg>!

IOW, a launcher; once TMPFILES is assigned, you need to start a new instance of VFP to reassign the TMPFILES directory. The odds are that writing a launcher in a non-VFP scripting language such as VBScript or JScript will have a significantly smaller footprint than even a 'small' VFP app, and will be less sensitive to things like getting started from a CD with the default drive also on CD. Using a non-VFP component allows you to do many things that might fail if, for example, a VFP app launched before rebooting the system if one of the running component DLLs might need updating.