Mailbag 23/09/2010 – Windows 7 Server Mode

The main problem I have been hearing this week is people using windows 7 as a file server or people trying to access their windows 7 machine in some way from a Windows XP machine. This is fine if the windows 7 pc gets regularly restarted, the reason for this, not fully known to me, is that windows 7 has an issue with memory allocation to system non-paged pool.

You may be getting this error log issued to your event logs:

Source: srv
Event ID: 2017
Level: Error
Description: The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

The fix is just a simple registry change below:

Set the following registry key to ‘1′:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

and set the following registry key to ‘3′:
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

This should definitely sort out the problem, if not please let me know.

I found a fix many months ago unfortunately I am unsure where I got it from, so I am not able to give recognition to the correct person.

Written by

Matthew Glover
Have a question or problem?
I can't guarantee an answer, but I'll try. Drop me a message!


Follow glovario on Twitter

Matt’s Mailbag – Ask me a Question

Inspired by Paul Thurrott’s SuperSite Mailbag, Matt’s Mailbag is a weekly collection of email I receive that I feel may help a wider range of people. I can’t guarantee a response, but if you have a question, problem, or would like to make a comment, please drop me a message.

So if you:

  • Have a question?
  • Got a problem you cant solve?

(And let me know if you’d prefer not to have your name published.)

Send me a message now.

Written by

Matthew Glover
Have a question or problem?
I can't guarantee an answer, but I'll try. Drop me a message!


Follow glovario on Twitter

Is Firefox losing the battle to Google Chrome?

Google Chrome vs Firefox

It’s now just over a year since Google Chrome was first released, back then it was Firefox flying the flag as the alternate browser. Since then it’s all been about Chrome, its update schedule is mighty impressive and new features are almost appearing in front of your eyes. So is it just a matter of time before Chrome starts to eat away at what Firefox has built up over time? Thanks in most part and ironically Google.

When Chrome was first released Google made it clear that it wasn’t going to be competing with Firefox, so Internet Explorer was clearly in its line of sight. Google once said that it really did believe there was room in the market for another browser, many didn’t believe it.

So with perfect timing for the browser ballot window Chrome made very quick gains, Chrome is now at the point where it can make new releases every 6 weeks. Google’s philosophy is if a feature isn’t ready for the next release, it will drop it in to the next release following that, this is allowing Chrome to be released at a much faster pace. This kind of development plan is so quick, neither Firefox nor Internet Explorer can keep pace, I think for almost entirely this reason Firefox will begin to flounder. It might not happen immediately, it might not happen for some time, but it will happen. Even the most loyal of fans will eventually become discontent with the lack of fast paced development. Continue reading

Written by

Matthew Glover
Have a question or problem?
I can't guarantee an answer, but I'll try. Drop me a message!


Follow glovario on Twitter