Comments on: Samsung HD753LJ SATA HDD 750 GB

By: Marvin

Marvin — Wed, 18 Aug 2010 06:49:07 +0000

AFAIK this burst speed stems from your hard drive’s cache to the computer’s RAM. SATA’s interface speed is too fast for current hard drives (except SSDs) so switching to 1.5 Gb/s is no problem. Especially considering you’d otherwise be unable to use this drive on your current motherboard but had to buy a new one.

Weird btw, that I can’t reply to your comment but only to my own…

By: DaRuSsIaMaN

DaRuSsIaMaN — Tue, 17 Aug 2010 08:33:53 +0000

My HD is the Samsung F3 Spinpoint 1TB model HD103SJ. According to HD Tune benchmark, the max transfer rate I had was 124 MB/s:

http://img237.imageshack.us/img237/7647/hdtunebenchmark2samsung.png

This is actually the exact same as the max write speed achieved in this review:
http://www.bit-tech.net/hardware/storage/2009/10/06/samsung-spinpoint-f3-1tb-review/3

So I guess that settles that: I can conclude there’s no performance lost in that department. Right? But why is the burst speed so different?? That review reports 258.9 MB/s whereas I got 107 …

By: Marvin

Marvin — Tue, 17 Aug 2010 05:25:49 +0000

You tell us:

SATA 1.0 (SATA 1.5Gb/s) ≅ 143.05 MiB/s
SATA 2.0 (SATA 3 Gb/s) ≅ 286.10 MiB/s)

How fast are your harddrives?

By: DaRuSsIaMaN

DaRuSsIaMaN — Mon, 16 Aug 2010 22:38:04 +0000

Hi again. Btw, this either is a stupid newb question to which everyone but myself already knows the answer to, or it should have been raised and answered a long time ago. The question is, is there any performance loss from switching the SATA II interface on the HD down to SATA I interface to get it to work with VIA?? If not, then why did they bother making the SATA II standard if it’s not any better? If there is a performance loss, exactly what am I losing?

Thanks!

By: notabene

notabene — Thu, 10 Jun 2010 21:08:12 +0000

Thank you so so much, stumbled across this site after trying many a suggestion to get my samsung f2 working with my old asus k8v-x board with the vt8237 chipset. and happy to say i got the drive working, at last.

thanks to all again esp mr cowin

By: Marvin

Marvin — Sun, 06 Jun 2010 04:50:28 +0000

Well, I’m glad it worked out and Samsung apparently has gotten it finally right.

By: DaRuSsIaMaN

DaRuSsIaMaN — Sat, 05 Jun 2010 20:46:50 +0000

Well I admit I got a bit lazy/impatient and didn’t want to record what it said. But it was just some useless stuff. I think part of it said copyright such-and-such year(s). I got the impression it was like that info programs sometimes print at the end after they stop executing like written by so-and-so copyrighted such-and-such year, bla bla bla.

And yes, of course I did it from booting off the boot disk. I followed Ken Cowin’s instructions.

But in any case, immediately after that attempt failed (and after I posted the posts below) I tried the other method, using ESTOOL, as suggested by spodosaurus. It’s up to version 3.00g now on Samsung’s website, so that’s the one I used. And it worked! I installed winxp on it and have been running diagnostics on the drive, using the computer/mobo which did not detect it before. So it seems like Ken Cowin’s method is no longer necessary anyway. Using ESTOOL is a little simpler, more straightforward. And it worked for both me and spodosaurus. And it has the settings correct, not backward like in SSpeed.

I’m thinking that perhaps the reason SSpeed wasn’t working was because my HDD was having issues? I was getting the infamous “a disk read error occurred. Press ctrl alt del to restart” problem.
http://www.tomshardware.com/forum/250364-32-solution-disk-read-error-occurred
I was getting the error on both my friend’s computer, which I used to do this procedure, and on mine at home after it was able to actually detect it.

By: Marvin

Marvin — Thu, 03 Jun 2010 08:40:11 +0000

Right, and what does that line say? You did run the tool from a boot disk or boot cd and not from inside Windows, right?

When I boot from this disk/cd and type ‘run’, I can select 1. or 2. and choose the latter, setting to 3.0 GB/s which actually sets to 1.5 which I can verify immediately after by firing up ESTool (from another disk or cd) under SET MAX UDMA MODE > Display current mode which is set to Mode 1 (SATA 150).

By: DaRuSsIaMaN

DaRuSsIaMaN — Thu, 03 Jun 2010 06:37:47 +0000

P.S. Correction, actually. When I said nothing comes up on screen, it actually did spit out one more line of text before finishing and going back to the same DOS prompt. Anyway, no screen with options came up.

By: DaRuSsIaMaN

DaRuSsIaMaN — Thu, 03 Jun 2010 06:35:13 +0000

Ok I finally got around to doing the Ken Cowin method. Why is it not doing anything?? I did everything according to the steps. After I type in “run” after I’m inside the sspeed directory, it spits out some text, sits there for a while, and then *nothing comes up on screen*! It just goes back to the same prompt: “A:\SSPEED>”. And that’s it. I never got any screen with options to come up. What’s going on??