Shponglefan wrote on 2024-11-20, 14:19:My own experience with building 286 machines (including recreating our first computer ever) was that once the nostalgia itch was […]
Show full quote
RetroPCCupboard wrote on 2024-11-20, 13:43:
Of course there are likely some games from that period that I will want to play, that will be too fast on the slowed MMX. I am honestly torn. Part of me wants a 286. Part of me thinks it will be more hassle and money than it is worth. Prices on ebay seem rather high for these.
My own experience with building 286 machines (including recreating our first computer ever) was that once the nostalgia itch was scratched, I didn't have much use for it beyond that.
This is where you need to figure out was is driving that want. If it's just to play certain games, as you said, the games you want to play can run on faster systems. If it's just the nostalgia of using a 286 again, once that is satisfied you may find yourself not really wanting to use it anymore.
There are also some other options than just a pure 286. Some 386 and 486 systems can be natively throttled to 286 speeds. For example, I have a 486 DX-33 that can throttle to an 8MHz 286 using the turbo button plus L1 cache disabling.
There are also Tandy 1000 XT/286 hybrids (e.g. Tandy 1000 TL series) that are interesting machines. They include native Tandy sound support, which is useful on a variety of games including original Sierra adventure games. This can offer better sound than just the PC speaker.
I find real 80286 PCs quite interesting, though.
The original IBM PC/AT was a real 16-Bit computer, for example.
The PC/XT still was an 8-Bit design, as far as motherboard hardware was considered.
ISA bus and AT-Bus are natively being supported, more or less. Depends on how the chipset interferes, if it is used.
The 80286 also is free of V86, so hardware solutions for UMBs and EMS must be used.
Which are less of a headaches in terms of compatibilty, once acquired. ;)
Looking back, I'm somewhat grateful to initially have missed out on 386+ and all the headaches that came with V86 memory managers.
Not that they're all bad (Helix is cool, I think), but stability was better doing things the proper way.
Which had been a necessity on an pure 16-Bit system.
Windows 3.1x in Standard-Mode ran rock-solid, too.
The krnl286 didn't load any VXDs and didn't virtualize PS/2 keyboard and mouse.
I barely had seen blue screens back then, whereas it was more common to users of 386 Enhanced Mode (or 386 Enchanted Mode, as I used to joke). :D
PS: That being said, I've collected quite a few 386 components for later life.
The 80386 was the brother of the 80286 and made by same team.
Some rumors even say that the 80386 design is older than that of the 80286, but couldn't be made a reality in early 80s.
That's why the 80286 was released as we know it. Not sure if it's true, but it's a fascinating thought!
Also, last but not least, the 80386 was very legendary in the 80s.
The Compaq Deskpro 386 introduced it in 1985 and many higher end software products supported it. Such as Windows /386, for example! 😂
Seriously, though, 386 extenders were a thing by turn of the decade.
Profesional Windows 3.0 applications had used Watcom's Win386 extender early on and required a 386 PC, thus.
Thinking about this, it seems very funny that many of us nowadays aim to run Windows 3.0 in Real-Mode on an PC/XT (me included).
Back in 1990, IT people would have either thought we're crazy or just poor.
Because, serious Windows 3 software development had required a hot-rod 286, at least.
The compiling times alone were very long due to be being very CPU intensive for commercial applications.
A 386 with lots of cache, a quick HDD and a large HDD software cache was heartly welcome!
"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel
//My video channel//