RR does not check if drive is present

[GoogleCodeExporter]

I am ripping all my CD's to an usb drive. In preferences, I have set up to
create a new directory for each CD on that drive. Today I started to rip a
CD, RR ripped it without complaints.
When I removed the CD after ripping I realized that I forgot to attach the
usb drive. RR did not realize that, nor did it generate an error message.

Original issue reported on code.google.com by heinz.weigand@gmail.com on 21 Jul 2007 at 4:00

[GoogleCodeExporter]

If I understand it correctly, the issue at hand is:
* Rubyripper doesn't check if the output directory exists.

What Rubyripper does do is to check if the output directory exists. If not, it 
creates it. Well at least it should. Are you sure the data isn't written to the 
(unmounted) mount point?

Original comment by rubyripp...@gmail.com on 21 Jul 2007 at 4:53

[GoogleCodeExporter]

Yes, I am sure. The directory does not exist when I start to rip. My filename 
pattern
in Preferences is: <basedirectory on usb-drive as per settings in RR>/%a/%b/%a 
- %b -
%n - %t. %a sometimes exists, %b never exiasts and has to be created by RR.

Original comment by heinz.weigand@gmail.com on 21 Jul 2007 at 5:55

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Do you have write acces on the directory when not mounted? Perhaps it goes 
wrong 
there. I should code a check for write acces anyway.

Original comment by rubyripp...@gmail.com on 6 Aug 2007 at 6:31

[GoogleCodeExporter]

I do have access to that directory...

Heinz

Original comment by heinz.weigand@gmail.com on 27 Sep 2007 at 11:08

[GoogleCodeExporter]

Can you check if latest commit (147) fixes your issue? If not, I'll have to dig 
a 
little deeper about what we can do about this.

Original comment by rubyripp...@gmail.com on 29 Sep 2007 at 4:49

• Changed state: Started

[GoogleCodeExporter]

It seems that this is NOT rr fault. Here is what I did:

- unsave removal of the external drive (just plugged it out)
- start rr and rip a CD
- rr writes the ripped and encoded files in the directory of that mountpoint

Heinz

Original comment by heinz.weigand@gmail.com on 30 Sep 2007 at 3:57

[GoogleCodeExporter]

I guess then the status can be updated to fixed... It seems to me this is a 
very 
productive weekend :)

Original comment by rubyripp...@gmail.com on 30 Sep 2007 at 8:39

• Changed state: Fixed

[GoogleCodeExporter]

>I guess then the status can be updated to fixed... It seems to me this is a 
very 
>productive weekend :)

seems so :-))

yes, issue can be closed

Original comment by heinz.weigand@gmail.com on 30 Sep 2007 at 9:22