Agreed: with 2 drives, and not using VPM, and not supporting users using tools that depend on location, installing on other-than-c is a good idea.

>was takling about tmpfiles - the other ones were not specified ;-)
>Benefits: less defragmentation on C:, Speed if on SSD
>(17' has SSD in second bay, thinking about exchanging DVD with SSD in 15')
>The freedom to just format a play partition and start afresh:
>makes sense even if housed on same device. Less danger to the OS...
>
>>Because typically there's one drive on a developer machine, so what's the benefit of being on the d: drive or whatever (although my next machine will have an SSD for OS and temp files, and a hybrid for the rest)? That's especially the case when dealing with a laptop.
>>
>>Plus, when working with ProMatrix, it always installs itself in c:\vpme9.
>>
>>Plus, when working with VSS and then SourceSafe and then Vault, life is a lot easier if everyone uses the same directories for their projects, which dictates the lowest common denominator, which argues for c:.
>>
>>>>Here are 3 lines I have in my config.fpw, which is in the default directory specified by the shortcut (c:\vfp9lib):
>>>>
>>>>tmpfiles=c:\temp\vfptemp
>>>>DEFAULT=\vfp9lib
>>>>RESOURCE=\vfp9lib\foxuser
>>>
>>>why on C: ? SSD ?