Re: Windows 3.1 Support

Re: Windows 3.1 Support

[Stas Sergeev]

Hello.

TP Reitzel wrote:
> So, will we actually be able to fully utilize Windows 3.1 capabilites, 
> e.g. DOS shell to run games?
OK, for all the DOS shell lovers: it is
now working in windows Standard mode.
Supporting it for Enhanced mode is not
easy and will not happen in a near future -
one can just start multiple dosemu instances
instead.

Windows 3.1 Support

[TP Reitzel]

Stas -

"So, will we actually be able to fully utilize Windows 3.1 capabilites, e.g.
DOS shell to run games?"

I meant to use virtual memory as the example per our previous discussion on 
Windows 3.1.

Windows 3.1 Support

[TP Reitzel]

"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."

Superb! My machine looks more like an old '386 everyday which is a real good 
testimony about DosEmu's emulation ability.. :)

"Also the VxD loader is under development
now - if this works, the compatibility
level will burst."

So, will we actually be able to fully utilize Windows 3.1 capabilites, e.g. 
DOS shell to run games?

"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."

OK, I'll keep a record of your progress in pictures. ;)

"Have you tried IE 5.5? AFAIK the win16
port exists, although I don't have one.
Would be interesting to test that."

I haven't been able to find a 16 bit version of MSIE5.5 either. I do have 
MSIE 5.01, however, but I'll stay with Netscape unless someone points me to 
MSIE5.5

"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."

I had just upgraded DosEmu to the latest CVS which was causing errors with 
the TAP interface for some bizarre reason. After rebooting, the problem 
vanished.

When FM synthesis is added to DosEmu, I'll finally remove DosBox from my 
computer.  Thanks again to all of you for your work on DosEmu. Soon, DosEmu 
will be King of the DOS Emulators. :)

Re: Windows 3.1 Support

[Stas Sergeev]

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.

Windows 3.1 Support

[TP Reitzel]

Stas -

I thank you for adding support to DosEmu so VFW runs movies in 16 bit color! 
I'll try to refrain from posting YAP (yet another picture) showing 
Gulliver's Travels in full color. :) I know that I'm not alone in saying, 
THANKS!

P.S. I'm now using Netscape 4.0.8, too! ;)

Re: Windows 3.1 Support

[Stas Sergeev]

Hello.

TP Reitzel wrote:
> BTW, 16 bit versions of Netscape 4.0x, specifically 4.06 and 4.08, 
> crash DosEmu.
Not any more. Our new (anonymous)
friend from www.japheth.de worked
out that problem. (on his web-site
you can find the tool-set for running
the console win32 apps under dos
and dosemu).
Now I am hardly restrain myself
from posting the screen-shot too:)
There is a Screenshots section on
dosemu SF page
http://sourceforge.net/projects/dosemu
but it is inactive.
Bart, would it be possible to enable
it somehow?

Another nice addition is that you no
longer need the WinOS2 mouse driver.
But it still work better in most cases,
without it you'll need to enable the
mouse-grab mode for better results.
So overall you no longer need WinOS2
at all. Windows now can be used
completely unmodified.

Re: Windows 3.1 Support

[Stas Sergeev]

Hello.

Julius Schwartzenberg wrote:
> Does the setup program for MS Windows also work now in Dosemu?
I am glad to "announce" that now it
does. Moreover, you can now use win.com
to start windows, as you did in real
DOS. win /s and win /3 will work exactly
as expected and will produce the the
very nice window title (my special
addition for Windows users:)
So you don't need to do any file mods
now. The only thing you still have to
do, is to copy the mouse.drv from WinOS2
to your windows distribution directory.
Then install that windows under dosemu
and enjoy. Unfortunately this windows
will work only under dosemu and not
under pure DOS. For some strange reasons
the mouse driver of WinOS2 works under
dosemu but doesn't work without dosemu.

> What versions are currently tested? (Both 3.1, 3.11 and Workgroups, 
> non-Workgroups?)
I am still working on some issues of
wfw3.11. 3.1 looks better. But of course
there are (and will be) still the limitations.

Windows 3.1 Support

[TP Reitzel]

