Runtime Error 52 - Bad file name or number

[Rassilon]

Hello,
I am getting a "Runtime Error "52": bad filename or number with any DVD that I want to rebuild and on both one click mode and 3 click. I double checked that the files and paths under Options>Setup are correct and I even reselected them. I've even deleted the directory and reinstalled DVDRB in case something there was corrupt to no avail.

If there is any other information that you require for further diagnosis, just ask and I'll try and get it to you.

Thanks.

[Rockas]

I think you might want to check the paths to the source, Work folder and Output folder, too. :)

[pg55555]

Aren't you using a non occidental Windows, are you?

RB has problem with paths containing extraing caracters

Have you been successful with RB in other DVDs?

[Rockas]

Originally posted by pg55555
Aren't you using a non occidental Windows, are you?

RB has problem with paths containing extraing caracters

Have you been successful with RB in other DVDs?

Well... I didn't thought of that... he says that he is from Sidney Australia :)

[Rassilon]

I'm using WinXP SP2,I did notice however, that a DVD slideshow that I made will let DVDRB execute properly without an error, where as "Battle Star Gallactica" and "Who framed Roger Rabbit" result in the runtime error. I have also tried it again on "Last Samurai" wich I have rebult already, but it also returns an error now.. :-(

[jdobbs]

What version of DVD-RB are you using?

[Cwluc]

This error is cropping up on my rebuilds with the latest version 0.79(Pro). I am trying to revert back to an older version and doing the whole re-encode all over again. If you need any specifics I can provide if necessary. But there is no preprocessing at all on this disc and I don't know why I am getting this error during the third stage.

[Rassilon]

Originally posted by jdobbs
What version of DVD-RB are you using?

V0.78

[jdobbs]

Originally posted by Rassilon
Hello,
I am getting a "Runtime Error "52": bad filename or number with any DVD that I want to rebuild and on both one click mode and 3 click. I double checked that the files and paths under Options>Setup are correct and I even reselected them. I've even deleted the directory and reinstalled DVDRB in case something there was corrupt to no avail.

If there is any other information that you require for further diagnosis, just ask and I'll try and get it to you.

Thanks. At what point does this happen? Is it immediately upon start, halfway through? Do you have your rebuilder.ini, rebuilder.inf, or status files I can look at?

You gotta throw me some crumbs, here...

[Rassilon]

Originally posted by jdobbs
At what point does this happen? Is it immediately upon start,

As soon as I hit "Prepare"

Originally posted by jdobbs
Do you have your rebuilder.ini,

[Paths]
Source=H:\VIDEO_TS\
Working=F:\DVD REBUILDER\
Output=F:\DVD REBUILDER\

CCENEW=D:\Program Files\CCE\EclCCE.exe
REJIG=D:\Program Files\ReJig\ReJig.exe
QuEnc=D:\Program Files\QuEnc\QuEnc.exe
MPEG2DEC=D:\Program Files\AviSynth 2.5\plugins\MPEG2Dec3dg.dll
DECOMB=D:\Program Files\AviSynth 2.5\Decomb521.dll
[Options]
HalfD1=00
Convert_16_9=00
DisableInterlace=00
CCE=3
[Audio]
Selected=

Originally posted by jdobbs

rebuilder.inf, or status files I can look at?

These two I can't find. :(

Originally posted by jdobbs
You gotta throw me some crumbs, here...

I'll give you the whole loaf if it helps... :)

[jdobbs]

What drives are "H:" and "F:" -- DVD drives, hard drive partitions, Daemon Tools mounted drives?

[Cwluc]

Reverting to the older CCE (2.66.01.07) and latest build of DVD-RB did not have the same problem as my other setup.

I will note the one that had the error was on a new computer (tester if you will) that had a different version (2.67.00.27) installed. Also the same folder was used for both rebuilds just one was over the network, which shouldn't been a problem, but I will say that running a clean rebuild with a tried and true box did not create the error. I will try to run again and save all files so you will know exactly where the problem might lie.

[Rassilon]

Originally posted by jdobbs
What drives are "H:" and "F:" -- DVD drives, hard drive partitions, Daemon Tools mounted drives?

H is a DVD Rom Drive - In this case the source DVD location
F is a partition on a HDD

50gb Split into C: (20gb) and D: (30gb)
200gb Split into E: (100gb), F&G are 50gb Each.
C: Master/Boot
D: "My Documents" and "Program Files"
E: Storage
F: Temp/Work Drive
G: Capture Drive (For video, autio, etc)
H: DVD Rom Burner
I: DVD Rom

