by vermis_rex » Tue Feb 27, 2007 11:51 pm
Hmm... hadn't thought about it myself, but this raises an interesting point.
OK, if you look through the EOS manual (post 4.0), on page 64 there's the definitions of the memory statistics that appear on the Master screen (Resident, Preset, and Sample).
According to the manual, "Resident memory... shows the amount of preset memory available for the optional ROM or Flash RAM banks." What does that actually mean? Damned if I know... if you had an E-synth, I think that's where it would store the preset data to go with the samples in the 16mb sound ROM. Now, you might (and I can't quote you a reference on this theory, since the explanation of the various memory types in the manual are difficult to follow at best) be able to store some preset data that points to samples on your hard drive, and it would be battery backed preset memory, meaning it would be there when the system powered on (but the samples from the hard drive still have to be loaded into sample RAM... it's really much more useful if you have a sample Flash RAM or sample ROM installed, since then the samples are accessible on start up too). I haven't tried this, experiment at your own discretion. The manual does suggest using that memory to store templates of presets you might create (see EOS 4.0 manual, page 30).
None of this is helped by the fact that the manual seems to use three different terms to refer to what appears to be the same memory (CPU Flash, Preset Flash, and resident memory... not to be confused with the four other types of memory you might have... again, see page 30).
As for your preset memory... don't forget to go into the Master>Setup>Memory menu item and jiggle around the balance of preset to sequencer memory. If (for example) you're not going to use the on-board sequencer, might as well allocate no memory or the bare minimum to sequences.
If I remember right (and there's no guarantee that I do), the memory upgrade was to handle the larger 4.0 and after EOS, and doesn't actually increase your preset memory at all. Yeah, it is a limitation at times... there are some ESi banks from the Formula 4000 E-mu CD-Roms that I can't load because I run out of preset memory on my e6400 classic (although I can break the large banks down into smaller ones by loading the presets one by one... not ideal, but you only need to do it once and save the resulting smaller banks on a hard drive)
You might just have to make do with smaller banks of fewer presets.
After installing 4.62 and initializing the EEPROM and recalibrating, you just have to go through the Master>Setup items the make sure they're set the way you want (for example, I think initing the EEPROM throws out the "avoid SCSI host on ID" setting).