[-- Attachment #1: Type: text/plain, Size: 362 bytes --]

Stas -

Your advice in addition to Bart's helpful additions on networking with 
TUN/TAP in the Readme for DosEmu 1.2 enabled Windows 3.1 to run Netscape 
3.04 on my system.

BTW, 16 bit versions of Netscape 4.0x, specifically 4.06 and 4.08, crash 
DosEmu. I haven't tried any others so far. Some "16 bit" applications 
probably needed win32s.

Thanks again. :)


[-- Attachment #2: DosEmu-Netscape3.png --]
[-- Type: image/png, Size: 38832 bytes --]

Re: Windows 3.1 Support

[Stas Sergeev]

Hello.

TP Reitzel wrote:
> You mentioned that it was possible to use networking with Windows 3.1
Yes, networking must work, otherwise
running windows would be useless.

> 1. Trumpet Winsock 2.0f or something like it which includes the
I tried both 2.0 and 3.0d.

> 2. Running current DosEmu CVS as root with direct connection to eth0.
This is very risky.
I set up dosemu on tap0, without giving
it root. Then I added this to my iptables
configuration:
---
*nat
-A POSTROUTING -o eth0 -j MASQUERADE
COMMIT
---
(eth0 is connected to Internet),
and configured winsock.

> 3. Installed Netscape 3.04 Gold since newer versions of 16 bit Netscape 
> crash DosEmu.
Which ones crash it?

> After configuring Trumpet Winsock, I can only partially retrieve 
> Google's webpage.
With 3.04 Gold I had no problems accessing
everything. Works flawlessly. Perhaps when
you set dosemu to use eth0, something else
also reads it, and that's why you have the
lost packets.
If you set up everything on the TAP interface
and establish the masquerading, then you'll
get the much better results. Don't forget to
write 1 to /proc/sys/net/ipv4/ip_forward

Windows 3.1 Support

[TP Reitzel]

Stas -

You mentioned that it was possible to use networking with Windows 3.1 so I 
just had to try it! ;)

It works... sort of. My test configuration is a follows:

1. Trumpet Winsock 2.0f or something like it which includes the winpkt.com 
driver. I also tried the latest version, 3.0d, but it didn't help the error 
below
2. Running current DosEmu CVS as root with direct connection to eth0.
3. Installed Netscape 3.04 Gold since newer versions of 16 bit Netscape 
crash DosEmu.

After configuring Trumpet Winsock, I can only partially retrieve Google's 
webpage. However, Netscape doesn't appear to crash. Google's webpage just 
fails to load completely. Of the many URL's that I've attempted to view, 
only Google's will load partly.  The other URLs generate the following 
error:

"A network error occurred while Netscape was receiving data
[Network Error: Socket is not connected]
Try connecting again."

What's the cause of this error? ... probably something that I'm NOT doing, 
but should be.  ;)   I've actually been able to retrieve a couple of 
webpages quickly and completely, but ONLY once just after installing Trumpet 
and Netscape. After the initial installation, I get the error as previously 
mentioned.

Re: Windows 3.1 Support

[Stas Sergeev]

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.

Windows 3.1 Support

[TP Reitzel]

"Hmm, was it also possible with WinOS/2 to play videos? It doesn't seem
to work for me, but that might have to do with the format.
My current WinOS/2 installation uses a Trident driver (TRIDENT
1024x768-256c), I suppose it would also work in in Windows 3.1.
Julius"

Julius -

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. 
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. I'm using unmodified Windows 3.1.  I'm not really sure the 
SOURCE of this conflict, but it SEEMS to be interfering with the audio. 
Currently, it's not possible to use a 8 bit color driver with Video For 
Windows 1.1 AFAIK.



Stas -  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.

Re: Windows 3.1 Support

[Stas Sergeev]

Hello.

Julius Schwartzenberg wrote:
> The docs on setting it up would be pretty similar right?
I think so.

> Does the setup program for MS Windows also work now in Dosemu?
To my great surprise no it doesn't,
it still has the same problem as WinOS2
had...

> What versions are currently tested?
> (Both 3.1, 3.11 and Workgroups, 
> non-Workgroups?)
3.11 and "Windows for Workgroups" is
the same thing AFAIK.
Both 3.1 and 3.11 are known to work.

> Are you sure there aren't any extra advantages with this?
I don't know. People seem to not like
WinOS2, but as for me there are no
advantages in avoiding it at all.
It may even be a little faster as it
doesn't need the virtualization of LDT.

