VOGONS


ESS 1938 under DOS

Topic actions

First post, by andrewls

User metadata
Rank Newbie
Rank
Newbie

Hi guys,
Have a PC with windows 98 and trying to get an ESS es1938S (1938 chipset) PCI card going under DOS.
The SYS file loads OK but the ESSOLO.COM in the autoexec.bat file comes back with the message:

Please use Windows Software Applet to enable Sound Blaster, MPU401 and Game port for Real/Windows DOS

I have tried installing a Windows 98 version and can't locate this supposed 'software applet'.
Has anybody got a working configuration under DOS for a ES1938S card they can share?
Cheers

Reply 1 of 10, by Holering

User metadata

You need to load appropriate files in config.sys before loading essolo.com. Can't remember but I think it's essolo.drv and esfm.drv in config.sys. I don't even think you need the Windows driver (only the plain dos driver files from the package).

Reply 2 of 10, by cde

User metadata
Rank Member
Rank
Member

Sorry to wake up an old thread, but after getting an ESS Solo-1 from eBay and installing it, initially I couldn't manage to get it to work under DOS and Windows 98 SE using the drivers provided on Phil's computer lab website: https://www.philscomputerlab.com/ess-es1938s-solo-1.html , on a K8M890-based motherboard (MSI K9VGM-V), which has TDMA support, same as K8T890-based motherboards as reported in PCI sound cards and Chipsets from various manufacturers...

The first issue was under DOS, I would get the message "Please use Windows Software Applet to enable Sound Blaster, MPU401 and Game Port for Read/Windows DOS. Cannot find the AudioDrive". After some digging, this was caused by the lack of file "ESSOLO.INI", a 16-byte file that can otherwise be found here: https://www.vogonsdrivers.com/getfile.php?fil … =60&menustate=0

Note that Phil's DOS driver includes a file named ESSCFG.INI that I found unneeded (contrary to ESSOLO.INI). His archive provides ESSVOL.EXE which is very useful, however his suggestion of setting /a:0 mutes the waveblaster, so if you have installed a waveblaster card and get no MIDI sound use instead /a:10 . After this change FM, SFX and MIDI all work fine 😀

As mentioned by gerwin in another thread, there are three possibilities wrt/ ESSOLO.INI:

20 02 01 00 88 03 09 00 01 02 30 03 00 00 00 00 == DDMA
20 02 01 00 88 03 09 00 01 02 30 03 01 00 00 00 == TDMA
20 02 01 00 88 03 09 00 01 02 30 03 02 00 00 00 == SB-link (PC/PCI)

In my experience, the first one works fine with the K8M890, the driver seems to use TDMA mode anyway.

Secondly, the driver provided in solo1_drv_w9x_4.12.01.1165.zip (WDM version 4.12.01.1165) did not work at all for me in Windows 98 SE despite the card using IRQ 5, and working fine in DOS/XP/Linux. The "ESS SOLO-1 PCI AudioDrive" driver would have a yellow exclamation mark with the error message "This device is either not present, not working properly, or does not have all the drivers installed. (Code 10.)".

I could not get this driver to work regardless of any BIOS settings. So I collected a number of ES1938 drivers from the Internet in the hope of finding one that works, and indeed version 5.12.01.3047 works just fine 😀 To make it easier for other people, I have sorted all the drivers and put them in the attached "ES1938-dos9x.7z" and "ES1938-nt2kxp.7z" archives, in particular the fixed DOS driver but also:

win31
win95/4.05.00.1060
win95/4.05.00.1065
win95/4.05.00.1080
win95/4.06.00.1140
win95/4.06.00.1154
win98/4.10.3038
win98/4.10.3012
win98/4.10.3014
win98/4.12.01.1164
win98/4.12.01.1165
winme/5.12.01.3047a-unsigned
winme/5.12.01.3047b
winme/5.12.01.3047c
winme/5.12.01.3047d
winnt/4.03.00.5033
winnt/4.05.23
winnt/4.05.06
winnt/4.05.08
winnt/4.05.26
win2k/5.2.3633.0
win2k/5.12.3045a
win2k/5.12.3045b
winxp/6.12.10.3055

