Edit: I just remembered one of them was "Eye of the Beholder III"
If it's any consolation, you didn't miss much - III was a wet rag compared to the majesty of the first two games!
Edit- Dune 2, not Dune 2000
a rather difficult game.
f16 however was a joy. happy days
Hint: Pentium FPU was faster
Unfortunately the trick doesn’t work on early AMD K5/6 nor Cyrix CPUs - although Cyrix CPUs probably had other more serious problems.
https://www.phatcode.net/res/224/files/html/ch63/63-02.html
Here a non perspective correction related Quake FPU code example https://github.com/id-Software/Quake/blob/bf4ac424ce754894ac...
Lcliploop:
fld ds:dword ptr[0+0+esi]
fmul ds:dword ptr[0+0+ebx]
fld ds:dword ptr[0+4+esi]
fmul ds:dword ptr[0+4+ebx]
fld ds:dword ptr[0+8+esi]
fmul ds:dword ptr[0+8+ebx]
fxch st(1)
faddp st(2),st(0)
fld ds:dword ptr[0+0+edx]
fmul ds:dword ptr[0+0+ebx]
fld ds:dword ptr[0+4+edx]
fmul ds:dword ptr[0+4+ebx]
fld ds:dword ptr[0+8+edx]
fmul ds:dword ptr[0+8+ebx]
fxch st(1)
faddp st(2),st(0)
fxch st(3)
faddp st(2),st(0)
faddp st(2),st(0)
fsub ds:dword ptr[12+ebx]
fxch st(1)
fsub ds:dword ptr[12+ebx]
fxch st(1)
fstp ds:dword ptr[Ld0]
fstp ds:dword ptr[Ld1]
FXCH instruction is free (zero cycles) on Pentium for most instruction combinations, AMD caught up in late 1998 with CXT revision K6-2. http://www.azillionmonkeys.com/qed/cpuwar.htmlWe kind of marveled back then because MHz meant speed.
Some Pentium ran at 60, not 66.
And that's why it's first x86 that was superscalar.
EDIT: Present day, rocking a thread ripper with 48 logical cores. Still running Linux.
It seems Weitek also had a coprocessor to go with 386.
By that era they appear to have mostly pivotted to their own 486 clones and VGA chipsets though.
edit: I just realised, it could have been like the Cyrix 487S which installed as a PCB carrier that plugged into the 486DX socket, and then had a socket on the carrier for the CPU itself, alongside the 487S chip.
Although the infocom 'boot' step suggests a race condition somewhere? Or some register not being properly set by the os.
To be sure, the author should remove and reinstall the coprocessor 10 times, testing after each. :)
When I pushed it into the socket it made such a loud “ker chunk” noise that I wouldn’t want to constantly pull out and reseat these chips. Especially since I don’t have the Intel “rake” like puller I had to use a pair of card edge blanks to gently rock it out of the socket.
Although I do appreciate the 10x humor of it.
It’s weird that so many people focus on the software, which runs perfectly fine in emulation, but seem to lose their minds that an $8,000 machine from 1987 shipped with a buggy CPU…
Hopefully this tbh t will encourage someone out there with a 386 to try to replicate this.
My best guess would be something of the following: The software tries to determine if the CPU has a 80(2/3)87 device some way. Thinks it does have it and then tries a FPU instruction to get the error signal firing and getting the eventual INT02 to blow up in it's face. But I'm not limited by any actual knowledge here so this might just as well be something completely different.
Also it looks like there may be some issues with FP/FP emulation on the OS/2 DOS extender host: https://www.os2museum.com/wp/floating-point-exceptions-and-d...
Poor though my memory is, it happens often enough that I have a decent chance.
There is no problem with the drive on dos, windows or os/2 1.2 so it’s something about it being an early 2.0 beta and probably an older 386 cpu.
I still don’t know why the addition of the math coprocessor helped so much
I have my own story of living happily without a math coprocessor for quite some time: from 1992 to 1997, I had an IBM PS/1000 with a "Blue Lightning" CPU which can be best described as a "486SX3" (25 MHz bus clock, 75MHz internal). Then I tried to run the Quake demo and found out that "real" 3D games need an FPU :(