AWE32 should be okay. If you are loading drivers resident, try initializing only without TSRs.

Also try JEMMEX instead of EMM386, or HIMEM only. That might help some games to run properly.

keenmaster486 wrote on 2022-04-20, 16:41:

Also try JEMMEX instead of EMM386, or HIMEM only. That might help some games to run properly.

Oooh, Thank you. I'll be sure to give JEMMEX a try, I've downloaded it already, though i've not had a chance to try it out yet.
I've seen other memory managers mentioned here before, and some clever RAM configurations too.

Usually i would only load HIMEM.SYS. I'd only load EMM386 if i'm sure a game or software requires it.
Then i'd get over 600k of base ram with this. NOEMs would cause some games to complain, RAM would cause a reboot with Tyrian's Setup program for example.
DEVICEHIGH and LOADHIGH on anything i can use it for.

Didn't DOS 6.xx have trouble with more than 64MB of ram? Could you test things with only 64 or 32 MB installed?

Still a nice setup though 😁

waterbeesje wrote on 2022-04-22, 13:47:

Didn't DOS 6.xx have trouble with more than 64MB of ram? Could you test things with only 64 or 32 MB installed?

Yes. HIMEM.SYS in MS-DOS 6.22 was limited to 64MB RAM, replacing it with HIMEMX would address this limitation.

Aside of that certain DOS games using the DOS/4GW extender won't work with more than 64MB RAM. The workaround is to replace the DOS extender with DOS/32A or limit the amount of available RAM thru software (either with HIMEMX or XMSDSK for example).

Gmlb256 wrote on 2022-04-22, 13:55:

waterbeesje wrote on 2022-04-22, 13:47:

Didn't DOS 6.xx have trouble with more than 64MB of ram? Could you test things with only 64 or 32 MB installed?

Still a nice setup though 😁

Yes. HIMEM.SYS in MS-DOS 6.22 was limited to 64MB RAM, replacing it with HIMEMX would address this limitation.

Aside of that certain DOS games using the DOS/4GW extender won't work with more than 64MB RAM. The workaround is to replace the DOS extender with DOS/32A or limit the amount of available RAM thru software (either with HIMEMX or XMSDSK for example).

You know, something you both said that I didn't actually consider was the MS-DOS memory limitation. I honestly didn't think about this being an issue or that there was even a limitation.
I'm now realising that it doesn't support above 64MB going by MEM and MSD. I just wasn't expecting issues.
Luckily, I do still have a 64MB module from when i 1st built this computer, so i will try that to see if there's any difference.
Thank you both for pointing this out to me 😀

Also, Thank you @Gmlb256, I've always enjoyed using this build.

CodeFuApprentice wrote on 2022-04-22, 14:55:

Also, Thank you @Gmlb256, I've always enjoyed using this build.

You're welcome!

I have a quite similar but non-Super Socket 7 build like yours using a AMD K6-2+ CPU which is mostly focused on DOS and could relate the things you mentioned notably the "Passive Release" and "Delayed Transaction" options.

In the BIOS settings if available, playing with 8-bit and 16-bit I/O recovery times can also help with ISA sound cards.

Update:
I've had a chance to try JEMMIX without HIMEM.SYS and EMM386.EXE, I was actually surprised at how much conventional RAM became available.
Also pleased that i had various memory specs available. XMS/EMS/UMB etc. I did also reinstall my 64MB module.
I've just been briefly messing around with Autoexec.Bat/Config.sys settings that i'm aware of would work, but haven't made notes of whats worked.
I've also changed some BIOS settings like IO Recovery, AT Bus Clock, ISA Line Buffer etc. Disabled PNP OS, Assigned relevant IRQs and DMAs to Legacy ISA etc.

Following this, and Regarding Adlib/Midi: I've remarked out the Config.sys drivers, and ran Diagnose.exe /S in Autoexec.bat. No change, No adlib and only sound effects,
However, now, after running the Diagnose utility, Adlib/MID is working, saved config,Tried some games with Adlib and it worked ,rebooted, and no adlib again?? What's going on?
Have i missed something? Does Diagnose have issues with some versions? I have v2.03.

Any ideas?
I forgot to mention, I haven't installed Windows 3.1x yet, so just DOS for now.

Your AWE32 in DOS must be initialized like this in AUTOEXEC.BAT:

1DIAGNOSE /S
2AWEUTIL /S /R:0 /C:0
3MIXERSET /P /Q

BLASTER and SOUND environment variables must be set prior setting these lines. AWEUTIL and MIXERSET are located in the same directory where DIAGNOSE is.

The /S command line switch on AWEUTIL is for initialization only and sets the reverb and chorus to 0%. The reasoning for this is that on certain AWE32 models (including yours) has the FM synth output routed through the EMU8K chip.

And MIXERSET is for loading the mixer configuration for the sound card. Two command line switches are used:

• /P: Loads CTMIX.CFG file for setting the mixer values. Located in the same directory where MIXERSET is.
• /Q: Don't display anything.

