From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Newbie with terminal video problems
Date: Sun, 01 Dec 2002 20:34:32 +0300 [thread overview]
Message-ID: <3DEA4828.10405@yahoo.com> (raw)
Hello.
Mushroom wrote:
> Yes - the problem remains as it was. I'll try playing with some more
> settings but it doesn't seem promising.
OK, I think all the problems we have
with video, are because dosemu is
trying to POST the video bios not
accordingly the PCI specs.
I intended to introduce a POST-less
video init together with the VESA
support, which is stalled due to some
problems with kernel, but I think
I just can introduce the POST-less
video init code also without a VESA
support, which is rather easy to do.
I'll let you know when if I'll get
the patch ready soon.
> BTW the sound which was working
> well in 1.1.3.0 seems partly broken again in 1.1.3.7
Fine :-/
Now, when my new sound engine finally
made it in (which was the one of the
top requested features), there will
surely be someone who will call it
broken:)
> but that's not something that really concerns me.
That is important and concerns me.
My sound engine is not perfect overall,
but compared with an old crap, I
don't want to have any drawbacks.
Please open the bug report on dosemu
SourceForge BTS and attach you program
to that report so that I can reproduce
and fix the problem.
next reply other threads:[~2002-12-01 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 17:34 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-01 18:37 Newbie with terminal video problems Stas Sergeev
2002-12-01 12:33 Stas Sergeev
2002-12-01 16:59 ` Mushroom
2002-11-30 14:33 Stas Sergeev
2002-12-01 9:58 ` Mushroom
2002-11-30 3:55 Mushroom
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=3DEA4828.10405@yahoo.com \
--to=stssppnn@yahoo.com \
--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.