All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julius Schwartzenberg <julius@zgod.cjb.net>
To: linux-msdos@vger.kernel.org
Subject: Re: Some problems with version 1.3.3
Date: Mon, 09 Jan 2006 12:51:03 +0100	[thread overview]
Message-ID: <43C24E27.3010102@zgod.cjb.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0601092101080.4256@enm-bo-lt.localnet>

Bart Oldeman wrote:
> Just to make sure, I downloaded keen4 from:
> ftp://ftp.3drealms.com/share/4keen.zip
> 
> unzip, start dosemu, run install.exe, run keen4e, fine, no delay.
Yep, I just tried it with this version, same problem.

>> Have you ever looked at the VGA emulation in Dosbox btw? It seems to 
>> handle some stuff (such as Commander Keen) better. I don't know what 
>> possibilities there are when it comes to sharing code between Dosbox 
>> and Dosemu though. I prefer Dosemu myself because it runs faster, but 
>> there also seem to be some nice developments on the Dosbox side.
> 
> 
> Yes I have looked at the VGA emulation in Dosbox, and the Dosbox 
> developers have looked at the VGA emulation in DOSEMU. It makes for a 
> good comparison when game xxx does not work in DOSEMU but works in 
> DOSBOX, and a few fixes were made that way.
> 
> Directly sharing code is not so easy, partly because dosbox uses C++ 
> (although it's C++ with a lot of C, not using STL for instance) and we 
> use plain C.
> 
> Just recently I went through the licenses in the dosemu-freedos package 
> and found that shsucdx.exe is unclear. That in combination with the a 
> report that you could not obtain the (possibly LFN) volume label from an 
> lredir'ed cdrom directory was a god incentive for me to port the mscdex 
> code from dosbox. I even noticed a few errors in the dosbox code, will 
> report them back when I have the time.

Cool that stuff is indeed shared between Dosemu and Dosbox :)
Commander Keen seemed to run much smoother with the VGA emulation in 
Dosbox, which is why I asked about this.

>> PS: While typing this mail, (about 15-20 minutes after I launched 
>> Keen) it indeed seems to get further.
> 
> where does it get stuck? The init screen?
After the init screen. As Stas said, it doesn't really get stuck, it's 
just really slow, taking ~20 minutes before the title screen shows 
(having pressed a button).

Thanks,
Julius

  reply	other threads:[~2006-01-09 11:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 13:38 Some problems with version 1.3.3 Stas Sergeev
2006-01-08 23:31 ` Julius Schwartzenberg
2006-01-09  8:13   ` Bart Oldeman
2006-01-09 11:51     ` Julius Schwartzenberg [this message]
2006-01-10 20:49       ` Bart Oldeman
2006-01-10 21:05         ` Alain
2006-01-10 23:02         ` Julius Schwartzenberg
2006-01-10 23:58           ` Bart Oldeman
  -- strict thread matches above, loose matches on Subject: below --
2006-01-12 18:58 Stas Sergeev
2006-01-12  4:58 Stas Sergeev
2006-01-12  9:38 ` Julius Schwartzenberg
2006-01-11 16:47 Stas Sergeev
2006-01-11 17:54 ` Julius Schwartzenberg
2006-01-11 20:32 ` Bart Oldeman
2006-01-11  6:36 Bart Oldeman
2006-01-11  4:56 Stas Sergeev
2006-01-10 19:59 Stas Sergeev
2006-01-10 22:57 ` Julius Schwartzenberg
2006-01-11  0:14   ` Julius Schwartzenberg
2006-01-03 21:06 Julius Schwartzenberg
2006-01-05 20:01 ` Bart Oldeman
2006-01-06 23:16   ` Julius Schwartzenberg

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=43C24E27.3010102@zgod.cjb.net \
    --to=julius@zgod.cjb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.