Gmlb256 wrote on 2022-04-22, 21:55:

Your AWE32 in DOS must be initialized like this in AUTOEXEC.BAT: […]
Show full quote

Your AWE32 in DOS must be initialized like this in AUTOEXEC.BAT:

Copy code to clipboard

1DIAGNOSE /S
2AWEUTIL /S /R:0 /C:0
3MIXERSET /P /Q

BLASTER and SOUND environment variables must be set prior setting these lines. AWEUTIL and MIXERSET are located in the same directory where DIAGNOSE is.

The /S command line switch on AWEUTIL is for initialization only and sets the reverb and chorus to 0%. The reasoning for this is that on certain AWE32 models (including yours) has the FM synth output routed through the EMU8K chip.

And MIXERSET is for loading the mixer configuration for the sound card. Two command line switches are used:

• /P: Loads CTMIX.CFG file for setting the mixer values. Located in the same directory where MIXERSET is.
• /Q: Don't display anything.

I kept thinking i've done all you've suggested, right until you mentioned Mixerset? Isn't that a Windows utility? I haven't seen that in my AWE32 Directory, I had SB16Set, I then started thinking look for another driver package.
I don't have original disks or CDs for my card anymore, but i did download from this site a little while ago. Copied across and now referring to those files. (They're a little bit newer than what i was using)
I re did Diagnose, Ok, that worked like last time, Tried some games, Yay!! Adlib and midi again 😀
Rebooted expecting the same again. Booted up Jill of the jungle..ADLIB?? Holy smokes it's working!! No need to Diagnose. Tried Tyrian 😀, Tried DOTT, Skyroads!! WOW!! Jumpman Lives. FINALLY!!!!
I thought i'd used the right drivers and was beginning to think my card was failing!! Not at all now 😀
Happy Happy Joy Joy!!

CodeFuApprentice wrote on 2022-04-23, 01:02:

I kept thinking i've done all you've suggested, right until you mentioned Mixerset? Isn't that a Windows utility? I haven't seen […]
Show full quote

Gmlb256 wrote on 2022-04-22, 21:55:

Your AWE32 in DOS must be initialized like this in AUTOEXEC.BAT: […]
Show full quote

Your AWE32 in DOS must be initialized like this in AUTOEXEC.BAT:

Copy code to clipboard

1DIAGNOSE /S
2AWEUTIL /S /R:0 /C:0
3MIXERSET /P /Q

BLASTER and SOUND environment variables must be set prior setting these lines. AWEUTIL and MIXERSET are located in the same directory where DIAGNOSE is.

The /S command line switch on AWEUTIL is for initialization only and sets the reverb and chorus to 0%. The reasoning for this is that on certain AWE32 models (including yours) has the FM synth output routed through the EMU8K chip.

And MIXERSET is for loading the mixer configuration for the sound card. Two command line switches are used:

• /P: Loads CTMIX.CFG file for setting the mixer values. Located in the same directory where MIXERSET is.
• /Q: Don't display anything.

I kept thinking i've done all you've suggested, right until you mentioned Mixerset? Isn't that a Windows utility? I haven't seen that in my AWE32 Directory, I had SB16Set, I then started thinking look for another driver package.
I don't have original disks or CDs for my card anymore, but i did download from this site a little while ago. Copied across and now referring to those files. (They're a little bit newer than what i was using)
I re did Diagnose, Ok, that worked like last time, Tried some games, Yay!! Adlib and midi again 😀
Rebooted expecting the same again. Booted up Jill of the jungle..ADLIB?? Holy smokes it's working!! No need to Diagnose. Tried Tyrian 😀, Tried DOTT, Skyroads!! WOW!! Jumpman Lives. FINALLY!!!!
I thought i'd used the right drivers and was beginning to think my card was failing!! Not at all now 😀
Happy Happy Joy Joy!!

As you mentioned SB16SET it becomes clear that you were using older drivers. MIXERSET is the DOS version of the mixer software found on the latest drivers and it gave you the idea to get these drivers. 😀

I'm glad that this fixed your problem with the AWE32. 👍

One more thing: JEMMEX is only useful in pure DOS. Windows 3.1 only works with HIMEM.

keenmaster486 wrote on 2022-04-23, 04:41:

One more thing: JEMMEX is only useful in pure DOS. Windows 3.1 only works with HIMEM.

Oooh, Now that is good to know, Thank you 😀 I probably might've found that out myself eventually.
I've also been switching between using JEMMEX or HIMEM.SYS and/or EMM386.EXE depending if i need it for a game or program.

Otherwise, I've actually been enjoying messing around with my now fully functioning DOS system.

As i've resolved the issues i had before, I've also encountered some other minor issues which i've managed to sort out.
I had audio crackling which i've resolved using Mixerset, lower volumes etc. I really need to get a TOSLINK backplate.
A few games are still giving me trouble, Flashback CD version being one.
I'll update my post if i can think of any others.