>>>Is the new drive formatted as NTFS or a FAT partition?
>>>Could the application be ignoring config.fpw and defaulting inside it to the C drive windows\temp or c:\temp, so if you added a
>>>new drive it would not use it?
>>>
>>>Just some thoughts...
>>
>>Good thoughts.... Its NTFS alright. And I can tell the apps using the config.fpw because I keep playing with the default drive setting, and when I launch the app the first thing it does is prompt to pick a "day" which is a table of call records, and the open dialog is coinciding with where I'm setting the default drive in config.fpw.
>>
>>But here's something even stranger, on this same machine I opened up a regular FPW 2.6 session and open every big table I have (used like 30+ work areas)and cant get a disk space error for the life of me. Any other ideas before I give and setup multiple partitions?
>
>My guess is that if the other foxpro 2.6 app opened ok and used the NTFS drive then that may not be the problem.
>Could the AT&T app have compiled a config.fpw in their executable that the line 'TMPFILES =' is frozen to be looking at a drive with
>space insufficient to run the system? How much space does the drive holding the application have on it now? Is it on the C drive?

It might be the case. Run a short test to identify whether config.fpw was included in EXE: write your own Config.fpw with Title=... line, and see what's happened with app title.