On Mon, 16 Dec 2002, Jan Willem Stumpel wrote:
> OK.. used the new dosemu.conf (everything commented out), set
> hdimage to "dos" to make it boot on my system, then only changed
> hogthreshold. Tried it (1.1.3.9) with
>
> hogthreshold = 0 --- 99 % CPU
> hogthreshold = 1 --- quiet behaviour
= 1 is the default. This is what dosemu.conf mentions.
> hogthreshold = 800 --- 99 % CPU
> hogthreshold commented out altogether --- quiet behaviour
>
> Mmm.. not very intuitive, this. Somewhere in the DOC's it
> says that hogthreshold should be related to the clock speed, and
> the higher hogthreshold, the quieter dosemu gets. Anyway, you know
> what I think about the dosemu doc's.
Much of what is in the docs is out of date that it one of the problems.
Anyway the thing you stated was taken out of context:
"Usually it is a good idea to format the drive after it."
this applies to a new disk image. The other "problem" is that new
Linux users are in general less technical than they were in say 1994, and
while this statement looks obvious to me it apparently does not do so for you.
(violating the art of technical writing).
"the drive" here means, "the DOS drive that you get if you use the freshly
created hdimage". in any case, hdimages aren't necessary for most people
anymore and here the out-of-date problem shows its ugly head.
> Mmm.. not very intuitive, this. Somewhere in the DOC's it
> says that hogthreshold should be related to the clock speed, and
> the higher hogthreshold, the quieter dosemu gets. Anyway, you know
> what I think about the dosemu doc's.
now to the point: hogthreshold, see README.txt:
The HogThreshold value determines how nice
Dosemu will be about giving other Linux processes a chance to run.
$_hogthreshold = (1) # 0 == all CPU power to DOSEMU
# 1 == max power for Linux
# >1 the higher, the faster DOSEMU will be
what this means is that the higher, the _faster_, not _quieter_, DOSEMU
will be, that is, the more CPU time DOSEMU will get! So (800) will get
DOSEMU much more CPU time than (1). You can basically view (0) as (infinity).
and there's also something in README-tech.txt
The HogThreshold value determines how nice Dosemu will be about giving
other Linux processes a chance to run. Setting the HogThreshold value
to approximately half of you BogoMips value will slightly degrade
Dosemu performance, but significantly increase overall system idle
time. A zero value runs Dosemu at full tilt.
the HOWTO says:
Daniel Barlow([EMAIL PROTECTED]) reported (95/4/8) that
HogThreshold should now be set to approximately half of the BogoMips
value that the system reports on boot.
this is really out-of-date, as you have seen. hogthreshold has been
tweaked recently, it is really something you have to play with to see
what's the best compromise, mind you, you can use "speed" inside dosemu
to change it, ie.
c:\>speed 1
(be nice)
c:\>speed 0
(be fast)
> > So you have applied some patches, havent you?
>
> Well of course I did. The patch set posted yesterday by Bart
> Oldeman. Or isn't that what you mean? Anyway I get a boot-up
> message which begins
well there are some related (experimental) patches at
http://dosemu.sourceforge.net/stas
to get sound going for duke3d and doom.
Bart
-
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
