Windows inside OS/2 MVDM

[Lucss21a]

So I was experimenting around which versions of Windows are capable of running inside the OS/2 2.1 MVDM (Tested on VirtualBox). Here's my results:

• Windows 1.0 Development Release 5: n/a
• Windows 1.0 Beta Release: n/a
• Windows 1.0 Premiere Edition: n/a
• Windows 1.01 + PS/2 Mouse patch: Works, but the mouse isn't working
• Windows 1.02 + PS/2 Mouse patch: n/a
• Windows 1.03 + PS/2 Mouse patch: n/a
• Windows 1.04: Works, but the mouse isn't working
• Windows 2.01: n/a
• Windows 2.03: n/a
• Windows 2.10: Works, but the mouse isn't working
• Windows 2.11: n/a
• Windows 3.0: n/a
• Windows 3.0 MME: n/a
• Windows 3.1: n/a
• Windows For Workgroups 3.1: n/a
• Windows For Workgroups 3.11: n/a
• Windows 3.11: Setup fails after finishing the text based preinstallation enviroment (probably due to something like WinOS/2 is running in the bg, idk)

Also, thanks in advance if you posted the OS/2 mouse driver for Windows 1.01 to 2.11.

[vbdasc]

"Windows 3.11: Setup fails after finishing the text based preinstallation enviroment (probably due to something like WinOS/2 is running in the bg, idk)"

And this tells you the reason of all these versions not running. The OS/2 (even the pre-IBM versions) was telling its DOS sessions that it was running, and the (newer) Windows 2.x/3.x versions were taught to check for it and refuse to run/install. Windows under OS/2 was supposed to run as Win-OS/2, and under OS/2 1.x was not supposed to run at all.

[Lucss21a]

Here's more I run on OS/2 (more versions of OS/2 + eCS)

OS/2 1.3
- Windows 3.0
- Windows 2.1 (i don't remember tho)

[z8coder]

So think to yourselves guys! When did IBM and Microsoft have their falling out ?
They were building OS2 together back in the early 80's I believe.
Designing COWS.lib LIBRARY for Windows anybody getting the picture yet?
When the broke up them MS did their Windows stuff with it! that's why COWS is used to build QBASIC?
And the SETUP program to install DOS?

[Lucss21a]

So think to yourselves guys! When did IBM and Microsoft have their falling out ?
They were building OS2 together back in the early 80's I believe.
Designing COWS.lib LIBRARY for Windows anybody getting the picture yet?
When the broke up them MS did their Windows stuff with it! that's why COWS is used to build QBASIC?
And the SETUP program to install DOS?

I don't understand what stuff you saying. Unrelated.

[z8coder]

DOS text windowing libraries and the like . They refined it enough to get the look and feel they wanted for Windows!!!!!!!! NOW are we understanding yet!

[Lucss21a]

DOS text windowing libraries and the like . They refined it enough to get the look and feel they wanted for Windows!!!!!!!! NOW are we understanding yet!

Oh... Don't shout. By the way, I can test Windows on AcraOS if there's an iso on the internet, but yeah, OS/2 MVDMs are some kind of marketing strategy to pull DOS users to use OS/2.

[Angelahelen]

OS/2 is incompatible with Windows device drivers (VxDs) and applications that require them since it only executes the user-mode system components of Windows. If you want more details to check out the page https://jealouscomputers.com/7-best-way ... le-gaming/.

[techLinuxtux]

OS/2 is incompatible with Windows device drivers (VxDs) and applications that require them since it only executes the user-mode system components of Windows. If you want more details to check out the page https://jealouscomputers.com/7-best-way ... le-gaming/.

Offtopic Comment

just a "how to cool the laptop while gaming!" tutorial, doesn't say anything about OS/2 or its VDR (virtual DOS runner)

[vbdasc]

A possible explanation is that, slightly simplifying things, Windows 3.1 in Enhanced mode contains two important layers:

First, Win386, which is the 32-bit "kernel" of Windows, provides the DOS virtual machines with preemptive multitasking, the EMS emulator, the virtual memory pager, the VXD "arena" and the DPMI host.

Second, Krnl386, which is the 16-bit "kernel" of Windows, runs in protected mode in a DOS virtual machine provided by Win386, using its DPMI services to get to that protected mode. It loads and starts USER, GDI and all other Windows API libraries, all 16-bit binaries, the shell, the Windows applications and basically everything that the user sees on the screen.

The "Windows" that runs inside OS/2 is basically a slightly modified version of the latter of the aforementioned two layers, made to use the DPMI, virtual memory and EMS provided directly by the OS/2 MVDM instead of Win386. One consequence of this is that VXDs are not supported in this scenario. The reason is that the Win386 layer (with its features like VXDs) is not used and is completely replaced by its native OS/2 counterpart.

[os2fan2]

did you look at the winos2 beta. It might provide some clue.

[Lucss21a]

did you look at the winos2 beta. It might provide some clue.

Well, actually no... I'll try when I got my monitor either fixed or replaced.