Here sound not work in dos mode

In general, cards fully configured via jumpers don't need DOS drivers.
But nowadays, there's UNISOUND, which often removes the need to install the original DOS drivers for ISAPNP cards - I've tried it with SB AWE64, and it worked fine.

Strictly speaking no sound cards works without drivers.

In the early days of sound cards, games would include their own drivers for specific sound cards (e.g. Adlib, Game Blaster, early Sound Blaster cards, etc.).

However, by the time you get to the mid-to-late 90s (e.g. Windows 95/98) sound cards will typically require manufacturer supplied drivers for whichever OS you want to use. This includes DOS.

For AWE64 specifically, I recommend the above suggestion to use UNISOUND. It's much more straight-forward than trying to use the official Creative Labs drivers.

Note that card will still need to have free hardware resources (IRQ/DMA) to be able to be used in DOS. If there is an issue trying to get it configured, it could be a hardware resource conflict. You might need to reserve specific resources in your BIOS, depending on whatever hardware you have in your system.

DataDragons wrote on 2024-07-12, 17:26:

idk why i try many ways and i cant install awe64 drivers in dos mode not work in win98se dos mode

Wait, didn't Creative driver have trouble with MS-DOS 7.x because they think you're running Windows 95 or 98?
Because they think MS-DOS 7.x = Windows 9x?

If so, I installation with MS-DOS 6.22 may help or faking another DOS version (say 6.22) may help.
There's SETVER.EXE as part of MS-DOS, as well as a Freeware utility called "DOSVER".
DOSVER can be used to temporarily set a version number for all applications.

Edit: Sound cards I know of that need no initialization programs:
AdLib, Rainbow Arts Soundman, Covox Sound Master Plus and Sound Master II,
Sound Blaster 1.0/1.5/2.0, Thunderboard and clones (Protac),
ES688 (needs MIDI driver), SB Pro 1 and 2, CPS Sound Blaster 2 (Aztech Sound Galaxy BX II),
Sound Blaster 16 CT1740, CT1750 etc.

Personally, I had a PAS16 back then. It needs init and drivers, but the setup utility is user friendly.

Shponglefan wrote on 2024-07-12, 20:04:

Strictly speaking no sound cards works without drivers. […]
Show full quote

Strictly speaking no sound cards works without drivers.

In the early days of sound cards, games would include their own drivers for specific sound cards (e.g. Adlib, Game Blaster, early Sound Blaster cards, etc.).

However, by the time you get to the mid-to-late 90s (e.g. Windows 95/98) sound cards will typically require manufacturer supplied drivers for whichever OS you want to use. This includes DOS.

For AWE64 specifically, I recommend the above suggestion to use UNISOUND. It's much more straight-forward than trying to use the official Creative Labs drivers.

Note that card will still need to have free hardware resources (IRQ/DMA) to be able to be used in DOS. If there is an issue trying to get it configured, it could be a hardware resource conflict. You might need to reserve specific resources in your BIOS, depending on whatever hardware you have in your system.

Hey thank a lot when I ran unisound it work immediately
Idk how but it just work thx for suggestion

But I have to run unisound program every time I run game on dos

Jo22 wrote on 2024-07-12, 21:02:

Wait, didn't Creative driver have trouble with MS-DOS 7.x because they think you're running Windows 95 or 98?
Because they think MS-DOS 7.x = Windows 9x?

Yep, CTCM checks how the sound card is configured in Windows instead of looking for the CTPNP.CFG file. This is due to MS-DOS 7.x never being intended to be standalone.

If so, I installation with MS-DOS 6.22 may help or faking another DOS version (say 6.22) may help.
There's SETVER.EXE as part of MS-DOS, as well as a Freeware utility called "DOSVER".
DOSVER can be used to temporarily set a version number for all applications.

Later versions of CTCM have the /T command line switch, which makes it work like in older version of MS-DOS.

There is a patch to get around this as well.

DataDragons wrote on 2024-07-12, 17:26:

i want soundcard that no neeed to install drivers in dos mode for easy to explain i want soundcard that use cd install driver on win98se and work in dos immediately

idk why i try many ways and i cant install awe64 drivers in dos mode not work in win98se dos mode

Non-PnP ISA cards work without any need of drivers as long as they're fully jumper-configurable. My very first ESS 688 sound card was one such examples.

However, you still need to properly set BLASTER environment variable as many games refer to it for accessing Sound Blaster compatible cards.

I'm not sure about your problem with AWE64 drivers with Win98SE DOS mode, as by principle VxD drivers can access DOS stuffs directly unlike WDM, and I don't think Creative sound cards ever had WDM drivers for 9x.

(Side note: ESS, on the other hand, did have WDM drivers for 9x, including my ESS 688.)

LSS10999 wrote on 2024-07-13, 08:29:

Non-PnP ISA cards work without any need of drivers as long as they're fully jumper-configurable. My very first ESS 688 sound car […]
Show full quote

DataDragons wrote on 2024-07-12, 17:26:

i want soundcard that no neeed to install drivers in dos mode for easy to explain i want soundcard that use cd install driver on win98se and work in dos immediately

idk why i try many ways and i cant install awe64 drivers in dos mode not work in win98se dos mode

Non-PnP ISA cards work without any need of drivers as long as they're fully jumper-configurable. My very first ESS 688 sound card was one such examples.

However, you still need to properly set BLASTER environment variable as many games refer to it for accessing Sound Blaster compatible cards.

I'm not sure about your problem with AWE64 drivers with Win98SE DOS mode, as by principle VxD drivers can access DOS stuffs directly unlike WDM, and I don't think Creative sound cards ever had WDM drivers for 9x.

(Side note: ESS, on the other hand, did have WDM drivers for 9x, including my ESS 688.)

yeah after i use UNISOUND driver it work fine now but i have to run eveytime i start new DOS MODE but it's Better than nothing

DataDragons wrote on 2024-07-13, 08:44:

yeah after i use UNISOUND driver it work fine now but i have to run eveytime i start new DOS MODE but it's Better than nothing

IIRC the DOS mode PIF file can include its own CONFIG/AUTOEXEC settings.

You can just edit the PIF (or make your own copy), add the line to run UNISOUND in its AUTOEXEC setting, and it will load UNISOUND automatically when you launch it to enter DOS mode.