You'd need to do the PnP setup for the AWE64 to make sure the two cards don't conflict, but if you're not using it in DOS, don't bother loading any of the AWE magic, or any TSRs, etc. The PnP setup tool shouldn't take any memory, except for while it's actually running.

jade_angel wrote:

You'd need to do the PnP setup for the AWE64 to make sure the two cards don't conflict, but if you're not using it in DOS, don't bother loading any of the AWE magic, or any TSRs, etc. The PnP setup tool shouldn't take any memory, except for while it's actually running.

AWEUTIL /S only right?

IF I DO use the AWE64 for Soundfonts and MIDI and the Audician for FM how much conventional RAM do I lose? Is it worth it?

Yeah, just AWEUTIL /S should be the right thing, IIRC. (It's actually been a while since I've set one up in DOS; the last machine I built with an AWE was using Win2k, and then the board exploded, yay...) I'm not sure how much conventional RAM the other tools cost - I'd have to play with it and see.

If it turns out to be a major problem, you might look at PC DOS 2000, which has a "DOS=HIGH,UMB" option that can free up a bit more conventional RAM than is possible in MS-DOS or DR-DOS. Also, you might try 4DOS instead of COMMAND.COM (can use UMB and XMS), and some of the AWE64 utilities might be able to be loaded high. I'd have to play around with it to see, actually.

Thanks. I will probably just use a Dreamblaster X3M with the Audician's game port and not fully load the AWE64; so basically Audician32 and Dreamblaster X3M connected together, their mixes line out is routed through a pnp initialized awe64 I keep for use in Wi9x/2k on the same multiboot PC. Good plan?

I used to do the line-out to line-in thing but bought myself a little passive mixer a while ago and haven't looked back - no more fiddling around with software mixer levels to get it perfect and having to in it 2+ cards at once.