Cezar Fistik <[EMAIL PROTECTED]> writes:
> Hello Kendall,
>
> Friday, April 22, 2005, 8:50:42 PM, you wrote:
>
> > Anyhow, my understanding is that the current work-around to this
> > problem is to turn DMA off for your ata drives. I guess this can be
> > done manually with the atacontrol comman
Hello Kendall,
Friday, April 22, 2005, 8:50:42 PM, you wrote:
> Anyhow, my understanding is that the current work-around to this
> problem is to turn DMA off for your ata drives. I guess this can be
> done manually with the atacontrol command as I've been doing (though
> as you'll see in my messa
On 4/22/05, arax <[EMAIL PROTECTED]> wrote:
>
> Oh, no. Hope that's not true. I jsut finished installing and configure
> all the software, it would be a big pain starting over again. So, as
> far as I get it, there isn't a definite answer to this issue. You're
> suggesting that it's the drive, I s
Hello,
> arax writes:
>> I was just wondering if there's a solution to fix the WRITE_DMA problem. I've
>> searched the archives but couldn't find a complete answer to this,
>> like why it's happening and what to do about it. I'd appreciate any help.
> I had the same problem (same logical device,
arax writes:
> I was just wondering if there's a solution to fix the WRITE_DMA problem. I've
> searched the archives but couldn't find a complete answer to this,
> like why it's happening and what to do about it. I'd appreciate any help.
I had the same problem (same logical device, in fact, and a
Hi all,
I was just wondering if there's a solution to fix the WRITE_DMA problem. I've
searched the archives but couldn't find a complete answer to this,
like why it's happening and what to do about it. I'd appreciate any help.
It seems that this doesn't do any harm to my system, but I'm not sure
