Dream Machine ( Build your own PC ) Message Board

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.

Pastimes : Dream Machine ( Build your own PC )

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: peter michaelson who wrote (2965)	10/16/1998 9:07:00 PM
From: Spots	Read Replies (2) of 14778

>>system resources? GDI resources (which sounds like what it's usually called but stands for Graphical Device Interface). These resources are grabbed for GUI operations on device contexts. <Something else> resources, which I forget the name of, but where non-graphical operations grab resources (e.g., file opens). User memory, which is otherwise unallocated virtual memory. The first two of these are limited by Windows, and you cannot affect them by adding RAM. The last you can affect by adding RAM and/or by increasing your swap file size. Win 95 greatly reduced the strain on the first two by various fixup strategies, but you can still run it out if you try hard enough. Maybe Win 98 goes further -- I don't know details about Win 98. Also, Win 95 still requires certain DOS resources in rare occasions (yes, the LOW MEMORY stuff) when running legacy programs, but get it low enough and even system programs can fail. NT does not have the fixed limits at all. Spots

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next