From: Julius Schwartzenberg <julius@zgod.cjb.net>
To: linux-msdos@vger.kernel.org
Subject: Re: Windows 3.1 Support
Date: Fri, 12 Nov 2004 13:21:24 +0100 [thread overview]
Message-ID: <4194AAC4.1040902@zgod.cjb.net> (raw)
In-Reply-To: <419399AF.7030708@aknet.ru>
Thanks a lot for your message :)
Stas Sergeev schreef:
>> How did you suddenly manage to get this to work :)
>
> The trick is to bypass the windows
> ring0 startup code and run its kernel
> directly. It requires only a little of
> ring0 - LDT read/write access. Virtualization
> of LDT appeared to be possible. Minimal
> VxD code was stolen from Wine.
Ah, I understand.
>> Or do I need to wait for a documentation update for this?
>
> Or you can try to do that yourself, which
> would be a bit faster than waiting:)
The docs on setting it up would be pretty similar right? You would also
need the WinOS/2 mouse driver, the Trident video driver and the
Soundblaster audio driver.
Does the setup program for MS Windows also work now in Dosemu?
What versions are currently tested? (Both 3.1, 3.11 and Workgroups,
non-Workgroups?)
> I agree that the screenshot section would be
> nice to have, but as for Win31 - there is
> nothing new as you could use WinOS2 patch
> since dosemu-1.2.0. And running the unmodified
> one gives you no advantages. And you still
> need the mouse driver from WinOS2 if you
> want the mouse in Win to work under xdosemu.
> So it won't be any better than here:
> http://www.dosemu.org/old
My current MS Windows install in Dosemu is also dutch :)
(Windows for Workgroups 3.11 NL with WinOS/2 stuff)
Are you sure there aren't any extra advantages with this? I cannot run
MS-DOS programs from within WinOS/2 for example. I always thought this
was a WinOS/2 limitation.
Also I tried to install a game in MS Windows at some point
(Phantasmagoria) and it didn't work. I also couldn't play the videos
that came with it.
> Mainly I view that as a first significant
> move towards win95 support, but nothing more.
That would be really great of course :)
Dosemu would be pretty similar to Win4Lin then I think.
Julius
next prev parent reply other threads:[~2004-11-12 12:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 16:56 Windows 3.1 Support Stas Sergeev
2004-11-12 12:21 ` Julius Schwartzenberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-16 13:45 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 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-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=4194AAC4.1040902@zgod.cjb.net \
--to=julius@zgod.cjb.net \
--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