Has anyone tweaked the IOPageLockLimit setting?

"The Default is When IOPageLockLimit =0 is 512 KB" - from Microsoft

Doing a google search I found many recommendations for increasing the
IOPageLockLimit but they ALL included a table of values that gave a smaller
value than the default.

At their suggestion I tried 40000 HEX (262KB ) it worked for a while, then
Outlook and IExplorer started to have intermittent errors.

I reset the values and IE and Outlook began operating correctly again.


Respectfully,
Richard

"Richard -" <rich44@aa9kz.com> wrote in message
news:esUpmkRwFHA.3860@TK2MSFTNGP09.phx.gbl...
>
> Has anyone tweaked the IOPageLockLimit setting?
>
> "The Default is When IOPageLockLimit =0 is 512 KB" - from Microsoft
>
> Doing a google search I found many recommendations for increasing the
> IOPageLockLimit but they ALL included a table of values that gave a
smaller
> value than the default.
>
> At their suggestion I tried 40000 HEX (262KB ) it worked for a while, then
> Outlook and IExplorer started to have intermittent errors.
>
> I reset the values and IE and Outlook began operating correctly again.


I just discovered I had RAM faults. Changing the IOPageLockLimit changed
RAM usage and that is why I may have been getting errors.

Sorry about jumping gun.

> Respectfully,
> Richard
>
>
>
>

In microsoft.public.win2000.registry Richard - wrote:

>
> "Richard -" <rich44@aa9kz.com> wrote in message
> news:esUpmkRwFHA.3860@TK2MSFTNGP09.phx.gbl...
>>
>> Has anyone tweaked the IOPageLockLimit setting?
>>
>> "The Default is When IOPageLockLimit =0 is 512 KB" - from
>> Microsoft
>>
>> Doing a google search I found many recommendations for
>> increasing the IOPageLockLimit but they ALL included a table of
>> values that gave a
> smaller
>> value than the default.
>>
>> At their suggestion I tried 40000 HEX (262KB ) it worked for a
>> while, then Outlook and IExplorer started to have intermittent
>> errors.
>>
>> I reset the values and IE and Outlook began operating correctly
>> again.
>
>
> I just discovered I had RAM faults. Changing the IOPageLockLimit
> changed RAM usage and that is why I may have been getting
> errors.
>
> Sorry about jumping gun.
>

Thanks for posting the follow-up!