4 ms·
Or installing the coprocessor reseated a slightly-loose cable or created a better connection on a broken trace. The "boot step" could simply result in the syste
by wzdd 3y ago
Or installing the coprocessor reseated a slightly-loose cable or created a better connection on a broken trace. The "boot step" could simply result in the system being warmer, which would make marginal connections like this behave differently.
To be sure, the author should remove and reinstall the coprocessor 10 times, testing after each. :)
- scruffyherder 3y agoI replaced the 386 today with one from 1990. I was able to boot a disk I keep around that has MS-DOS 3.30a and Windows/386 2.11 on it. I also have Battletech on there and yes it ran with no issues! It didn’t work at all on the older processor. 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.