From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: please explain to me why video/bios shadowing must be disabled to use graphics...
Date: Sun, 22 Sep 2002 02:43:40 +0400 [thread overview]
Message-ID: <3D8CF61C.4040800@yahoo.com> (raw)
Hello.
Bart Oldeman wrote:
> your problem is mostly not video shadowing
I tried this privately already - doesn't work:)
> but just that DOSEMU does
> not support this video card and does not open up enough ports.
Note however that this must not be the case for
VGA modes.
And esp. if the person have a terminal chars in
a dos box (which most likely means that the video
bios was not even mapped in), yet have a text-based
progs working.
> ports it tries to access and dosemu doesn't understand. You can enable
> then in the "ports" section.
If someone could explain why this method works
no more with the modern cards, I would be very happy.
What you now get opening these ports, is a hard lock-up:(
> Stas tried hard to get
> DOSEMU working on his ATI Radeon, and Vesa modes do not work for him.
But not all hopes are lost here: now XFree 4.2 can set
any vesa mode on my Radeon, while 4.1 couldn't. So at least now
I know that getting VESA to work again is somehow possible,
probably by stealing some code from XFree.
next reply other threads:[~2002-09-21 22:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 22:43 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 4:22 please explain to me why video/bios shadowing must be disabled to use graphics Stas Sergeev
2002-09-24 13:20 Stas Sergeev
2002-09-24 1:20 Stas Sergeev
2002-09-24 2:18 ` Bart Oldeman
2002-09-23 22:12 Stas Sergeev
2002-09-23 23:11 ` Bart Oldeman
2002-09-23 20:52 Stas Sergeev
2002-09-23 21:14 ` Bart Oldeman
2002-10-01 0:19 ` phrostie
2002-09-24 10:31 ` phrostie
2002-09-09 4:09 matt
2002-09-09 11:26 ` phrostie
2002-09-20 20:57 ` matt
2002-09-20 21:29 ` Bart Oldeman
[not found] ` <Pine.GSO.4.05.10209202215490.18306-100000@sh.enm.bris.ac.u k>
2002-09-20 23:37 ` matt
2002-09-21 5:21 ` Pat
2002-09-10 2:08 ` Pat
[not found] ` <Pine.LNX.4.44.0209091837470.20167-100000@feather.sunbird.s ys>
2002-09-20 20:52 ` matt
2002-09-21 4:53 ` Pat
[not found] ` <Pine.LNX.4.44.0209201954350.30609-100000@feather.sunbird.s ys>
2002-09-21 8:42 ` matt
2002-09-21 16:04 ` Bart Oldeman
2002-09-23 17:33 ` phrostie
2002-09-23 19:25 ` Bart Oldeman
[not found] ` <Pine.GSO.4.05.10209211648440.21069-100000@sh.enm.bris.ac.u k>
2002-09-21 20:08 ` matt
2002-09-22 20:46 ` Pat
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=3D8CF61C.4040800@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox