Running IBM OS/2's Interface on Windows 10?

preview_player
Показать описание

Today's video is a followup to my IBM WorkPlace Shell video that I did back in December. Today, we're going to attempt to run that shell on Windows 10!

● Affiliate Links

● Follow Me:

● Music/Credits:

Outro Music: Silent Partner - Bet On It
Source: YouTube Audio Library

Some materials in this video are used under Section 107 of the Copyright Act of 1976, which allows "fair use" for purposes such as criticism, commenting, news reporting, teaching, and research.

#MichaelMJD #OS2 #Windows10
Рекомендации по теме
Комментарии
Автор

i interact with OS/2 every day sadly. the NYC Subway uses it for fare payment

justinoboyle
Автор

15:54 maybe the ibm os/2 shell is searching "notepad.exe" or "control.exe" in the system32 or windows folder of the otvdm virtualized folder and the C drive.
Obviously because otvdm doesn´t come with win 3.11 apps preinstalled in the virtualized windows\system folder and because windows 10s system folder is now system32 it can´t find these files.

Only WordPad opens because it is still under C:\Windows\write.exe in Windows 10

uwu_peter
Автор

BRB, updating all of our work Windows 10 PCs.

ActionRetro
Автор

Somehow, the colour scheme of the Workplace Shell blends well with Windows 10’s system colour (especially the taskbar)

MondySpartan
Автор

Great video! The most likely reason why your WPShell 1.5.1 failed to install is because that source was indeed corrupted. I did a search for WPShell 1.5.1 in Google and downloaded the first hit for download and encountered the very same error with License.TXT when attempting to install WPshell in Win3.1 running in DosBox.(I tried installing it in a Win 3.11 VirtualBox VM and it too failed the same way) I ended up finding a copy from another site and it worked correctly. (ETA: I just noticed that your link points to WinWorldPC... that is where I originally downloaded it from and failed)

sracer
Автор

Most built-in applications are in SYSTEM32, maybe thats why all the apps wont run :)

ZakHooiTM
Автор

I used to program with IBM's Visual Age, it created Windows executables with the look and feel of OS/2. Maybe we could recreate what the Workplace Shell did in the 90's but now for Win10.

carlospc
Автор

Hey MJD... I love these kind of videos, and I love doing retro stuff with modern equipment. I really appreciate your content, and you're always good at providing quality.

So, will the WineVDM launch modern apps from the old interface?

And, I'm assuming it would launch the era-appropriate apps, too, if they were put in folders within the VDM directory structure.

Correct?

redfonzie
Автор

This is bringing back some deep memories from my dad's work computer.

BokBarber
Автор

Sooo....basically I spent ovewr 20 minutes watching you install an OS that does NOTHING!


Brilliant.

eddieoconnor
Автор

Wow.That"s actually very interesting also I like the video alot

PCWindowstechguy
Автор

So it's sorta like Program Manager in Win 3x? I never got a chance to use OS/2 back in the day.

thysonsacclaim
Автор

Nobody:
Michael MJD: Check~ that~ out~

mmmmmmmmicoooooooo
Автор

Why didn't you use a Windows 10 32bit VM to run 16-bit apps?

RodrigoBadin
Автор

write.exe in Windows 10 is in c:\windows, but it just opens wordpad.exe which is in "c:\Program Files\windows NT\Accessories". Perhaps it's somehow able to locate wordpad.exe even though it can't actually see write.exe because of OTVDM.

monkeywithocd
Автор

Just an idea - could you symlink the OTVDM WINDOWS folder to the host folder?

herne
Автор

and i still can't find a 9x taskbar texture for classic shell

aarontrupiano
Автор

Now that 1.4 is running I'd try upgrading to 1.5 (or just copy all the files over from the working Win3.1 installation). Copy over the old accessories exes from the Win3.1 install too?

stevecps
Автор

Thank you for the pointer towards winevdm/otvdm.

zxcvb_bvcxz
Автор

I wonder if it is possible to use the shell elements from windows NT 3.x on windows XP to make it look like windows 3.x..

Bort_