I too was having this problem but ran across the following info when I ran a search from goole.com (used MMSYSTEM007 as the search criteria): "This error may occur on some configurations when you try to play, record, or monitor the VU level. It is a Windows error that probably relates to insufficient memory resources available for the sound card. Possible Solutions to MMSYSTEM 007 and MMSYSTEM 256 errors: Make sure the [boot] section of SYSTEM.INI has "drivers=mmsystem.dll" to load the mmsystem drivers on bootup instead of while running an application. Check that the [drivers] section of SYSTEM.INI has "wave=mmsystem.dll" and "midi=mmsystem.dll" Try lowering the "FILES=x" line in CONFIG.SYS Try lowering the "BUFFERS=x" line in CONFIG.SYS to 23, then down to 13 at the lowest. Don't use any 16-bit sound drivers. Try not to load any 16-bit sound drivers in CONFIG.SYS, and if they must be loaded, load them high (DEVICEHIGH=)." the url for the above is: http://www.wireready.com/tech%20support/FAQ/completefaqs/cooledit/faq/shared/mmsys07.htm It help me, hope it helps you. :-)

0

EASY ANSWER TO WINAMP PROB open up options .. and select plugins and output in the plugin options .. select direct sound output .. then give it a play .. this works on my system fine :)

0

Same problem after upgrading to 98 ver 2,adding 128mb ram, and new video card. Tried Manta's fix, worked a treat many thanks.

0

Hi The fix suggested by manta is actually NOT a fix: it's just a workaround: you're using DX instead of the MM ressources. For those suggesting running less programs in the BG, adding more ram, etc. This won't do it either. This is actually a problem with windows (big surprise uh ?) that happens when some multimedia components are missing or damaged, or are the wrong version of the file. You can have this error message and still have 70% of your computer ressources free!!! Go the support site of microsoft (knowledge base) and enter this error message (MMSYSTEM007 Not enough blablabla). This is a (tedious) solution to the problem...

0

Goa303's response is dead on. The direct sound output option in Winamp is strictly a workaround for the Winamp player only! I still have the "Out of Memory" problem randomly occurring during RealPlayer (.ra, .ram, .rm, .ram files) playback. Like Matti, I've gotten to the point where I first launch a RealPlayer file to ensure it works (I know I can use Winamp via the workaround). If it fails, I keep restarting til it works. My 224MB of RAM should dismiss the need to add more RAM. I've searched microsoft's support site to no avail. It's been awhile since my last visit to its site, so I'll need to check again as Goa303 suggests. It is interesting to note that I've never received an "Out of Memory" error message when launching MICROSOFT's Windows Media Player! Is this an intentional design bug lending to Microsoft's conspicuous silence? Anyhow, it's been five or so months since this problem first reared it grotesque head and I'm still searching for that Silver Bullet!

0

I'm having the same problem with winamp. and the netphone that comes with the new MSN explorer. My solution (so far) is to be sure the volume control icon is shown on the systray (sometimes it isn't and the box is grayed out) and then run Norton Utilities windoc. Even if nothing is wrong, this seems to fix it. And of course turning the computer off and back on starts the whole process over again. I find I have to launch real audio right away or it thinks there is not enough memory, etc. BTW I have 128 megs of ram and virtual memory set to my 2nd drive with 10 gigs of space!

0

All these solutions that have been posted up...honestly, have they actually worked?I myself is having the same problems for a year and i still havent found a way to fix it. My procedures are as follows: I turn on my computer...wait till evryting loads up and like the rest of you guys check if winamp works....but then the error message mmsystem 007...pops up....I've been wondering if any of you find a definite way to fix the problem. Please,im just as desperate as any of few...please help!!!!!

0

!!!FINALLY!! I discovered a way to fix the problem. I haven't had that problem...ever since I posted my last message.Thanx for all of your help anyway!!!

0

Hey Jay Park! How 'bout sharing that with the rest of us. I've been following this thread down to the end and ... and ... So c'on and let the rest of us know what the solution was!

0

Okay, I THINK this will fix Winamp, it did for me, and it also worked for Sonique (which had the same error message). If you can just restart your computer and get rid of the problem, you're lucky. I had to reinstall 9 dll files to get Winamp back and running. Microsoft claims a reinstall of Windows Media Player or a few other programs will do it, but it didn't work for me. I went out and got the damaged (I assume) dlls and then put them into my C:\Windows\System directory. Here are the files that you need: Avifile.dll Dciman.dll Dciman32.dll Mciavi.drv Mmsystem.dll Msvidc32.dll Msvideo.dll Msvfw32.dll Wow32.dll and you can get them here: http://drd.dyndns.org/dll/win98se/ I downloaded all the files, went into DOS Mode (you have to go into DOS to replace mmsystem.dll) and copied them into the appropriate directory. This should probably be a last resort, but it works. I've had the mmsystem007 message in the past, but it was sporadic and I could get rid of it with a restart. This last time it wouldn't leave so I had to use the above solution. It wasn't a RAM problem (64 megs has worked fine for me, in fact my previous machine had 32 and no problem) or Config.sys File and Buffer number problems. The files corrupted, and that's how you fix em.

0