First post, by dionb
- Rank
- l33t++
Right, the spare room is finally cleared up to the point where someone can sleep there again. That means I get time to actually do stuff with my retro computers rather than just having to sell surplus & tidy up what's left.
One thing I've been wanting to do for a long time is a multi-sound card build to cover as many standards as possible with one system. My actual build log will go in System Specs of course, but before I get started I'd like to double-check the feasibility of my idea.
What I want to cover:
Covox/DSS
AdLib/SB(Pro) OPL3
AdLib/SB(Pro) CQM
SB16
PAS16
GUS
Intelligent MPU-401
So, cards I intend to use:
Aztech Sound Galaxy NX Pro (Aztech 1st gen chipset, SBPro2.0 compatible, real OPL3 and Covox, DSS & WSS)
Creative CT2950 SoundBlaster 16 (3rd gen SB16, CQM, PnP with CTCU/CTCM/diagnose)
Gravis Ultrasound Classic (GUS)
Mediavision PAS16 (PAS16, OPL3, SB2.0 compatible)
Music Quest PC Midi Card (MPU401)
All this will go into a Full Yes 82430I ver B motherboard (i430FX) chosen for its 5 ISA slots with Pentium 100, 64MB EDO and a Diamond Stealth 3D 3000 (Virge/VX). If I get all the sound cards working I might try to add networking too with a PCI NIC, but that's very low on priority list. OS is MS-DOS 6.22 (on a 512MB DOM, which I will upgrade to 2GB once I get it). There's a CF adapter on the second IDE controller I'd like to keep, which means IRQ15 is spoken for.
As for resources, this is what I intend:
NXPro: A220 I7 D1
SB16: A240 I5 D3 H7
GUS: A260 I11 D6 (rec&playback)
PAS16: A? I3 D5
MQ: A330 I(2/9)
The idea is that the oldest legacy will default to SB 220/7/1 (which is what will go in the SET BLASTER variable too) and MIDI 330/(2/9). More modern stuff will let me choose.
Now, I'm pretty confident I can get the first three to play ball. It's the last two I'm worried about. Three questions:
- I don't really understand PAS16's addressing, despite reading this several times. Completely disabling both Thunderboard (Soundblaster) and MIDI seems clear enough - and what I want to do here - but what about the PAS16's native AdLib. How do I ensure that doesn't conflict with the NXPro/SB16? I don't even know what they do for this (listen at 388?).
- MIDI is a problem. GUS doesn't do MPU-401 if you don't load MegaEm (yuck!) and I can explicitly disable it on the PAS16, but both the NXPro and SB16 seem to insist on emulating an MPU-401 (in UART mode, badly). I know I can get DIAGNOSE.EXE to skip MPU by invoking it with /DMPU flag - but what about CTCM? And the NXPro...? My plan B here is to tell both cards to set MIDI to 300 and simply not use it, with the MusicQuest set to 330. Would that work?
- does the overall resource scheme look suitable? I am disabling COM2 and LPT, which leaves me IRQs 10 and 12 for everything else (i.e. VGA and NIC). Alternately I could disable COM1 and use the PS/2 mouse header which lives at IRQ12, leaving IRQs 4 and 10 for the PCI cards. Am I missing something here?