Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Memory usage & open tables
Message
From
12/09/2000 08:55:13
David Fluker
NGIT - Centers For Disease Control
Decatur, Georgia, United States
 
 
To
12/09/2000 07:49:26
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00414466
Message ID:
00415338
Views:
22
>Michael:
>Can you give me more info about NT & Fox2.x tables? We have old Clipper 5.0 tables that we still access with our DOS app. At this time, we ecommend that our customers don't run on NT, but I'd like to know if this is an issue. We have a 3rd party communication program whose owner tells us we should ONLY run on NT (hopefully, 2000 soon!).
>
>TIA

Mike- our division is an NT shop - now switching to 2000. While I have had problems running DOS and Windows 3.x apps - FoxPro and others - I've never run into a problem with the Fox 2.x files. I've heard programers at other places mention it, I've just not run into it myself.
Our main problems -
*FoxPro for DOS - conflicts with NT's NTVDM memory management and FoxPro Extended's memory manager. The trick we found that usually worked was to not allow NT to automatically configure memory.
*FoxPro for Windows and other Win 3.x apps - problems with NT's wow.exe program hanging up and hoggong processor cycles. There are several knowledgebase articles on this and we have many machines running, but not all. So far, the problem seems to have gone away with Win2000.
David.
Previous
Reply
Map
View

Click here to load this message in the networking platform