Thanks to Stainlesscat for the Windows 3.1 driver. It is also possible to have MIDI sound by installing the MPU-401 (Roland) driver and selecting "General MIDI" in the MIDI configuration panel.

Hopefully this will be helpful to others in their attempt to find a solution for these issues.

Last edited by cde on 2021-12-22, 18:57. Edited 4 times in total.

Reply 3 of 10, by Stainlesscat

User metadata
Rank Newbie
Rank
Newbie

Hi!

Your attached post for the ESS-Solo1 drivers work as intended.

Many thx.

Last edited by Stainlesscat on 2021-11-22, 21:03. Edited 1 time in total.

Reply 4 of 10, by cde

User metadata
Rank Member
Rank
Member

Amazing. Thank you very much Stainlesscat

Reply 5 of 10, by Gopher666

User metadata
Rank Newbie
Rank
Newbie

Wow 1000x thanks for this, right out of the bat I was thinking the proposed solution is: throw your card out to the trashcan and buy an ISA SB16 😀

Works like a charm I can confirm both the MSDOS6.22 and Win3.X drivers, the 9X was always working even with phils driver.

Maybe some1 should hit phillybuster up to update that on his page to avoid wasting tons of others time since his page floats up to the top for that driver.

Oh I forgot he has pretty much zero contact info no email, no twitter, no nothing 😦

Reply 6 of 10, by cde

User metadata
Rank Member
Rank
Member
Gopher666 wrote on 2022-03-19, 16:28:
Wow 1000x thanks for this, right out of the bat I was thinking the proposed solution is: throw your card out to the trashcan and […]
Show full quote

Wow 1000x thanks for this, right out of the bat I was thinking the proposed solution is: throw your card out to the trashcan and buy an ISA SB16 😀

Works like a charm I can confirm both the MSDOS6.22 and Win3.X drivers, the 9X was always working even with phils driver.

Maybe some1 should hit phillybuster up to update that on his page to avoid wasting tons of others time since his page floats up to the top for that driver.

Oh I forgot he has pretty much zero contact info no email, no twitter, no nothing 😦

I have contacted Phil some time ago on that matter but I suppose he is too busy, unfortunately.

Gopher666, is the waveblaster header working on your card? I can't get anything out of it on two different ESS Solo-1, using a X2GS (that works on a SB16).

EDIT: my bad, it was indeed the lack of /a switch 😀 everything working well

Reply 7 of 10, by X3J11

User metadata
Rank Newbie
Rank
Newbie
Gopher666 wrote on 2022-03-19, 16:28:

Maybe some1 should hit phillybuster up to update that on his page to avoid wasting tons of others time since his page floats up to the top for that driver.

Oh I forgot he has pretty much zero contact info no email, no twitter, no nothing 😦

https://twitter.com/philscomputerlb

He's not that active on Twitter, but he does post and reply on occasion.

Edit: I just @ him, pointing him here.
Edit2: He replied, so he's aware of the thread at least.

Last edited by X3J11 on 2022-04-01, 13:16. Edited 1 time in total.

Reply 8 of 10, by dr.zeissler

User metadata
Rank l33t
Rank
l33t

WDM-Driver does not work for FM
Cannot find the "audiodrive" is irq/dma bios failure
messing with pci-sets/ini's does mostly not work or is not far better then using the standard config. (e.g. turrican II)
the driver phil recommends kills my wavetable-module, so I am alwas using 1149 driver on win9x.
for dos I install the win3x driver in win3x and let it do it's thing.
sometimes it's better to put the Printer-Port to IRQ5 so that the Solo1 takes IRQ7 but that depends on your chipset. the later intel chipsets do not rout digisound correctly so that it will perhaps not work if you are using a faster cpu and a later intel-chipset. ALI/VIA are much better, but it also depends on the speed of the cpu.

you can try to set the win9x environment differently in win9x to the dos-settings within win9x. that gives you sometimes better compatibility. eg. Adress 240 than 220. Win9x emulates SB16 at 220 therefore using 240 can make a difference.

Retro-Gamer 😀 ...on different machines

Reply 9 of 10, by xetura