[Rockas]

Have you tried to Rip the DVD to your hard drive first?

You should do that.

[Cwluc]

Originally posted by jdobbs
At what point does this happen? Is it immediately upon start, halfway through? Do you have your rebuilder.ini, rebuilder.inf, or status files I can look at?

You gotta throw me some crumbs, here...

I hope I gave you the entire cookie in your mailbox, if there is anything else please don't hesitate to ask.

Notes, I know that is occurs at the same point (about 75% of the way through phase 3) with CCE 2.67. Then while I was looking at the size of the completed 2.66 I noticed it was fairly undersized I'm not sure what you would consider enough to be noticeable but the size went from 7.90 GB to 3.83 GB (most times rebuilds being around the magic 4.30 GB) It looks like everything is still there on the disc. Thank you for your time.

[Cwluc]

Upon the suggestion of jdobbs I have upgraded my MPEG2 decoder. OK I ran through the instructions located here (http://www.doom9.org/mpg/dvdrb.htm). Step by step, more than once, but here is the most recent log below. If anyone knows why I am no longer getting the previous error and now a horribly undersized (and well under time – a 30 min job would be sweet thought!!) re-encode that would be awesome. Note I even tried another disc, same result. Thanks for the listen.




- Versions:
-- CCE Basic Version: UNKNOWN
-- CCE SP, ECLCCE reported version: ECLCCE
-- QuEnc Version: UNKNOWN
-- DECODER Version: UNKNOWN
-- AVISYNTH Version: 2.5.5.0

[13:05:39] One Click encoding activated...
-----------------
[13:05:41] Phase I, PREPARATION started.
- CCE SP ECLCCE encoder selected.
- VTS_01: 1,086,463 sectors.
-- Scanning and writing .D2V file
-- Processed 107,259 frames.
-- Building .AVS and .ECL files
- VTS_03: 249,985 sectors.
-- Scanning and writing .D2V file
-- Processed 18,550 frames.
-- Building .AVS and .ECL files
- VTS_06: 639,727 sectors.
-- Scanning and writing .D2V file
-- Processed 51,315 frames.
-- Building .AVS and .ECL files
- VTS_08: 1,792,581 sectors.
-- Scanning and writing .D2V file
-- Processed 134,314 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 44.7%
- Overall Bitrate : 1,948Kbs
- Space for Video : 3,088,550KB
- HIGH/LOW/AVERAGE Cell Bitrates: 2,622/1,479/1,948 Kbs
[13:16:03] Phase I, PREPARATION completed in 11 minutes.
[13:16:04] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
- Creating M2V for VTS_01 segment 30
- Creating M2V for VTS_01 segment 31
- Creating M2V for VTS_01 segment 32
- Creating M2V for VTS_01 segment 33
- Creating M2V for VTS_01 segment 34
- Creating M2V for VTS_01 segment 35
- Creating M2V for VTS_01 segment 36
- Creating M2V for VTS_01 segment 37
- Creating M2V for VTS_01 segment 38
- Creating M2V for VTS_01 segment 39
- Creating M2V for VTS_01 segment 40
- Creating M2V for VTS_01 segment 41
- Creating M2V for VTS_01 segment 42
- Creating M2V for VTS_01 segment 43
- Creating M2V for VTS_01 segment 44
- Creating M2V for VTS_01 segment 45
- Creating M2V for VTS_03 segment 0
- Creating M2V for VTS_03 segment 1
- Creating M2V for VTS_06 segment 0
- Creating M2V for VTS_06 segment 1
- Creating M2V for VTS_06 segment 2
- Creating M2V for VTS_06 segment 3
- Creating M2V for VTS_08 segment 0
- Creating M2V for VTS_08 segment 1
- Creating M2V for VTS_08 segment 2
- Creating M2V for VTS_08 segment 3
- Creating M2V for VTS_08 segment 4
- Creating M2V for VTS_08 segment 5
- Creating M2V for VTS_08 segment 6
- Creating M2V for VTS_08 segment 7
- Creating M2V for VTS_08 segment 8
- Creating M2V for VTS_08 segment 9
- Creating M2V for VTS_08 segment 10
- Creating M2V for VTS_08 segment 11
- Creating M2V for VTS_08 segment 12
- Creating M2V for VTS_08 segment 13
- Creating M2V for VTS_08 segment 14
- Creating M2V for VTS_08 segment 15
- Creating M2V for VTS_08 segment 16
- Creating M2V for VTS_08 segment 17
[13:20:43] Phase II ENCODING completed in 4 minutes.
[13:20:43] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 1 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 2 VOBID: 3 CELLID: 1
- Updating NAVPACKS for VOBID_03
- Rebuilding segment 3 VOBID: 4 CELLID: 1
- Updating NAVPACKS for VOBID_04
- Rebuilding segment 4 VOBID: 5 CELLID: 1
- Updating NAVPACKS for VOBID_05
- Rebuilding segment 5 VOBID: 6 CELLID: 1
- Updating NAVPACKS for VOBID_06
- Rebuilding segment 6 VOBID: 7 CELLID: 1
- Updating NAVPACKS for VOBID_07
- Rebuilding segment 7 VOBID: 8 CELLID: 1
- Updating NAVPACKS for VOBID_08
- Rebuilding segment 8 VOBID: 9 CELLID: 1
- Updating NAVPACKS for VOBID_09
- Rebuilding segment 9 VOBID: 10 CELLID: 1
- Updating NAVPACKS for VOBID_10
- Rebuilding segment 10 VOBID: 11 CELLID: 1
- Updating NAVPACKS for VOBID_11
- Rebuilding segment 11 VOBID: 12 CELLID: 1
- Updating NAVPACKS for VOBID_12
- Rebuilding segment 12 VOBID: 13 CELLID: 1
- Updating NAVPACKS for VOBID_13
- Rebuilding segment 13 VOBID: 14 CELLID: 1
- Updating NAVPACKS for VOBID_14
- Rebuilding segment 14 VOBID: 15 CELLID: 1
- Updating NAVPACKS for VOBID_15
- Rebuilding segment 15 VOBID: 16 CELLID: 1
- Updating NAVPACKS for VOBID_16
- Rebuilding segment 16 VOBID: 17 CELLID: 1
- Updating NAVPACKS for VOBID_17
- Rebuilding segment 17 VOBID: 18 CELLID: 1
- Updating NAVPACKS for VOBID_18
- Rebuilding segment 18 VOBID: 19 CELLID: 1
- Updating NAVPACKS for VOBID_19
- Rebuilding segment 19 VOBID: 20 CELLID: 1
- Updating NAVPACKS for VOBID_20
- Rebuilding segment 20 VOBID: 21 CELLID: 1
- Updating NAVPACKS for VOBID_21
- Rebuilding segment 21 VOBID: 22 CELLID: 1
- Updating NAVPACKS for VOBID_22
- Rebuilding segment 22 VOBID: 23 CELLID: 1
- Updating NAVPACKS for VOBID_23
- Rebuilding segment 23 VOBID: 24 CELLID: 1
- Updating NAVPACKS for VOBID_24
- Rebuilding segment 24 VOBID: 25 CELLID: 1
- Updating NAVPACKS for VOBID_25
- Rebuilding segment 25 VOBID: 26 CELLID: 1
- Updating NAVPACKS for VOBID_26
- Rebuilding segment 26 VOBID: 27 CELLID: 1
- Updating NAVPACKS for VOBID_27
- Rebuilding segment 27 VOBID: 28 CELLID: 1
- Updating NAVPACKS for VOBID_28
- Rebuilding segment 28 VOBID: 29 CELLID: 1
- Updating NAVPACKS for VOBID_29
- Rebuilding segment 29 VOBID: 30 CELLID: 1
- Updating NAVPACKS for VOBID_30
- Rebuilding segment 30 VOBID: 31 CELLID: 1
- Updating NAVPACKS for VOBID_31
- Rebuilding segment 31 VOBID: 32 CELLID: 1
- Updating NAVPACKS for VOBID_32
- Rebuilding segment 32 VOBID: 33 CELLID: 1
- Updating NAVPACKS for VOBID_33
- Rebuilding segment 33 VOBID: 34 CELLID: 1
- Updating NAVPACKS for VOBID_34
- Rebuilding segment 34 VOBID: 35 CELLID: 1
- Updating NAVPACKS for VOBID_35
- Rebuilding segment 35 VOBID: 36 CELLID: 1
- Updating NAVPACKS for VOBID_36
- Rebuilding segment 36 VOBID: 37 CELLID: 1
- Updating NAVPACKS for VOBID_37
- Rebuilding segment 37 VOBID: 38 CELLID: 1
- Updating NAVPACKS for VOBID_38
- Rebuilding segment 38 VOBID: 39 CELLID: 1
- Updating NAVPACKS for VOBID_39
- Rebuilding segment 39 VOBID: 40 CELLID: 1
- Updating NAVPACKS for VOBID_40
- Rebuilding segment 40 VOBID: 41 CELLID: 1
- Updating NAVPACKS for VOBID_41
- Rebuilding segment 41 VOBID: 42 CELLID: 1
- Updating NAVPACKS for VOBID_42
- Rebuilding segment 42 VOBID: 43 CELLID: 1
- Updating NAVPACKS for VOBID_43
- Rebuilding segment 43 VOBID: 44 CELLID: 1
- Updating NAVPACKS for VOBID_44
- Rebuilding segment 44 VOBID: 45 CELLID: 1
- Updating NAVPACKS for VOBID_45
- Rebuilding segment 45 VOBID: 46 CELLID: 1
- Updating NAVPACKS for VOBID_46
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Processing VTS_03
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 1 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Processing VTS_06
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 1 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 2 VOBID: 3 CELLID: 1
- Updating NAVPACKS for VOBID_03
- Rebuilding segment 3 VOBID: 4 CELLID: 1
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_06_0.IFO
- Processing VTS_08
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 1 VOBID: 2 CELLID: 1
- Rebuilding segment 2 VOBID: 2 CELLID: 2
- Rebuilding segment 3 VOBID: 2 CELLID: 3
- Rebuilding segment 4 VOBID: 2 CELLID: 4
- Rebuilding segment 5 VOBID: 2 CELLID: 5
- Rebuilding segment 6 VOBID: 2 CELLID: 6
- Rebuilding segment 7 VOBID: 2 CELLID: 7
- Rebuilding segment 8 VOBID: 2 CELLID: 8
- Rebuilding segment 9 VOBID: 2 CELLID: 9
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 10 VOBID: 3 CELLID: 1
- Rebuilding segment 11 VOBID: 3 CELLID: 2
- Rebuilding segment 12 VOBID: 3 CELLID: 3
- Rebuilding segment 13 VOBID: 3 CELLID: 4
- Rebuilding segment 14 VOBID: 3 CELLID: 5
- Rebuilding segment 15 VOBID: 3 CELLID: 6
- Updating NAVPACKS for VOBID_03
- Rebuilding segment 16 VOBID: 4 CELLID: 1
- Updating NAVPACKS for VOBID_04
- Rebuilding segment 17 VOBID: 5 CELLID: 1
- Updating NAVPACKS for VOBID_05
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_08_0.IFO
Correcting VTS Sectors...
[13:35:42] Phase III, REBUILD completed in 15 minutes.

Done.
[13:35:43] PREPARE/ENCODE/REBUILD completed in 30 min.

[jdobbs]

Look at the output... it probably has reddish jagged lines at the bottom of a black screen... you're getting errors from AVISYNTH.

That could happen if:

1. DGDECODE isn't installed or the path is incorrect.
2. The source data is no longer available (but it was when the PREPARE was done).
3. Something or someone has incorrectly modified the AVS file.
4. AVISYNTH hasn't been installed properly or has been corrupted.
5. There is a conflicting version of DGDECODE or AVISYNTH referenced on the computer.

[Rockas]

here's my advice:

uninstall Avisynth
re-start your computer
Run a registry clean application (search for "Marcos Velasco Registry Cleanner" - it's free and very good... the best :))
re-install avisynth (v.2.5.5 - it works I garantee)
Use my installer (it will install the version 0.79free - if you got 0.80PRO all you got to do is replace the Rebuilder.exe file 0.79 with 0.80)

Finnaly... give it another try :)

[Cwluc]

Originally posted by jdobbs
Look at the output... it probably has reddish jagged lines at the bottom of a black screen... you're getting errors from AVISYNTH.

That could happen if:

1. DGDECODE isn't installed or the path is incorrect.
2. The source data is no longer available (but it was when the PREPARE was done).
3. Something or someone has incorrectly modified the AVS file.
4. AVISYNTH hasn't been installed properly or has been corrupted.
5. There is a conflicting version of DGDECODE or AVISYNTH referenced on the computer.

Please despite however you might read my text, I am here for help, not step on anyone's toes. I would like to get DVD-RB working again I miss using my burner... Oh I have all the windows set to minimize so I don't see anything except DVD-RB ticking along.

1. Filelist of the plugins folder.

C:\Program Files\AviSynth 2.5\plugins>dir
Volume in drive C is WINDOWS
Volume Serial Number is 4156-0E4B
Directory of C:\Program Files\AviSynth 2.5\plugins
03/29/2005 12:59 PM <DIR> .
03/29/2005 12:59 PM <DIR> ..
08/17/2004 02:55 AM 81,920 DirectShowSource.dll
08/17/2004 03:10 AM 167,936 TCPDeliver.dll
08/17/2004 03:06 AM 10,272 colors_rgb.avsi
2/22/2005 07:20 AM 266,318 DGDecode.dll
4 File(s) 526,446 bytes
2 Dir(s) 1,417,183,232 bytes free
C:\Program Files\AviSynth 2.5\plugins>

2. Both computers are online, switch it operating properly, there is no loss in coneectivty, i have have complete encodes of the network before without issue.

3. - 4. How could i set them up improperly? How do I see if the install is corrupted?

5. Full Program name (Filename)

AviSynth 2.5.5 (AviSynth_255) / DGMPGDec Version 1.2.1 Executables (dgmpgdec121)
Originally posted by Rockas
here's my advice:

uninstall Avisynth
re-start your computer
Run a registry clean application (search for "Marcos Velasco Registry Cleanner" - it's free and very good... the best :))
re-install avisynth (v.2.5.5 - it works I garantee)
Use my installer (it will install the version 0.79free - if you got 0.80PRO all you got to do is replace the Rebuilder.exe file 0.79 with 0.80)

Finnaly... give it another try :)

Humoring your suggestion I looked for a link for your software, and found a translation of something, Google asked me I if I mean Cleaner instead of Cleanner so the first link was a blog about malware, and someone I assume the creator step over some line (not sure what the blog was talking about), I did press on and found a version I am going to assume is in Spanish and no I am not able to read said language. So while I know that my computer has successfully completed a few (many) encodes properly I tried this new setup and still no luck.

I love this program since day one, I am a HUGE CCE fan, I have never had more than a small issue with having to revert back to 2.50 for some HBO discs, it's so not DVD-RB's fault I know it's the stupid HBO TV screen intro. I had been "cheating" my setup of DVD-RB and just installed the latest DVD2SVCD which had an older MPEG2 decoder (but was working, so I assume), even changing to the different more up to date decoder has proven unsuccessful. Now I say all this asking one question.

Why would DVD-RB stop working one day, when all I use my one computer is for ripping DVD's and running SETI (not at the same time)?

[jdobbs]

It didn't just stop working... something has changed. If I recall correctly I think that installing DVD2SVCD may change the registry entry as to where the AVISYNTH plug-in directory is.... it may point it to itself... if I'm not confusing it with another package. That may be the source of the problem.

Have you pointed the path in the SETUP screen of DVD-RB to the path of DGDECODE.DLL??? Are you using any other filters?

Also -- you should be using DGDECODE version 110 with DVD-RB... download it from this link (http://neuron2.net/dgmpgdec/Archives/dgmpgdec110.zip). I'm not sure whether the version you are using even works with DVD-RB.

[ADDED] Yes I confirmed... installing DVD2SVCD changes the pointer to the AVISYNTH plug-ins folder... that is very possibly at least part of your problem. Read it here (http://forum.doom9.org/showthread.php?s=&postid=575243&highlight=dvd2svcd+registry#post575243). If you had followed Rockas' directions by using his installer rather than "humoring" him -- it probably would have fixed your problem.

It was also very rude.

So of the 5 things I mentioned that you disregarded my best guess is that #1 is true, #4 is true, and #5 is true... hmmm...

[Cwluc]

I'm tired, and to tell you the truth this has been my escape from lack of playing WoW. It has nothing to do with your software. My apologies if my wording appeared rude to anyone.

An apology, to Rockas, I tried to look into his reg cleaner suggestion, that was a no go.

Nothing has changed, I have use the DVD2SVCD install with DVD-RB for months without one single problem (except HBO, which isn't an DVD-RB issue, as I said I found out I just had to revert to 2.50, which are both safely and well installed on one computer) I know my computers, I have 8 of them to my name if there is anything going on with them and being changed it's a windows or norton update that is it. No lie I have one computer that only uses DVD-RB and SETI. Each and everyday it sits under my dorm room bed buzzing along (with 4 other friends at the moment) like nobodies business I have it for those two reasons alone. I do not download anything onto it, I do not play any games, I install no known OR unknown software from any source that I do not know of, there isn't even MS Office to spell check my slightly heated response to you, I have other computer to get messed up from monkeying around with, NOT this one. Now as I calm down because I think you really took my post in the worst possible light. Everything was working until I got The Legend of Ron Burgundy disc. Now I cannot complete any rebuilds with this updated encoder?

Please understand I am trying my best here I did remove, and clear out any and all files from DVD2SVCD, AVISYNTH, DVD-RB, and any others that I cannot remember at this time. I did reboot and then reinstalled only AVISYTH 2.5.5 (NO DVD2SVCD at anytime you said it was old, I say ok, I stopped making SVCD's months ago) with the recommended decoder and still no go. Also I did not see any information telling me the latest version wasn't "tested" I will go back and try with 110. I didn't see any of this information because I was not looking for that, I read your response in my mailbox it said nothing about which version to get, I'm sorry if I didn't know my version of MPEG2DEC.dll was out of date, and that I should go and use an older version than listed on the sites page. I thought the 1.3.0 beta 5 Executables would be a little questionable. I did not see the logic at the time of using anything but the most recent build. Like I said I'm sorry.

Next, jdobbs, I disregarded nothing, I did try and look into each and everyone one of your suggestions, I listed my findings so that you might be able to help me with my issue, if it were to come back what would you think that problem might be caused by? I now am running a test with nothing but the DVD-RB installer, and CCE. I will report my findings in the morning. Nothing has been changed, all items are pointed to the correct locations in the setup page. No I am using no filters, unless any are setup by default. Reading my previous post I see that you didn't acknowledge my response of your 5 suggestions. I did show you that it appeared correctly to my eyes, I installed everything as fresh as can possibly be, like the two of you had suggested and tried to keep an open mind because for whatever reason this problem would not go away. I am not one of the many people who come to this site countless times before STF. I did respond to someone else query about an Error 52. You tell me what I did wrong I and I am trying to make the adjustments. You came back and get in my face?

Lastly please don't get upset by my words, if you think I am being rude, sorry I'm having an issue with Blizzard, if anyone lives in the greater Irving, CA area take a trip for my sake and take care of some business? I would greatly appreciate it. Yes I know WoW means nothing to most if not all of you, but hey I have been having some free time sue me if it's now looking at my computer screen and a bunch of programs (none in particular) that aren't working as expected.

[jdobbs]

If you are as experienced with computers as you say -- then you know there is no mystery to them. Only logic in processing. Nothing changes on its own...

Please put your ego aside and download the installer package from this link. (http://dvd-rb.dvd2go.org/modules.php?name=Downloads&d_op=getit&lid=77) If you have the .80 package -- just install the new exe over the old one when it is done. Your problems should go away.

[Rockas]

@Cwluc
Sorry about the "cleanner" :D

Here's the download link (english version) - believe me, this is the best (free) registry cleanner that I know off. Very simple to use, too:
http://www.velasco.com.br/mvregcln-installer-eng.zip

keep it UP

edit:
Two points:
1st. The language you might have found on your quest for the "Cleanner" could be Portuguese, don't make any confusions between Portuguese and Spanish (both countries are Independent and very proud of it :))

2nd. As most of the freeware applications, when I made the Installer was for my own use (I got Avisynth corrupted often :D) 'cause I know that there are many applications that change the Registry Values of Avisynth's Paths... even if I don't use many of them, I always test any new software, that's why I first made it... then It just got better and it has been solving many users problems since then... give it a try.

[Rassilon]

Originally posted by jdobbs
It didn't just stop working... something has changed. If I recall correctly I think that installing DVD2SVCD may change the registry entry as to where the AVISYNTH plug-in directory is.... it may point it to itself... if I'm not confusing it with another package. That may be the source of the problem.

I have re-installed AVISynth 2.5 but I still get the same error.

Originally posted by jdobbs
Have you pointed the path in the SETUP screen of DVD-RB to the path of DGDECODE.DLL??? Are you using any other filters?

Just the ones that I mentioned previously.

Originally posted by jdobbs


Also -- you should be using DGDECODE version 110 with DVD-RB... download it from this link (http://neuron2.net/dgmpgdec/Archives/dgmpgdec110.zip). I'm not sure whether the version you are using even works with DVD-RB.

I installed DVDRB using the instructions that I used previously and there was no mention on dgmpgdec, but I did install it and point to the dll file that you mentioned and the error still occurs. :confused:

[Rockas]

@Rassilon
Have you tried to install using my installer?
(if you mentionad this before... I'm sorry :))

[jdobbs]

Originally posted by jdobbs
Please put your ego aside and download the installer package from this link. (http://dvd-rb.dvd2go.org/modules.php?name=Downloads&d_op=getit&lid=77) If you have the .80 package -- just install the new exe over the old one when it is done. Your problems should go away. I'm done giving advice... you apparently refuse to take it.

[Cwluc]

Hey I listened, it completed without error, suffice to say the latest DGDECODE is not compatible with DVD-RB, a note to myself I will not be forgetting soon. Thank you all for your help. Please don't get all bent out of shape.

Last question, is 3.96 GB a good size or is it too small?

@Rassilon I don't know your story but here is mine. I had the same error as you, I didn't know was going on everything was dandy until this last disc. I make a few post, got the correct information to help me get a complete rebuild. For our sake, remove any and all encoders / decoders / awesome versions of any programs you swear you need to get your job done. Next REBOOT your PC. When restarted check to make sure not only your programs are no longer listed in add/remove, their folders are removed for each of their respective names under their program installation (yes make sure the plug-ins you had once install and whatnot are no longer listed, or available to cause any confusion). Then try to install only AVISYNTH 2.5.5, afterward Rockas' installer. I'm not sure which of the supported encoders you are currently using, follow more specific instructions as needed. Finally after all that is said and done, (I would say if you weren't ripping the disc to your HDD now would be a good time to a full file mode rip with DVD Decrypter which will save time and hair loss) load up DVD-RB check that your paths are correct in the setup, working and output folders, the correct encoder is selected, and that you have adequate space available. Press the Prepare/Encode/Rebuild or Backup DVD and walk away. Hopefully everything goes smoothly. Write back so we know if you got it working.

[jdobbs]

Last question, is 3.96 GB a good size or is it too small? Too small. Encodes (using the default TargetSize) should always hover around 4.32GB. Is that using OPV? Sometimes that's the best it can do with one pass...

[Cwluc]

OPV?? Not sure what that stands for, the DVD-RB installer was defualt settings, just changed the encoder, and changed the number of passes to 6 (so 5). I thought it was undersized, anything I can do?

[jdobbs]

Sorry, OPV is "One Pass Variable bitrate" encoding. It is a feature that exists only in the SP versions of CCE. I don't think the number of passes will have any significant effect on output size.

[Cwluc]

No that option is not enabled, it's ok, it is close enough to 4gb. Time to move on, if my next rebuild comes out smaller than usual I will get back to you.

[nahmeen]

DVDRB stores huge amounts of files (app. 3.8gis worth) in
C:\Documents and Settings\username\My Documents\DVD-RB\WorkPath
in previous builds of RB (can`t remember exact numbers)
I would just highlight the folder "WorkPath" and delete it ,gettin rid of the files.The next time I used RB it would just recreate the folder.
In the latest builds ,including 80 RB doesn`t recreate the folder ,hence the runtime error 52.
If you phisically go into C:\Documents and Settings\username\My Documents\DVD-RB\ and make the folder "WorkPath" the error goes away.
sorry it took 5 days to post ,hope it helps.

[jdobbs]

???? DVD-RB uses no such path... maybe Rockas' installer creates it. But if it isn't listed as one of your paths, or you've installed DVD-RB in it --- I can guarantee you DVD Rebuilder doesn't reference it.

[nahmeen]

um, i don`t know what to say.
i did use rockas installer ,and i`m using the latest build of RB
\username\ would be whatever your login name is
on the main screen of RB I have

sourse path H:\TEMP\

Working Path C:\Documents and Settings\username\My Documents\DVD-RB\WorkPath

Output Path:\I:\TEMP\

I have no Problems with RB by the way ,it `s near perfection and thank you!
but this is how i got rid of runtime error 52
maybe i could change work path to anothe drive

[Rockas]

The installer creates the paths you choose. It's asked for you to do so.
If you delete the folders, Rebuilder won't find it, it can't find something that doesn't exist ;)

[jdobbs]

Well... yes and no... what it should do is give a message that says "The output directory doesn't exist... do you want me to create it?" -- rather than pump out a cryptic "52"...

I'll take a look at that and will definitely fix it. I must have been out of coffee when I wrote that section.

Thanks! Another one bites the dust.

[Rockas]

:cool:

[Rassilon]

Originally posted by Rockas
@Rassilon
Have you tried to install using my installer?
(if you mentionad this before... I'm sorry :))
Hi Rockas,
I used your installer and things still remained unchanged, and then all of a sudden they came good and things are rocking along well now, confusing! :confused:

Thanks to all the ppl for all your help :D

[evestorm]

I am posting in this thread mostly because I have done the things suggested to fix the Runtime error and am at a loss. I have downloaded the reg cleaner and run it (cool program by the way Rockas) and re-installed AVISYNTH and RB using the installer (Which is cool as hell also) and I still get the run time error 52 bad file name or number about 2 minutes into the prepare phase. Rebuilder is the latest version of the installer as well as the latest AVISYNTH. I pasted the .ini is below.

DVD is Apocolypse Now R1.
Windows XP SP1
Only one new app installed since the last working backup and that is Anydvd.


[Audio]
Selected=
[Options]
Mode=1
OneClick=1
ReduceOpt=3
NoWarn=1
AdditionalOutput=1
LogFile=1
QuEncHQ=1
EncoderMinimized=1
RemoveDTS=1
Skin=Simple Blue
HC_Quality=1
HC_Matrix=1
SkinVersion=3
CCE=1
HalfD1=000
Convert_16_9=000
DisableInterlace=000
Backcolor=14215660
[Paths]
QuEnc=C:\Program Files\DVD-RB\QuEnc\QuEnc.exe
ReJig=C:\Program Files\DVD-RB\ReJig\ReJig.exe
DECOMB=C:\Program Files\AviSynth 2.5\plugins\Decomb521.dll
ProCoder=C:\Program Files\DVD-RB\EclPro\EclPro.exe
MPEG2DEC=C:\Program Files\DVD-RB\DGDecode.dll
Working=C:\Processed\
Output=C:\Processed\
HC=C:\Program Files\DVD-RB\HC Encoder\HCbatch.EXE
CCE250=C:\Program Files\Custom Technology\Cinema Craft Encoder SP\EclCCE.exe
Source=J:\VIDEO_TS\
CCENEW=C:\Program Files\Custom Technology\Cinema Craft Encoder SP\EclCCE.exe

[Subpictures]
Selected=
[Setup]
Languages=1111111111111111111111110111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111101
sLanguages=1111111111111111111111110111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
[CCEOptions]
VBR_bias=25
Quality_prec=16
eclPasses=4

[jdobbs]

Version 93 (freeware) or 1.00? What kind of drive is your J drive?

See if it goes away if you delete this line:

Source=J:\VIDEO_TS\

[evestorm]

I have a suggestion for future releases. I would appreciate it if you would consider adding it and making a special version just for me.

Under the setup could you please add an option to point to the "you_are_a_dumbass.dll"
I NEED this option.

The next time I mount an ISO image with daemon tools and at some point delete my .mds file so that my virtual drive doesnt know what the hell I am talking about, then this option would kick in and save me the trouble.

Or perhaps I could just NOT be a TOOL and check to make sure my image file is complete.

...Thanks for the great app jdobbs...my fault again as usual with this problem.

I think I will donate now in effort to cleanse my self of stupidity.

[jdobbs]

I could add that right after the "WhoWroteThisCrap.dll" that kicks in whenever a non-specific error message pops up....

[Fishman0919]

I have a suggestion for future releases. I would appreciate it if you would consider adding it and making a special version just for me.

Under the setup could you please add an option to point to the "you_are_a_dumbass.dll"
I NEED this option.

The next time I mount an ISO image with daemon tools and at some point delete my .mds file so that my virtual drive doesnt know what the hell I am talking about, then this option would kick in and save me the trouble.

Or perhaps I could just NOT be a TOOL and check to make sure my image file is complete.

...Thanks for the great app jdobbs...my fault again as usual with this problem.

I think I will donate now in effort to cleanse my self of stupidity.


I could add that right after the "WhoWroteThisCrap.dll" that kicks in whenever a non-specific error message pops up....


LMAO..... :goodpost: ...I've had a long morning and this made my day...THX

[Rassilon]

I have also found that I get this error if I point to a DVD that has encryption.

[Rockas]

LMAO..... :goodpost: ...I've had a long morning and this made my day...THX
lol lol lol DIDO