OK thanks for the useless "advices" i managed to uninstall ms kernel audio
drivers (I happened to recieve information that special system variable must
be set to allow the invisible drivers in Device Manager to be seen) and maybe
also added missing wmaudio.inf then the MPU401 part of soundcard driver got
detected and then all the kernel drivers and sound card driver got
reinstalled. From here on sound can be heard. Case closed
"DL" wrote:
> Presumably you checked HP site for any updates FAQ's
> Try Dxdiag the direct x checking tool, see what it reports
>
> "Mike" <(E-Mail Removed)> wrote in message
> news:9EB87933-4C4C-4F1D-94AD-(E-Mail Removed)...
> > Update:
> > I have found out on the net that this problem may be associated with MS
> > sound kernel and ms streaming proxies... MS Kernel audio driver, splitter
> > etc.. I noticed one uknown yellow unknown device which i manually
> installed
> > and which showed to be MS kernel GS wavetable synthesizer. Anyway by now
> the
> > these MS drivers are missing in the AUDIO drivers tree. They only show up
> for
> > a second when i reinstall the Soundcard driver, than they disappear. I
> > noticed there is kind of solution related to this called MESoundFix which
> > fixes the registry but is aimed at Windows ME.
> >
> > "Mike" wrote:
> >
> > > I have Omnibook 510 with integrated ESS 1988 audio. After some tinkering
> the
> > > driver installation is messed up. Uninstallation, reinstallation update
> of
> > > driver gives same result:
> > > driver is reported to be installed correctly but the sound devices under
> > > driver properties are reporting error like : driver is enabled but not
> > > working properly (i have different language version WIN), also Sound
> devices
> > > menu under Control panels says sound device does not exist.
> > > Driver consists of four files
> > > system32/drivers/es198x.sys
> > > system32/drivers/ks.sys
> > > system32/ksproxy.ax
> > > system32/ksuser.dll
> > >
> > > The last 3 files are some Microsoft libraries for DirectX Kernel
> streaming
> > > or what.
> > > They seem to be latest version (service pack 2). I suppose the problem
> is
> > > somewhere with the registration of those files. Anyway how can i solve,
> debug
> > > this.. Any clues..
>
>
>