fcastro

Adobe has redone the forums. But I attached the necessary reg edit in the above post that fixes the issue.

Same here took i365 about a week to fix my drive. At least seagate is making things right.

Hi all, I am running windows xp x64 on a gigabyte motherboard with ACHI enabled. I have noticed that when I connect my external sata drive on I dont get the "safely remove hardware" icon in the task panel. When I run the "safely remove hardware sata" the drive does not even show up in the menu. Neither does my primary internal sata drive. If I turn the external drive off while windows is on and nothing is being done to the drive I get a an event viewer message about ftdisk. So that means I have to find a way to safely remove the sata before ejecting it. I can't seem to find why this is happening in x64. Anyone have any suggestions?

I honestly think the problem is much much larger then seagate is letting people know. I have done a lot of reading and people have suggested that the problem is based on a specific value in the firmware which the probability of hitting is suppose to be super high but that just can't be the case. Drive failure a few months after purchase is unreal. This wouldn't be the first time a corporation the size of seagate try's to cover up a massive failure problem in order to not nose dive its stock. But lets see how they continue to handle this problem.

First off that can't be correct. I purchased my drive at my local MicroCenter in October of 2008, so there is no way that statement is correct. My drive is at i386 as we speak. I would call up and talk to tech support. Its easier for them to deny you over email.

Found this online: Seagate offers fix, free data recovery for bricked Barracudas by Cyril Kowaliski — 3:54 PM on January 16, 2009 Well, how about that. Seagate has acknowledged the bricking issue surrounding Barracuda 7200.11 hard drives, and it's trying to make things right by offering a firmware fix and data recovery services. Here's the full statement we received from company spokesman Mike Hall: Seagate has isolated a potential firmware issue in certain products, including some Barracuda 7200.11 hard drives and related drive families based on this product platform, manufactured through December 2008. In some circumstances, the data on the hard drives may become inaccessible to the user when the host system is powered on*. As part of our commitment to customer satisfaction, we are offering a free firmware upgrade to those with affected products. To determine whether your product is affected, please visit the Seagate Support web site at http://seagate.custkb.com/seagate/crm/self...sp?DocId=207931. Support is also available through Seagate's call center: 1-800-SEAGATE (1 800 732-4283) Customers can expedite assistance by sending an email to Seagate (discsupport@seagate.com). Please include the following disk drive information: model number, serial number and current firmware revision. We will respond, promptly, to your email request with appropriate instructions. There is no data loss associated with this issue, and the data still resides on the drive. But if you are unable to access your data due to this issue, Seagate will provide free data recovery services. Seagate will work with you to expedite a remedy to minimize any disruption to you or your business. For a list of international telephone numbers to Seagate Support and alternative methods of contact, please access http://www.seagate.com/www/en-us/about/contact_us/ *There is no safety issue with these products. The free data recovery for already-bricked hard drives seems like a nice touch, especially considering the cost of third-party services. According to the knowledge base entry, though, the issue may affect a fairly large number of drive models—not just the 1TB four-platter drive we talked about earlier this week. Seagate recommends that users with 1.5TB, 750GB, 640GB, 500GB, 320GB, and 160GB Barracuda 7200.11 drives, along with some Maxtor and ES.2 models, all install the firmware update.

Guys this is a Global problem from what I am reading non stop. I have the Barracuda 7200.11 firmware SD15 500GB hard drive and today on boot up the bios no longer sees the drive (My drive is 3 months old). Everyone I have just emailed the consumerist about this issue. http://www.consumermediallc.org/contact.html Everyone please take a moment and send them an email informing them of the issue. If we can get the consumerist to raise an alert, not only will it help our case but it will also alert people out there who don't know about this flaw.

9QM5KH4M:ST3500320AS:9BX154-335:SD15:09055:KRATSG:2008-10-01:2008-01-28:RETAIL/MICROCENTER:fcastro:USA:(no bios detect):XP:ThermalTakePurepower500W Has anyone figured out a solution? OMG this is unreal! I have my research paper for school on this drive that has now disappeared. 1 month of my work if I can't get my data back I will fail there is no time to write all of my paper...

Finally found a work around thought I would share. http://www.adobeforums.com/webx?7@@.59b61a73/67 Post #65 which requires a registry tweak seems to be the only fix. Notice that this works for both Nvidia and ATI video cards. Open the registry editor (regedit) Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management Add a new REG_DWORD entry called SessionImageSize with a value (decimal) of 20.

Hi everyone, Huge problem that I can't seem to get much information on Just built a new rig that is running XP x64 with latest drivers and updates, specs are below. Installed my otf's (openType fonts) and have tried 2 different type managers (Extensis Suitcase and FontAgent Pro 4) to get my fonts to activate and they are not activating. This lead me to check the windows font folder and I noticed that any OTF in the folder was not showing up in my applications (photoshop etc). So I double click on the fonts and I am getting a "the requested file /path to font/ was not a valid font file" message. I installed the fonts directly from my cd so I know the fonts are valid. Only thing that I have been able to fine online is that it could be a graphics driver problem. I am running the latest version of ATI catalyst drivers 8.12. Of note I also have 8 gigs of memory. Specs: Gigabyte Ep45-UD3P Motherboard MSI ATI Radeon HD3850 512MB Intel Core 2 Quad Processor Q9300 8gb PC2-8500 (DDR2-1066) OCZ Reaper Memory