|
FAQ
Before you think about reporting a bug, please go through this FAQ to see if your problem
is already answered here. All questions mailed to me but already answered here will be ignored.
| Q : |
Emulator crashes when trying to exit (Voodooł/Banshee users)
| | A : |
Make sure you are not running the emulator at exactly the same resolution as your desktop. Also, setting
your desktop to 32-bit colour may help. This is a bug in the Voodooł/Banshee drivers.
|
| Q : |
"Mutual exclusion prohibits this" error message
| | A : |
If it happens every time you run PSEmu, then it is probably down to one of the following :
- You are running a background task/application that is hogging the Voodoo card. Taskbar applications used to
configure Direct3D options can do this. Try stopping any that you have running in turn until you find the one (if
there is one) that is interfering.
- You have an OpenGL plugin in the plugins directory, and you have installed the 3dfx OpenGL driver. Unfortunately,
due to the way PSEmu handles plugins (I guess), the OpenGL plugin with 3dfx OpenGL driver hogs the 3dfx card, so my
plugin can't use it. Try removing the 3dfx OpenGL driver, and only put it back when you _really_ want to use it. If
you are using the OpenGL plugin more than my Glideł plugin, then I need to do some serious work :(
"Mutual exclusion prohibits this" error is a new "feature" of Glideł, designed to prevent program contention. Previous
versions of Glide did not handle multi-tasking situations, which 3dfx have tried to address.
If this problem happens occasionally, it could be that a program you have previously run since last rebooting your
PC did not close down cleanly, and has left Glide in a bad state. The only way around this is to reboot.
|
| Q : |
"VXD Error: expected v1.4 found v1.x" error message
| | A : |
The file in question is FXMEMMAP.VXD. What the error message means is this: Glide is loading, and looking for the file
it needs, FXMEMMAP.VXD. The file it is finding is the wrong version: it is too old. Therefore, Glide can't run :(
This can happen for a number of reasons, but the main reason is due to stray copies of FXMEMMAP.VXD on the computer,
that are not getting updated when the main drivers are getting updated.
A common place for an extra copy of FXMEMMAP.VXD is in the WINDOWS directory (it should only be in the WINDOWS\SYSTEM
directory, and the WINDOWS directory is checked first in the path). If you have a copy of FXMEMMAP.VXD in the WINDOWS
directory, rename it to FXMEMMAP.OLD (you can search your entire hard-disks, and rename all copies that are not in the
WINDOWS\SYSTEM directory). Then make sure the latest version of FXMEMMAP.VXD is in the WINDOWS\SYSTEM directory (there
should already be a copy of the file there, so make sure it is up-to-date ... the latest version is in the 3dfx driver
archive that you installed).
Once you are happy your problems are resolved, you may deleted any FXMEMMAP.OLD files, as they are unnecessary and are
just taking up your hard disk space :)
|
|
|
