Community Page
- KnightKnetwork.com Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- Godaddy drive me nuts. They seem to have a knack of making this more complicated that they should be.
- Great post, really help me alot. Thanks. Cheers, <a href="http://sain-web.com" rel="nofollow">Buit Duit Blog</a>
- Awesome news. I can't wait to get to work on this.
- ffasfasf
- Ah, if you only knew how many commentors are actually getting paid to comment on blogs, you'd be amazed. Some are easy to spot and others are completely legitimate and harder to see. Many...
Jump to original thread »
Old, dead, obsolete computers
Originally uploaded by Extra Ketchup
This is a picture of a HEAP of Desktops. Recently I found out the hard way that Windows XP also has a Desktop HEAP. I recently was upgraded at work to a Dell Optiplex GX620 with Windows XP Pro. I re ... Continue reading »
Originally uploaded by Extra Ketchup
This is a picture of a HEAP of Desktops. Recently I found out the hard way that Windows XP also has a Desktop HEAP. I recently was upgraded at work to a Dell Optiplex GX620 with Windows XP Pro. I re ... Continue reading »
1 year ago
I found the solution here:
http://www.mikedopp.com/archive/2007/07/13/incr...
Everything works just fine with the handle limit. But now some windows seem not update and I would need to Alt-Tab or mouse over parts of it to refresh. It might have something to do with the additional registry mods of the GDI process handle and user process handle limit that was suggested ini the above link.
Are you experiencing any delay in windows re-drawing? If not, then maybe I need to look into those other reg edits.
1 year ago
10 months ago
5 months ago
2 months ago
In particular, this maybe helpful to people experiencing this problem:
"The portion of interest is "SharedSection=1024,3072,512". The three values under Shared Section determines how much memory in kilobytes (KB) is allocated to each component of the desktop heap. At this point, there is a major caveat here: Please do not modify these values on a whim. Changing the second or third value too high can put you in a no-boot situation due to the kernel not being able to allocate memory properly to even get Session 0 set up. Values up to about 8mb are generally safe, but may be pushing it, and frankly settings that high are not usually needed unless an installed program is misbehaving in the first place. We recommend raising these values in 512kb increments and only enough to alleviate whatever problem you are experiencing. "
2 months ago
http://blogs.technet.com/askperf/archive/2007/0...