Linked by Thom Holwerda on Mon 5th Feb 2018 23:08 UTC

In November last year I wrote about the forgotten and obscure feature of early Windows 95 builds that lets you run Windows 3.1 in a window on Windows 95. Since then I was wondering if this would still work on the final build (950) of Windows 95, considering so much has changed since build 58s.

I won't spoil it.

Thread beginning with comment 653563
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Reminds me of OS/2 2.0
by galvanash on Tue 6th Feb 2018 03:47 UTC in reply to "Reminds me of OS/2 2.0"
Member since:

Once you have MSDOS virtualized there is very little left to do to be honest... Windows 3.1 was basically a DOS application. The only obstacles are presenting it with compatible virtualized hardware (video card, sound card, etc.) with working windows drivers for them.

You can still do this on Windows 10 if you like btw, just use dosbox:

Or if your nostalgic and want to do it the old school way (and can get your hands on the version of WINOS that OS/2 used with DPMI support) you can use dosemu on Linux to do it (this has worked for like 20 years)

Of course nowadays there is little point as dosbox exists on Linux now...

Reply Parent Score: 2

RE[2]: Reminds me of OS/2 2.0
by Darkmage on Tue 6th Feb 2018 08:20 in reply to "RE: Reminds me of OS/2 2.0"
Darkmage Member since:

Except Dosbox still fails to emulate a lot of timings correctly and runs slowly in a lot of cases. It's a brilliant piece of code/emulation, but still flawed. This isn't written in anger. The Dosbox developers are some of the loveliest people on the internet. I suspect there are limits to what a PC can actually do to emulate PC architecture and it wouldn't surprise me if Dosbox is hitting those limits hard.

Reply Parent Score: 5

Zoidberg Member since:

I believe it can be installed using PCem now, which probably works much better.

Reply Parent Score: 3

RE[3]: Reminds me of OS/2 2.0
by Morgan on Tue 6th Feb 2018 12:29 in reply to "RE[2]: Reminds me of OS/2 2.0"
Morgan Member since:

I always understood it was because DOSBox was optimized for DOS gaming, and Windows 3.x suffered as a result. From the DOSBox FAQ (emphasis mine):

According to its developers, DOSBox is focused on DOS games. Non-gaming DOS applications are not the primary focus of DOSBox, even though most DOS applications might in fact work within DOSBox. The DOSBox project has a policy of not adding features that aren't used by DOS games if they take significant effort to implement, are likely to be a source of bugs or portability problems, and/or impact performance. For example, features such as parallel ports, long filenames and Ctrl-Break emulations are never officially supported in DOSBox. Some enhanced DOSBox SVN Builds may support these features, and you may try these builds if you want or need such features, but they are not supported by the DOSBox Team. If you want to run serious DOS applications within a DOS emulator, you'd better try dedicated emulators such as vDos and vDosPlus instead, which are designed to run DOS applications rather than games.

Reply Parent Score: 7

RE[2]: Reminds me of OS/2 2.0
by Z_God on Tue 6th Feb 2018 19:00 in reply to "RE: Reminds me of OS/2 2.0"
Z_God Member since:

Note that you can run the regular Windows 3.1 on DOSEMU for many years already.

Reply Parent Score: 1

RE[2]: Reminds me of OS/2 2.0
by Drumhellar on Tue 6th Feb 2018 21:28 in reply to "RE: Reminds me of OS/2 2.0"
Drumhellar Member since:

Windows 3.1 was basically a DOS application.

No, it wasn't. It was an actual operating system, really, by any reasonable definition of the word. Basically, everything that an operating system does, Windows 3.1 without using DOS, and handled many things that DOS couldn't.

Sure, it started from DOS, but when you launched Windows, it would replace DOS with a 32-bit hypervisor that would run a virtual machine with a single instance of Windows 3.1, as well as DOS virtual machines for running DOS apps. The Windows 3.1 instance and the DOS virtual machines were pre-emptively multitasked.

As for the Windows 3.1 machine, it provided virtual memory (including paging to disk), its own interrupt handler (and didn't use DOS's), it used its own drivers for disks, mouse, audio, printing, and networking (When available - it could also use DOS drivers if Windows drivers weren't available). The disk driver is especially significant, as it as a 32-bit protected mode driver that completely by passed DOS and BIOS function calls.

Sure, it was closely tied to DOS, but it was definitely an operating system in its own right, and certainly not just "basically a DOS application."

It's really more like... an operating system that runs next to DOS, and sometimes asks DOS for a cup of sugar or whatever.

Reply Parent Score: 7

RE[3]: Reminds me of OS/2 2.0
by ianm on Tue 6th Feb 2018 23:34 in reply to "RE[2]: Reminds me of OS/2 2.0"
ianm Member since:

Good times!

Your post brought be back to Usenet newsgroup discussions from late 80's through early 90's.

Reply Parent Score: 1

RE[3]: Reminds me of OS/2 2.0
by Andre on Fri 9th Feb 2018 10:25 in reply to "RE[2]: Reminds me of OS/2 2.0"
Andre Member since:

What makes an operating system an operating system rather then an application, especially in the (MS-)DOS days? Back in the days where each application that handles sounds had to include its own support, rather then rely on the operating systems support.

Stating that Windows 3.1 used its own drivers, well.... running on top of (MS-)DOS you had to for most hardware. Okay, there were DOS drivers for mice, but that's about it. And for CD-ROM drives, Windows 3.1 depended on the support DOS offered.

Reply Parent Score: 1