From my experience, I have seen people higher than me, like managers and leads, and have been around longer (e.g., a decade) get the axed more. It's sad!:(
Thanks Maxtorman! I did subscribe to the notifications to those KB documents and the forum threads. And of course my/. replies to your/. comments. I want this resolved before it is too late.:)
"Then the bricking issue came to their attention. It took so long because it's an issue that's hard to track down - pretty much the journal or log space in the firmware is written to if certain events occur. IF the drive is powered down when there are 320 entries in this journal or log, then when it is powered back up, the drive errors out on init and won't boot properly - to the point that it won't even report it's information to the BIOS."
Can we view and clear this with ourselves to avoid the bricking in advance?
That's the title of my VMware image to test the CD and to screen capture. Ever use a virtual machine program like VirtualBox (http://www.virtualbox.org)?
I find it ironic that our HDDs are about to be bricked EITHER way (on its own) or with the pulled firmware updater (released twice already too; first one crashed with memory dumps and stuff for everyone; second one bricks 500 GB models).
The firmware updater uses FreeDOS from a CD image (ISO). Users had to burn it to a CD and boot from it. Here's an example when I tried it (first release that crashed while upgrading -- did not brick for people and me) under VMware to see if my CD booted: http://img403.imageshack.us/img403/7128/screenshotsa7.gif from Sunday night. I didn't bother to try the second one because that one totally bricked 500 GB HDDs which I have!
So do what I do since I hate slides too... Click on the each page number into tabs in background. Then, use ctrl-w to close each one when done.:)
Instead of annoying slides with ads, how about making subscription accounts that show all pictures in one page and no ads? I am sure some people would willing to pay for that.
Slashdot Mirror
And a senator proposed a bill to extend Windows 7 beta's distribution like the digitial television/TV requirements. [grin]
VideoSift shares a YouTube video playlist (seven videos) showing a tour: "A day in the life of a space station astronaut, follows Garrett Reisman, as he goes about his day to day tasks onboard the International Space Station (ISS)."
Fron AQFL.
From my experience, I have seen people higher than me, like managers and leads, and have been around longer (e.g., a decade) get the axed more. It's sad! :(
Ah, try http://forums.seagate.com/stx/board/message?board.id=ata_drives&thread.id=4771 (another thread).
BG isn't OTA unless I missed something.
If this was an emergency like on 9/11/2001, then this would had been very bad.
Thanks Maxtorman! I did subscribe to the notifications to those KB documents and the forum threads. And of course my /. replies to your /. comments. I want this resolved before it is too late. :)
Poor chairs in the White House. :)
"Then the bricking issue came to their attention. It took so long because it's an issue that's hard to track down - pretty much the journal or log space in the firmware is written to if certain events occur. IF the drive is powered down when there are 320 entries in this journal or log, then when it is powered back up, the drive errors out on init and won't boot properly - to the point that it won't even report it's information to the BIOS."
Can we view and clear this with ourselves to avoid the bricking in advance?
Forum threads look OK to me.
That's the title of my VMware image to test the CD and to screen capture. Ever use a virtual machine program like VirtualBox (http://www.virtualbox.org)?
Go here http://forums.seagate.com/stx/board?board.id=ata_drives to see the angry users and posts in Seagate's official forum. Most of us are pretty angry and upset. Definitely read this super long thread: http://forums.seagate.com/stx/board/message?board.id=ata_drives&message.id=6272 (42 pages).
I find it ironic that our HDDs are about to be bricked EITHER way (on its own) or with the pulled firmware updater (released twice already too; first one crashed with memory dumps and stuff for everyone; second one bricks 500 GB models).
FYI, http://support.seagate.com/firmware/MooseDT-32MB-SD1A.ISO was the ISO file that was released (404 error now due to brickings) according to my download history. Seagate needs to get the next one right!
The firmware updater uses FreeDOS from a CD image (ISO). Users had to burn it to a CD and boot from it. Here's an example when I tried it (first release that crashed while upgrading -- did not brick for people and me) under VMware to see if my CD booted: http://img403.imageshack.us/img403/7128/screenshotsa7.gif from Sunday night. I didn't bother to try the second one because that one totally bricked 500 GB HDDs which I have!
So do what I do since I hate slides too... Click on the each page number into tabs in background. Then, use ctrl-w to close each one when done. :)
Instead of annoying slides with ads, how about making subscription accounts that show all pictures in one page and no ads? I am sure some people would willing to pay for that.
Is Indy a pushing robot now? No wonder Indy 4 movie was awful. [grin]
Damn. :( Now, I am worried about mine! And Seagate is not replying to people! Ugh.
InSSIDer is better and updated. NetStumbler hasn't been updated for years. I recall it was due to money. :(
Damn! How long did your girlfriend's model last?
They mentioned Barracuda 7200.11 which I have. I don't have 1 TB. Are smaller sizes affected? None of the links said so.
I just bought a 500 GB SATA HDD (ST3500320AS). Does my model have this problem too? :( Is there a way to check?
Spock, is that you or am I hallucinating? 8)
In the summer in L.A. with a decent sized house, one can go up that high easily with air condition (central unit). :(
I can run Vista on 512 MB of RAM, but not nicely.
Already done. Watch this YouTube video. [grin] :)
Hmm, this sounds like Beauty and the Geek.