First configure it in Windows. Change the MPU401 of the AWE to 300.

To configure MS-DOS mode, do NOT use the DOS 6.22 drivers, they won't work.

You need to use the 95dosapp.exe drivers as well as ctcmbbs.exe drivers.

95dosapp comes with a readme that you need to follow to install the drivers.

I've done a video tutorial on this which might help a bit: https://youtu.be/ZiSM5pUGab4

You should be able to change the AWE's MPU address through the Device Manager

Thanks for the hand guys. Back in the day when I ran Win98SE on my main PC, I had a PAS16, and then later a Live!...I'm rather rusty at the old Win98/DOS cross configuration tricks now, where I used to pride myself on them. 😢

philscomputerlab wrote:

First configure it in Windows. Change the MPU401 of the AWE to 300. […]
Show full quote

First configure it in Windows. Change the MPU401 of the AWE to 300.

To configure MS-DOS mode, do NOT use the DOS 6.22 drivers, they won't work.

You need to use the 95dosapp.exe drivers as well as ctcmbbs.exe drivers.

95dosapp comes with a readme that you need to follow to install the drivers.

I've done a video tutorial on this which might help a bit: https://youtu.be/ZiSM5pUGab4

This is awesome, but seems quite convoluted.

Is it just a matter of the DOS 6.x versions of CTCM/CTCU refusing to run if WINBOOTDIR environment variable is detected? Because they always worked fine for me once that is worked around.

It the CTCMBBS you show in your video basically contains versions that do not have this limitation? Or is it that somehow "booting into MS-DOS mode" from Windows avoids setting that variable altogether, as opposed to normal DOS boot (BootGUI=0)? Or is it another setting somewhere?

In the video I am following the readme file and doing it the Creative way.

Creative didn't want noobs to run the DOS installer under a Windows 9x system.