public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 24 Sep 2002 00:52:32 +0400	[thread overview]
Message-ID: <3D8F7F10.7080900@yahoo.com> (raw)

Hello.

phrostie wrote:
>> not support this video card and does not open up enough ports.
>  what ports?
>  could you expand on this part?
>  i have a S3
For S3 cards you must not worry about this issue
at all. Setting $_chipset="s3" worked for my S3 Trio
flawlessly both for VGA and VESA modes. Don't remember
about setting $_chipset="plainvga", but I think it could
work as well.
This problem exists only on some (modern?) cards for VESA
modes, but for VGA modes there must be no such problem at
all (Bart, do you really have any examples when this is a
problem even for VGA? Correct me then, please).
To verify if you have this "port" problem, just start your
DOS prog under WinNT. If it can't set mode also there, then
yes, you have this problem (I bet you don't have it with
S3 though). Unfortunately opening the ports doesn't always
help: still no VESA modes on my Radeon7500, but VGA works
perfectly. Thinking about returning my old S3...


             reply	other threads:[~2002-09-23 20:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 20:52 Stas Sergeev [this message]
2002-09-23 21:14 ` please explain to me why video/bios shadowing must be disabled to use graphics Bart Oldeman
2002-10-01  0:19   ` phrostie
2002-09-24 10:31 ` phrostie
  -- strict thread matches above, loose matches on Subject: below --
2002-10-04  4:22 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-21 22:43 Stas Sergeev
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=3D8F7F10.7080900@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