>>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
>
>Well somebody's trying to hand me something alright. OK.. so it is definitely 2.6, I'm sitting here looking at the directory structure and I see like 150 *.app files, the foxw2600.esl, and another 100+ dbf files. What a lovely app this is! And my tech support person is swearing there is swearing there's no problem with user disk space allocation. (yes I made him check but I dont know what he checked) I'm now wondering whether I give in and reformat the server with less than 1 GB partiitons or do I tackle all these *.app with a decompiler I have somewhere and try and fix it myself.
>
>There's some kinda of deadline og the 15th of each month for using this app to generate a report. Tomorrow's the 15th (groans) anybody got a virtual beer?

If I were you (and right now I'm glad I'm not), before I went and did the partition and reformat thing, I'd pull the app onto a stand alone machine and make sure that it would work. Might want to check on one that had more than a gig too.

Not enough space on the local drive maybe for temp files, etc.?

If I had a virtual beer, it would be yours. And if the problem is that FPW can't see beyond a gig, I'll eat my virtual hat. :-).

George