" Intel has a task team in place " Why don't they join us?

[idata]

It's been a week since the problems began and basically no word from Intel. This is really a lame response to a major problem.

Why doesn't someone from the "task team", who are supposedly working on this issue, join this forum? Start a thread, let us know what's going on and, most importantly, seek some feedback. There are alot of smart folks on this forum, and maybe if you let us know whats going on and ask some questions, you might get some helpful answers.

Or, are you just too big and important that it would be too low for you to stoop?

[idata]

If a solution is not going to be forthcoming anytime soon why can't we have an interim solution like being able to revert back to the old firmware, which is currently not possible?

Right now I've got 2 G2 drives. One I can use for a door stop and the other for a paper weight. I've submitted a support ticket to ask if I should RMA or wait for a firmware update, but no reply. I can't send them back for a refund either so that it not an option, however appealing that is right now.

After spending over $1K on 2 Intel drives I will now have to go out and buy a hard drive whilst this fiasco gets sorted out so I can continue to use my pc.

What is going on Intel? Clearly pre launch testing was woefully inadequate. There is no direction in this forum or from official support channels about what we are supposed to do.

I'm seriously regretting selling my G1 drives and getting G2 drives. I did it because I knew the G1's would not get TRIM, which is another staid point of contention that is only made worse by this situation.

[idata]

Well said. I personally don't need Intel engineer to discuss all technical details, but I definitely AT LEAST need som sort of feedback from Intel. There are people who already "RMA"ed their drives, but there are many others who are awaiting Intel response as how to act (RMA or not etc.). There are others who just WAIT in their bussineses (which they make their money in) whether to use G2 drives or not (at the moment and even in general). I also agree that it is absolutely not a good bussines practice to shut the door and keep the silence. Aside the technical part, this is the other sad side of this story And I am also concerned, why IT media has not ring the bell yet. Strange.

For my part, I used Intel SSD just beacuse I thought if anything happens, there is a strong company to solve the problem. I am deeply dissapointed by Intel's lack of response and information at the moment. And I am sad that I was THAT wrong

[idata]

I seriously agree with Redux. I have sent several emails to Intel support (one which was before the whole firmware fiasco) and I never received a response. Now a week after their latest firmware f*7!k up, no updates, no news, nothing! I seriously doubt I will purchase any more Intel products whether they be CPU's or SSD's and will advise people against them due to the HORRIBLE/non existent customer support.

[idata]

For those posters who are upset about the lack of response from Intel, you have made ONE FALSE assumption/conclusion. YOU ASSUME that it is Intel's fault. I said in one thread you better hope that it is an issue that they can correct. There are folks that upgraded to the new frimware and experienced NO PROBLEMS. Check the POLL thread. Therefore, it is false assumption to assume that the bricked drives are the result of the "firmware" not working. If the Intel engineers conclude that the bricked drives are the result of some factor out of their control, then they have every right to say that they cannot fix it and plz contact your motherboard vendor and/or Microsoft. I guarantee that you will be doubly pissed if this is the case.

They are probably trying to device a solution that will at least keep the data contents of your drive in tact.

I work with software/hardware and anybody that has experienced this type of problem will tell you that this is a tough nut to crack.

[idata]

I don't understand the new statement either.

In my case, the issues are surely not related only to Windows 7 x64, because I tried also with Vista and Ubuntu getting the same results: after some reboots or a shutdown I get the "not a system disk" error.

I don't know if you noticed, but now also the SSD Toolbox (version 1.1, dated 2009/11/05) is unavailable.