JTee

Member
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JTee

  • Rank
    Member
  1. Well, with any new hard drive I purchase, I do some testing until I'm convinced that the drive is good (not a lemon) and that I'll not lose data. I've done a lot of testing on the drive and so far, it has not corrupted any files. By testing, I am dumping torrents there, dvd disc images, file archives and so far there hasn't been any issue. Also remember that the firmware we are talking about is for the eSATA interface, not the hard drive itself. The fact is that most external firewire enclosures use Oxford chipsets and its likely that most of the eSATA enclosures are using Oxford chipsets as well... and those Oxford eSATA interfaces are probably using the same March 9th firmware (or newer), otherwise they will have the same speed issue. That said, I believe the beta warning you are referring to was a warning about the Oxford Updater program itself, not the March 9th eSATA firmware. They recently updated the Oxford Updater to deal with USB and eSATA. Previous versions were for firewire only. I know this because I have 4 firewire enclosures I've been using the Oxford Updater for years. I'm not going to tell you what to do, but I'm not having any problems.
  2. 3.afk is the revision of the firmware on the physical hard drive itself located within the FreeAgent Pro's case, not the eSATA interface, which has its own firmware. The update I posted previously upgrades the eSATA interface firmware on the FreeAgent Pro from v0.34.0010, dated February 26, 2007, to v0.34.0011, dated March 9, 2007. The only way to see that version info is through the Oxford Updater. FYI: the Oxford Updater is NOT a Seagate product. It is a product of Oxford Semiconductor, which is the company that makes the eSATA interface on the FAP.
  3. Just an FYI... I'm not having any problems writing to the drive, nor am I experiencing any disconnects over eSATA. I use an ST117R SATA controller card in my system (since my older mb does not have native SATA support)... http://www.lycom.com.tw/ST117R.htm It uses a Silicon Image SiI3114 Rev 2 controller chip. I have 2 internal Seagate SATA drives and the FAP connected to it. Since I updated the FAP's eSATA interface firmware, it's been working great. BTW, that card is dirt cheap, and maybe that or a card like it could fully solve your eSATA issue.
  4. The update has existed since August, 2007, at minimum. That is the date of the review on Newegg which contained the link I provided here. Sorry about your issues, but when someone goes out of their way to help you, you could say thank you.
  5. I just happened upon this thread from a web search... boy, are you guys going to be happy... :-) I bought the 750GB FreeAgent Pro a few days ago and saw the same absymal ESATA performance. I did some research. I found this little gem posted in a review on NewEgg's website: http://support.seagate.com/rightnow/downlo...SATA_Update.zip This is a firmware update that will completely transform the ESATA performance! After the update, HDSpeed is reporting ~61MB/sec read performance on my PC... still a 22ms access time, but a drastic increase in read/write performance over ESATA! My notes on the firmware update process: I didn't install the included JAVA VM as they directed as I already have JAVA VM V1.6.0, so installing 1.5.x was unnecessary for me. For those of you who have never used the Oxford updater before (I've used it many times before on Oxford chip firewire enclosures).. do be careful and don't change anything you aren't sure of. Follow the instructions provided with the update and you should have no problems. Note that you may have to scan the USB bus a few times until it picks up the FreeAgent.. that's okay. At the end of the update (and the updater says that the update was successful), the drive will just sit there glowing at you - that's normal. At this point, you need to unplug it to power it off. Wait 10 or 20 seconds... then you can power it back up and either check the esata firmware version using the oxford updater (with the drive still plugged in via usb) or unplug from usb, plug in your ESATA cable back in and reap the rewards immediately. Also, on my machine, the drive had to be re-recognized by XP after the update (in my experience, typical behavior after an Oxford firmware update). Also, I have not tried this update on Vista, but I would think that it would work fine. GOOD LUCK!