> I cannot run
> MS-DOS programs from within WinOS/2 for example. I always thought this
> was a WinOS/2 limitation.
It appears not. This is the limitation
of both FreeDOS and dosemu. FreeDOS can
be improved, but dosemu will have to
provide the whole lot of VxD code to
allow the concurrent DOS sessions. Such
a code is not in Wine, neither it is
documented. So unless someone is to
invest some *real* work into it (like
Win4Lin guys did), I'd say there are no
hopes. But hey, that's silly:) You can
just start multiple xdosemu sessions
and get much more reliable environment
that the one of Win3.1.

> 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.
There are many things to improve in
windows support. You may start filling
up the bug reports on it, but right
now there are still many known problems
to work out, so the bugs will have to
wait (on BTS).

>> move towards win95 support, but nothing more.
> That would be really great of course :)
> Dosemu would be pretty similar to Win4Lin then I think.
Win4Lin did a great work. Dosemu is
unlikely to catch up. But running win95
with the very limited capabilities would
also be nice.
Btw, it may be possible already I think.
AFAIK some very early Chicago betas were
able to boot in 3.1 mode (by executing
win31.exe IIRC). Later the kernel was
reworked and the 3.1 mode was abandonned.
I think this may even run under dosemu.
But getting such a Windows looks problematic
these days.

> Hmm, was it also possible with WinOS/2 to play videos?
Depends on dosemu version I think. Since
1.2.2 it might be possible.

Re: Windows 3.1 Support

[Julius Schwartzenberg]

Stas Sergeev schreef:
>> What versions are currently tested?
>> (Both 3.1, 3.11 and Workgroups, non-Workgroups?)
> 
> 3.11 and "Windows for Workgroups" is
> the same thing AFAIK.
> Both 3.1 and 3.11 are known to work.
I also used to think this, till I came across disk images of Windows 
3.11 and Windows for Workgroups 3.1 on Usenet.
I still had the ones for Windows for Workgroups 3.1 on my comp, so I'd 
thought I'd try them out. Here are some screenshots I created a couple 
of minutes ago using VMware:
http://middelvinger.student.utwente.nl/screenshots/
I also came across this page from MS:
http://support.microsoft.com/kb/q114301/

>> Are you sure there aren't any extra advantages with this?
> 
> I don't know. People seem to not like
> WinOS2, but as for me there are no
> advantages in avoiding it at all.
> It may even be a little faster as it
> doesn't need the virtualization of LDT.
I think the reason many people don't like it, is because it seemed less 
compatible (while that may not be true, since the problems weren't with 
WinOS/2 but with Dosemu).
Other reasons might be that you would need to get os2win31.zip and mess 
with some stuff before it works.
There might also be people that would like to use Windows 3.1 in a 
situation, where licenses and stuff is important. (And you need an OS/2 
license according to the Dosemu documentation for WinOS/2.)

>> I cannot run
>> MS-DOS programs from within WinOS/2 for example. I always thought this
>> was a WinOS/2 limitation.
> 
> It appears not. This is the limitation
> of both FreeDOS and dosemu. FreeDOS can
> be improved, but dosemu will have to
> provide the whole lot of VxD code to
> allow the concurrent DOS sessions. Such
> a code is not in Wine, neither it is
> documented. So unless someone is to
> invest some *real* work into it (like
> Win4Lin guys did), I'd say there are no
> hopes. But hey, that's silly:) You can
> just start multiple xdosemu sessions
> and get much more reliable environment
> that the one of Win3.1.
Hmm, yes this indeed isn't really necessairy. I'm using PC DOS 2k 
instead of FreeDOS btw.

>> 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.
> 
> There are many things to improve in
> windows support. You may start filling
> up the bug reports on it, but right
> now there are still many known problems
> to work out, so the bugs will have to
> wait (on BTS).
Win32s support would be really nice btw, because many newer applications 
seem to depend on it.
Hopefully I'll have a clean Windows install soon in Dosemu and I'll be 
able to do some testing.

