Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Windows 95 Sound Problem

531 views
Skip to first unread message

Michael Drevno

unread,
Dec 28, 1996, 3:00:00 AM12/28/96
to

Recently, I upgraded from Windows 3.1 to Windows 95 and am having
trouble hearing anything from my sound card. I use a Dell Dimension
XPS 466V (a 486-66) and have a ESS Technology sound card model 1833.
The sound card is an OPL3-compatible, 16-bit stereo sound card that
supports Plug and Play functionality. In addition, the sound card
supports Adlib, Sound Blaster, and Sound Blaster Pro functionality.
The sound card worked perfectly while I was using Windows 3.1. Now
that I am using Windows 95, I hear nothing.

I used Windows 95's Add New Hardware Wizard to automatically install
the sound card's drivers. The Wizard detected the sound card and
installed device drivers for Ad Lib Compatible (OPL2). When I use
"Control Panel...System..." and review Ad Lib Compatible (OPL2)
Properties, the Device Status box reports "This device is working
properly." In addition, the Ad Lib Compatible (OPL2) Properties
reports there are no device conflicts. Unfortunately, when I use
"Control Panel...Multimedia...Audio," Windows 95 reports "No Playback
Devices" and "No Recording Devices"

I tried a different installation method. After removing the drivers
that were already installed, I used Windows 95's Add New Hardware
Wizard to manually install the sound card's drivers that were supplied
by ESS Technology. The ES ESS1688 Plug and Play AudioDrive driver was
installed. The driver's files include: ESSMPU.DRV, ESFM.DRV,
ES1688.DRV, and ES1688.VXD. When I use "Control Panel...System..."
and review ES ESS1688 Plug and Play AudioDrive Properties, the Device
Status box reports "This device is not present, not working properly,
or does not have all the drivers installed. See your hardware
documentation. (Code 10.)" The ES ESS1688 Plug and Play AudioDrive
Properties does not show a Resources tab; consequently, its not clear
whether there are any device conflicts. When I use "Control
Panel...Multimedia...Audio," Windows 95 reports "No Playback Devices"
and "No Recording Devices."

I would appreciate anyone's advice on how to solve my problem. Please
send your advice to my e-mail address shown below. Thank you very
much for your help.


Michael Drevno
Hong Kong
m...@hk.super.net


William G. Schlake

unread,
Dec 28, 1996, 3:00:00 AM12/28/96
to

Fairly common problem. Main reason why Microsoft's Plug and Play is
also known as Plug and Pray. I'll assume you checked the card's
manual to see if you need to change any jumpers, that you plugged in
your speakers correctly, the sound card is seated properly in your PC
and any necessary connections between your sound card and your CD (If
you have one) are in place.

If so, boot your system, after it comes up, right click on my
computer, then Properties then select Device Manager. Look for your
sound card. Click on it's icon, and remove ALL references. OK your way
out. Turn off system. Reboot.

Windows will likely find the card and try to install it again the next
time you boot your system. In most cases, you'll be given an option
to use the CD or floppies that came with your sound card to install
it's drivers which is a better choice then letting Windows use any
drivers it may find in the Windows CD or floppies.

You should see Windows bring up a little window with a status bar as
it tries to load the needed drivers. If you don't see the files being
copied by evidence of the status bar moving to the right, you did
something wrong and not all or none of the drivers were copied which
will prevent your sound card from working correctly. Try again.

If that don't do it, remove the sound card from your PC. Reboot. Let
Windows finish coming all the way up. Turn off. Reinstall your sound
card again and repeat the above steps.

If that don't fix it and you have a lot of cards in your PC, one of
the other cards is likely taking an IRQ and/or DMA channel that the
Sound card needs. This may not have been a problem in WIN 3.1.

Assuming you don't have any conflicts (any red x's or yellow
exclamation marks in Device Manager) and if your game, remove all your
other cards except your video adapter and your disk controller card if
you have one. Then install only the sound card. If that don't install
it, you're getting into deep water and you're better off calling the
sound card Mfg. for additional suggestions.

jble...@voy.net

