# PM123's Troubleshooting

## 1. The player skips and/or the audio doesn't sound right!

> There might be multiple reasons if you encounter this problem. Some of them are listed here. First of all, check your audio file. It may be broken. It might play succesfully on another player, but mpg123 may not necessarily like it. If you think it's not related to the input stream, maybe the problem is one of these:
> - You have a polling device driver (for example, a very old 2x CD-ROM or `PRINT01.SYS` without `/IRQ` switch)
> - Bad CD-ROMs tend to seek the disk often. This usually takes 100% CPU and halts I/O operation until the drive completes the seek. You can try cleaning the CD.
> - You have a process that hogs all the CPU. Get a CPU monitor (we recommend CPUMon) and a process killer from `hobbes.nmsu.edu`.
> - Your CPU is too slow (or overheated).
> - You have outdated, old or buggy sound drivers. This is a common problem. Many sound drivers out there for OS/2 just plain suck. We have tried to test PM123 on as many drivers as we can, but some drivers are incomplete and/or buggy.
> - You have a very old or just generally bad motherboard, video card or IO controller card. This is a rare problem, though.

## 2. The volume control in PM123 doesn't works.

> Try to change state of checkbox "Control master volume" in settings of DART output plug-in.

## 3. After starting some applications the music stops and continues after closing this application.

> Your sound device doesn't support a sharing mode. Try to remove mark from "Sound device is shared" in settings of DART output plug-in.

## 4. The player crashes on startup.

> - You have an old `MPG123.DLL` (or some other DLL PM123 comes with) in your `LIBPATH`.
> - Your system doesn't support DIVE (Direct Video Extensions). Try renaming `visplug\analyzer.dll` to something else.
> - Something is very wrong....

## 5. My mouse cursor is jerky or jumpy!

> - You have a colored or animated mouse pointer that is not supported properly by your video driver. They are software mouse cursors and they don't mix very well with high performance multimedia applications that draw rapidly to the screen. Switch back to the old black and white OS/2 default mouse pointer and/or disable pointer animation. The default b/w pointer is a hardware mouse cursor. This problem is often caused by all high speed DIVE applications.
> - If all fails, one way to fix this problem is to set analyzer disabled by default (Properties -> Plug-Ins -> analyzer.dll -> Configure). Of course you won't see the cool graphics then.