>>> move towards win95 support, but nothing more.
>>
>> That would be really great of course :)
>> Dosemu would be pretty similar to Win4Lin then I think.
> 
> Win4Lin did a great work. Dosemu is
> unlikely to catch up. But running win95
> with the very limited capabilities would
> also be nice.
> Btw, it may be possible already I think.
> AFAIK some very early Chicago betas were
> able to boot in 3.1 mode (by executing
> win31.exe IIRC). Later the kernel was
> reworked and the 3.1 mode was abandonned.
> I think this may even run under dosemu.
> But getting such a Windows looks problematic
> these days.
> 
>> Hmm, was it also possible with WinOS/2 to play videos?
> 
> Depends on dosemu version I think. Since
> 1.2.2 it might be possible.
Video for Windows currently seems to hang for me with Dosemu 1.3.1. That 
might be because I removed some stuff from some ini at some point 
because I got errors about it though. I've also installed other junk in 
my Windows install, which is why it is kind of messy.
That Chicago stuff sounds very interesting. I've seen it several times 
on Usenet, so I'll watch out for it :)
What I also always found weird was that the setup of Windows 98 uses the 
Windows 3.1 style (only with different colors). I'm wondering how much 
of Windows 3.1 is actually still in there.

Julius

Re: Windows 3.1 Support

[Kevin Noseworthy - Specialty Software]

Windows 3.11 did actually escape before the Workgroup features were 
added but this was very short lived.   I'm not sure Microsoft even 
released 3.11 as if my memory is correct the Windows without Workgroups 
I saw was from a third party company.  Perhaps Zenith.   I may even have 
this kicking around somewhere.   At any rate perhaps you can enlighten 
me as to why one would want to run 3.1 instead of WFW3.11.   Also,   
does the networking function.  i.e. can I connect to say a Win98 server?

Re: Windows 3.1 Support

[S Iremonger]

>me as to why one would want to run 3.1 instead of WFW3.11.   Also,
>does the networking function.  i.e. can I connect to say a Win98 server?

Because  windoze 3.1 can run in 'standard' mode.

windoze-for-workgroups insists on 386-enhanced (386 protected mode).

I'm not 100% sure how 386 control programs like QEMM386 ''dealt'' with
  windoze-3.0/3.1/3.11 'protected mode' (QEMM386 definitely takes
  account of it, though).

Maybe qemm386 ''cooperates'' // becomes-a-slave   using VCPI
  (virtual control program interface) with win386, giving windoze
  'full control 'over the 386. That situation is NOT acceptable
  inside DosEmu, etc. ...

However, if win386 can run under DPMI (e.g. qdpmi.sys, cwsdpmi,
  dosemu, dosbox (?))  [DOS protected mode interface], then windoze
  is being a ''slave'' to DPMI.  Iirc. win386 doesn't support this.

Anyway, for running inside an environment like dosemu (unless dosemu
  takes particular precautions // workarounds for win386),  386 protected
  mode is NOT SUITABLE for working inside dosemu  (i.e. Linux/similar is
  a '386 control program', and so is win386, and only 1 program can be
  in control of the 386 at any time).


I do not now how standard mode (286 protected mode) works, either, so
  tbh. I'm not sure how that would work inside dosemu, either! argh!


-S Iremonger <exxsi@bath.ac.uk>

Re: Windows 3.1 Support

[Stas Sergeev]

Hello.

Kevin Noseworthy - Specialty Software wrote:
> does the networking function.  i.e. can I connect to say a Win98 server?
Yes, the networking can work via
dosemu's packet driver support.
You need winpkt.com on the DOS side
and Trumpet Winsock (or something else
that supports the packet driver) on a
Windows side.

Re: Windows 3.1 Support

[Stas Sergeev]

Hello.

TP Reitzel wrote:
> I thought you'd like the attachment. ;)
Yes, but attachments to the public ML
is probably not the good idea (that's
why I always encourage people to use BTS
before asking them for logs).

> P.S. I'm looking forward to someone adding mouse support for Windows 
> 3.1 without having to resort to the the Win-OS/2 driver.
But why? It seems people (not only you)
do not like WinOS2, but I really fail to
see the reason. Is there really something
that makes WinOS2 such unappealing?

> Is 8-bit color
> currently possible with an appropriate graphics driver for Windows 3.1?
Very probably. AFAIK even qemu suffers
the same problem.

> Also, I plead once again for OPL-3 FM Synthesis support as my Voyeta 
> Super SapiFM. :)
Have you tried my ancient hack like this:
http://dosemu.sourceforge.net/stas/opl1c.diff
I know it is not perfect, but it used to
work in the past (havent tested it lately).
The proper integration of OPL3 is imminent,
but it will require the redesign of the
current sound code, which is a damn too much
of work for now.

