Skip to main content
Home Forums System 7.5 memory issue System 7.5 memory issue
Thread

System 7.5 memory issue

System 7.5 memory issue Hardware 7 posts Oct 22, 2008 — Oct 22, 2008
I'm going to go ahead and admit there's some voids of my knowledge about the classic macos. What I have is a quadra running System 7.5 who's system software is using over 33mb of 36 available and won't launch word citing not enough memory. it can't be too complicated. Is there too many extensions messing things up? How do you terminate programs that launch on start?

thanks

What I have is a quadra running System 7.5 who's system software is using over 33mb of 36 available
That is definitely wrong. You can run 7.5 on a box with 4Mb.

Is there too many extensions messing things up? How do you terminate programs that launch on start?
Are there too many....

(a) Go through extension manager and disable all the cruft you don't need.

( B) Confirm you don't have a RAM disk.

© Use the Get Info to see how much memory Word actually needs.

(d) See if changing the screen resolution makes a difference.

(e) Look in the startup folder in the system folder and remove applications you don't need.

I'm going to go ahead and admit there's some voids of my knowledge about the classic macos. What I have is a quadra running System 7.5 who's system software is using over 33mb of 36 available and won't launch word citing not enough memory. it can't be too complicated. Is there too many extensions messing things up? How do you terminate programs that launch on start?
thanks
That sounds the usual for a system not running in 32bit mode.

Turn 32-bit addressing on in the memory control panel ( looks like http://vectronicsappleworld.com/collection/articlepics/maciisi/memory.jpg ) then reboot, and you should get all your RAM.

Dana

If that fails reset your PRAM, which will remove any ram disk if it somehow was present.

It's almost certainly the case that you aren't running in 32-bit mode. Just turn it on, reboot, and all will be well, I betcha!

Check the disk cache in the memory control panel too

Cough... and check the PRAM battery voltage, which is where it all possibly started.

mp.ls