SE/30 Death Chimes after enabling Virtual Memory

[andyretro]

Hi Everyone,

I am trying to enable MacSSH on my SE/30 so I can use it as a terminal! I'm running OS 7.1 so need some extras. I've added the Thread Manager extension, "upgraded" the HD with Apple HD SC Setup (whatever that means), and then enabled 10M of Virtual Memory per


But now, I get chimes of death!! Can I disable virtual memory at boot time, or is my SE/30 an ex-SE/30? :s

Cheers,

andy

 

[andyretro]

Fixed it.

After boot chime, quickly held down ctrl+option+command+reboot, then press shift very fast so you start without extensions.

Then, revert the virtual memory change, and I'm back to normal.

Now to get MacSSH running...

 

[Daniël]

Instead of mucking with Virtual Memory, you can always upgrade the memory of your SE/30. Remember, with MODE32 or a clean 32-bit ROM (I'd recommend a custom ROM solution that allows you to bypass RAM-check-on-boot), this beast will take 128MB!

 

[Franklinstein]

So basically it sounds like it works, then you enable virtual memory, reboot, and instant death chimes? Then a PRAM flash with no extensions makes it work again? Or am I missing a step here?

I don't know if there's a ready way to run a diagnostic to test the MMU, or even anything outside of VM or RamDoubler that bothers with the MMU.

Try a fresh OS load on another drive. If it keeps having problems with VM or RamDoubler or whatever it's possible that there's a fault in the processor that affects the MMU section.