Next: Developers Manual
Up: Frequently Asked Questions
Previous: Frequently Asked Questions
Windows Vapc driver specific
The following are errors messages that might appear in the cphost log
along with a short description what caused them and how to avoid them.
- The DLL vocp.dll couldn't be loaded
- the vocp.dll wasn't found. be sure that it's loadable, that
means somewhere in your path. windows\system should
be a good place
- WARNING: Couldn't set priority class! or WARNING: Couldn't set thread priority!
- the host couldn't instruct windows to give him more cpu-power. there
will be serious skipping while playing.
- ERROR: Couldn't load VAPC.VXD! Is the VAPC.VXD in your textttwindows\system-directory?
- yeah, the vapc.vxd must be in your system directory.
- DEVPDX5: couldn't lock primary ... or DEVPDX5: couldn't play on primary ...
- no problem, the driver will use secondary buffer.
- DEVPDX5: couldn't create directsound-object
- your soundcard is in use by some other stuff, maybe a dosbox, maybe
this dosbox. remove all other hardware-devices from your
cp.ini, as described in the beginning of this document.
If you own a sound card supported by OPENCP and have difficulties using
the vapc drivers there is the chance that both drivers interfere. You
may try to remove all native OPENCP drivers from the ini file. The
corresponing lines should look like this:
The native-driver will use the soundcard, and windows will reserve
the device for the OPENCP-task.7.1 If this
occurs, you will find something like couldn't create
dsound-object in the cphost-log. so, remove the other
device-driver, restart the dosbox, and enjoy.
It must be possible to launch some direct-sound-output while
the cp is running (not neccesarily playing). try a
winamp or something first (using DirectSound, not
WaveOut). If this works, continue using OPENCP with DirectSound.
Footnotes
- ...OpenCP-task.7.1
- better: OPENCP-VM
Next: Developers Manual
Up: Frequently Asked Questions
Previous: Frequently Asked Questions
documentation by doj / cubic