From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Windows 3.1 Support
Date: Wed, 22 Dec 2004 21:02:51 +0300 [thread overview]
Message-ID: <41C9B6CB.8030402@aknet.ru> (raw)
Hello.
TP Reitzel wrote:
> I thank you for adding support to DosEmu so VFW runs movies in 16 bit
> color!
Yes, Windows support is maturing and
doing swell. There are already the
VESA drivers (created by Japheth) that
will soon be able to replace the Trident
ones, so that you can use Windows in hi
color modes also under console.
Also the VxD loader is under development
now - if this works, the compatibility
level will burst.
> I'll try to refrain from posting YAP (yet another picture) showing
> Gulliver's Travels in full color. :)
Why not? The gallery have to be updated:
http://sourceforge.net/project/screenshots.php?group_id=49784
Every new achievement deserves being
screenshooted. But there is a limit of
6 screenshots, thats the problem.
> P.S. I'm now using Netscape 4.0.8, too! ;)
Have you tried IE 5.5? AFAIK the win16
port exists, although I don't have one.
Would be interesting to test that.
> With the latest CVS, I've noticed that DosEmu seems to be killing the
> TAP connection to eth0.
You should be more specific. "connection"
between tapX and eth0 is maintained by
kernel so it is not easy for dosemu to
kill it. Make sure the route to tapX
device exist in your routing table.
Mine looks like this:
---
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.254.254.0 * 255.255.255.0 U 0 0 0 tap0
...
---
Make sure the IP forwarding is enabled.
next reply other threads:[~2004-12-22 18:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 18:02 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 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 13:56 Stas Sergeev
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=41C9B6CB.8030402@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