mkarcher wrote on Yesterday, 16:34:
I wonder who could make use of a 386 processor, but considered Hercules graphics sufficient. Classic Hercules cards are 8-bit cards and do not even manage to run without extra wait-states in a 4.77 MHz PC/XT.
Hi, I assume that DESQView+QEMM, DESQView 386 or Windows/386 or CEMM could have utilized the the 386 that early.
PC-MOS/386 also existed by 1987, but it was rather niche maybe. It just comes to mind because my father had it..
Concurrent DOS and Xenix had 386 versions, too but I have little experience here.
By late 80s, AutoCAD had 386 versions available, I think.
The DOS Extra Magazine does list Windows 2.03 and Windows/386, at very least.
But to be honest, I assume that the average user simply wanted an 386 in first place because it had offered noticeable better performance. 😟
The enhanced MMU and V86 were next on the wish list, maybe.
286 with 512 KB RAM? In 1988? Seriously??? What a beautiful machine for the brand-new OS/2 1.1, with Presentation Manager! 🤣
Hey, the Magazine wasn't called "DOS Extra" for nothing! 😃
It it was about OS/2, it'd been called "BS/2 Extra", after all! 😉
Seriously, though. As-is the models shown wouldn't have run OS/2 Presentation Manager anyway because IBM refused to support Hercules graphics.
Microsoft by contrast did support Hercules in Windows/386, for example.
Speaking of OS/2 1.1, it also ran on 386 systems, but there were differences between IBM and MS releases.
And tzere were different editions. Standard, Extended etc. Some might have needed 286 or 386 to run properly.
The HPFS 386 filesystem driver needed an 80386, for example.
The whole LOADALL vs LOADALL386 differences might have mattered, too.
AFAIK the average 80386 chip didn't have normal LOADALL instruction of the 80286 anymore (for security reasons), so the AT 386 BIOS emulates it for software requiring it.
However, if an OS is not running in Real Mode but Protected-Mode that emulation may or may not work?
An AT with an 386 CPU upgrade doesn't have LOADALL emulation, either, maybe.
Because, I assume, the AT BIOS is unware of the situation and treats the 80386 like an 80286.
PS: My apologies for being a bit off-topic. I didn't mean to de-rail the thread here through my replies.
It's just that I got a little bit carried away. I hope the OP doesn't mind.
"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//