Originally posted by Darkstar: Any ideas about the startup sound? I couldn't find it in any of the ROMs, so does anyone have a clue where it might be? I'd really like to ditch my self-recorded version because it sounds so crappy
I fear it might be in some other ROM or, even worse, in a chip that cannot be accessed by the system but only by the sound processor.
The sound is always in the boot PROM, it's a matter of whether or not it's in a known format or not. The Indy, Indigo 2 (non-Impact, that is), and the Octane store the startup, shutdown and error sounds in a semi-standard ADPCM format. Load the ROM up in GoldWave as a 44khz ADPCM file, and in amongst all of the garbage from trying to decode data will be the three sounds strung together. No guarantees for other systems, though - the IRIS Indigo has a programmable DSP for sound, so there's no telling what codec it uses (it's not u-Law, A-Law, PCM, or ADPCM, though), and both the Fuel and the Indigo 2 Impact don't use any encoding that I was able to figure out, either.
Originally posted by Darkstar:
P.S.: I might be able to dump an Octane and/or O2 PROM too in the near future. Is it mapped at the same address on these machines (i.e. do I use the same dump command as on an Indy?)
If the system uses an R5000, R4600, R4400, R4000, or R3000, the range for the dump command is 0xbfc00000:0xbfc80000. If it uses an R10000, R12000, R14000, or R16000, the range is 0xffffffffbfc00000:0xffffffffbfd00000. The latter range is 1MB as a "just in case" measure, as the Octane's boot PROM is 1MB, but the Indigo 2 Impact's isn't, and in the event that you're dumping too wide a range it will just repeat the data at the 512k mark (and I'll be able to see that and correct it). I'm not sure which to use for the RM5271, RM7000 or R8000-based systems, so just try both, and whichever one doesn't fault is what you're looking for.