Looks like you didn't make a keyword search first? For shame! Lots of others have asked the same question already. Don't make others do the searching until you've at least done some searching for yourself first. Now that I said that, here are some of the many threads I saw. Also, you may want to search in the FoxPro (not Visual FoxPro) forum for similar DOS-to-W2K issues they have experienced.
thread290-501606 - workstation CPU is too fast (tempfile naming fails to get unique names?)
thread290-84526 - "File already open" error (CPU too fast)
thread290-403244 - slow typing, runs better locally on workstation
thread290-184253 - slow response caused by antivirus in background
thread290-376247 - how to handle "Too many files open" error
thread290-118797 - mixing W2K with older Win98, WinMe
thread290-50114 - various issues mentioned
thread290-451431 - various issues
Windows 2000, like earlier WinNT and newer WinXP, does not really run "DOS" natively. I may be stretching it to say this, but think of it as a sort of emulation. M$ wants DOS to die, though there really are times when CLI (command line interfaces) are preferable and simpler than point and click.
Another issue in Windows 2000 is that the DOS window's property called "QuickEdit" should be unchecked so that the mouse will work in the window.
Also, Microsoft never set the default number of file handlers higher than 30 (as I recall). Sort of like selling you a car with only one door working, usable, but quite limited. So when you add or change FILES=nnn to CONFIG.NT, make it at least 50 or 80 but do not go higher than 225.
(30 default + 225 user-selectable = 255 max)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.