Log in

View Full Version : DoCCE4U headaches


engineer04ue
12th August 2003, 16:19
I've been closely following the DoItFast4U, Reauthorist, DoCCE4U guides in backing up my DVD collection. Everything seems to flow smoothly until I click on the start encoding button on DoCCE4U (using CCE 2.50). The CCE program window loads up and just hangs without showing any information of the current job. The program will not close normally when this happens unless I close by task manager. This is with DoCCE4U 1.0.1.5. I'd appreciate any help.

69Mws
12th August 2003, 18:11
Try this:

Check your install directory of DoCCE4U. There should be an eclcce.exe and an eclcce.ini.

Open the ini with a texteditor and see if it points right to your "cce.exe".

If there is no eclcce.ini, startup eclcce.exe and then a dialogue should ask you for the location of your cce.exe

If that doesn't help, maybe your version of CCE is not supported, so it would be helpful to know which version of CCE you're using

Greetz
69Mws

daddy_fizz
12th August 2003, 20:08
Originally posted by engineer04ue
I've been closely following the DoItFast4U, Reauthorist, DoCCE4U guides in backing up my DVD collection. Everything seems to flow smoothly until I click on the start encoding button on DoCCE4U (using CCE 2.50). The CCE program window loads up and just hangs without showing any information of the current job. The program will not close normally when this happens unless I close by task manager. This is with DoCCE4U 1.0.1.5. I'd appreciate any help.

69Mws
12th August 2003, 20:25
mkay, CCE 2.50.....I should read more carefully... :D

NetZwerg
12th August 2003, 22:36
Make sure there's no trailing backslash in the 'working directory' in Reauthorist before you click 'encode'.

wenn you set eclcce in debug-mode you see that the ecl-file will be passed over with two backslashes and that will generate an error that is unfortunately not displayed when you're not in debug mode.

so the working directory in Reauthorist:

WRONG: D:\dvdrip\title\

RIGHT: D:\dvdrip\title

That worked for me with exactly the same problem.

Actually this seems to be a bug in Reauthorist, that produces the double backslashes. I'm not sure, if it may be also a bug in eclCCE and/or CCE, as double-slashes are at least legitimate in GNU/Linux.

engineer04ue
12th August 2003, 23:09
Thank you for all the responses... I will test that to see if the backslash is apparent when I get home later.