3 ms·
Really? What I was told by various people who tried this is that Intel had no idea how people actually coded for the x86/weren't willing to make segment sizes
by hga 13y ago
Really?
What I was told by various people who tried this is that Intel had no idea how people actually coded for the x86/weren't willing to make segment sizes larger than the original 64 KiB, and the penalty for loading a new segment register was "tens of cycles" per Wikipedia, I've heard on the order of 40 earlier.
So a lot of existing code bases, including a couple I worked on for PCs (Gosling Emacs and a write once filesystem) ran, or would run, fantastically slower in Protected Mode.
Yeah, sure, you could with no small amount of pain write more efficient code for OS/2 1.x, but why bother after Windows 3.x became a big hit?
Oh, yeah, now you're reminding me that the cost to develop for it was $6K for the SDK in 2013 dollars, plus of course a PC-AT with a lot of memory (at least 1.5 MiB, which wasn't cheap back then, nor was the AT).
- yuhong 13y agoThe 32-bit OS/2 2.x and "NT OS/2" was a different story however, and while this decision was made before MS turned this project into a fiasco, this reminds me of how abandoning segmentation altogether and going for a flat address space for OS/2 2.0 and "NT OS/2" was a mistake for security reasons, and I realized that the Morris worm spread around Sept 1988, when both was in development (MS sent the first OS/2 2.0 SDKs to developers at the end of 1989).