config.sys

DEVICE=c:\ctcm\ctcm.exe

autoexec.bat

SET CTCM=c:\ctcm
c:\sb16\aweutil.exe /s

Other (more ubiquitous) information -

autoexec.bat

Edit: SET BLASTER=A220 I5 D1 H5 P330 E620 T6
SET MIDI=SYNTH:1 MAP:E MODE:0
SET CTSYN=c:\windows (NB: not sure what this does!)
SET SOUND=c:\sb16

c:\sb16\diagnose /s
c:\sb16\mixerset /p /q

I'm sure you'll get something out of your CT3990 with these lines. Perhaps someone more knowledgeable than me can improve on them.

(Also, I'm not sure if you need to include the 'typical' SB .SYS file DEVICEs or not.)

Is really DIAGNOSE.EXE needed when you initialize the card with CTCM.EXE?

Amigaz wrote:

Is really DIAGNOSE.EXE needed when you initialize the card with CTCM.EXE?

Good point. Don't know. 😐

Guess: No.

it's not really needed but it does check the card and settings quickly...

Get the AWE32 Drivers from "HERE".
Run the install program and let it do the placement of the statements for you.
Incidentally, it's you who posted the drivers. 😁 Or, of course, you can copy and paste from the retro games 100's post above.

I've got it to work but I'm stuck with creative's crap mixer (mixerset.exe) since Mr Gun's Mastermixer messes up the sound completely when I use the AWE's native midi synth stuff 😜

Malik wrote:

Get the AWE32 Drivers from "HERE".
Run the install program and let it do the placement of the statements for you.
Incidentally, it's you who posted the drivers. 😁 Or, of course, you can copy and paste from the retro games 100's post above.

Those are the DOS drivers which doesn't work with win9x DOS 😉

Does any of this stuff apply to the awe64? I have yet to get any music out of it in dos.. just sfx.

prophase_j wrote:

Does any of this stuff apply to the awe64? I have yet to get any music out of it in dos.. just sfx.

Yess....

prophase_j wrote:

Does any of this stuff apply to the awe64? I have yet to get any music out of it in dos.. just sfx.

Try running Creative's Diagnose.exe utility, to figure out what's wrong. It should allow you to test both sfx and AWE music.

Also, you need to put that aweutil /s line mentioned above in your auto file.
And you need SET BLASTER=A220 I5 D1 H5 P330 E620 T6
Note: 620 is the usual setting. (But it does depend on what your Creative PnP config/manager has set it to.)

Any probs, please post results and I'll see what I can do.

PS - excellent avatar you've got! 😎

Okay I'll try it out. I figured I was missing a device driver... I never put anything in the autoexec or config. I remember the diagnose.exe checking out ok, but a lot of the other commands from aweutils not working right. So even though I had the files there was no documentation and so yeah...

Amigaz wrote:

Those are the DOS drivers which doesn't work with win9x DOS

I see.

prophase_j wrote:

Does any of this stuff apply to the awe64? I have yet to get any music out of it in dos.. just sfx.

Yep, I've tried interchanging the AWE32 and AWE64 cards, keeping the Auotexec statements (installed via AWE32 software) constant. CTCM initialized the AWE64 perfectly. And all the rest of the statements work perfectly too. Including mixerset.

Sounds like a MIDI Port address problem interfering with....say, any other midi soundcard installed with it? Try loading all the statements low (if loaded otherwise). Disable write behind cache of smartdrv for all drives, if enabled.