Error Messages […]
Show full quote
Error Messages
This page contains information the following errors:
The Config N*50 does not exist
Out of Memory
DINPUT.DLL Not Found
"GLIDE.DLL Not Found" and "Get Caps Failed"
Error: Executible not defined in Config
Error: Missing software=0, missing hardware=3dfx
Warning: Please Insert POD CD-ROM
Error: POD cannot run in 8/24/32 bits graphic mode
POD FATAL ERROR: GCD INIT FAILURE
Pod Fatal Error: grSstWinopen error
The Config N*50 does not exist:
There are two main times when this message will appear:
If it shows up when you put the POD CD in the CD-ROM drive, it usually just means that the version of POD that is installed is different from the version of POD that is on the CD. Just close the program, and run POD from your normal shortcut. Thanks to Coney for mentioning that one.
If you are starting POD from your normal shortcut, or directly from the POD EXE file on your hard drive, and you get this message, or if you get this message while you are running a POD patch, it means there is a general error in your UBI.INI file. The simplest way to recover from here is to uninstall POD, delete all the config files, and start over. Please read the Uninstalling POD Completely page, for details on which folders you need to delete after uninstalling POD.
Back to Top
Out of Memory:
This error most often occurs after using a POD patch. The patches are not good at changing shortcuts, usually they put invalid data into the shortcut, or damage it. All you need to do is:
Launch the Windows Explorer. Go to the [C:\UBISOFT\POD] directory and find a file called something like "PODATIX.EXE" or "PODMMX.EXE" OR "POD3DFX.EXE", depending on which graphics card you have. Either way, the file will have the letters "POD" in it and will display the Pod Icon next to it's name.
Double-click the filename, and if Pod loads, you can change your shortcut to point to this file.
Back to Top
DINPUT.DLL Not Found:
This usually means that you don't have the correct version of Microsoft's DirectX API installed. POD OEM requires DirectX 2 or better, while Pod Full Retail requires DirectX 3 or better. I recommend getting a copy of the newest version, which you can download from Microsoft's DirectX Resource Page.
Back to Top
"GLIDE.DLL Not Found" and "Get Caps Failed":
This usually means that POD is looking for the old Voodoo1 GLiDE driver files, but cannot find them. If you have a new 3dfx card in your system you should un-install/re-install POD, and use the 24MB 3dfx patch. If you have a Voodoo1 card in your system, try using the GLiDE 2.11 files from ftp.3dfx.com/pub/glide211/gld211rt.exe. More help with 3dfx POD can be found on the 3dfx Voodoo FAQ Page.
Back to Top
Error: Executible not defined in Config:
This can be caused by two things, either using the wrong patch, or because of some form of corruption to your UBI.INI file. The best thing to do if this error is encountered is to start from a totally fresh base install of POD:
If you have any track lap records you want to save, make a copy or ZIP of the [C:\UBISOFT\POD\DATA\RECORDS] folder.
Go to Start/Settings/Control Panel. Double-click Add/Remove Programs. Click on POD in the list and click the Add/Remove button.
Delete the [C:\UBISOFT\POD] and [C:\WINDOWS\UBISOFT] folders, and re-boot the computer.
Re-install POD from your CD, ideally choosing a medium or large install.
Try using whatever patch you were using when the error occured.
Back to Top
Error: Missing software=0, missing hardware=3dfx:
This error means that the pod installer cannot find your 3dfx card. Please see the 3dfx Voodoo FAQ Page for details of how to install and/or patch POD to work with any 3dfx Voodoo card.
Back to Top
Warning: Please Insert POD CD-ROM:
The main reasons for this error are:
The obvious one - The POD CD must be in your CD-ROM drive whenever you want to play POD.
Adding too many cars or tracks - As you can see from number three below, each version of POD has a limit to how many cars and tracks should be added, if you have added too many, try removing some until you get back to the limit for your version. If POD still doesn't work, search for these two files, VOITURES.BIN and CIRCUTS.BIN on your POD CD and on your hard drive, and copy the ones off the CD to the hard drive, then re-add the cars and tracks, remembering to stop at the upper limit. If that doesn't help, you will have to re-install POD.
Using the wrong version of the CD-Patcher - Ubisoft never really made this clear, but there are two versions of the CD-Patcher. If you have the basic retail version of POD, which includes the OEM patched to Retail version, you should use the CD-Patcher version 1 and you have a limit of 32 tracks/cars. If you have used any of the new graphics patches, you should use the CD-Patcher version 2 and you have a limit of 47 cars/tracks. The solution to this problem is to first try removing all additional cars/tracks, then re-adding them with the correct version of the CD-Patcher. If that doesn't help, you will have to re-install POD.
Missing track or car data files - POD uses two types of data file, a low-quaity and a high-quality one. Patches such as the 3dfx and D3D-DX5 use the high-quality (Often referred to as '3dfx' format) data files, but there is a problem with these patches where sometimes they don't update the Ubisoft configuration file correctly, so other Ubisoft programs - especially the CD-Patcher - think POD is using the low-quality data files, when really POD is using the high-quality data files.
This causes the Insert CD message because when you, for example, patch a track or car on with the CD-Patcher, it will install the low-quality data files (the .bl3 or .bv3 data files) but POD will be looking for the high-quality data files (the .bl4 or .bv4 data files) and when POD cannot find a file on your hard drive, it looks on the POD CD, and when it cannot find the file there, it assumes you don't have the CD in, and asks for it.
The solution to this problem is simple. If you are using the 3dfx or D3D-DX5 patch, after adding a car or track to POD with the CD-Patcher, look in one of these folders - [C:\UBISOFT\POD\DATA\BINARY\VOITURES] or [C:\UBISOFT\POD\DATA\BINARY\CIRCUTS] - for cars and tracks respectively, and make sure the data files for the car or track have the extension .bv4 (Cars) or .bl4 (Tracks) and if they do not, just copy those files into the relevant folder - If you were using POD Gold/Back to Hell, the files will be in a similar folder on the CD, if you downloaded the car or track ZIP package, the file should be in the ZIP package.
Thanks to Skubidou for that tip.
Back to Top
Error: POD cannot run in 8/24/32 bits graphic mode:
You need to set your monitor to "HIGH COLOR (16-BIT)", by right-clicking the Windows Desktop, choosing Properties, and the Settings tab. Click the Color Palette combo box, choose HIGH COLOR (16-BIT) (Or 65,000 colors under Windows NT4), click Apply and Ok. If you are asked if it is ok to restart the computer, close all open programs (Saving any work !) and click Yes. POD should now run ok.
Back to Top
POD FATAL ERROR: GCD INIT FAILURE:
Try this: (Thanks to Shiv for this tip)
Find your current DXinput5.DLL file - It is in the [CPA\DLL] folder of your POD install, the default location is [C:\UBISOFT\POD\CPA\DLL]
Either ZIP this file or copy to to another location, for backup purposes.
Download the New DXinput5.DLL (ZIPPED) [About 15KB]
Extract the ZIP to the folder where your old DLL was.
Fire up POD and see if it made a difference.
If you experience any major problems, just copy the old DLL back.
Back to Top
Pod Fatal Error: grSstWinopen error
If you have a Voodoo2 SLI setup, try disabling SLI support (There should be an option in the Display Control Panel to do this). Thanks to Swift for the tip. If you don't have SLI but you do have a 3dfx-based 3D card (Any version) try removing and re-installing the drivers for your card.
Back to Top