View Full Version : Debugging CLI Codec problems

04-09-2002, 07:16 AM
written by: totalXSive

Here's a quick guide to fixing problems with CLI Codecs, especially the Generic CLI Encoder.

You will need to use the Windows Registry Editor. Be aware that this is a very powerful program, and if you make a mistake, you may render your Windows installation useless.

To access the Registry Editor, click on the Start button, and choose Run. You'll see a dialog like the one below (these screenshots are all taken from Windows XP Pro, so they may look different on your OS).


In the box, as above, type "regedit" (without the quotes), and click OK. In the directory structure on the left, open the HKEY_CURRENT_USER branch, then the Software branch, then the Illustrate branch, and finally the dBpowerAMP branch. You should see something like the image below:


Right-click in a bit of empty space, select New and then DWORD Value. You'll now be asked for a name, as below...


Call the value "CLIDebug" (without quotes). Once you have named it, double click on it. You'll see this dialog:


Set the value equal to "1" (without quotes). Then click OK, and then close the Windows Registry Editor.

Now, run the CLI Codec that you are having problems with. You'll see a dialog saying that the pathname has been copied to the clipboard. Open this forum page, and paste the error into a new message (use Ctrl+V to do this), and we'll have a look at it.

04-09-2002, 07:16 AM
Also follow the instructions in the Dialog - open a command window:

Start >> Run

cmd (in NT/2K/XP)


command (in Win95/98/ME)

Paste the clipboard onto the command (select the close box) >> Edit >> Paste

Run the command by pressing enter, and look for the error message.