Hola Stas Sergeev! El 09/03/2004 a las 23:16 escribiste: > >I'm trying to run a clipper program inside dosemu. It runs ok, but it > >eats all the CPU cycles when it's idle. > You haven't specified your dosemu version.
Now I'm using dosemu 1.2.0 and 1.2.1, previous versions do the same. > >I've already tried changing the hogthreshold value, with no changes in > >the result. > You must keep that value to 1 - that's > the most optimistic one. I have it set at 1. > >I've been told this is a known problem, > Problem of clipper I presume? If it > just runs in a busy loop while idle, > dosemu can't really help. Yes, that dosemu doesn't detect the clipper idle calls. > >but I'm hoping it can be fixed > >in some way. > You can assign a lower priority level > to dosemu process, see nice/renice > commands. That will help as to not > crawling the system any more. It still eats the cpu, with nice -n 19, but now the 60% is marked as nice. > You can also try the patches from here: > https://sourceforge.net/tracker/index.php?func=detail&aid=716137&group_id=49784&atid=457450 > They release the CPU cycles by making > dosemu slower, which is perhaps also > not what you really want. This particular application doesn't have an speed requirement. So, it may be solution, although not a general one. > The real solution (if it exists) can > be found if you trace your program with > dosdebug, see what it really does when > idle, and think about adding the > appropriate heuristic to dosemu to catch > that case (but it already catches most > of the common "idling" cases). I up to it now. I'm trying to understand the freedos idle. -- "UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." -- (Dennis Ritchie) Saludos /\/\ /\ >< `/ - 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
