Re:NeXTstep Manual, Systems Programming with Objective-C and...
by pjmlp on Sunday June 05, 2016 @10:35AM
(#11841160)
Lack of user accounts meant we could kill user32.exe, that had to be followed up by a reboot.
[ Parent
| on HN ]
Re:NeXTstep Manual, Systems Programming with Objective-C and...
by justin66 on Sunday June 05, 2016 @11:20AM
(#11841411)
It'd be interesting to go back and run some of the software from the Windows 95 era (and the OS) on a higher-quality machine. I and most of my friends were using low-quality 486s and Pentium clones and it's certainly possible a lot of the problems had to do with hardware quality.
I honestly remember the later Windows 98 experience as being almost crash-free, and since the architecture was basically the same a lot of that probably has to do with higher quality hardware (and better drivers, of course). That was the golden time of the Intel 440lx and 440bx and ECC RAM support on desktop motherboards, when just about every blue screen could be attributed to those newfangled AGP graphics accelerators...
Re:NeXTstep Manual, Systems Programming with Objective-C and...
by kijiki on Sunday June 05, 2016 @07:44PM
(#11843765)
If your PC is faster than a certain speed Win95 won't boot.
This bit us at VMware, since it was common to want to run old Win95-only software in a VM on fast machines. We ended up having the VMM (Virtual Machine Monitor) patch up the bug when it did binary translation.
Re:NeXTstep Manual, Systems Programming with Objective-C and...
by justin66 on Sunday June 05, 2016 @09:36PM
(#11844131)
> If your PC is faster than a certain speed Win95 won't boot.
That's interesting. What's the threshold there?
Re:NeXTstep Manual, Systems Programming with Objective-C and...
by gattilorenz on Monday June 06, 2016 @06:23AM
(#11845682)
300Mhz. But you can work around that...
http://virtuallyfun.superglobalmegacorp.com/2011/01/10/windo...