On Wed, 01 Nov 2017 23:06:44 +0100, Andreas K. Foerster wrote: > Sorry if I sounded harsh, I didn't mean it that way.
Don't worry :) > But I was happy that I found a solution that worked well for me, and > then you say it's bad. That's a bummer indeed. > And INT 28 doesn't solve the problem of heavy > load for me. As I read it's just an IRET by default. True, if "by default" you mean "under raw DOS without any configuration". But in such configuration, DOS itself will spike your CPU to 100%, too. That's why POWER.EXE (MS-DOS) and FDAPM (FreeDOS) came around. I don't know about DR-DOS, OpenDOS, PTS-DOS and friends, but I suspect they have similar power management drivers as well. You just need to a) have such driver loaded and b) let it know when your program is idle. > With DOSBox on GNU/Linux it works fine. (AFAIK that's not a virtual > machine, but an emulator.) IIRC DOSBox had some issues with being "green" in the past, so I wonder whether it's a good reference point. Did you try DOSEmu? Just launched DOSBox (0.74) here - sitting in an idle shell while waiting for input, it consumes 15% of my CPU... After I changed its configuration to "core=dynamic" it dropped to ~6%. Mateusz -- FreeDOS is present on the USENET, too! alt.os.free-dos ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
