Ross Boylan wrote: > I have tried various settings of hogthreshold, but I can't prevent a > certain program (GrandView) from grabbing all the CPU when it runs. > Is there something I can do about this? Currently there is probably nothing to do, but you can still try playing with nice(1).
> The program is a full-screen character mode program (an outliner) from > the DOS era. It does respond to the mouse, which I suspect is the > problem (that is, the program responds to the mouse by polling > continuously). dosemu can handle mouse polling condition. But it doesn't handle (AFAIK) direct keyboard polling via port 0x60 and that seems to be a problem in most cases. > When I run it under MS Win 2K it consumes almost no CPU. There are some plans on improving the setuation during the current or next devcycle of dosemu, but you know how slowly the things are going... > By the way, I find the description in README.txt a bit confusing. It It is confusing in many places:) > says: > $_hogthreshold = (1) # 0 == all CPU power to DOSEMU > # 1 == max power for Linux > # >1 the higher, the slower DOSEMU will be The last line is probably a mistake: there are alot of places in dosemu sources with the code like this: if(++trigger>=config.hogthreshold) usleep(...); > Does this mean that 1 essentially is the same as setting the value to > infinity? AFAICS, 0 is "infinity" here. The more the value, the more CPU power dosemu eats, I think. > The discontinuity of scale is a bit surprising; based on > the description of >1 I would expect 1 means "DOSEMU runs as fast as > possible". It just means that someone who wrote this doc was not as good in Math as you are:)) - 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
