[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
rSounds - affect on available free memory
Ever since System 6.0, the 'Sound' CDev/Control Panel has
allowed users to assign digital sound effects to system events
(using rSounds). All very nice, but I noticed that once a sound
is assigned and loaded into memory, that memory becomes reserved
and leaves you with less free memory for applications. Or at least
the Finder reports this when selecting "About this Apple IIgs".
I also noticed that any sound assigned to 'Startup Sound' (which
is used _once_ when starting GS/OS) is taken and never given back.
If your startup sound is 2MB in size, you'll have 2MB less available
free RAM.
Are there any patches to change this? Perhaps something which
would have GS/OS only load sounds _when_ an event occurs and then purge
it from memory. I would think my hardrive and RamFAST would be quick
enough where there wouldn't be much of a noticable delay. In the
meantime, I've avoided the use of rSounds for system events (expect
one: a small sound for the system-beep) because it quickly eats _much_
of my available memory and even adds a few seconds to my boot time.
I can understand using up memory on DAs, INITs and Finder-Extensions,
but for some cute sound effects...? If I'm not mistaken, even Mac
System 7 and Windoze 95 (which have a similar feature) do not lose
any or much RAM for system event sounds.
Mitchell Spector
spec@vax2.concordia.ca