Quote:
Originally Posted by ApK
"General Protection Fault" was the wording IIRC.
|
Ahh... you brought back memories. UAE became GPF (and "Illegal Instruction Execution Error"). UAE was more fun because we used to say "Windows UAE'd on me again!" (pronounced "yoo-ee"). Because UAEs were typically caused by programs writing on memory that did not belong to them, renaming actually made sense, but marketing made it sound like they actually fixed something...
You could also get UAEs by executing data (which was renamed to "Illegal Instruction Execution" error). Back in those days, the MS C compiler was horrendously expensive and often generated bad code, so everybody but microsoft used borland turbo C. Many windows errors were no doubt caused my microsoft using their own compiler to build it.