VOGONS


First post, by Meatball

User metadata
Rank Oldbie
Rank
Oldbie

This post is for the individuals looking to find out if EDO RAM installed on a Sound Blaster AWE32 will work in lieu of FPM 30-pin modules. I had been through the forums, and I had seen all-but-confirmation the modules would work, but I hadn’t read any follow-up for 100% confirmation. You need to do some digging in threads, too, for the discussion.

It works. Set the jumper near the expansion sockets (if applicable), and you’re good to go.

RAM shown (2x):

16MB 30-pin SIMM 60ns EDO 16x8 non-parity

Attachments

Reply 2 of 2, by mkarcher

User metadata
Rank l33t
Rank
l33t

Actually, while I don't think the AWE32 was designed with EDO RAM in mind, it's not that surprising that it works with EDO RAM. EDO and FPM only behave significantly different if you are actually keeping pages open for more than a single access or a single burst. Controllers designed for FPM RAM make EDO RAM cause bus conflicts when a page is left open speculating for further page hits.

A sample playback chip like the EMU8000 might use page mode to fetch four consecutive data samples for the four-point interpolation - but it doesn't use the data bus for anything else while it is fetching the samples, so no chance for a bus conflict. As the EMU8000 processes data in real time, it needs to use timings that work if every of the nominal 32 voices is played from a different page, so there needs to be enough time to close the page used by one sample before the page containing the next sample is opened. There is no potential performance gain that could be realized from page hits - we don't need to be faster than real time. Thus the most simple and straightforward implementation closes the current memory page after each individual voice is accessed, so there will be no conflict between a RAM voice and a ROM voice (which could happen with EDO RAM, if a page were left open).