I #*(&!%@ hate OS/2 Warp 4!
I've been trying to install it on real hardware (Pentium 200mhz) for a demonstration, and it reminds me how stupid IBM was.
Right off the bat, put the wrong "boot" floppy in the drive an instead of getting a meaningful english "non system disk" type error I just get some crap like "!!SYS49221" that tells me nothing.
Then it makes you load three "boot" floppy disks, which takes a long time as expected, only to make you START ALL OVER if the drive is not already first partitioned!
Of course, it can't deal with an 80GB hard drive on a machine which lacks LBA support. Setup craps itself unless I manually partition it, but not too surprised there and at least that part works.
Then, it appears that if I install networking components on this machine it will crash and burn at startup, with no obvious way to recover other than wiping the drive and starting all over again.
It took quite a bit of retrying to finally get to the OS/2 desktop.
And then, if I run the fixpack directly from a real CD it seems to crap itself and leaves the system in a half updated state, that if course won't boot and forces me to start all over from scratch AGAIN!
Oh, yea, it has a "dual boot" feature that lets you start up in DOS if it was already installed. But it is not a boot manager like most would think of. It is just a pair of programs that renames the boot system files and reboots. Of course, that requires you to fully start OS/2 (or DOS) to run the program. Unless you have read the manual, you would have no idea what program to run under DOS to return to OS/2. If you just happen to guess that it is BOOT.COM in the OS/2 folder, it completely and unhelpfully informs you that you specified incorrect parameter. Turns out the appropriate magic incantation is "BOOT /OS2". I'm supposed to know this how exactly?
It wouldn't be true-blue IBM if it did not make you pull a thick three-ring binder off of a shelf filled with dozens more, and flip through it by numeric code for the answer. :P
I also tried installing in in VirtualBox. A bit less of a hassle, but the boot loader would just sit there for 20 minutes or so before the boot disk or OS/2 would actually start. Problem seemed to go away after the final fixpack was installed. Probably a VirtualBox problem.
Oh, and the sound driver is supposed to be installed after the fixpack.
Of course no one made video card drivers for it, so it's off to the half assed Scitech Display Doctor, which seems to cause OS/2 to hang at shutdown.
Oh, well, I thought I got it all installed and working, only it hoses the hard drive for no obvious reason, it boots but claims the desktop folder is missing. SO I HAVE TO START ALL OVER! Well, this time I thought I was smart and zipped the contents of the hard drive. Unzip over the files... and it still thinks the desktop is missing AND it crashes in a loop.
Ok, so started over AGAIN... this time I wized up a bit more and created a second partition and now I will use Norton Utilites to backup the the primary partion to an image file in the second partion after every tiny step. (at least so far nothing has hosed the partitions and its just keeping it FAT16).
Good thing I did, because after running the fixpack, it wouldn't boot again!
At this point I'm thinking Solaris 8 would be less of a disaster (but not by much).
Edit: Try to work on some VMs on my Windows 10 test box while OS/2 is flopping around, and of course Windows 10 shuts down while I am working on it and decides it MUST do some massive "update" right this moment. I just can't get a break can I? I wonder what features Microsoft has removed now?