audio is gone
Pierre Jelenc
for instance) and video ones (VLC, KMP, etc) refuse to play sound (the
video apps do play the video parts) with the same error message:
"Cannot load MMPM2 driver".
They all worked fine about a week ago (I don't usually play sound or video
on the computer, but occasionally I need to.)
I see an MMPM2.INI file in \MMOS2 but nothing that looks like a driver.
Unfortunately my backups are all too recent and they don't either seem to
have any such driver. Where is it supposed to be? I'm currently still
using eCS 1.2.
Thanks,
Pierre
--
Pierre Jelenc
The Gigometer www.gigometer.com
The NYC Beer Guide www.nycbeer.org
Peter Brown
Pierre Jelenc wrote:
> I seem to have lost something in my audio setup: both plain audio apps (Z!
> for instance) and video ones (VLC, KMP, etc) refuse to play sound (the
> video apps do play the video parts) with the same error message:
> "Cannot load MMPM2 driver".
>
> They all worked fine about a week ago (I don't usually play sound or video
> on the computer, but occasionally I need to.)
>
> I see an MMPM2.INI file in \MMOS2 but nothing that looks like a driver.
> Unfortunately my backups are all too recent and they don't either seem to
> have any such driver. Where is it supposed to be? I'm currently still
> using eCS 1.2.
>
> Thanks,
>
> Pierre
What audio driver do you use?
Is it definitely loading at boot?
Do you have system sounds?
Check mmpm2.ini to make sure the driver is listed eg uniaud will have
several entries [UNIAUDWAVE01], [UNIAUDWAVE01-PLAY],
[UNIAUDWAVE01-RECORD], [UNIAUDAMPMIX01]
Maybe 1 of the above is missing in the mmpm2.ini file.
Regards
Pete
Pierre Jelenc
config.sys has:
DEVICE=C:\MMOS2\UNIAUD32.SYS /V
DEVICE=C:\MMOS2\UNIAUD16.SYS /V /C
> Is it definitely loading at boot?
I assume so, there is no interruption of the boot process. The files are
where they should be:
8-02-05 5:57 61,594 226 uniaud16.sys
1-19-06 16:00 568,236 276 uniaud32.sys
> Do you have system sounds?
I do have the usual beeps upon error and new mail notification, but those
come through the system's speaker, as they've always done.
> Check mmpm2.ini to make sure the driver is listed eg uniaud will have
> several entries [UNIAUDWAVE01], [UNIAUDWAVE01-PLAY],
> [UNIAUDWAVE01-RECORD], [UNIAUDAMPMIX01]
No, all four sections are there.
Peter Brown
Pierre Jelenc wrote:
> Peter Brown<losepeteS...@ntlworld.com> writes:
>>
>> What audio driver do you use?
>
> config.sys has:
> DEVICE=C:\MMOS2\UNIAUD32.SYS /V
> DEVICE=C:\MMOS2\UNIAUD16.SYS /V /C
>
>> Is it definitely loading at boot?
>
> I assume so, there is no interruption of the boot process. The files are
> where they should be:
> 8-02-05 5:57 61,594 226 uniaud16.sys
> 1-19-06 16:00 568,236 276 uniaud32.sys
>
>> Do you have system sounds?
>
> I do have the usual beeps upon error and new mail notification, but those
> come through the system's speaker, as they've always done.
>
>> Check mmpm2.ini to make sure the driver is listed eg uniaud will have
>> several entries [UNIAUDWAVE01], [UNIAUDWAVE01-PLAY],
>> [UNIAUDWAVE01-RECORD], [UNIAUDAMPMIX01]
>
> No, all four sections are there.
>
> Thanks,
>
> Pierre
I wonder if you have a corrupt or missing \mmos2\dll\mmpm.dll file?
Regards
Pete
Pierre Jelenc
>
> I wonder if you have a corrupt or missing \mmos2\dll\mmpm.dll file?
it's there:
6-24-04 1:43 432,003 0 mmpm.dll
[c:\desktop]BLDLEVEL \mmos2\dll\mmpm.dll
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature: @#IBM:14.075#@
Vendor: IBM
Revision: 14.75
File Version: 14.75
Description:
I don't suppose these things have an internal checksum to test for
integrity?
ivan
wrote:
> Peter Brown <losepeteS...@ntlworld.com> writes:
> >
> > What audio driver do you use?
>
> config.sys has:
> DEVICE=C:\MMOS2\UNIAUD32.SYS /V
> DEVICE=C:\MMOS2\UNIAUD16.SYS /V /C
>
> > Is it definitely loading at boot?
>
> I assume so, there is no interruption of the boot process. The files are
> where they should be:
> 8-02-05 5:57 61,594 226 uniaud16.sys
> 1-19-06 16:00 568,236 276 uniaud32.sys
>
> > Do you have system sounds?
>
> I do have the usual beeps upon error and new mail notification, but those
> come through the system's speaker, as they've always done.
>
> > Check mmpm2.ini to make sure the driver is listed eg uniaud will have
> > several entries [UNIAUDWAVE01], [UNIAUDWAVE01-PLAY],
> > [UNIAUDWAVE01-RECORD], [UNIAUDAMPMIX01]
>
> No, all four sections are there.
>
> Thanks,
>
> Pierre
There is also the possibility that the sound card has died, hence no
response even if the drivers are loading.
ivan
--
KO Myung-Hun
Pierre Jelenc wrote:
> Peter Brown <losepeteS...@ntlworld.com> writes:
>>
>> I wonder if you have a corrupt or missing \mmos2\dll\mmpm.dll file?
>
> it's there:
>
> 6-24-04 1:43 432,003 0 mmpm.dll
>
> [c:\desktop]BLDLEVEL \mmos2\dll\mmpm.dll
> Build Level Display Facility Version 6.12.675 Sep 25 2001
> (C) Copyright IBM Corporation 1993-2001
> Signature: @#IBM:14.075#@
> Vendor: IBM
> Revision: 14.75
> File Version: 14.75
> Description:
>
> I don't suppose these things have an internal checksum to test for
> integrity?
>
How about re-installing an audio driver ?
And I've found the article which says the same problem as you.
They fixed the problem using 'checkini'.
See for the details,
http://www.os2world.com/component/option,com_smf/Itemid,63/action,printpage/topic,1354.0/
Good luck.
--
KO Myung-Hun
Using Mozilla SeaMonkey 2.0.3
Under OS/2 Warp 4 for Korean with FixPak #15
On AMD ThunderBird 1GHz with 512 MB RAM
Korean OS/2 User Community : http://www.ecomstation.co.kr
Pierre Jelenc
I guess, but I have no idea where the current one comes from.
> And I've found the article which says the same problem as you.
> They fixed the problem using 'checkini'.
That's not the same as mine: I don't usually run FireFox (I prefer
SeaMonkey), the problem exists right after a fresh reboot, and I do clean
my INI files regularly with both checkini and Unimaint. There have been no
changes of hardware, no changes to config.sys and no changes to any
program that is run from the startup folder.
Pierre Jelenc
>
> There is also the possibility that the sound card has died, hence no
> response even if the drivers are loading.
Ah, I did not think of that. I guess it's possible for the card to still
respond enough during boot to prevent a config.sys error, yet have a
problem later on. (The speakers work fine when plugged into a portable CD
player, by the way.)
Is there a way to test that, to send a signal directly to the card?
Ilya Zakharevich
> ivan <iva...@free.fr> writes:
>>
>> There is also the possibility that the sound card has died, hence no
>> response even if the drivers are loading.
>
> Ah, I did not think of that. I guess it's possible for the card to still
> respond enough during boot to prevent a config.sys error, yet have a
> problem later on. (The speakers work fine when plugged into a portable CD
> player, by the way.)
>
> Is there a way to test that, to send a signal directly to the card?
IIRC, if Z! does not give you errors, your software setup is correct
(as far as DART is concerned). So I also suspect your card... (But
maybe I just like to argue with everybody who claims "my hardware did
not change" - without trying an alternative OS. ;-)
Ilya
ivan
wrote:
> ivan <iva...@free.fr> writes:
> >
> > There is also the possibility that the sound card has died, hence no
> > response even if the drivers are loading.
>
> Ah, I did not think of that. I guess it's possible for the card to still
> respond enough during boot to prevent a config.sys error, yet have a
> problem later on. (The speakers work fine when plugged into a portable CD
> player, by the way.)
>
> Is there a way to test that, to send a signal directly to the card?
>
> Pierre
There is no easy way to test and be sure it is the card without a lot
of expensive equipment.
It could be that just the output stage is faulty - that would let the
OS see the card at boot but nothing would get out to the real world.
One quick and dirty test would be to get one of the linux live cds and
see if that will produce sound. If it doesn't then I think a new card
is in order.
ivan
--
KO Myung-Hun
Pierre Jelenc wrote:
> KO Myung-Hun <ko...@chollian.net> writes:
>>
>> How about re-installing an audio driver ?
>
> I guess, but I have no idea where the current one comes from.
>
You can get it here,
Ilya Zakharevich
Oups, forgot to mention two other viable causes of Z! being OK with
no sound:
2) mixer sitting at 0;
3) speaker/earphone wire.
Ilya
Lars Erdmann
> ivan<iva...@free.fr> writes:
>>
>> There is also the possibility that the sound card has died, hence no
>> response even if the drivers are loading.
>
> Ah, I did not think of that. I guess it's possible for the card to still
> respond enough during boot to prevent a config.sys error, yet have a
> problem later on. (The speakers work fine when plugged into a portable CD
> player, by the way.)
>
> Is there a way to test that, to send a signal directly to the card?
>
> Pierre
Use "unimix.exe" for help on the parameters.
Use "unimix.exe -names" to get the IDs (and names) of the controls you can manipulate.
You can then subsequently use "unimix.exe -id2 -val100" or the like to change the value.
You will need to fumble around with it a little. You want to increase the master playback volume
+ potentially the PCM playback volume.
Search google on its use.
Lars
Pierre Jelenc
>
> One quick and dirty test would be to get one of the linux live cds and
> see if that will produce sound. If it doesn't then I think a new card
> is in order.
Well, the sound is fine in Linux, so it's not hardware.
Pierre Jelenc
[c:\desktop]unimix.exe
Command line mixer for UNIAUD. Version 0.02
Copyright 2004 by Vlad Stelmahosky aka Vladest
Error: unsupported version of uniaud
(Why would it have changed spontaneously anyway, and how could it cause Z!
to say it's unable to load a driver?)
ivan
> ivan <iva...@free.fr> writes:
> >
> > One quick and dirty test would be to get one of the linux live cds and
> > see if that will produce sound. If it doesn't then I think a new card
> > is in order.
>
> Well, the sound is fine in Linux, so it's not hardware.
>
> Pierre
That is good in that we now have to concentrate on the software side.
There is nothing worse than spending weeks trying to find a problem
with software only to find it was hardware all along. The more parts
of the system that can be eliminated the better.
ivan
--
Steve Wendt
> Command line mixer for UNIAUD. Version 0.02
> Copyright 2004 by Vlad Stelmahosky aka Vladest
> Error: unsupported version of uniaud
You must have an outdated version:
9-22-10 12:17p 18253 0 unimix.exe
Command line mixer for UNIAUD32. Version 1.0
Detected UNIAUD version 1.92
Pierre Jelenc
Thanks; that did the trick (just copying the uniaudxx.sys over the old
ones.)
Thanks to all.