I'm using 3.0.7, but it came with the Fedora install (unless the up2date
patched it last week). I didn't install any non-RH version though.
However, frustrated, I started poking around with CDparanoia. When I
tried to rip something straight from that, I got roughly the same error
message - that the cd is busy. I guess I should have tried doing that
right away, before blaming Grip! :) Again, I can only plead linux
newbie ignorance. I'm still trying to get my head around the fact that
linux is so modular, so that Grip is a nice GUI frontend for a
completely accessible and functional program, rather than a monolithic
But back to the subject in hand, I am quite pleased to report that after
testing the cddrive with cdparanoia -vsQ that the hardware all tested
out quite nicely.
And best of all...after that command I can now rip and encode in both
cdparanoia and Grip. Although the "whys" of this elude me, it does seem
to work now.
Thanks for the quick response Mike. Much appreciated.
On Fri, 2004-03-19 at 20:19, Mike Oliphant wrote:
> What version of Grip are you using? Redhat patched both grip and
> cdparanoia at one point in a way that caused problems if you installed a
> non-redhat version of grip.
> It should be ok with versions of grip 3.1.4 and later, though.
> Tony wrote:
> >This is somewhat odd. Suddenly I am unable to rip & encode CDs. Here's
> >what grip --verbose had to say, in truncated form:
> >Drive status is 4
> >Drive status is 4
> >In CalculateAll
> >We aren't ripping now, so let's zero encoding values
> >Total rip size is: 37961280
> >Total enc size is: 3436177
> >In RipNextTrack
> >First checked track is 4
> >Ripping away!
> >Ripping track 4 to
> >Calling CDPRip
> >Error trying to open /dev/hdc exclusively (Device or resource busy).
> >retrying in 1 second.
> >Unable to open cdrom drive.
> >Rip finished
> >I am somewhat of a beginner in linux, so I apologize if it is dead
> >simple to determine what else is using the CD drive and how to stop it
> >(as I'm guessing something else is preventing Grip from obtaining an
> >exclusive lock on that dirve?)
> >As far as I can figure, it stopped working after I did an up2date on my
> >Fedora Core 1 distro about a week ago.
> >Thanks in advance for anyone able to help me!
> >This SF.Net email is sponsored by: IBM Linux Tutorials
> >Free Linux tutorial presented by Daniel Robbins, President and CEO of
> >GenToo technologies. Learn everything from fundamentals to system
> >Grip-users mailing list