Installing the CardD under NT nukes the AWE32 drivers
Anyone sucessfully running multiple soundcards under NT??
I've checked for IRO/DMA conflicts and there appear to be none,
any help appreciated.

Paul

as far as i know, the card d's use a seperate interupt for the input and output...I gotta dal dig only card d and it uses IRQ 5 & 6 for the in & out.....wheras the tahiti uses only one......... maybe one of them is unseen & clashing with the awe...... generally tho...card manufacturers are not to keen on developing NT drivers....and the awe can be a bastard at the best of times

I've got it working, but only after four hours of hacks, and trial and
error. Here is my conclusions:

1. It appears that adding multimedia drivers under NT
(ControlPanel/Multimedia/Drivers/Add) wants to add the driver as
"wave1" no matter what you do, which drivers you use etc. This means
that the AWE32 overwrites the Digital Only CardD and vice versa.

2. It is possible to get the AWE32 and CardD to co-exist but only by
hacking the registry; Process as follows:


A. Install the AWE32 (Soundblaster) using the normal method of
ControlPanel/Multimedia/Drivers/Add - I used the Feb98 V6 Duplex
drivers for NT4.0 SP3.

B. Reboot and check they work

C. Using "Regedit" (Start/Run/Regedit) search for "wave1", and change
all entries for "wave1" to "wave2". The changes I made were as
follows; your mileage may vary (using regedit may screw your system,
usual caveats apply - backups, recovery disks recommended);

==================================================================
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\
CurrentVersion\Drivers32\wave1 = "sb16snd.dll"
to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\
CurrentVersion\Drivers32\wave2 = "sb16snd.dll"
==================================================================
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\
CurrentVersion\related.desc\wave1 = ""
to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\
CurrentVersion\related.desc\wave2 = ""
==================================================================
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\
CurrentVersion\Userinstallable.drivers\wave1 = "sb16snd.dll"
to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\
CurrentVersion\Userinstallable.drivers\wave2 = "sb16snd.dll"
==================================================================
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{key1}
\0000\Drivers\wave\sb16snd.drv\Alias= "wave1"
to:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{key1}
\0000\Drivers\wave\sb16snd.drv\Alias= "wave2"
==================================================================
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{key2}
\0000\Drivers\wave\sb16snd.drv\Alias= "wave1"
to:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{key2}
\0000\Drivers\wave\sb16snd.drv\Alias= "wave2"
==================================================================
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{key3}
\0000\Drivers\wave\sb16snd.drv\Alias= "wave1"
to:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{key3}
\0000\Drivers\wave\sb16snd.drv\Alias= "wave2"
==================================================================

As can be seen I found five entries.

D. Reboot the system and check the Soundblaster still works.

E. Assuming the Soundblaster still works now install the Digital
Audio Labs Digital Only CardD.

F. Reboot and test.
If all went well you should have an AWE32 and Digital Only CardD
co-existing.

For me I have both cards working full duplex.

Bottom line is that it now works, one hell of a hack to get it there
though! I would still like to understand what the AWE and DAL drivers
for NT will not just install as "Wave1" and "Wave2", but at the end of
the day I'm just satisfied that it works.

Paul