SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?


To: david_si who wrote (41993)4/13/2000 9:46:00 PM
From: dav  Read Replies (1) | Respond to of 74651
 
What you mean "completely solved by Windows2000" ? How can you be so sure unless Microsoft has removed that window and that error message from WIN2000 and give it a different name.

eom



To: david_si who wrote (41993)4/14/2000 6:45:00 AM
From: SunSpot  Read Replies (1) | Respond to of 74651
 
Then why does my Windows 2000 crash quite often? OK - I'm running software on top of it, but I thought Windows 2000 should be able to run software without crashing itself?

One of the times it crashed was because I was looking on a web-page with several MBytes of JPEG graphics. The web-page designer designed it so that it was HTML tags that resized the pictures. When Windows 2000 had allocated approx. 250MB of memory for Microsoft Internet Explorer alone Windows crashed... (I found out by trying again). I could only view the page using Netscape. The page was dybdahl.dk but the page has been redesigned now to have smaller image files.

Additionally, certain games also makes Windows 2000 crash. But OK - Windows 2000 isn't meant to be used at home. Especially a game named "Half-Life" gives trouble - and the Windows version (!) works fine with Linux on the same machine, even with OpenGL hardware accelleration.

So as long as you don't play games and don't surf the internet, the operating system stays cool and the process list works. If you play games or surf the internet, you might use the reset button. I wouldn't call that "completely solved".