From: Ralph Alvy <ralvy@warpmail.net>
To: linux-msdos@vger.kernel.org
Subject: Re: [announce] dosemu-1.2.2
Date: Tue, 20 Jul 2004 21:09:03 -0700 [thread overview]
Message-ID: <cdkq90$urq$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.44.0407211551090.7020-100000@aitken.math.auckland.ac.nz
Bart Oldeman wrote:
> On Tue, 20 Jul 2004, Ralph Alvy wrote:
>
>> >> patch < lpt2.diff
>> >>
>> >> and try again.
>> >>
>> >> Bart
>> I mean, should that have been
>>
>> patch -p0 < lpt2.diff
>>
>> instead?
>
> yes, sorry for forgetting that -p0.
Okay, I figured that after reading the patch man page, so went ahead and did
patch -p0 < lpt2.diff
on a configured 1.3.1 untarred source. After 'make' and 'make install' I
find that I no longer crash like before, but I have the same problems
previously outlined:
hogthreshold of 1 lets my cpu stay down, but won't let me print without
taking extraneous steps after issuing the print command.
hogthreshold of 2 keeps my cpu at about 86%, but lets the app's print
command yield immediate printing without extraneous steps.
next prev parent reply other threads:[~2004-07-21 4:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 21:35 [announce] dosemu-1.2.2 Stas Sergeev
2004-07-21 1:39 ` Ralph Alvy
2004-07-21 2:16 ` Bart Oldeman
2004-07-21 2:25 ` Ralph Alvy
2004-07-21 3:24 ` Bart Oldeman
2004-07-21 3:39 ` Ralph Alvy
2004-07-21 3:44 ` Ralph Alvy
2004-07-21 3:52 ` Bart Oldeman
2004-07-21 4:09 ` Ralph Alvy [this message]
2004-07-22 14:03 ` Ryan Underwood
2004-07-22 15:26 ` Ralph Alvy
2004-07-21 3:42 ` Ralph Alvy
-- strict thread matches above, loose matches on Subject: below --
2004-07-19 10:04 Stas Sergeev
2004-07-19 14:47 ` Ralph Alvy
2004-07-20 4:48 ` Ralph Alvy
2004-07-20 4:56 ` Bart Oldeman
2004-07-20 6:26 ` Ralph Alvy
2004-07-16 17:40 Stas Sergeev
2004-07-19 4:05 ` Ralph Alvy
2004-07-11 8:43 Bart Oldeman
2004-07-11 19:28 ` Ralph Alvy
2004-07-13 0:17 ` Ralph Alvy
2004-07-13 16:41 ` Ralph Alvy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='cdkq90$urq$1@sea.gmane.org' \
--to=ralvy@warpmail.net \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox