>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.

My guess too... gotta be something funky in this app

>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?

There is no executable here, just 130 app files. And I'm positive the config.fpw I'm playing with is affecting the app's behavior. The app is now on back on the new "C" drive which has 3.16 GB available. (I was wrong in earlier msg., seems I hace two 4 GB drives in this machine). Earlier I had it on the new "E" drive with 2.65 GB available. (is humming twilight zone theme now)