From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Windows 3.1 Support
Date: Sat, 13 Nov 2004 16:56:58 +0300 [thread overview]
Message-ID: <419612AA.2020304@aknet.ru> (raw)
Hello.
TP Reitzel wrote:
> I acted on your suggestion and installed version 1.4 of the TVGA8900C
> driver for Windows 3.1. It works in both the 800x600x8 and 1024x768x8 bit
> modes.
Actually you can get even more than 8bpp
(which I thought your original question
was - misreaded it). You need to get the
newer trident drivers uc51-win.exe and
you'll be able to get 16bpp by using the
trix800.drv. But you'll need to switch
your X server to 16bpp either because the
dosemu doesn't support 16bpp->32bpp
remapping :(
> HOWEVER, this Trident driver conflicts with Video For Windows 1.1 and I
> haven't been able to find a newer version of the Trident driver which
> fixes the problem.
Newer version doesn't help :(
The problem is not in the driver itself
but in the vtdapi.386 that dosemu emulates
by using the code stolen from wine. And
this doesn't work.
I think perhaps dosemu needs the LE loader
so that it could load and use the native
.386 drivers. They may require ring0, but
most of them are likely only need the hardware
access, which is not a problem.
Any ideas where is some LE loader code in C
can be stolen? :)
> When I attempt to change virtual memory settings, I'm getting an
> error about nonstandard Windows files. Consequently, I can't change
> virtual memory settings with krnl386.exe.
Virtual memory in windows is handled by
the VxD code which is not in dosemu. And
you don't need it anyway because the
virtual memory is provided by Linux kernel.
Duplicating that functionality under dosemu
is possible (32rtm can do this), but there
is no real use because the Linux kernel
does it more effectively. So if you need
more memory to your Windows app, just increase
the $_dpmi value in dosemu.conf, and Linux
will do the rest.
next reply other threads:[~2004-11-13 13:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 13:56 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-16 13:45 Windows 3.1 Support Stas Sergeev
2004-12-23 12:39 TP Reitzel
2004-12-22 21:49 TP Reitzel
2004-12-22 18:02 Stas Sergeev
2004-12-22 8:46 TP Reitzel
2004-11-28 10:13 Stas Sergeev
2004-11-22 18:23 Stas Sergeev
2004-11-21 5:53 TP Reitzel
2004-11-20 14:17 Stas Sergeev
2004-11-18 20:50 TP Reitzel
2004-11-13 11:46 TP Reitzel
2004-11-12 20:18 Stas Sergeev
2004-11-12 22:56 ` Julius Schwartzenberg
2004-11-13 1:53 ` Kevin Noseworthy - Specialty Software
2004-11-13 3:07 ` S Iremonger
2004-11-13 9:35 ` Stas Sergeev
2004-11-12 19:29 Stas Sergeev
2004-11-12 10:16 TP Reitzel
2004-11-12 11:57 ` Julius Schwartzenberg
2004-11-11 16:56 Stas Sergeev
2004-11-12 12:21 ` Julius Schwartzenberg
2004-11-08 16:18 Stas Sergeev
2004-11-10 23:49 ` Julius Schwartzenberg
2004-11-08 2:46 TP Reitzel
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=419612AA.2020304@aknet.ru \
--to=stsp@aknet.ru \
--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