This means that, under the licensing policy, a dual- or even quad-core processor counts as a single processorsomething that confused many people in the early days of dual-core technology. Knowing that, the limit of the number of processors is determined by your version of Windows XP. If you're not sure which version you're running, check the sticker on your computer.
It will say the version there beside your license key; you may right-click "My Computer" and click "Properties. The Home edition of Windows XPthe edition that came with most machines home users bought from the likes of Dell and HP, before Windows Vistasupports only one processor. This means if you want to install more than one processor and you run Windows XP Home, you may need to switch to Professional, or upgrade Windows to a newer version with support for multiple processors.
If you want to use two processors, Windows XP Professional is the way to go. While this advanced program cannot run more than two processors, this is an improvement over Home. Note that, because dual-core processors count as a single processor, you could theoretically have four cores with this license or even eight, if you are willing to buy two quad-core processors.
For example, drivers could map the "lost" memory regions located above 4 GB and expose this memory as a RAM disk. Physical Address Extension. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful?
Connect and share knowledge within a single location that is structured and easy to search. I understand that the answer to this question may depend on registry settings and on the version of Windows, and perhaps on the amount of RAM if there is not enough memory.
If an application 3rd party application in this case leaks handles at a few hundred an hour, how many total handles can that application leak before other applications will run into troubles? By "troubles" I mean, for example, fail to start a thread, fail to open a file, and so on. I've seen some servers lightly loaded run just fine with a process usually a database process using a few tens of thousands of handles, so the old handle limit is clearly not the issue here.
And that was a per-process limit anyway, so wouldn't affect my application which is well under that point. Can someone either answer the question or point me at some resources that explain about how many total handles a Windows server will allow before you effectively run out of handles or other system resources?
See Raymond Chen's post on this topic. The window manager enforces a limit of 10K per process, and has a total limit of 32K across the system. So if it "only" leaks handles per hour, then you have a few days of uptime before it starts misbehaving. Note that not all handles are equal. Window handles are not DB handles, for example, and may follow different rules.
So this restriction might not apply, depending on what sort of handles the program is leaking. Also read this blog post. The desktop heap , which is a pool of memory where the real "stuff" the handle represents lives. It's sometimes not so much how many handles you have allocated but how much memory each object under that handle is using. You can debug the heap this way. With your subscription - you'll gain access to our exclusive IT community of thousands of IT pros. We can't always guarantee that the perfect solution to your specific problem will be waiting for you.
If you ask your own question - our Certified Experts will team up with you to help you get the answers you need. Who are the certified experts? How quickly will I get my solution? We can't guarantee quick solutions - Experts Exchange isn't a help desk.
We're a community of IT professionals committed to sharing knowledge. Our experts volunteer their time to help other people in the technology industry learn and succeed.
0コメント