Hello, I changed my mother board PEG I to PEG II last week and I'm
having some memory trouble.

Sometimes MOS doesn't boot after the quark kernel charged.
sometimes, when I run Quake I or Quake II, there's a message telling :
cant allocate memory.
After a reboot, it works.
I use stateline and it tells me I have more than 180 MO when I run
this games.
I have 1 module 256 MO ECC from samsung.

help please .?

[ Edited by serge on 2004/11/7 13:22 ]

@Serge:

Change you memory module.

Run several "memtest EXTENSIVE" to be sure your nrw module is safe. You may want to buy this new one from a Pegasos dealer.
Also, there are some memory module compatibility on MZ.

Bye

@ NicoPPC: which memory test can I use ?
thanks

Hello Serge,

On your Morphos 1.4.2 cd and on your system partition memtest is present in the directory MorphOS/c. To use it open a shell and type "memtest EXTENSIVE" or "memtest EXTENSIVE REVERSE" to verify your memory module(s).

Brumiga

OK so,
since I removed one memory module, my peg is more stable, but it
continues to do strange things about memory.

I did a lot of memtets succesfully with only 1 module, so I use this
module.
But sometimes, morphos dont want run more appplications. Stateline
tells me I have more than ›150 MO free.
at this moment, I do a memtest and have a strane result.

Tests done with succes and without trouble take more than 10 secondes
to do and this is the output :
New Shell process 5
Ram Disk:> memtest EXTENSIVE
Allocated memory at 0x213EAF70 -> 0x2DC676AF, 210224960 bytes
Writing 0x00000000... 473 MB/sec.
Verifying 0x00000000... 221 MB/sec.
Writing 0xFFFFFFFF... 476 MB/sec.
Verifying 0xFFFFFFFF... 221 MB/sec.
Writing 0xFFFF0000... 475 MB/sec.
Verifying 0xFFFF0000... 222 MB/sec.
Writing 0x0000FFFF... 476 MB/sec.
Writing 0x55AA55AA... 474 MB/sec.
Verifying 0x55AA55AA... 221 MB/sec.
Writing 0xA5A5A5A5... 474 MB/sec.
Verifying 0xA5A5A5A5... 221 MB/sec.
Writing 0x5A5A5A5A... 475 MB/sec.
Verifying 0x5A5A5A5A... 221 MB/sec.
Memory is ok!
Ram Disk:>

I cut a prt of it because it's long.

When I have problems, the test is done in 1 seconde with this output :

Verifying 0x00FF00FF... 305 MB/sec.
Writing 0xF0F0F0F0... 609 MB/sec.
Verifying 0xF0F0F0F0... 309 MB/sec.
Writing 0x0F0F0F0F... 608 MB/sec.
Verifying 0x0F0F0F0F... 309 MB/sec.
Writing 0x55555555... 606 MB/sec.
Verifying 0x55555555... 254 MB/sec.
Writing 0xAAAAAAAA... 589 MB/sec.
Verifying 0xAAAAAAAA... 296 MB/sec.
Writing 0xAAAA5555... 610 MB/sec.
Verifying 0xAAAA5555... 307 MB/sec.
Writing 0x5555AAAA... 609 MB/sec.
Verifying 0x5555AAAA... 313 MB/sec.
Writing 0xAA55AA55... 619 MB/sec.
Verifying 0xAA55AA55... 310 MB/sec.
Writing 0x55AA55AA... 600 MB/sec.
Verifying 0x55AA55AA... 297 MB/sec.
Writing 0xA5A5A5A5... 602 MB/sec.
Verifying 0xA5A5A5A5... 307 MB/sec.
Writing 0x5A5A5A5A... 611 MB/sec.
Verifying 0x5A5A5A5A... 310 MB/sec.
Memory is ok!
Ram Disk:>


It tells me memory it's ok, but the duration test is 1 seconde and
programmes dont run
help

Welcome to the club. I am using a Samsung HD and got problems. Also, I have TwinMOS which I think my MorphOS freezes.

My mos freezes when using ANY software that using sound. And dont tell me to install new or older AHI. Because I've tried everything :)

Maybe there is just something scary with Samsung HDs and PegasosII. Does this error come in Linux too?

My MorphOS freezes without notice, and now I am finally going to do something with it.

Cheer up,.. just try to replace your Samsung membrick with something else. hehe :) I am going to switch from Samsung hardware completely very soon now.

Regards,
Michal, www.amitopia.tk