>>>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??
>>
>>well, it's only 2GB now for tables. not sure what the limit was in 2.6, but might have been less.
>
>Thanks Dave... guess I know what I'll be doing for the remainder of the week, One of those nice long soothing reformat/reinstall & become braindead ordeals. :P Oh joy!

Roxanne,

I think someone's handing you...well, you know. If FoxPro (any version) can't see it, then I doubt if the ROM BIOS could either. Why, because in order to determine how much diskspace is available, the developer would simply call one of the interrupts (21h) for the information. In Windows 95, there's an API call for this. Further, my FPW 2.6 apps can "see" a total amount of over 2GB in total space.

I think you mentioned something about NT. Could it possibly be a problem with the user disk space allocation?

BTW, an FPW 2.6 EXE will show a linker version of 5.01 when you examine it with a Quick View from the Win95 Explorer.

HTH

George