ARCHIVED: In MS Windows 3.1, what causes system resource problems?

Some poorly-written applications will not release all of the system resources they have been using when you exit the application. You can check the Free System Resources figure before and after using an application to see whether this is the problem. Check the Free System Resources figure, then start an application, work in it for some time, exit the application, and then check the Free System Resources figure again. If the Free System Resources figure is not the same as before you started, your application is not properly freeing its resources and it is time for you to call the vendor and complain.

Free system resources are things such as "window handles" and global memory block handles (handle is a Windows programming term, but it is basically an identifier for a window or any other global item). Each window (dialog, icon, memory block, etc.) requires a handle.

Windows 3.0 has a limit of 64K of resources (32,768 handles), and Windows 3.1 has a limit of 128K of resources (65,536 handles). Windows NT does not have a global resource limit.

You cannot increase system resources by just adding more memory; the only real solution is to close some applications if you are running low. Windows 3.0 Program Manager was a resource hog, but the 3.1 version is much better.

The best way to resolve resource problems would be to switch to Windows 95. Windows 95 has a much bigger resource limit, and a separate, huge, resource heap for 32 bit applications. To switch to Windows 95, however, you will need adequate RAM (at least 16 MB) and adequate free disk space. CPU speed (unless you have a 386SX, or a 16 or 25 MHz CPU) should not be an issue.