Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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: dav who wrote (42008)	4/13/2000 11:07:00 PM
From: david_si	Read Replies (2) \| Respond to of 74651

"What do you mean completely solved by Windows2000?" When you get those memory access violations, or exception faults, it's because the program you're running has a bug, in that it tried to access an old memory address, or memory being used by other parts of the system. In Windows 9x, such a bug would sometimes crash the system and require a reboot because the program being run could have overwritten the memory of another program. In all cases, such a bug crashes the program being run. In Windows 2000, specific memory ranges are given to each program, so that programs can only access their own memory space. If a program has such a bug as mentioned above, you'll still get the error about a "memory access violation," but the bug will not affect the stability of the operating system or other running programs. No reboot will be required. I've always thought Microsoft should rename this error message to clarify that the problem was with the application being run, and not the operating system. "Access Violation" doesn't clearly identify the problem, or give users knowledge about how to fix it.