From: Kacper Wysocki <kacperw@online.no>
To: linux-msdos@vger.kernel.org
Subject: Re: slowing down dosemu?
Date: Thu, 24 Feb 2005 23:09:33 +0000 [thread overview]
Message-ID: <1109286577l.25921l.1l@comotion> (raw)
In-Reply-To: 421A2747.6070106@aknet.ru
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On 02/21/05 13:24:07, Stas Sergeev wrote:
> Hello.
>
> Kacper Wysocki wrote:
>> Didn't have troubles with crashing, but never heard of dos32a before,
> The crash usually happens if you press the key in the game intro
> to skip it. If you use mouse to skip it, then no crash. Does it
> work the same way for you? That assumes you are using dos4gw 1.8,
> which is what my Syndicate Wars have. With dos4gw 1.97 it works
> better (the real problem is not in dosemu and not even in dos4gw
> actually).
My Syndicate Wars came with dos4gw 1.97, and pressing a key in the
intro doesn't crash anything. dos32a works nicely too.
>> thanks! However, Syndicate Wars is still running too fast
> Sorry, the bug appeared to have been fixed 3 days after 1.3.1 was
> released :( For some very strange reasons I thought the fix is in
> 1.3.1, but it appears not. Can you please try the CVS code?
[snip]
Syndicate Wars under the latest CVS version is still too fast to be
playable - no change from 1.2.1 nor 1.3.1
> What CPU do you have?
I'm running a dual athlon mp 2400+
Cheers,
Kacper
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-24 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 18:24 slowing down dosemu? Stas Sergeev
2005-02-24 23:09 ` Kacper Wysocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-25 4:22 Stas Sergeev
2005-02-25 12:42 ` Kacper Wysocki
2005-02-27 13:28 ` Albert
2005-02-21 4:50 Stas Sergeev
2005-02-21 8:07 ` Kacper Wysocki
2005-02-21 1:14 Kacper Wysocki
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=1109286577l.25921l.1l@comotion \
--to=kacperw@online.no \
--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