AWE32 DOS Command Line Config Question

[Tom]

I need help.  I'm unable to find the old Sound Blaster AWE32 FAQ that contained this info, and I can't find any reference to it online.  Someone helped me with this a while ago (I believe it was Martin), but I need help, again.  

I'm using the external MIDI port on an AWE32 card while running MS-DOS.  The "SET MIDI=SYNTH:1...." line below determines where MIDI signals are sent -- to it's INTERNAL synth, or external MIDI port.  This current setting directs MIDI to the AWE's INTERNAL synth.

SET MIDI=SYNTH:1 MAP:E MODE:0
C:\SB16\DIAGNOSE /S
C:\SB16\AWEUTIL /S

I need to know the proper settings to direct MIDI to the EXTERNAL MIDI port.  Does anybody know?  I thought it was "SYNTH:0", but that's not doing it.

[Zemus]

SYNTH:1 directs it to the internal synthesizer and SYNTH:2 directs it to the MIDI port according to my manual.

[Tom]

Thanks.  I'll give that a shot.  I have the original AWE32 Installation Diskettes and Manual....but nowhere does it refer to these settings.

[Alistair]

My Pentium 1 with AWE32's autoexec.bat has synth:1 as well, but mine runs on the external port. But, I'm running in Windows 95 of course.

- Alistair

[Zemus]

I have the original AWE32 Installation Diskettes and Manual....but nowhere does it refer to these settings.

My card came with two manuals. User's Guide and Getting Started. It's the latter one that has all the instructions for the DOS utitilites and the variables.

My Pentium 1 with AWE32's autoexec.bat has synth:1 as well, but mine runs on the external port.

I believe the SET MIDI parameter is only for programs that read it, like the SET BLASTER parameter which some games use to determine whether or not there's a Sound Blaster card installed.

[Tom]

Well, this is quite strange.  I have two AWE32 cards, in two different PC's:  a Pentium II and a Pentium III, both running Win98SE.  Both cards are setup using I/O 300 for the MIDI port address, as well IRQ 7, and all other parameters are the same.  Both PC's also have a Roland MPU-IPC card installed.  

While in Windows, there's no problems.  The AWE32's port is easily accessible.  However, in DOS, the new PC I've setup won't output MIDI to the external port -- only the internal synth.  I did the "SET MIDI=SYNTH:2 MAP:E MODE:0" thing on the second PC hoping that would help, but it doesn't.  The first PC doesn't have an AUTOEXEC.BAT at all, nor do I reference this statement, and it works fine under DOS.

Now, here's the strange part:
If I "Boot to MS-DOS prompt" upon Windows startup ...OR... if I "Restart in MS-DOS mode" from Windows 98 shut down screen, the AWE32 functions perectly in DOS, and MIDI is properly sent to the external MIDI port.  

Perhaps this is a "MS-DOS Prompt" properites issue.  I need to keep Windows running in the background, so I access my DOS software using the "MS-DOS Prompt" program option.  I have the properties set to "Do not allow MS-DOS programs to detect Windows", the same as on my other music PC.  Beyond that, I don't know what else to do.  As usual, there's something in Windows that's preventing it to work properly under the DOS prompt.

[Great Hierophant]

Well, this is quite strange. I have two AWE32 cards, in two different PC's: a Pentium II and a Pentium III, both running Win98SE. Bot cards are setup using I/O 300 for the MIDI port address, as well IRQ 7, and all other parameters are the same. Both PC's also have a Roland MPU-IPC card installed.

I hate to shift the subject, but have you had any problems using an MPU-IPC in systems designed over a decade later than the systems it was intended to be used in.  Those systems are orders of magnitude faster than the early systems?  Does the Windows driver work with the card or do you use a Roland one?  

By the way, is the waveblaster header on the AWE32 considered the internal, external or as separate port?  Do you need to load AWEUTIL to access the external port?

[Tom]

