Post by Larry Walters on Jul 20, 2008 8:48:04 GMT -5
zombo
post Jul 18 2008, 04:53 PM
i don't know if this has been posted before but for those with 1g of memory, they can set the memory - maxblocksize in nr2003 to 1048576 but you have to change the poolsize to the same value and it won't crash. i guess this will work with 2g memory too. i don't know the value for 2g though. i guess you would just double this value. just make sure the poolsize is the same value. i done this on 2 systems without problems.....
backstop
post Yesterday, 10:37 PM
This fixed my 'unable to load replay' problem. Running a dual core athlon with 4mb of memory. I think I set it for 3mb worth, and nothing but smooth sailing thus far.
Without this change, I don't think NR03 was recognizing how much RAM my system has, and my replays were limited to about 28 min. If I tried to add to the ReplayMemOveride, I couldn't load a track.
post Jul 18 2008, 04:53 PM
i don't know if this has been posted before but for those with 1g of memory, they can set the memory - maxblocksize in nr2003 to 1048576 but you have to change the poolsize to the same value and it won't crash. i guess this will work with 2g memory too. i don't know the value for 2g though. i guess you would just double this value. just make sure the poolsize is the same value. i done this on 2 systems without problems.....
backstop
post Yesterday, 10:37 PM
This fixed my 'unable to load replay' problem. Running a dual core athlon with 4mb of memory. I think I set it for 3mb worth, and nothing but smooth sailing thus far.
Without this change, I don't think NR03 was recognizing how much RAM my system has, and my replays were limited to about 28 min. If I tried to add to the ReplayMemOveride, I couldn't load a track.
