"0_Qed" wrote:
|
| Hey Jef ,
|
| Going back to the OP's original post ...
|
............................................................................ . | I recently installed more memory on my VP6 Motherboard. I now have 1 | 128MB, and 2 256MB modules. Since the installation, my system has been | randomly locking up on me. Usually when doing something involving | music, java, or flash. A hard reset is required. | ............................................................................ . | | His/her 'text' suggests that there mite be a mem module construction | mis_match | which causes the random lockup ... I'd =guess= at the 128MB module ... | | A 'lockup' is suggestive of a hdwr glitch | as opposed to | a 'parm glitch' causing an err msg ... | | Generally not a good idea to mix-n-match mem module construct types. |
Good point. Perhaps a good test would be to attempt to boot the board with only the new memory to ensure that it's good. Boot again with only the original memory to ensure that it's still good. If they don't play nice together... you've got your answer.
| btw ...
| as the Careful Conservative Craftsman that I am ...
| as opposed to being a Niggling Nitwit Nitpicker ...
|

...
| I think I found, & used, an obscure 'ref' that suggested that | "one" mite use MaxFileCache=600000 as a V_Mem limit ... | not a M$ ref , 3rd party as I recall .
I've seen the "fix" listed as MaxFileCache=500000 a few times... but never
600000. That defeats the fix since 600000 is more than 512 megabytes.
|
| Qed.
|
| PS- I hope Jerry P's new thumb-lock 'tether' isnt all that contrictive | ... | . I hate to see "things" atrophy, dry up, turn blue, & fall off. | . Besides, ... hes no good as a soprano.
You know... Jerry must be very durable given that he's been taken on by a very strong woman. I'm sure he sings soprano quite often for her.
On the other hand, imagine she ties him in the yard by his thumb-lock tether... just like the dog, he gets himself all tangled up around the spike he's tied to.
Jef