unread,
Dec 29, 1996, 3:00:00 AM12/29/96
to

On Sat, 28 Dec 1996 06:25:32 GMT, m...@hk.super.net (Michael Drevno)
wrote:

>Recently, I upgraded from Windows 3.1 to Windows 95 and am having
>trouble hearing anything from my sound card. I use a Dell Dimension
>XPS 466V (a 486-66) and have a ESS Technology sound card model 1833.
>The sound card is an OPL3-compatible, 16-bit stereo sound card that
>supports Plug and Play functionality. In addition, the sound card
>supports Adlib, Sound Blaster, and Sound Blaster Pro functionality.
>The sound card worked perfectly while I was using Windows 3.1. Now
>that I am using Windows 95, I hear nothing.
>
>I used Windows 95's Add New Hardware Wizard to automatically install
>the sound card's drivers. The Wizard detected the sound card and
>installed device drivers for Ad Lib Compatible (OPL2). When I use
>"Control Panel...System..." and review Ad Lib Compatible (OPL2)
>Properties, the Device Status box reports "This device is working
>properly." In addition, the Ad Lib Compatible (OPL2) Properties
>reports there are no device conflicts. Unfortunately, when I use
>"Control Panel...Multimedia...Audio," Windows 95 reports "No Playback
>Devices" and "No Recording Devices"

The adlib did not support bitmaped sound. Operating as an adlib will
give only support to MID, CMF, or other FM systhisis sound players.
This distinctly does not include WAV files.


>
>I tried a different installation method. After removing the drivers
>that were already installed, I used Windows 95's Add New Hardware
>Wizard to manually install the sound card's drivers that were supplied
>by ESS Technology. The ES ESS1688 Plug and Play AudioDrive driver was
>installed. The driver's files include: ESSMPU.DRV, ESFM.DRV,
>ES1688.DRV, and ES1688.VXD. When I use "Control Panel...System..."
>and review ES ESS1688 Plug and Play AudioDrive Properties, the Device
>Status box reports "This device is not present, not working properly,
>or does not have all the drivers installed. See your hardware
>documentation. (Code 10.)" The ES ESS1688 Plug and Play AudioDrive
>Properties does not show a Resources tab; consequently, its not clear
>whether there are any device conflicts. When I use "Control
>Panel...Multimedia...Audio," Windows 95 reports "No Playback Devices"
>and "No Recording Devices."
>

I use an ESS1688 (not plug and pray) and it works perfectly with the
drivers included with win95. Try forceing win95 into installing it as
a Sound Blaster Pro while you are looking for a different set of
drivers. Personally I like jumpers.

Michael Drevno

unread,
Dec 29, 1996, 3:00:00 AM12/29/96
to

After receiving a number of useful responses, I solved the Windows 95
sound problem. Some responses reminded me to remove ALL of the old
sound drivers before installing the new sound driver. Another
response pointed me to the following web site:

http://www.acscompro.com/faqdir/scardfaq.html#Win95

The web site indicated that one should delete any references to the
old Windows 3.1 sound drivers for the sound card from the AUTOEXEC.BAT
file. I looked at the Windows 95 Device Manager's screen more
carefully and discovered that the old Windows 3.1 sound drivers were
listed under "Other devices." I had overlooked this extra entry
earlier because I had been focusing on the entries listed under
"Sound, video, and game controllers."

After deleting the references to the old Windows 3.1 sound drivers
from the AUTOEXEC.BAT file and removing the old Windows 3.1 sound
drivers from Device Manager's listing for "Other devices," my sound
card began working again.

I can listen to RealAudio files of radio broadcasts from the U.S. and
my kids can use their educational software. Again, I would like to
thank all of the kind people who responded to my request for help.

Michael Drevno
Hong Kong
m...@hk.super.net


m...@hk.super.net (Michael Drevno) wrote:

