VOGONS


First post, by zwrr

User metadata
Rank Member
Rank
Member

I own the sound card pictured here, manufactured by Labway and bearing the text identifiers A021-770 and LWHA021770. The card features the following chips: ES688, ES968, and DXP44Q. I initially assumed it was a Plug-and-Play (PnP) card; however, the board contains jumpers for manually configuring Interrupts, I/O Addresses, and DMA channels. When attempting to initialize the card using UNISOUND, the utility reported that no sound card could be detected. By using the `/nopnp` command-line parameter, I was able to successfully initialize the card; however, the initialization output did not list an MPU-401 interface, and the card was identified specifically as an ES668 model.

I am quite puzzled: does the ES968 chip on this particular card not function as a PnP controller? Alternatively, is there any method available to enable the MPU-401 interface?

The attachment es688.jpeg is no longer available

SBC1: Cyrix 5x86-120, HS-5x86HVGA, 16MB EDO, GD54M30, SB Pro II, HardMPU-wt
SBC2: VIA C3-800, PCISA-C800, 128MB SDRAM, Savage4 Pro, SB AWE64 Gold
SBC3: Tualatin-S 1.4G, PCI-6872, 256MB SDRAM, FX5200 PCI, Voodoo2 SLI, SB Live

Reply 1 of 5, by Ozzuneoj

User metadata
Rank l33t
Rank
l33t

I don't have any hands on experience with these cards, but a quick google search did turn this up with regard to the MPU-401 capabilities of the ES688:
https://dosdays.co.uk/topics/Manufacturers/ess.php

"The MPU-401 (UART) interface is emulated in software, so a driver must be loaded to use a Wavetable daughterboard on these cards (ESSCFG.COM). There is also a TSR from ESS called ENMPU.EXE which is apparently required to enable the MPU-401 interface. Having said that, there are some later cards that came with the ES968 interface chip as well, which provide hardware MPU-401 capability (so no driver is needed) as well as PnP functionality for chips like the ES688 and ES1688 that were not PnP. "

You might already know all of this though.

I can't find anything specific regarding using unisound with ES688 + ES968 cards. If the card doesn't cooperate with unisound and you disable PNP, it is possible that this bypasses all of the functionality of the ES968 which would mean that you also need to use the TSR\emulation for MPU-401 compatibility. Alternatively, using some original ESS drivers (possibly from the dosdays link above) would presumably enable all of the ES968 features to provide PNP and hardware MPU-401 support.

Just an idea.

Now for some blitting from the back buffer.

Reply 2 of 5, by zwrr

User metadata
Rank Member
Rank
Member
Ozzuneoj wrote on 2026-05-07, 07:57:
I don't have any hands on experience with these cards, but a quick google search did turn this up with regard to the MPU-401 cap […]
Show full quote

I don't have any hands on experience with these cards, but a quick google search did turn this up with regard to the MPU-401 capabilities of the ES688:
https://dosdays.co.uk/topics/Manufacturers/ess.php

"The MPU-401 (UART) interface is emulated in software, so a driver must be loaded to use a Wavetable daughterboard on these cards (ESSCFG.COM). There is also a TSR from ESS called ENMPU.EXE which is apparently required to enable the MPU-401 interface. Having said that, there are some later cards that came with the ES968 interface chip as well, which provide hardware MPU-401 capability (so no driver is needed) as well as PnP functionality for chips like the ES688 and ES1688 that were not PnP. "

You might already know all of this though.

I can't find anything specific regarding using unisound with ES688 + ES968 cards. If the card doesn't cooperate with unisound and you disable PNP, it is possible that this bypasses all of the functionality of the ES968 which would mean that you also need to use the TSR\emulation for MPU-401 compatibility. Alternatively, using some original ESS drivers (possibly from the dosdays link above) would presumably enable all of the ES968 features to provide PNP and hardware MPU-401 support.

Just an idea.

Yes, I also own an ES1688 sound card. Since the ES1688 chip does not support Plug-and-Play (PnP) and features a built-in MPU-401 circuit, I initialize it using the command `unisound /nopnp`; this allows it to function correctly, and the MPU-401 works properly as well.

According to the UNISOUND documentation, sound cards featuring the ESS688 + ES968 chip combination should be capable of being initialized normally as PnP devices, without the need for the `/nopnp` parameter. However, with this specific card, simply running UNISOUND fails to detect the sound card at all. While using the `/nopnp` parameter does allow for initialization, the card model is misidentified, and the MPU-401 remains unusable.

Regarding this ES688 + ES968 card, what I find puzzling is that—according to ESS's specifications—the ES968 chip is supposed to provide both PnP support and the MPU-401 circuitry. Yet, on this particular card, it appears the ES968 chip is not functioning as intended; the card does not support PnP, and the MPU-401 remains inaccessible.

Additionally, this card does not have any jumpers for enabling or disabling the PnP function.

SBC1: Cyrix 5x86-120, HS-5x86HVGA, 16MB EDO, GD54M30, SB Pro II, HardMPU-wt
SBC2: VIA C3-800, PCISA-C800, 128MB SDRAM, Savage4 Pro, SB AWE64 Gold
SBC3: Tualatin-S 1.4G, PCI-6872, 256MB SDRAM, FX5200 PCI, Voodoo2 SLI, SB Live

Reply 3 of 5, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie

This is a weird one, because you would not expect to have resouce jumpers on a PnP card unless there is a PnP disable jumper, but this card doesn't have that. It seems to me this is a hybrid card where the 688 is non-PnP and the 968 which handles IDE/JoyPort/MPU401 is PnP.

I don't think this was common and is not likely to be supported by Unisound. I expect there was a DOS driver written specifically for this configuration which may be floating around somewhere. The win95 drivers on retro web likely support PnP initialisation for the 968's features since each VXD runs independently.

You may also have better luck with the ESSCFG/ESSVOL drivers, as ESS may have accounted for this scenario with their original driver set.

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 4 of 5, by MagefromAntares

User metadata
Rank Member
Rank
Member

Hi,

This site seems to be legit, and has versions of DOS and Windows 3.1 drivers for these particular chips:
https://www.dosdays.co.uk/topics/Manufacturers/ess.php#ES968

Unfortunately I lack a sound card with this configuration to actually try if these drivers work, but they might be of some use.

"A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it." - Dune

Reply 5 of 5, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie
MagefromAntares wrote on 2026-05-07, 08:32:

This site seems to be legit, and has versions of DOS and Windows 3.1 drivers for these particular chips:
https://www.dosdays.co.uk/topics/Manufacturers/ess.php#ES968

The ES968.COM in that driver package may be useful for this card

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer