resources?

in XP. Definitely far less a factor, because XP controls the assigned resources [memory] far better. [in 9X and ME it was 64K that set the limit, even though 98 and ME had added another MB for resource use]

In the case of XP though, in order to allow the system to perform faster than a snail, MS still allows some software to run at the kernel level, where the software assigns its own memory amounts and establishes its own range. Thus it is possible for poorly written software to be a resource hog, and have XP not have enough memory to perform an additional function. Basically it will try to use the paging file, but it can run out of that also.

Windows controls memory use for software installed at level 2 of the CPU.

But the problem is still caused by too many programs open at one time, and the solutions the same, except that in some cases more memory or more page file space CAN help.

One way to lose resources is to open a program and close it before the program gets loaded completely. In this case the memory resource it took does not get returned for use.

Its a free program to control what starts when windows does. Right click on an entry and it will google it so you can see if you need it to run or not. Good luck

device drivers run in kernel mode along with the microkernel itself but their memory allocation is through the Windows executive.

Software applications run in user mode and in protected memory so they can't crash the system.

"Too many windows open" will not cause a resource problem, it will only cause a slowdown due to the memory/disk bottleneck when paging into and out of the virtual memory.

Excess processes might cause a slight slowdown but normally the only problem is when a poorly written application gets greedy about CPU cycles and doesn't allow preemption.

You can verify that using sysmon and perfmon.

Startup and shutdown do take longer as you add services or startup applications or applets but system resources is not a problem.

that some app's DO run at kernel mode and DO have the ability to change the memory amount and boundaries after MS assigns them. Nothing that I have ever done with a system could be used to stress that.

Also saw an article somewhat related in the knowledge base with a networking example where a system in a network could report low resources because of insufficient memopry.

The slowdown can get slow enough to not allow starting another process at points in time as far as I could see.

Since there are resources other than memory, it could be caused by them I guess.

It seems to say that since each app could ask for 2 GB memory minus the bottom and top 64 it looks as if in an extreme case the system can actually run low enough on resources at moments. Especially in a system with low amounts of memory.

And of course, where would such a message regarding low resources come from, if not from the Op Sys.
Noticed this reply late.

Will try to find more tomorrow or so.

1. The article "Q194924" explains that it is unlikely that a single 16-bit program will exhaust any one particular type of resource within Windows XP, but if enough 16-bit applications are running in a single Virtual DOS Machine (VDM), it is possible that they will collectively exhaust available VDM resources.

2. Let's be clear about using the word resources by reviewing the Microsoft Knowledge Base article, "Explanation of error codes generated by Device Manager (Q310123)" that may identify something eating them.

3. [Driver Verifier] checks Driver unload to catch drivers that unload and do not clean up resources used (which increases the possibility of a system bug check shortly after the driver unloads). Resources that the driver may not delete include look-aside lists, pending deferred procedure calls (DPCs), worker threads, queues, timers, and other resources. Substandard, or drivers which simply do not work should be upgraded or at least reinstalled.

4. Supplemental reading, "Invalid Universal Plug and Play Request can Disrupt System Operation (Q309073)."

hadn't read it in a while, so re-read it. Yes all the apps run in User mode, however they can ask for memory at any time [up to the 2 GB memory LOL] and the Op Sys will provide it EVEN IF there is actually none available. The Op Sys relies on using the virtual mem/page file to cover the shortage.

I had been trying to find the XP error reports that refer to resources and memory shortage. Never saved them because I had no real interest, Good ole texas Bill gave the link that shows the ones that I had read about before. Codes 3 and 12

All the original newbie poster said was "My resource usage went up so high that I couldn't load a web page". Without saying what resources, how he measured that they were high and what happened if he tried to open a webpage (system halt, error message, just a one minute delay with heavy disc traffic) it's clearly impossible to pinpoint the problem. Even the term "opening a webpage" doesn't say much. It could mean starting IE or Firefox, opening a new tab or window in a browser or loading a new page over the current page, which is the most common operation.

All one can say that there is probably some overload on the system. It won't harm at all to look at the start-up programs, as the poster did. But it's not sure that it will offer a full or even partial solution.

Resources, of course, is a very general term. My manager, talking about resources, means people and money for a project. Windows 95/98/ME mean some very specific 64 kB area of memory. Anybody writing any program giving an error message about resources can mean anything: it probably means he got some unexpected error message. Probably a lazy programmer not taking the time to program a more meaningful error message.
Again, one would have to know the details to say anything sensible on the cause. And probably have a look at the system also.

That's my opinion anyway.

Kees