>Recently, I upgraded from Windows 3.1 to Windows 95 and am having
>trouble hearing anything from my sound card. I use a Dell Dimension
>XPS 466V (a 486-66) and have a ESS Technology sound card model 1833.
>The sound card is an OPL3-compatible, 16-bit stereo sound card that
>supports Plug and Play functionality. In addition, the sound card
>supports Adlib, Sound Blaster, and Sound Blaster Pro functionality.
>The sound card worked perfectly while I was using Windows 3.1. Now
>that I am using Windows 95, I hear nothing.

>I used Windows 95's Add New Hardware Wizard to automatically install
>the sound card's drivers. The Wizard detected the sound card and
>installed device drivers for Ad Lib Compatible (OPL2). When I use
>"Control Panel...System..." and review Ad Lib Compatible (OPL2)
>Properties, the Device Status box reports "This device is working
>properly." In addition, the Ad Lib Compatible (OPL2) Properties
>reports there are no device conflicts. Unfortunately, when I use
>"Control Panel...Multimedia...Audio," Windows 95 reports "No Playback
>Devices" and "No Recording Devices"

>I tried a different installation method. After removing the drivers


>that were already installed, I used Windows 95's Add New Hardware
>Wizard to manually install the sound card's drivers that were supplied
>by ESS Technology. The ES ESS1688 Plug and Play AudioDrive driver was
>installed. The driver's files include: ESSMPU.DRV, ESFM.DRV,
>ES1688.DRV, and ES1688.VXD. When I use "Control Panel...System..."
>and review ES ESS1688 Plug and Play AudioDrive Properties, the Device
>Status box reports "This device is not present, not working properly,
>or does not have all the drivers installed. See your hardware
>documentation. (Code 10.)" The ES ESS1688 Plug and Play AudioDrive
>Properties does not show a Resources tab; consequently, its not clear
>whether there are any device conflicts. When I use "Control
>Panel...Multimedia...Audio," Windows 95 reports "No Playback Devices"
>and "No Recording Devices."

>I would appreciate anyone's advice on how to solve my problem. Please

Waroth Khantanaphar

unread,
Jan 2, 1997, 3:00:00 AM1/2/97
to

In message <5a2eil$6...@tst.hk.super.net> - m...@hk.super.net (Michael
Drevno)Sat, 28 Dec 1996 06:25:32 GMT writes:
:>
:>Recently, I upgraded from Windows 3.1 to Windows 95 and am having

:>trouble hearing anything from my sound card. I use a Dell Dimension
:>XPS 466V (a 486-66) and have a ESS Technology sound card model 1833.
:>The sound card is an OPL3-compatible, 16-bit stereo sound card that
:>supports Plug and Play functionality. In addition, the sound card
:>supports Adlib, Sound Blaster, and Sound Blaster Pro functionality.
:>The sound card worked perfectly while I was using Windows 3.1. Now
:>that I am using Windows 95, I hear nothing.
It did happen to me when I installed Win95 to PC with this kind of card
for the first time. Just remove those drivers that Windows 95 tried to
put them there, go to ESS web page and get 1833 driver for Windows 95.
It works well with my system.

Regards


Waroth Khantanaphar, M.D.
Dept. of Surgery
Nopparat Rajathanee Hospital
Bangkok, Thailand
----------------------------
E-mail: war...@loxinfo.co.th
Homepages: http://www.loxinfo.co.th/~waroth
http://www.angelfire.com/pg9/nopparat
----------------------------


Michael Yocca

unread,
Jan 6, 1997, 3:00:00 AM1/6/97
to

Unfortunately www.esstech.com informs you that drivers are the responsibility
of the sound card manufacturer not the chip manufacturer.  That is unless I was
referring to the wrong web address?  Please post and e-mail me.  Thanks.
--
Michael Yocca Database Analyst PPG Industries, Inc., Pittsburgh, PA  yo...@ppg.com
disclaimer "The opinions expressed are those of the writer and not of PPG Industries, Inc. nor any PPG-associated company."

Waroth Khantanaphar <war...@loxinfo.co.th> wrote in article <5agjsf$7...@netnews.loxinfo.co.th>...

Zoltan A. Ori

unread,
Jan 10, 1997, 3:00:00 AM1/10/97
to

Guys,

