Didn't do anything with retro hardware, but instead got to play with some newly acquired retro development software. 😀 Dunno how many other people here are actually interested in old-school DOS coding.

Sure, Open Watcom is a thing and is freely available for download and is probably just better all around ... but I don't care! All the manuals except for the white "Getting Started" one are for Watcom 9.5 unfortunately, but after checking the copies of the 10.0 manuals included on the CD, the 9.5 manuals look to be pretty close overall and certainly will be very applicable. I do very much love me some hard copies of documentation, so that is nice. 😀
I had been using a copy of DJGPP from 1997-98 so far for my DOS coding adventures and have been happy so far. But I do like collecting copies of original development tools. After playing with this for a while, I am unsure if I will switch to Watcom or not. From a purely technical perspective, it makes absolutely no sense to switch at all. The version of GCC that comes with even the older version of DJGPP that I have been using is very good. I've not had many reasons to need to drop to assembly so far to get good performance writing graphics code. However, I do also recall that being a commonly touted thing about Doom's development (which built with Watcom). Anyway it does feel sort of "cool" to me to use the same development tools that a lot of DOS games were built with (that infamous "DOS/4GW" banner ... 😉 ). Also, while the Watcom editor and IDE (they are separate executables!) feels primitive in some areas, the editor is a bit more sane in some other areas that really matter to me compared to RHIDE (the DJGPP editor). Also I was surprised that the 32-bit DOS executable debugging story for Watcom is more decent then I had previously read ... mixed accounts from various forums from many years back, some claiming it didn't work and some claiming you had to start up multiple DOS boxes manually beforehand. It all seemed to "just work" for me when fiddling with some VGA mode 13h toy code and running it through the debugger this afternoon (though it's maybe a bit slow compared to GDB).