>Boy I tell ya, just when you thought you seen it all, something like this crosses my desk:
>
>Somewhere in my company their using a FPW app made by AT&T called Billing Edge. Its a desktop analysis tool and I cant tell if its 2.5 or 2.6 but here's the deal... This app uses tons of call records that get imported each day. Now theres documentation out the whazoo on how to manage swap file and temp files so as to not max out disk space, none of which is helping me.
>
>We are getting custom error messages from the app that disk space is low and it refuses to do anything. So we added a new 2 GB harddrive to the NT 4.0 Server running this AT&T package and reinstalled it, but it didnt help. App still believes its low on disk space.
>
>I did the usual settings in CONFIG.FPW to specify where temp files and sortwork goes to get that stuff on the new drive with lots of space. I've stripped down unnecesary files, forced the swap file to be out of the way, etc. App still insists we be low on disk space, yet I have like a total of 2.5 GB available. In a standard FPW 2.6 session I see SYS(2020) gives me just over a GB no matter which drive I'm on.
>
>I called the AT&T Tech Support and they tell me matter of factly that its a limitation of FoxPro, that FPW cant see a disk any larger than 1.x (so mad forgot what the x was). Is this right? Older FoxPro cant see the full space on the new bigger drives? How come I never tripped on this before? I cant believe it... what ever happened to 4GB max on data? If this is the case then I guess all I can do is strip the server down completely and partition it up like real estate and set the defualt path to multiple drive letters??

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