Did you leave all your config.sys and autoexec.bat settings in place? If
you did, do sysedit and rem them out. Then, go to control panel, select
system and remove your sound card. Reboot Win 95.
These cards have been installed and work with no problem on other systems
using Win95.

For DOS use, you will still need all the settings that you rem'd out for
Windows. You can make a seperate DOS boot config.sys and autoexec.bat

Ezekiel Krahlin <e...@wco.com> wrote in article <5b7avc$c...@news.wco.com>...
> Michael, I have experienced the identical problem, upgrading from Win31
to
> Win95...only I have a SoundBlaster 16 card.

> In microsoft.public.win95.setup Michael Drevno <m...@hk.super.net> wrote:
> > Recently, I upgraded from Windows 3.1 to Windows 95 and am having >
> trouble hearing anything from my sound card. I use a Dell Dimension >
XPS
> 466V (a 486-66) and have a ESS Technology sound card model 1833. > The
> sound card is an OPL3-compatible, 16-bit stereo sound card that >
supports
> Plug and Play functionality. In addition, the sound card > supports
> Adlib, Sound Blaster, and Sound Blaster Pro functionality. > The sound
> card worked perfectly while I was using Windows 3.1. Now > that I am
> using Windows 95, I hear nothing.
>
>

> ----------------------------------------
> B4 HairClub4Smileys: (:( After: =(:)
>

Ezekiel Krahlin

unread,
Jan 11, 1997, 3:00:00 AM1/11/97
to

Michael, I have experienced the identical problem, upgrading from Win31 to
Win95...only I have a SoundBlaster 16 card. Everything you said re.
Win95's control box and wizard responses, are identical to my situation.
I have no answer, but this is just to acknowledge that something in very
wrong somewhere, with Win95. Let's keep our fingers crossed that someone
has a real answer. By the way, do you still get sound in DOS mode? I do.

Ezekiel Krahlin

unread,
Jan 11, 1997, 3:00:00 AM1/11/97
to

In microsoft.public.win95.setup Michael Drevno <m...@hk.super.net> wrote:
> After receiving a number of useful responses, I solved the Windows 95
> sound problem. Some responses reminded me to remove ALL of the old
> sound drivers before installing the new sound driver. Another
> response pointed me to the following web site:

Well: I just wrote about the same problem you had, then a few messages
down, you have a solution. Thanks! Looks like it will work for me, too.

Ian Carney

unread,
Jan 12, 1997, 3:00:00 AM1/12/97
to

On 11 Jan 1997 06:11:56 GMT, Ezekiel Krahlin <e...@wco.com> wrote:

>Michael, I have experienced the identical problem, upgrading from Win31 to
>Win95...only I have a SoundBlaster 16 card. Everything you said re.
>Win95's control box and wizard responses, are identical to my situation.
>I have no answer, but this is just to acknowledge that something in very
>wrong somewhere, with Win95. Let's keep our fingers crossed that someone
>has a real answer. By the way, do you still get sound in DOS mode? I do.
>
>

>In microsoft.public.win95.setup Michael Drevno <m...@hk.super.net> wrote:

>> Recently, I upgraded from Windows 3.1 to Windows 95 and am having >
>trouble hearing anything from my sound card. I use a Dell Dimension > XPS
>466V (a 486-66) and have a ESS Technology sound card model 1833. > The
>sound card is an OPL3-compatible, 16-bit stereo sound card that > supports
>Plug and Play functionality. In addition, the sound card > supports
>Adlib, Sound Blaster, and Sound Blaster Pro functionality. > The sound
>card worked perfectly while I was using Windows 3.1. Now > that I am
>using Windows 95, I hear nothing.
>
>

>----------------------------------------
>B4 HairClub4Smileys: (:( After: =(:)

Don't know if this helps, but no-one is offering you anything more. After hours with the same
problem (1) if your BIOS does not support PnP, then make sure any PnP jumpers are set to deactivate
PnP on your card (2) '95 seems to assume my cards are PnP by default but with old BIOS I could not
get scard to work - I had to overide it and once the jumper was changed - everything was OK. Regards
> Ian Carney.

0 new messages