someone in NBR mentioned they had Dell replace his SSD drive and the new one supported TRIM.
So an exchange may get you one, but it's probably hit and miss as far as that goes.
As far as using the non dell firmware updated, i would be concerned that doing so may void your warranty
Some of you may have also found the following thread on the Alienware forums
It's definitely for the bravehearts, since it's not an approved DELL approach. Am toying with the idea of giving it a go though - coz I'm a little crazy like that.
On p13 of the thread you'll see Quadzilla reports success against upgrading from VMB19D1Q using the approach from the first post - that's the same firmware version I have.
You'll also see on p8 there's a link to a Samsung supplied OEM installer, which seems to actually be a similar approach. Using an official Samsung download seems a preferable route - except that all the references in the Samsung docs talk about it in terms of upgrading from VBM18.
I'll report back if I get brave enough!
The problem is that while the hardware piece of drive is EXACT same as every other (Samsung P22-J, Corsair P256, Dell F342T, etc etc [YES THEY ARE IDENTICAL inside - THE SAME]) the OS/microcode or whatever driver is running differs them. I realy don't know by what - mayby just the reseller microcode as I suppose.
Why? When I tried to apply TRIM patch from other brands it's either not recognizing the drive or say that my microcode differs from the ones that this patch is meant to and instantly abort update...
Different apps act different on the same mashine. Is it a excuse for DELL - NO! SAY ON YOUR RESPONSIBILITY, NO WARRANTY, WILL PERMAMENTLY ERASE DATA, CAN CAUSE HARM TO YOUR HARDWARE OR YOU , NOT OFFICIALY SUPPORTED but GIVE THE PATCH OUT.
Don't get me wrong... I LOVE(d?) Dell.
I've spent over 70+ bucks to have a DELL SSD (not other brand) piece in my system. Why? I thought it's reliable, stable AND HAS SUPPORT!!!
What turns out is that I didn;t only overpaid, I throwed my cash foolishly. NO TRIM in my recently purchased drive with VBM94D1Q firmware. NO support to do reflash (even with other dranded software - others with other firmware succeed). THERE HAS TO BE A WAY for a person like me/us. THERE HAS TO BE ANSWERS!!!
Straight form Dell.
Totally agree - there has to be an answer technically, even if it involves some not very easy steps and has risk of data loss which DELL could caveat.
Whether DELL will actually go down that road only time will tell, I have a sinking feeling they won't though.
In terms of drive recognition, it does seem that some drives/firmware combinations fare better than others when an attempt is made to upgrade - if you read through the Alienware thread (apologies if you did already), there seem to be some quite strict hardware requirements for the machine that the drive can be mounted in for the upgrade utility to recognise the drive and work. From memory, I think it mentioned needing an Intel chipset with SATA II support. I think there was just one laptop that mentioned that had been successfully used to mount the driver and do an upgrade - a Latitude D620.
Locally here I have an oldish Shuttle that may suit - and - ahem - I also have a D620 in the office but it's not mine, it's my girlfriends work machine. Not sure I'll get away with taking it apart to mount my SSD for update purposes however much I tell her it won't damage it. Maybe I'll risk it when she's out one evening
I've tried all the various flashers with my Dell 256gb drive (VBM15D1Q) from Mushkin, Lenovo Samsung, Corsair, OCZ all to no avail, both on my SXPS16 laptop and several desktop PCs including one at the office that does have a functioning IDE compatibility mode.
Thought I'd post my experiences with each them since I have found three different flash utilities in the wild, each of which behaves differently. To my knowledge no one has been able to update a Dell drive with the VBM15D1Q firmware.
1) Lenovo utility (fw2.exe) will see the drive on my SXPS16 laptop in AHCI mode but will cannot update firmware, even after modding the fw.pro config file; must be checking for a specific firmware version or OEM microcode that is not there
2) Mushkin utility (maindiag.exe) will see drive on a generic desktop PC in IDE but gives an error after failing to write the firmware. Clear NAND option does work, however.
3) Samsung, Corsair, OCZ utilities (DSRD1_0.exe) never find the drive; must be checking for a specific firmware version or OEM microcode that is not there
Guess at this point only options are to sell the drive or keep waiting for Dell.... someone's post on NBR indicated Dell was 'working on it' but I wouldn't hold my breath.
The case is that the drive WAS/IS recognized in all of my gear.
Not only old workstation thinkcentre a51/s50, ibm laptops x61, t60, t61, dell hardware but even in my homecenter...
All of those computers SEE the drive, TRY to reflash and FAIL with a message: "Mainfirmware OEM Version is different , Please Check Your Code Version".
No harm to the drive happened or whatsoever. I took pictures for those faint hearted... quality is poor but Youll see what You shoud.
Attempt made with MAINDIAG.exe and all sort of versions of MF.bin and IF.bin
In all cases (on all PC/LAPTOP/HCenterPC) the initialize firmware passes like here:
The problem occures while trying to upload main firmware:
When AHCI in BIOS is set ON the drive itself is recognized but after an attempt on main firmware "generic ATA error" is outputed - no changes to the drive have been made:
Other flashers like the samsung generic one called DOSRD1_0.exe are even faster than a toilet flush. But they do nothing. The drive is recognized and ... wrong firmware for the drive message is stated with an quick exit produced
I'm realy considering buying a corsair or ocz drive in a short while to replace eight F342T...
Thanks guys for the feedback on experiences with the utility and hardware combinations you've tried - it'll help all of us gain a better understanding of what may or may not work.
If/when I get brave enough I'll post my findings too.
Observant followers of this thread will notice my "ponderings" email has gone ... apparently I violated the TOS for postings and the moderators have taken it down. I'll let you draw your own conclusions on that.
They have asked me to edit it to comply with the TOS and repost - but I think everyone will have got a copy by email anyhow - and it was just my random ponderings, so I think I'll pass on the that one. Suffice to say - unless something official arrives soon to fix this mess and help us all ou, I think it's fair to say at least one or more of the conclusions I drew may have been too close.
Wonder how long before this post also gets removed ..
Dell doesn't even bother to answer my support mails...
Glad to know that there are working people at DELL, disappointed to know their job is to hide the truth instead of solving the issues and giving some piece of information about it...
I think I'll try to use my warranty and exchange the SSD, but I fear it won't have TRIM enable either...
They don't seem to have any centralized knowledge base at DELL.
Each customer problem is new to them and they don't know anything about it...
Samsung released the firmware that's a fact. (I read they send it to DELL in early December)
DELL has nothing to say and apparently doesn't care at all...