Ygor
11-19-1999, 01:16 PM
That must be a driver for the motherboard or the sound card. Look on your cd that came with the mobo or your sound card for that file & replace it.
| //flex table opened by JP
Click to See Complete Forum and Search --> : Oh Dear!!! Ygor 11-19-1999, 01:16 PM That must be a driver for the motherboard or the sound card. Look on your cd that came with the mobo or your sound card for that file & replace it. Axel 11-19-1999, 05:03 PM Few questions - What kind of ASUS board is it - model # - I.E. - is the sound card on board?? Have you checked the ASUS site for software driver patches for that board? Where does the error message show up in your boot sequence? hit <pause> to freeze the screen and <esc> to make the win logo go away. Perhaps you can tell if it's happening in your config.sys file or later in your autoexec.bat file and that might help you isolate fixing it. Might be there, but "rem"ed out so it won't execute. - also - can you get into your system at all to do a search for that file name? Axel 11-19-1999, 05:13 PM A few other things that come to mind - If you are talking about just the CD-ROM playing music? - try headphones to see if those work - if they do - then check inside the case to make sure you have a (typically) gray cable going between the CD drive and the sound card - this cable typically has a 4 conductor black plug at both ends. Sometimes there is also a similar cable going from the modem to the sound card. Is the sound card is seperate from the mobo - did you load a wave table? Have you tried plugging in a mic and recording a sound file? Do the speakers you have require batteries to amplify the sound? - have you tried head-phones directly into the sound card? Y Cymro 11-19-1999, 05:14 PM The m/b is aP5A with no on board sound. The sound card I have is an old SB16Value which only has drivers for Win 3.11. I'm not sure if my problem is anyhting to do with C:\MM_Patch.com now as I've just put in Tomb Raider II and there it was - SOUND! But then anything played through Windows no sound. I've tried removing the card then re-installing, but this doesn't change anything. Confused now! Y Cymro 11-20-1999, 12:55 AM I've just upgraded to an Asus m/b with an AMD K6 iii 400, everything is hunky dorey exept for sound. There is none. When my system boots up I get a message saying C:\MM_PATCH.COM is missing or corrupted in my config.sys. What does it mean and what do I do? Flash 11-20-1999, 02:00 AM This may seem strange but did you ever have a free Y2K check thing on your PC, I'm sure this is what this mm_patch.com is from, I had it and after I had used the program to check my PC, each time it started up it flashed up a little green caption saying that my PC was ok. This may be stupid but look in your autoexec.bat and see if it mentions mm_patch.com in there. I just deleted that entry because the little green screen was annoying me. It is possible that the you deleted the file that is called upon startup. As to your original problem, who knows? Don't alter the autoexec.bat if you are not sure what the mm_patch.com was, it's just a thought. Good luck! CMonster 11-20-1999, 04:09 AM If your sound card is a genuine Sound Blaster and your OS is Win95 this should work; Go to device manager and insure that there are no resource conflicts; next, under "Sound," find your sound card entry, highlight it and click "Properties," then click the "Driver" tab and let Windows search for an updated driver. Be sure that you have the Windows CD in the CDROM drive. If Windows does not find a driver browse to the Windows CD /Drivers/Audio/asb16 directory and then click all the necessary "OK" to finish. [This message has been edited by CMonster (edited 11-20-1999).] Y Cymro 11-20-1999, 07:00 AM Tried your suggestions CMonster. I'm still getting some error messages when I boot up relating to my config.sys. But then windows will start and I get about 1/2 a second of the opening sound then silence. medo 11-20-1999, 07:18 AM Hello, Check your settings. Usualy by default: Interrupt 5 Direct mem. access 1 (Low) " " " 5 Input-Output 220 You realy have to check system settings, because something use memmory or inerrupt. I hope it will help. CMonster 11-20-1999, 03:12 PM medo is very likely correct. Did you check for resource conflict again after installing the new drivers? Look for a yellow exclaimation mark in front of the devices in Device Manager - correct any of these problems that you find. You will probably have to edit your config.sys file to correct the other problems. Probably you can just save "config.sys" as config.bak and do the same with "autoexec.bat" save it as autoexec.bak then you can delete autoexec.bat and config.sys and boot directly into Windows - yep, believe it or not Windows 9x doesn't really need them except in a few rare instance (like doing a startup antivirus scan or loading DOS level CDROM drivers). If something doesn't work you can always do the reverse of the above instructions and get back to where you are now. Y Cymro 11-21-1999, 06:53 AM Just noticed that MIX0014 LOW LEVEL DRIVER ERROR also appears on booting up. Anyone know what this means? CMonster 11-21-1999, 10:59 AM Did you try the thing with autoexec.bat and config.sys? I have nothing but a WAG (wild-*****-guess) on the thing you just mentioned, but it could be a low-level sound/mixer driver that is loaded from one of your configuration files autoexec.bat or config.sys; You could also try editing autoexec.bat and config.sys and look for a reference to any old sound drivers; in autoexec.bat put a "rem" and a space in front of that line. welsh wizard 11-23-1999, 07:12 AM you prob done this, try uninstalling sound card driver and then reinstall with windows. might just work. WW ktwebb 11-23-1999, 10:00 AM REM out the line in your config.sys and reboot to see if that solves anything. To do this: while in windows (you can do it in dos if you like) go to the start menu, and run, in the run window type sysedit. Your system editor configuration window will pop up with your autoexec, config.sys, and pertinent ini files. Click on the config.sys window and either put REM and a space in front of the line that you are getting the error on or simply put a ; in front of the line with no space. Then next time you boot, that line will not be recognized. You say you here sound for a second when you first boot up. If this is true you dont have an IRQ problem, you would get that problem while windows was loading. Get back with the board on your progress. Y Cymro 11-23-1999, 06:20 PM Cheers all. Using a combination of all (or most) of the above, problem sorted - nice one. SysOpt.com
Copyright Internet.com Inc. All Rights Reserved. |