User metadata
Rank Newbie
Rank
Newbie
cde wrote on 2021-08-13, 17:54:
Sorry to wake up an old thread, but after getting an ESS Solo-1 from eBay and installing it, initially I couldn't manage to get […]
Show full quote

Sorry to wake up an old thread, but after getting an ESS Solo-1 from eBay and installing it, initially I couldn't manage to get it to work under DOS and Windows 98 SE using the drivers provided on Phil's computer lab website: https://www.philscomputerlab.com/ess-es1938s-solo-1.html , on a K8M890-based motherboard (MSI K9VGM-V), which has TDMA support, same as K8T890-based motherboards as reported in PCI sound cards and Chipsets from various manufacturers...

The first issue was under DOS, I would get the message "Please use Windows Software Applet to enable Sound Blaster, MPU401 and Game Port for Read/Windows DOS. Cannot find the AudioDrive". After some digging, this was caused by the lack of file "ESSOLO.INI", a 16-byte file that can otherwise be found here: https://www.vogonsdrivers.com/getfile.php?fil … =60&menustate=0

Note that Phil's DOS driver includes a file named ESSCFG.INI that I found unneeded (contrary to ESSOLO.INI). His archive provides ESSVOL.EXE which is very useful, however his suggestion of setting /a:0 mutes the waveblaster, so if you have installed a waveblaster card and get no MIDI sound use instead /a:10 . After this change FM, SFX and MIDI all work fine 😀

As mentioned by gerwin in another thread, there are three possibilities wrt/ ESSOLO.INI:

20 02 01 00 88 03 09 00 01 02 30 03 00 00 00 00 == DDMA
20 02 01 00 88 03 09 00 01 02 30 03 01 00 00 00 == TDMA
20 02 01 00 88 03 09 00 01 02 30 03 02 00 00 00 == SB-link (PC/PCI)

In my experience, the first one works fine with the K8M890, the driver seems to use TDMA mode anyway.

Secondly, the driver provided in solo1_drv_w9x_4.12.01.1165.zip (WDM version 4.12.01.1165) did not work at all for me in Windows 98 SE despite the card using IRQ 5, and working fine in DOS/XP/Linux. The "ESS SOLO-1 PCI AudioDrive" driver would have a yellow exclamation mark with the error message "This device is either not present, not working properly, or does not have all the drivers installed. (Code 10.)".

I could not get this driver to work regardless of any BIOS settings. So I collected a number of ES1938 drivers from the Internet in the hope of finding one that works, and indeed version 5.12.01.3047 works just fine 😀 To make it easier for other people, I have sorted all the drivers and put them in the attached "ES1938-dos9x.7z" and "ES1938-nt2kxp.7z" archives, in particular the fixed DOS driver but also:

win31
win95/4.05.00.1060
win95/4.05.00.1065
win95/4.05.00.1080
win95/4.06.00.1140
win95/4.06.00.1154
win98/4.10.3038
win98/4.10.3012
win98/4.10.3014
win98/4.12.01.1164
win98/4.12.01.1165
winme/5.12.01.3047a-unsigned
winme/5.12.01.3047b
winme/5.12.01.3047c
winme/5.12.01.3047d
winnt/4.03.00.5033
winnt/4.05.23
winnt/4.05.06
winnt/4.05.08
winnt/4.05.26
win2k/5.2.3633.0
win2k/5.12.3045a
win2k/5.12.3045b
winxp/6.12.10.3055

Thanks to Stainlesscat for the Windows 3.1 driver. It is also possible to have MIDI sound by installing the MPU-401 (Roland) driver and selecting "General MIDI" in the MIDI configuration panel.

Hopefully this will be helpful to others in their attempt to find a solution for these issues.

I've been setting up a Gigabyte GA-5SMM board with the solo-1 card. I followed philscomputerlab.com's instructions and had the exact same issues. Your post fixed my DOS setup and I now have sound in dos! Thank you so much. Now I just need to find a VBE that works.

Reply 10 of 10, by MechWarriorZero

User metadata
Rank Newbie
Rank
Newbie

I still get the message in dos: please use windows software applet to enable sound blaster, mpu401 and game port for real/windows dos