Sata Speed Test?

[Newbury]

I just installed a Maxtor 300 Gig Sata drive that went well. The drive shows
up along with the IDE drives one being another Maxtor 300 Gig. I am able to
access this drive.I am unable to capture to the Sata drive with a report of
3600 Mbits read and write while the identical drive on the IDE channel is
reporting over 63411Kbits read and 32902 write. The Sata is running on
channel 1 while on channel 0 report of drive failure and no boot. My main
system drive is on IDE. Intel mainboard D915PBL/Intel 630 processor. WinXP
Pro with 2 gigs DDR2. System captures, renders and burns well with Pinnacle
Studio 8 but not on any SATA drive. Is there any way I may have gone wrong
with the installation? I ran Maxblast 4 that came with the drive. I
reformatted and replaced both cables but still no speed from this setup. Did
I somehow set up this drive as a RAID drive my mistake or aren't RAID and
SATA the same?

Thanks for any help.

Newbury

 

[Paul]

I just installed a Maxtor 300 Gig Sata drive that went well. The drive shows
up along with the IDE drives one being another Maxtor 300 Gig. I am able to
access this drive.I am unable to capture to the Sata drive with a report of
3600 Mbits read and write while the identical drive on the IDE channel is
reporting over 63411Kbits read and 32902 write. The Sata is running on
channel 1 while on channel 0 report of drive failure and no boot. My main
system drive is on IDE. Intel mainboard D915PBL/Intel 630 processor. WinXP
Pro with 2 gigs DDR2. System captures, renders and burns well with Pinnacle
Studio 8 but not on any SATA drive. Is there any way I may have gone wrong
with the installation? I ran Maxblast 4 that came with the drive. I
reformatted and replaced both cables but still no speed from this setup. Did
I somehow set up this drive as a RAID drive my mistake or aren't RAID and
SATA the same?

Thanks for any help.

Newbury

Sounds like it is running in PIO mode. That is "polled I/O",
where the processor transfers every byte itself. The other
mode is called DMA (direct memory access), where the chipset
puts the drive data into memory, without help from the processor.

You need to set the drive to "DMA, if available".

http://groups.google.ca/groups?q="dma+if+available"

If errors are accumulated while using the drive, Windows can
crank down the rate until it is that low. Deleting the
entry for the drive, and letting Windows rediscover it, is
one way to fix the problem. Have a look through the posts
here for some other ideas.

http://groups.google.ca/groups?q="dma+if+available"+crc+errors&qt_s=Search

Paul