Run AWEUTIL /S.

I actually have that line in autoexec.bat. I tried running it manually once I get to the DOS prompt (computer is set _not_ to go to Windows GUI automatically on boot) but there's an error message "ERROR12: AWE32 initialization failed".

It is either a resource allocation issue, or the card is a castrated CT4520. Let's hope it's the former; could you post a picture of the card? Does it have the AWE chip and all the memory banks on it?

I don't have a picture of it handy, but I can confirm that it does have the RAM expansion headers and chips. The Creative software in Windows reports the built-in 512KiB as normal.

Does the software/games you're using actually support AWE cards? AWE cards are not MPU-401 MIDI compatible. They need explicit support from the software you use.

If you are using the MIDI emulator that comes with the AWE DOS driver (use "AWEUTIL /?" to see CLI options), then note that it's not always compatible. Many games will just not work with it.

Does the DOS software of the AWE card come with the DIAGNONE.EXE utility? Run that. At the end you will have the choice to test "AWE Synthesis". Select that. MIDI music should be playing.

realnc wrote:

Does the software/games you're using actually support AWE cards? AWE cards are not MPU-401 MIDI compatible. They need explicit support from the software you use.

That's irrelevant. It is evident that he is talking about FM synthesis not working as well. Because of the architecture of the AWE cards, AWE chip must be initialized to support even basic FM, because it goes through the EMU8000. If AWEUTIL /S says "AWE initialization failed", it means there is a problem.

realnc wrote:

Does the DOS software of the AWE card come with the DIAGNONE.EXE utility? Run that. At the end you will have the choice to test "AWE Synthesis". Select that. MIDI music should be playing.

Yes, it should come with DIAGNOSE.

Hopefully some combination of CTCU, CTCM and DIAGNOSE can juggle the resources until some working combination can be found.

Compare which IO, IRQ, DMA are assigned to the AWE in Windows versus DOS. Perhaps there is an IRQ conflict.

Also run MIXERSET.EXE to make sure the problem isn't just stuff being muted 😁 Run it without arguments to get the text-mode UI.

Perhaps just clarify your system specs and whether you're running your DOS game from a command prompt or did you boot into MS-DOS mode?
If you boot into MS-DOS mode, remember to also run CTCM (it will configure your sound card's settings by reading the CTPNP.cfg file in your Windows folder).

One other thing - could it be an outdated AWEUTIL that does not support AWE64? (not sure such a problem even exists) What is the version of AWEUTIL?

dr_st wrote:

One other thing - could it be an outdated AWEUTIL that does not support AWE64? (not sure such a problem even exists) What is the version of AWEUTIL?

I have come across this problem. Agree that the OP must use a later version of Aweutil. Mine uses version 1.35.

Reading through your replies, I found there was no line for CTCM. Added this to my autoexec.bat and I think it's all up and running now! DIAGNOSE.EXE now reports a lot more things in its test, including the onboard DRAM, etc., and my test application (Doom 😜) now has music.

Huzzah, and many thanks!

Glad to hear that!

Strange that you had any digital sounds without CTCM; I would think the games would not even see the card, but perhaps my memory is deceiving me...