Runtime Error 76: Path not found

[ljpp]

Not sure if this has been reported yet, but here's my 5 eurocents anyway.

Using RC4 the DVD-RB crashes if the output directory is missing.

STEPS TO REPRODUCE:
1) Define output directory
2) Run the prepare phase
3) Run the encoder phase
4) Rename or delete the actual folder on the HD where the output is pointed at
5) Start the Rebuild phase

Runtime Error 76: Path not found

DVD-RB crashes/closes.

[Rockas]

Let me see...
A user rips his DVD
Opens DVD Rebuilder
Sets the "Source Folder"
Sets the "Working Folder"
Sets the "Output Folder"
Starts the process
and then he decides to erase or rename the "Output Folder" without updating the path on Rebuilder before Rebuild!?!?!?!?

... I guess jdobbs can fix that ... but I also think that someone with a behaviour like that needs some fixing too :D - Sorry... I can't help myself :)

[ljpp]

Well, can't help it if I am a professional in software testing.
Noobs: http://www.google.com/search?sourceid=navclient-ff&ie=UTF-8&q=negative%20testing

[roux]

I can confirm this, i've posted this sometime earlier ( http://forum.doom9.org/showthread.php?t=87949 ) but they wouldn’t listen :D

[dozkid]

ljpp:
I can't help wonder what DVD-RB was supposed to do when you deleted the output folder?

[ljpp]

dozkid: Hm...how about asking the user for a proper output directory and not crashing the application with an runtime error? What do you generally expect your PC to do in error situations - crash?

[jptheripper]

i prefer a program to require a competent user. I say if a user doesnt something like that , the program shoul dunistall itself to protect its integrity!!

[ljpp]

jptheripper: Well, thank god professional developers don't think like that

[dozkid]

But if you change the output directory you should go into the program setup to change the output to the correct path. Thats the way the program is setup.

[Rockas]

@ljpp
Please... don't get me wrong...
As I said... I think jdobbs can fix that...
But you have to agree with me... it's a little odd that a user goes through all the config process just to delete one folder when he needs it :)

[ljpp]

Rockas: None taken mate ;)

Of course, it is an incorrect use case and fault of the user. I actually discovered this as I had something already encoded and rebuilt, but I realised that I didn't use the settings I was supposed to - so I deleted the whole destination folder and restarted the whole process.

[jptheripper]

i hope my comments were taken in jest

as ljpp suggested in last post, there are circumstances where this might happen

[jdobbs]

The problem with these errors is that they aren't consistent in networked/mounted environments. What I've found is that caching of information throws you off -- so I might check, and the directory exists, hmmm.. must be a good directory... but then the second attempt to read results in a failure....

Here's an example: I mount an ISO using Daemon tools from a networked drive. I access it a few times, then just as a test I reboot the networked computer. Go back in and look -- it seems to be still connected. But if I start DVD-RB it will crash as some random point... I can trap any error (but I don't usually do that while in beta) -- but it will make absolutely no sense and sometimes won't even seem to be related to the problems... the only real choice is to abort...