On Sat, Apr 11, 2015 at 11:43 AM, Alan Bourke <[email protected]> wrote:
> On Sat, 11 Apr 2015, at 05:50 AM, Man-wai Chang wrote: >> I wanna remind everyone that FoxPro DOS can waste a lot of CPU cycles. >> You need to run some RAM resident programs to reduce CPU usage > Correct. You need to get hold of a little EXE called TameDOS and start > that before FoxPro. Otherwise the Foxpro keyboard polling will hoover up > all the CPU cycles. All true, but Kevin and I are running DOSBox on non-Windows platforms (Ubuntu and Fedora Linux respectively, I think) and TameDOS runs on Windows. Inspired by this idea, I'm trying FreeDOS on a Qemu/KVM VM. Looks like it runs around 2% when idle on an old 2.5 GHz Core2 processor. DOSBox runs around 15% on the same hardware. FreeDOS looks like fun. It comes with configs to support HIMEM, EMS and/or XMS. Unfortunately, you do have to find, download and build ethernet drivers and a TCP/IP stack before you can network. I'm not sure I can justify the time... -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CACW6n4ujCppo03ch6FioLXC-mKj9L0dSUcGA8sdyGbW5AQag=a...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
