The same thing happens to my application, only that I get around 50% cpu usage. Here I have access to the wait loop: I check Keyboard (bios call), mouse, timers, event-queue and start again. What should I do to stop using so much cpu?
I'm sending a copy to the dosemu list, so we can have more eyeballs on the issue.
I have noticed that, just as it happens with Clipper, this usage is only idle time and that it falls as soon as someone start using cpu...
Yes, I've seen that behavior in my machine. As I told you, it was fixed with the patch I posted.
(jeff you can find it in http://gnuservers.com.ar/~maxy/clipper/)
I don't if this would help you, but in one of the programs I've another patch, which is a source level patch. This was supposed to recover the idle calls for the system, but it didn't do any difference.
So if you want to give it a try, I've just uploaded them in: http://gnuservers.com.ar/~maxy/clipper/nflib.zip http://gnuservers.com.ar/~maxy/clipper/nfpatch.zip
I hope you remember how to put the files in the correct place, because I don't. :)
You also have to add a line in the beginning of you program, something like:
FT_OnIdle({||FT_IAmIdle(30,.T.)})I have $_hogthreshold = (1),
Same here.
Mandrake linux 10.0, Dosemu 1.2.1.0 and FreeDOS 2035 (tom).
Debian sarge, dosemu 1.2.1 and freedos b8p.
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.10 - Release Date: 10/01/05
- To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
