VOGONS


awe64 midi troubles

Topic actions

First post, by Olly_K

User metadata
Rank Newbie
Rank
Newbie

Hi, guys, been reading this forum quite a bit recently. I'm a big fan of leisure suit larry, kings quest, doom, all the oldies. I remember the days of trying to get everything to load into upper memory to get stuff working, ah, the good old days.

So i though, sod it, bought a 233 p2 off ebay, bunged an awe64 soundcard in, and waited for the music to take me back.

But, it didnt. leisure suit larry series refuses to run with anything but the adlib setting, but im sure back in the day i was using mt32 with CMS soundblaster. Doom1 and Doom2 midi works fine, under general midi. Also day of the tentacle doesnt work, has sound effects, but no midi.

I have ctcmbbs installed, and the sb64basic disk. I'm not running windows, just dos 6.22. Although im gonna try windows 3.11 and run them through a dos window.

Any ideas guys ?

ive tried changing midi synth to mt32 (aweutil /em:mt32) but to no avail. If i change it to GM i get midi in DOTT, but all the instruments are wrong.

Your help is greatly apprieciated.

P.S, i've tried searching on here, but havent found much 🙁

Reply 1 of 7, by robertmo

User metadata
Rank l33t++
Rank
l33t++

you should also download older aweutil 1.20

awe32's mt32 emulation will not always work (in most cases it doesn't 😉 ) And even if it work it will not sound correctly in most cases 😉

Reply 2 of 7, by Olly_K

User metadata
Rank Newbie
Rank
Newbie

i take it you mean awe64's, or awe32s too ?

i;m gonna try aweutil /em:mt32 with the 1.20 version ive just downloaded.

i'll let you all know 😀

Reply 3 of 7, by Olly_K

User metadata
Rank Newbie
Rank
Newbie

hm.......its not that. MIDI works fine. I've found out its the SOUNDBLASTER setting which doesnt work. how can this be ?

any ideas would be greatly received

Reply 4 of 7, by robertmo

User metadata
Rank l33t++
Rank
l33t++

What do you mean exactly?

Reply 5 of 7, by teamster1975

User metadata
Rank Member
Rank
Member

Dusting off old memories; there was a command that had to be run from the autoexec to initialize the card. I've just found this on google:
The important command was: "aweutil /s" which initializes the card according to the "SET BLASTER" variable.

[edit] I should have included the link where I got the information! Doh!
computing.net/cgi-bin/printer.pl?13702|dos

[CONFIG.SYS]
...
DEVICE=C:\AWE64\CTCM.EXE
REM the next two lines are not required for all games
DEVICEHIGH=C:\AWE64\CTSB16.SYS /UNIT=0 /WIN95 /BLASTER=A:220 I:5 D:1 H:5
DEVICEHIGH=C:\AWE64\CTMMSYS.SYS

[AUTOEXEC.BAT for DOS 7.10/Windows 95/98]
...
SET CTCM=C:\AWE64
SET BLASTER=A220 I5 D1 H5 P330 E620 T6
SET SOUND=C:\AWE64
SET MIDI=SYNTH:1 MAP:E MODE:0
C:\AWE64\MIXERSET /P /Q
C:\AWE64\AWEUTIL.COM /S

[AUTOEXEC.BAT for DOS 6.22/Windows 3.x]
...
SET CTCM=C:\AWE64
SET BLASTER=A220 I5 D1 H5 P330 E620 T6
SET SOUND=C:\AWE64
SET MIDI=SYNTH:1 MAP:E MODE:0
C:\AWE64\MIXERSET /P /Q
C:\AWE64\CTCU /S /W=C:\WINDOWS
C:\AWE64\DIAGNOSE /S /W=C:\WINDOWS
C:\AWE64\AWEUTIL.COM /S

Reply 6 of 7, by Iron

User metadata
Rank Newbie
Rank
Newbie

Yeah that seems fine really. If you're still having problems tell more about the system and the settings and if you're sure the card is in fine shape. The mt-32 emulation with the soundblasters sounds pretty much horrible. Maybe I have listened to good examples of the worst pieces, but still it was not in the same galaxy with the real mt32 sounds. For getting instruments wrong, dunno this sounds a lot like the emulation 😀

Reply 7 of 7, by Hellworm

User metadata
Rank Newbie
Rank
Newbie

Here are the settings from my PC with an AWE64 Gold card.
(PII 333Mhz, 64 megs RAM, 15 Gig HD)
I have a dual partition (Pure DOS 6.2 & Windows 98SE), so I have the settings for both environments.

Pure DOS settings

Autoexec.bat

SET SOUND=C:\AWE64
SET BLASTER=A220 I5 D1 H5 P330 E620 T6
SET MIDI=SYNTH:1 MAP:G MODE:0
SET CTCM=C:\CTCM
LH C:\AWE64\DIAGNOSE /S
LH C:\AWE64\MIXERSET /P
LH C:\AWE64\AWEUTIL /EM:GM /R:90 /C:90

Config.sys

DEVICE=C:\CTCM\CTCM.EXE

There is a file called CTPNP.CFG in the same folder as CTCM.EXE.
This contains the setting information for the sound card using CTCM.

The settings in here need to match Blaster environment settings.

CTPNP.CFG

[PNP]
Readport=277

[SB16]
Csn=1
LogDev=0
CardId=CTL009E
Serial=0E5C2121
Port0=220
Port1=330
Port2=388
Irq0=5
Dma0=1
Dma1=5

[AWE]
Csn=1
LogDev=2
CardId=CTL009E
Serial=0E5C2121
Port0=620
Port1=A20
Port2=E20

[GAMEPORT]
Csn=1
LogDev=1
CardId=CTL009e
Serial=0e5c2121
Port0=200

If these settings do not match, CTCM will not configure the soundcard configuration properly.

There is a configuration tool called CTCU.EXE
This tools sets the environment based on the settings of the soundcard and is a good way to make sure the settings match in all places.

You should be able to download the drivers for the AWE64 for DOS from Creative's website.

Hope this helps, as this setup works perfect for my system.
Let me know if you need anything clarified.

Shop Smart, Shop S-Mart.