On Tue, Mar 18, 2003 at 06:20:20PM -0600, Joseph A Nagy Jr wrote:
> nate wrote:
> >Joseph A Nagy Jr said:
>
> >probably not so much a grip problem as an I/O problem. Any way to
> >check the kernel logs on the machine? I'm thinkin they are getting
> >flooded with I/O errors, in which case there's n
nate wrote:
Joseph A Nagy Jr said:
probably not so much a grip problem as an I/O problem. Any way to
check the kernel logs on the machine? I'm thinkin they are getting
flooded with I/O errors, in which case there's not a whole lot you
can do, besides try not to use discs that generate such errors.
Nicos Gollan wrote:
On Tuesday 18 March 2003 23:23, Joseph A Nagy Jr wrote:
Hi All,
I've recently been having problems where if grip encounters a particular
nasty track, it will totally slow down the computer but continue ripping
(albeit at 0.1x). Clicking repeatedly on abort rip (or abort rip +
Joseph A Nagy Jr said:
> Hi All,
>
> I've recently been having problems where if grip encounters a particular
> nasty track, it will totally slow down the computer but continue ripping
> (albeit at 0.1x). Clicking repeatedly on abort rip (or abort rip + encode
> (the encoding process dies just fin
On Tuesday 18 March 2003 23:23, Joseph A Nagy Jr wrote:
> Hi All,
>
> I've recently been having problems where if grip encounters a particular
> nasty track, it will totally slow down the computer but continue ripping
> (albeit at 0.1x). Clicking repeatedly on abort rip (or abort rip +
> encode (th
Hi All,
I've recently been having problems where if grip encounters a particular
nasty track, it will totally slow down the computer but continue ripping
(albeit at 0.1x). Clicking repeatedly on abort rip (or abort rip +
encode (the encoding process dies just fine)) seems to have no effect
and
6 matches
Mail list logo
