On 30 Oct 2002 at 14:51, David H. Bailey wrote: > Actually, not knowing how Macs operate internally I can't be sure, but > on Windows systems, no matter how much memory the machine might have, > there is still a small block reserved for actual program operation and > OS overhead, and when that gets used and not returned to the system > properly you get these messages. Good old Microsoft! Their slogan > should change from "Where do you want to go today?" to "WHERE did you > say we should go?" or "If we made it work properly the first time, we'd > be out of a job!"
The resource stack limitations of Win3.x and Win9x versions of Windows are long gone in the NT-based versions of Windows. However, one can still get "out of memory" errors (masking an actual "out of resources" problem) in them from really badly behaved programs that fill up the message queue or leave some huge block of memory improperly allocated. Generally, killing the offending program gets you back to normal. But occasionally one has to restart the GUI by logging off and logging back on. I've never had this kind of thing require a complete reboot in an NT-based version of Windows. -- David W. Fenton | http://www.bway.net/~dfenton David Fenton Associates | http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://mail.shsu.edu/mailman/listinfo/finale
