A blue screen of death (known as a "Stop error" in Windows NT/2000/XP) is not a WIndows bug. It is displayed when Windows cannot (or is in danger of being unable to) recover from a system error.
In XP-200_NT it occurs when the kernel encounters an error from which it cannot recover. This is usually caused by a driver that throws an unhandled exception or performs an illegal operation. The only action the user can take in this situation is to restart the computer, which results in possible data loss due to Windows not properly shutting down.
In 9x-ME the most common reason for BSOD's is problems with incompatible versions of DLLs. This cause is sometimes referred to as DLL hell. Windows loads these DLLs into memory when they are needed by application programs; if versions are changed, the next time an application loads the DLL it may be different from what the application expects. These incompatibilities increase over time as more new software is installed, and is one of the main reasons why a freshly-installed copy of Windows is more stable than an "old" one. They can also be caused bt ejecting media while it is being read.
>>Date: Wed, 14 Sep 2005 17:27:59 -0700
>>From: Sven-Ove Westberg <[EMAIL PROTECTED]>
>>Subject: RE: [LegacyUG] Memory Hog??
>>Reply-To: [email protected]
>>
>>If you get a BSOD when you run a user program it is a Windows bug, an
>>operating system should protect itself from programs that tries to
>>overwrite the operating system. The program (Legacy) can crash but
>>not the computer.
>>
>>I think it has to do with the size of your data set there are some
>>static definitions in Legacy or any library it use.
>>I have no idea on the Legacy internals but is they use 32bits
>>integers they can only handle +-32000 or +64000 or the libraries they
>>use can only handle that size.
>>
>>Does Legacy works on 64 bit widows?
>>
>>Sven-Ove
--
CoreComm Webmail.
http://home.core.com
- RE: [LegacyUG] Memory Hog?? Randy Palmer
- Re: [LegacyUG] Memory Hog?? J & K Sindberg