Microsoft's MPU-401 driver (in Win98SE) works very well with my MPU-IPC's.  I've never had any issues with these.  Additionally, the MPU-IPC's are always readily detected when I install Win98SE on these systems.  However, I normally use Voyetra's MPU DOS drivers (VAPI drivers) since I normally use the MPU-IPC's while in DOS.

Only one of my AWE32's has a WaveBlaster header.  It's considered the External port.  If something's connected to it (like my SCB-55 used to be), it will be accessed as the external synth.  MIDI signals will ALSO be directed to the MIDI port.  So, if you're using the WB header, and you also have something connected to the MIDI port, they will both play together -- unless you silence one of them with SysEx, or by some other means.  I haven't had to use AWEUTIL to access it.  Typically, I just let Win98SE detect the AWE32 (which it always does), and don't install any other Creative Labs software or drivers.  Win98SE's AWE32 support seems to function well in Windows and DOS.

[Alistair]

Is it maybe a config.sys issue, if not autoexec.bat?

I've never used Win 98SE, only Win 95, Win95Plus and XP Home, so my 'expertise' is really limited to those..

- Alistair

[Tom]

Yet, some more strangeness...

I've deleted all references to the SB AWE32 in my autoexec.bat and config.sys files; disabled the AWE32's Synth (using Windows' Device Manager), and now...everything's working fine!  I also installed the Fortissimo II sound card to serve as a digital source for the PC.  The "Front Speakers" output seems to act as a Line Out; perhaps it requires amplified speakers.  Anyway, it sounds good.

Now I have one music computer with a SC-8820, MT-32, and SW60XG installed (and a Roland S3000 keyboard)  ---- and a second with a SC-8850, another MT-32, and Yamaha CBX-K2 controller --- plus an AWE32 and MPU-IPC in each computer, for connecting the external modules.  

Wonder why the second AWE32 external MIDI port suddenly started working?

[zaphod77]

okay. i believe the problem was conflicts betwen the do sdrivers and the windows ones.

if it works in pure dos, then your dos drivers ar set up right. many plug and play cards need to be initialise dto work correctly in DOS.

usually installing creative's drivers will do the trick, installin g the plug and play configuration manager (CTCM), and making windows and dos play nice together.

Then you just need a special bat file to run ctcm to init the card when you boto int pure DOS.

and yes, that set midi line is only for programs that look for it.after all it's just an environment variable. certain dos programs will obey it if you tell it you are usigna sound blaster fo rmidi. that's ALL.

[Tom]

The AWE32 installation program didn't install the CTCM configuration manager in DOS...at least, my setup disks don't install it.  It DOES install with my AWE64 installation disks -- but not the original AWE32.  But in any event, I no longer have any AWE32 files being accessed in DOS.  Whatever files  Win98SE installed during its setup...that's all I have.  It didn't create an AUTOEXEC or CONFIG file, but may have added lines to a SYSTEM.INI or CONTROL.INI file.  I didn't check; it's all working just fine, so I'm happy.

I was never able to use the AWE64's MIDI port with DOS sequencers because of that CTCM utility.  The Sequencer Plus VAPIMPU or VAPISB didn't know what to make of it.

The digital capabilities of both of my AWE32's, sucks.  They both have problems and don't work well.  (Distorted, and one doesn't record digital at all.)  My AWE64 Gold, on the other hand, works well, digitally.  However, I use newer digital cards in both of my music PC's for recording (Santa Cruz and a Fortissimo II),  and use the AWE32's for their MIDI ports, only.

[Great Hierophant]

The digital capabilities of both of my AWE32's, sucks. They both have problems and don't work well. (Distorted, and one doesn't record digital at all.) My AWE64 Gold, on the other hand, works well, digitally. However, I use newer digital cards in both of my music PC's for recording (Santa Cruz and a Fortissimo II), and use the AWE32's for their MIDI ports, only.

Creative Labs' recording and playback capabilities have always been suspect.  Their early cards was noisy and often suffered from pops and crackles.  Their  Live! and Audigy work at 48kHz and upsample everything to that frequency with no particular accuracy.