Windows 3.1 Support

[TP Reitzel]

[-- Attachment #1: Type: text/plain, Size: 406 bytes --]

Stas -

I thought you'd like the attachment. ;)

P.S. I'm looking forward to someone adding mouse support for Windows 3.1 
without having to resort to the the Win-OS/2 driver. Is 8-bit color 
currently possible with an appropriate graphics driver for Windows 3.1? 
Also, I plead once again for OPL-3 FM Synthesis support as my Voyeta Super 
SapiFM. :)  driver needs it.

Cheers! Thanks for the fine work.


[-- Attachment #2: dosemu-win31.png --]
[-- Type: image/png, Size: 38555 bytes --]

Re: Windows 3.1 Support

[Julius Schwartzenberg]

Hmm, was it also possible with WinOS/2 to play videos? It doesn't seem 
to work for me, but that might have to do with the format.
My current WinOS/2 installation uses a Trident driver (TRIDENT 
1024x768-256c), I suppose it would also work in in Windows 3.1.
Julius

TP Reitzel schreef:
> Stas -
> 
> I thought you'd like the attachment. ;)
> 
> P.S. I'm looking forward to someone adding mouse support for Windows 3.1 
> without having to resort to the the Win-OS/2 driver. Is 8-bit color 
> currently possible with an appropriate graphics driver for Windows 3.1? 
> Also, I plead once again for OPL-3 FM Synthesis support as my Voyeta 
> Super SapiFM. :)  driver needs it.
> 
> Cheers! Thanks for the fine work.

Re: Windows 3.1 Support

[Stas Sergeev]

Hello.

Julius Schwartzenberg wrote:
> Hmm, what about all that stuff in the current documentation saying that
> this is impossible?
To be removed, most is just a plain crap.
Even the parts that were related to WinOS2,
were a total crap, see this for instance:
http://sourceforge.net/mailarchive/forum.php?thread_id=5879796&forum_id=33906

> (ring0 access wasn't possible or something like
> that.)
It still isn't in most cases, yes.

> 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.

> 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 though just came to me that a screenshot section on the Dosemu site
> would be nice ;)
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
Mainly I view that as a first significant
move towards win95 support, but nothing more.

Re: Windows 3.1 Support

[Julius Schwartzenberg]

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

Re: Windows 3.1 Support

[Stas Sergeev]

Hello.

TP Reitzel wrote:
> realize this potential of DosEmu. I can hardly contain myself.  My 
> Windows 3.1 directory is ready and waiting.  :)
What exactly does it wait for?
The code is all in CVS, people who
need it, already use it:)
What you really have to wait (maybe
indefinitely), is win95 support. But
as for Win31 - just rush to CVS!
It is still under development, but
works pretty fine. If there is some
demand for Win32s, I think it will
be worked out either.

Re: Windows 3.1 Support

[Julius Schwartzenberg]

Stas Sergeev schreef:
> Hello.
> 
> TP Reitzel wrote:
> 
>> realize this potential of DosEmu. I can hardly contain myself.  My 
>> Windows 3.1 directory is ready and waiting.  :)
> 
> What exactly does it wait for?
> The code is all in CVS, people who
> need it, already use it:)
> What you really have to wait (maybe
> indefinitely), is win95 support. But
> as for Win31 - just rush to CVS!
> It is still under development, but
> works pretty fine. If there is some
> demand for Win32s, I think it will
> be worked out either.

Hmm, what about all that stuff in the current documentation saying that 
this is impossible? (ring0 access wasn't possible or something like that.)
How did you suddenly manage to get this to work :)
Or do I need to wait for a documentation update for this?
The though just came to me that a screenshot section on the Dosemu site 
would be nice ;)
Julius

Windows 3.1 Support

[TP Reitzel]

I just wanted to say, "thanks", for adding support for unmodified Windows 
3.1 in a future release of DosEmu. I appreciate the time and effort to 
realize this potential of DosEmu. I can hardly contain myself.  My Windows 
3.1 directory is ready and waiting.  :)

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/