Overclock.net › Forums › Components › Hard Drives & Storage › SSD › How to get your Kingston 40GB SSD to support TRIM
New Posts  All Forums:Forum Nav:

How to get your Kingston 40GB SSD to support TRIM

post #1 of 283
Thread Starter 
Hello Members of Overclock.Net


As some of you will be aware the Kingston 40GB SSDNOW Drives do not support TRIM by default as Intel decided not to supply Kingston with a firmware for these drives to allow TRIM functionality and Kingston has cut off support of this drive as its reached End Of Life

Your probably asking why we are talking about Intel. Well in a nutshell. The Kingston 40GB SSDNOW drives feature Intel flash chips and an Intel memory controller. The Kingston V series Boot drives are pretty much identical to the Intel X-25-V SSD drives. Thus why this Intel firmware fix for trim is possible. As such Only Intel firmwares will work with this drive. As Intel gave Kingston the shaft it is up to the consumers to mess around and mod the Intel firmware to support TRIM Thanks Intel...Thanks

However there is a FIX for all the disappointed Kingston owners. Thanks to User '' Telnet ''' on OCN and his in-depth research, he has discovered that we can indeed enable TRIM on the Kingston 40GB SSDNOW drives.

All credit goes to Telnet for his amazing findings, effort and providing us with this modified update utility. I am simply compiling a simple guide for the newbies out there to follow This guide was inspired from this thread : http://www.overclock.net/hard-drives...b-ssds-fw.html

While this is a very simple procedure. Myself and Telnet will not take any responsibility for damage done to your drive by either negligence or failure to follow this guide properly. I would advise backing up your SSD drive before performing this procedure. While it should not effect the data, it is better to be safe than sorry. I did this on my SSD drive while my OS was installed and it had no ill effects. This guide is only for the Kingston SSDNow V Series SNV125-S2/40GB and SNV125-S2BD/40GB. Please do not attempt this guide on any other variant SSD



Here we go:

PART 1

Firstly you have the option to use the latest Intel Firmware on your Kingston SSD. However it is NOT a pre-requisite for TRIM as the stock Firmware 02HA is TRIM capable, If you wish to keep your stock firmware then please skip to PART 2 . However if you wish to update the SSD Firmware you have to use a modded version of the Intel Updater as the stock Updating Utility will not recognise the Kingston drive as a compatible drive to flash ( As its not branded Intel ).

1ST Method

1. Download the Modified Intel Updater Utility attached to this thread below.
2. Create a standard bootable Flash drive or DVD/CD ROM.
3. Place the ''iSSDFUT.Exe'' on the bootable Flash drive Or DVD/CD ROM ( Before burning of course )

For help on creating a bootable USB flash drive please take a look Here : http://www.bootdisk.com/pendrive.htm

2ND Method

1. Download my Intel Updater ISO from here : http://downloadcenter.intel.com/Deta...&DwnldID=18363 I have also attached the ISO at the bottom of this thread.
2. Use an ISO editor such as ''MAGIC ISO'' to edit the downloaded ISO.
3. When using the ISO Editor replace the ''iSSDFUT.Exe'' in the ISO with the ''iSSDFUT.Exe'' attached to this thread. Save the ISO and Burn it using your Burning software.

3RD Method ( Recomended )

1. I have created a CD Boot image with the ISSDFUT update utility on it. Download the ISO from here : http://www.megaupload.com/?d=MTXIA2IG
( I have also uploaded the ISO in RaR format here. Look to the bottom of this thread ''ISSDFUT UPDATER'')
2. Extract the ISO image from the RaR File.
3. Burn the ISO to disk.
4. Reboot your PC and make sure its set to boot from your optical drive first.
5. Your system will boot into the disk. Once it has completed booting type ''iSSDFUT'' without quotation marks. Hit ENTER
6. The Update utility will start. Follow the on-screen prompts.



Once you have created your bootable medium with the updating utility. Restart your PC and amend your BIOS settings boot either from your USB or DVD/CDROM drive first. You MUST also set your SATA mode to IDE. If you have it set to AHCI, the updating may fail to find your SSD. Please see below an extract from the Intel readme,

Quote:
2. "Drive not recognized" in AHCI SATA mode
ISSUE: Some platform BIOS implementations of SATA port settings
are not compatible with the update program's process for
locating the SSD within the system in AHCI mode.

WORKAROUND: For best compatibility, configure the BIOS SATA port mode to
The "Legacy" or "Compatibility" mode to perform the firmware upgrade
( In short. If in AHCI mode nothing is detected, Try IDE mode )

Once your PC boots into DOS on your USB or DVD/CDROM you will need to enter the flash utility by typing ''iSSDFUT'' and hit ''ENTER''.

You will now have entered the Intel SSD flashing utility. Follow the onscreen instructions and accept all the various disclaimer agreements etc. Very simple and straight forward process. Once you have done this it will move onto the SSD detection phase. With Telnet's modified utility it will now successfully detect our Kingston drives as viable for flashing.

During this process it will update your stock Kingston firmware of 02HA to the newer Intel firmware of 02HD

Please be aware that the flashing process is not instant. With me it took up to 60 seconds. Please be patient and DO NOT interrupt the process.

This is what you should see during the flashing process:



Done. This is the flashing procedure complete. You have successfully completed the first part to this 3 Part process.

.................................................. .................................

PART 2

Now we have to restore the the newly flashed firmware to defaults which in turn activates the TRIM functionality on our Kingston drives. When the Intel Firmware is flashed onto the Kingston drive it keeps the drives current configuration data. This is no good as with this configuration data TRIM is disabled. We need to restore the firmware configuration to default to allow a new configuration to be put in place enabling TRIM.

To do this you will need a DOS utility called ''HDAT2''. You can download this Utility in an ISO format here : http://www.hdat2.com/ . Go to the Download section and download the ''CD BOOT ISO IMAGE''.

Once downloaded Burn the ISO using your favourite DVD/CD burning software. I use CDBURNERXP. The ISO is already set as bootable so there is nothing else you need to do but burn the ISO as it is !

Once again amend your BIOS if you need to, so your system boots from your DVD/CD ROM drive and boots into the HDAT2 utility. Once within the utility you will be prompted with a blue screen with 4 options. Select option 1 and hit ''ENTER''.

Your system will now load into the HDAT2 utility. Follow the simple on screen prompts. You may get error messages but do not be alarmed. This is just due to HDAT not finding some devices in your system it may be accustomed to. Just hit ENTER or ANYKEY when prompted to.

Once loaded into the Utility you will be at the Device list main menu screen for HDAT2. You should see the below :



Within the Device list main menu you should see your Kingston SSD listed in the device list.

Highlight your Kingston SSD drive and hit ''ENTER'' You will then see this screen below which is the ''Device main menu''



From here you will want to select and highlight the 6th option on the list. '' Device configuration overly (DCO) Menu '' Hit Enter

Once within the Device configuration menu you will see the below screen :



From here select and highlight ''Restore''and hit Enter. You will enter the restore utility and from here follow the on-screen instructions for restoring the configuration on your drive. You will also be prompted to confirm your RESTORE command by pressing ''Y''. Now sometimes it will say the operation was ''Aborted''. However it would seem it does not matter in some instances. While with me it worked normally, I did try again just to make sure it was restored and it then I got the ''Aborted'' message. If it comes up aborted do not worry too much as it seems to work anyway.

Once you have cleared the configuration from your drive. ( I did it twice just to be sure ). Hit ESC multiple times until you get back to the blank DOS screen and simply restart your machine and remove the USB flash drive or DVD/CDROM from your system as you now want to boot back into you OS.

You have now completed Part 2. All the technical stuff is now out of the way. Congrats

.................................................. .................

PART 3

Now that we have flashed and configured the drive we now want to make sure that TRIM is enabled and functioning.

You will need to do two things.

Firstly we will want to download and install ''CrystallDiskInfo'' which you can obtain from here : http://crystalmark.info/software/Cry...o/index-e.html

Once installed run CrystalDiskInfo. You will see the below:




You will notice that by ''Supported Features'' that the ''TRIM'' function is highlighted in black. This means it is enabled and functioning !

You can also tell if Windows 7 has correctly enabled the TRIM service. This does not mean however that your drive is supporting TRIM. CrystalDiskInfo is the defining answer to whether your SSD is performing TRIM or not.

Open up a Command Prompt window and type the following without quotation marks:

''fsutil behavior query disabledeletenotify''

If TRIM is enabled Command prompt will issue the following statement:

''DisableDeleteNotify = 0'' This means TRIM is Enabled.

Below is an example of what you would see :




.................................................. ............................

Congratulations. Your Kingston SSDNOW 40GB SSD now has TRIM !

You may also be interested to know that you can now use the Intel SSD Toolbox application with your Kingston drive because of this firmware flash. Take a look at this guide : Using your Kingston 40GB SSD with Intel SSD Toolbox

Thanks again to Telnet's hard work in discovering this fix. Once again all Credit goes to him. I simply compiled this guide to make the process more understandable. I hope you find my guide useful


If you are a GUEST viewing this guide and need help then please do not hesitate to join Overclock.Net and we will endeavour to help you as much as possible.

HDAT2 Images obtained from http://www.hdat2.com/


ENTERPRISE
post #2 of 283
Thread Starter 
Testimonies

This is to serve as a testimony section for the guide. Here I will post issues that members have come across and how they managed to solve them and successfully flash their Kingston SSD. The problems are not with Telnets modified firmware nor the guide. However due to the massive array of Chipsets and SATA controllers on the market some have bumped into a few hiccups. I hope the below helps those who have also come across any hiccups.

1.
Quote:
Originally Posted by cjph View Post
Ok - thanks for the info. I had tried with only the SSD connected without success, so I checked out the process and thread again, and finally got it to work by combining all the steps I have tried and read ;

I had to disconnect the Western Digital disk drive on my system, and due to the 'frozen security' type issues I was having I left the SSD drive unconnected and booted to DOS. I reconnected it (in case it is relevent I used SATA 5 on my motherboard since SATA 0/1 may cause problems from what I have read), and ran HDAT2. HDAT2 did finally see the drive, but would not let me restore the settings (I did'nt note the warning but it mentioned HPA) until I selected the next menu option (Hidden Areas Test) and temporarily disabled HPA (from memory - I think that is what it is called). Tried the restore in the DCO menu again and it worked !

I then went back to the Intel Toolbox and it now allows me to run/use Optimizer as if it is an Intel drive - a very big thank you to you and Telnet for your help and this guide.

cjph
2.
Quote:
Originally Posted by Nano2k View Post
Hi I'm new here^^

I went through the procedure, flashed ok, but I had issues with Hdat2.
It would get stuck on Scanning Int13h devices and I wasn't able to get past that on my Gigabyte UD3R. So I connected my SSD on my older P5B Deluxe system and it worked.

I had another issue though, once in Hdat2, I could not restore DCO, it kept giving me an error. Finally I figured out (there was some message about it on the screen) there was something wrong with the MAX HPA setting.
So I had to go in the SET MAX HPA menu and delete the current setting. Then I went went back to restore the DCO and it worked.

Just a heads up since I didn't read about this in the guide, maybe I had a funny issue or whatever...

Thanks to those who made this possible^^
3.
Quote:
Originally Posted by marmalizer View Post
I burnt Hdat2 4.71 to a cd and just the exe on a memory stick but i get an bios error on both of these. I then tried hdat2 4.53 and that worked a treat, it now shows trim in win7.

Could there be a problem with hdat2 4.71?
I've noticed that you've used 4.7 in your guide.
4.
Quote:
Originally Posted by Rivethead View Post
Hello all!

First a HUGE thank you to Telnet and Enterprise for all the work done here and elsewhere. It feels good that the "little guy" can give the finger to the big, bad Intel on this. Enabling TRIM on the Kingston 40GB SSD is like the same rush as OCing a CPU!!

I wanted to let you know of my strange experience following this guide last night. I believe I was able to enable TRIM, but I was unable to flash the new firmware.

I followed the instruction in this guide in Part 1 and tried all three methods and still could not get the iSSDFUT to recognize my Kingston SSD. Now, this morning I re-read the instructions and realized I missed the part about setting SATA to legacy and not ACHI. So that mistake is on me!

Regardless, I tried booting into HDAT2 just......because. I had no problems finding my SSD and just for the hell of it I got to the DCO menu and hit "Restore". No problems.

I then installed CrystalDiskInfo and lo-and-behold......the old 2CV102HA was the listed firmware.....but TRIM was NOT grayed out!

Strange.

I tried the dos command test but got some error message about needing administration priviledges to run that command (I've since figured out how to do that - I'm new to Windows7/Vista).

So bottomline: I believe I still have the old firmware. But I think I have somehow enabled TRIM.

Tonight I'm going:

1) try the dos command to ensure I get the "= 0" reply which means TRIM is running, then
2) if TRIM is working, decide if I really want to update the firmware to 02HD (I think I do since having access to the Intel SSD Toolbox would be nice too).
3) if I decide to upgrade the firmware, I'll actually follow the guide closely this time and turn off ACHI before running the iSSDFUT file.

Thanks again Enterprise and Telnet!!
5.
Quote:
Originally Posted by SDMFlayne View Post
UPDATE

ENTERPRISE, Telnet, you guys are totally awesome. Turns out, there must have been an error on the first HDAT2 boot disc I burned using Active@ ISO burner. I used CDBurnerXP to burn the image, rebooted, and it worked perfectly. Thanks so much!
6.
Quote:
Originally Posted by Rivethead View Post
Success!

On my 3rd attempt to flash the new firmware, I was successful.

For those following along at home:

MSI 785GM-E65 (AMD mobo) = fail
ASUS A8N5X (AMD mobo) = fail
HP Compaq nx9420 Laptop (Intel) = success

Thanks again Enterprise and Telnet!
7.
Quote:
Originally Posted by pastia View Post
Hello,

Many thanks for this great guide! I have just finished upgrading the firmware on my new Kingston SDD.

During the guide i have encountered a problem, and i did a search on your forum and found nothing about it.

PROBLEM:
After launching utility, i got an error related about STACKS and config.sys, just when the utility was about to detect my drive. (you can search google for "an internal stack overflow has caused" to read more about this problem)

SOLVE:
I downloaded the modded utility attached to the thread, i created a bootable USB drive using Windows98 sources that i found on the internet, guided by the same site you recommended (i copied the config.sys file manually on the disk - in this config.sys i had a "stacks = 9000" or so line). Finally i copied the flash utility, booted, and everything worked out fine!

Hope this helps, and that you did not already talk about this problem!
8.
Quote:
Originally Posted by BinaryDemon View Post
I finally got around to doing this. I was a little worried since my C: is an actual Intel 80gb X-25 G2 SSD that the hacked updater might get confused but everything worked fine.

Now my GAME SSD is rocking TRIM as well!


Good job guys.
9.
Quote:
Originally Posted by Marcy View Post
Hello,

I got a huge problem and hope you can help.

After changing the HPA size in HDAT2 V453 to make the restore work on my Gigabyte X48-DQ6 my Kingston is now recognized with just 5.67GB. I tried to set back the original 40GB setting and also to "restore" but I always get an aborted message.

The SSD is still working normal but just has 5,67GB. Would be great if you could me tell how I can reset my drive to get back the full capacity.

EDIT

I was able to restore and change the HPA settings of my Kingston on my sisters computer which has an ASUS mobo inside. HDAT2 doesn´t seem to work proper on Gigabyte boards.

Thanks, great job guys.
10.
Quote:
Originally Posted by donalddb View Post
Just for information, I was able to get HDAT2 to restore the factory default settings on my SSDNOW 40gb. CrystalDiskInfo confirmed that TRIM was enabled on the drive. Since I am currently running Windows XP SP2, I did the Intel Toolbox hack to use the optimize function. At first, the toolbox did not seem to work, but after I attempted to flash the SSD firmware with the patched Intel updater, the toolbox launched and I was able to perform a TRIM. The TRIM operation took only a few seconds, and HDTach confirmed full performance restored.

Note that the patched Intel Updater misidentified my WD Scorpio Blue 640gb laptop drive as an SSD (installed in my desktop along with 3 more sata hard drives), and did not find my Kingston SSDNOW. So, I am still running the original Kingston firmware, but TRIM appears to be fully enabled.

Nice job and thanks to Telnet and all who assisted.
11.
Quote:
Originally Posted by Hotdog Storm View Post
Signed up just to share my experience and thank Telnet and ENTERPRISE for putting all this together, you guys rock along with everybody else who did this before me to prove it works! I noticed this guide yesterday after reading Anand's latest SSD article where he links it directly (http://www.anandtech.com/storage/sho...spx?i=3747&p=7) and promptly dropped my work to read up. Don't tell my boss!

I'll start off by saying I have a Gigabyte GA-EP35-DS4 and was concerned by Marcy's report of HDAT2 mangling his drive on an X48-DQ6. I don't readily have access to anything else with SATA support so I chose to go the Live CD/hdparm route (as per Spacedust's instructions). Having never actually used Linux outside of an SSH connection into some game servers I can assure anybody that's comfortable with a terminal window that it's rather straightforward.

Before I did anything, I didn't want to lose my current Windows install so I backed up an image using Clonezilla. I'd recommend this, it's simple and quick and can save you a headache later if something goes wrong.

Then, using the HP Format utility I put the modified iSSDFUT.exe file on a USB drive. This was something I've done before for BIOS updates and was no problem, the directions in the OP are spot on along with the provided links. I unplugged all other hard drives in my system (leaving them connected confused the updater for some reason) and the firmware installed just fine even with AHCI enabled. Went back into Windows to make sure everything was still there and confirm the update, it installed "New hardware" and asked for a reboot so I knew things were looking up.

Next I booted off the CentOS 5.4 Live CD (had to use the i386 edition even though my computer is x64) and installed the newest hdparm as described. This is where I started to run into issues, but some tinkering eventually got it to go.

The first problem I ran across was that hdparm's -I and --dco-identify commands (to verify my controller was recognized and I had the correct drive) were failing with an I/O error. This was resolved by disabling AHCI and SATA Native Mode in my BIOS.

The next problem was that --dco-restore was failing with a similar error, which turned out to be the same HPA problem mentioned here. hdparm -N was telling me that the sectors were at 78122887 available out of 78125000 total, so I did hdparm -N78125000 to temporarily free them up and disable HPA. After this I was able to --dco-restore successfully. I tried --dco-identify once more to see if it would list DSM under SATA Feature Sets in addition to NCQ and SSP, but no dice; maybe a bug in hdparm? Rebooting my computer restored the previous HPA settings, -Np would make the change permanent but it's only 1MB and I didn't want to risk it.

I then changed everything in my BIOS back to how it should be for Windows, and it booted right up. The difference is insane and I made sure to run benches before and after to confirm the results and demonstrate the benefits.

Here's Crystal Disk Info before I did anything, then after updating the firmware, and finally after enabling TRIM:



Notice that my drive has had hundreds of gigs of writes, without TRIM it was getting pretty sad. I further confirmed TRIM support was enabled with the Intel SSD Toolbox at Word 169 Bit 0 which was now set to 1, as well as with fsutil which told me that DisableDeleteNotify was 0.

Here's Crystal Disk Mark and AS SSD Benchmark before any changes, and after running an Optimizer pass in the modified Intel SSD Toolbox (which took all of 30 seconds):





Look at the increases! Even degraded it was leagues ahead of a mechanical drive, but fixing it up regained my speeds as they were the day I bought it. All without losing any data.

I really don't know what to say, the information on this forum was invaluable. I knew someone would eventually come up with a way to enable TRIM on these drives after Kingston abandoned us and I'm thrilled it was sooner rather than later.

I hope what I've written helps other people to try this for themselves (I've already convinced a friend), it was a scary proposition for me but in the end turned out to be nothing but time well spent. Maybe if this workaround gets enough attention Intel will cave to allow a proper and tested-safe update.
12.
Quote:
Originally Posted by apinunw View Post
I can confirm that "pre-production firmware" error is MB problem. When I move to ASUS P4P800, everything is perfect.
13.
Quote:
Originally Posted by T-Rez View Post
I just signed up to say thanks for this guide. I have a Gigabyte mobo (p55-ud4p) and I could not restore by using HDAT 2.

I ended up following what spacedust and Hotdog Storm did through linux and it worked out just fine!

So once again thank you Telnet, ENTERPRISE, spacedust, and Hotdog Storm!!
14.
Quote:
Originally Posted by zrtom View Post
I, too, had to join to say "thank you" to everyone; this worked for me without a hitch. I now have 2CV102HD firmware and TRIM enabled.
I guess I can delete that email from Kingston saying the SNV125-S2/40GB will never support TRIM!

I'll list some details, in case it helps anyone:
I used my Dell M1330, set to IDE mode in the BIOS, for both operations. I've had good luck using the laptop for flashing the Vertex units I have; with only one drive for the flasher to contend-with, I think it makes things simpler. Other than that, I updated the Firmware first; that went smooth. Then I booted the HDAT2 iso and that went quickly and smoothly also.

So, thanks again.
Tom
15.
Quote:
Originally Posted by pocris View Post
Working great here! See attach!
Took me a while to build up the courage to do it!
Used the 3rd method with CD!
One of my old 80GB WD appeared also in the Issdfut as having Intel pre-release firmware. ) Just kept going.

AS SSD bench [last version] is giving me some errors I have no results from it. I tried to locate the same version as in the first post, but no luck.

Crystal Mark was run before and after running Intel SSD Tool for the first time. Note: My Kingston is rarely used since I am lazy enough not to install all the software on it [still using the old drive for OS]

Big THANKS!

Intel!
16.
Quote:
Originally Posted by BigWopHH View Post
For those of you having trouble with Gigabyte motherboards and HDAT2, where the system hangs when scanning for inth13 devices, simply add the /D=10 parameter to the command line and all should be well. /D=10 excludes the inth13 scan from the launch routine. Incidentally, you can exclude other scans as well--just run hdat2 /? to see the full list of options available.

I just flashed my Kingston drive and TRIM is working properly now.
17.
Quote:
Originally Posted by Beretta93 View Post
Thanks for your answers both of you guys. And thanks Telnet for your workof course.

Actually, I am not qualified to modify any firmware updater, even if I would love to. But since the original firmware of Kingston SDD is Intel's 02HA, returning it back to RMA with 02HD, with trim locked back thanks to HDAT2,should be ok shouldn't it?

So the way to remove the trim with HDAT2 would be with the DATA SET MANAGEMENT command?

(I am asking all of this because some people of france hardware forums are asking for some similar solution. So I think this information may be useful for others. )

I don't want to send it back to Kingston the way it is, for they may just tell me to stick it in my ass. That's why I think that if I just remove the trim, htey might just not notice that it's been modified...

Thank you guys.
Quote:
Originally Posted by Telnet View Post
You have to enter Device Configuration Overlay (DCO) Menu, then select Modify and then set DATA SET MANAGEMENT to disabled.
post #3 of 283
I am about to impulse buy this drive as we speak just because of this. How is the performance in the long run though?
My Build
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X4 965 Black Edition MSI 790FX-GD70 Sapphire Radeon HD 5870 4gb G.Skill 1600 
Hard DriveOSMonitorKeyboard
60gb OCZ agility// 1tb caviar black Windows 7 ultimate N 64 bit 3 23" Samsungs G15 
PowerCaseMouseMouse Pad
Corsair 850w Antec Twelve Hundred Logitech G9 Steel Series 
  hide details  
Reply
My Build
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X4 965 Black Edition MSI 790FX-GD70 Sapphire Radeon HD 5870 4gb G.Skill 1600 
Hard DriveOSMonitorKeyboard
60gb OCZ agility// 1tb caviar black Windows 7 ultimate N 64 bit 3 23" Samsungs G15 
PowerCaseMouseMouse Pad
Corsair 850w Antec Twelve Hundred Logitech G9 Steel Series 
  hide details  
Reply
post #4 of 283
Thread Starter 
Well I suggest you look at some benchmarks also. However this drive is AWESOME. Its a great performer and has the best 4K writes going so far. Which is what you want if you are going to make this an OS drive.
post #5 of 283
Thread Starter 
Updated and added a 3rd method of updating. Nice and easy.
post #6 of 283
Ik tried updating the firmware using your ISO burnt on a CD. It does start the iSSDFUT, but when searching for the disc it doesn't seem to find it. Can that be motherboard related? I have a msi 790gx-g65 motherboard set on ahci mode.
post #7 of 283
Quote:
Originally Posted by Thran View Post
I am about to impulse buy this drive as we speak just because of this. How is the performance in the long run though?
The drive is $130 + shipping atm don't impulse buy just yet. It was around $80 when everyone bought them up.
    
CPUMotherboardGraphicsRAM
2500k ASUS P8P67 WS Revolution 2 x Asus GTX470 900/1800/1700 Corsair Vengence 8gb 
Hard DriveOSMonitorPower
120gb ssd, 4 x 1TB F3's Raid 0, 2TB F4 Backup Windows 7 Catleap 27 1440p Enermax Revolution 1050w 
Case
Case Labs M8 with pedestal  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
2500k ASUS P8P67 WS Revolution 2 x Asus GTX470 900/1800/1700 Corsair Vengence 8gb 
Hard DriveOSMonitorPower
120gb ssd, 4 x 1TB F3's Raid 0, 2TB F4 Backup Windows 7 Catleap 27 1440p Enermax Revolution 1050w 
Case
Case Labs M8 with pedestal  
  hide details  
Reply
post #8 of 283
Telnet needs to post here so he can receive his well-deserved rep!


You might want to make it a point to mention the Kingston Boot V-Series is an Intel 40GB X25-V with different firmware.
Once again...
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 920 [4.28GHz, HT] Asus P6T + Broadcom NetXtreme II VisionTek HD5850 [900/1200] + Galaxy GT240 2x4GB G.Skill Ripjaw X [1632 MHz] 
Hard DriveOSMonitorKeyboard
Intel X25-M 160GB + 3xRAID0 500GB 7200.12 Window 7 Pro 64 Acer H243H + Samsung 226BW XARMOR-U9BL  
PowerCaseMouseMouse Pad
Antec Truepower New 750W Li Lian PC-V2100 [10x120mm fans] Logitech G9 X-Trac Pro 
  hide details  
Reply
Once again...
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 920 [4.28GHz, HT] Asus P6T + Broadcom NetXtreme II VisionTek HD5850 [900/1200] + Galaxy GT240 2x4GB G.Skill Ripjaw X [1632 MHz] 
Hard DriveOSMonitorKeyboard
Intel X25-M 160GB + 3xRAID0 500GB 7200.12 Window 7 Pro 64 Acer H243H + Samsung 226BW XARMOR-U9BL  
PowerCaseMouseMouse Pad
Antec Truepower New 750W Li Lian PC-V2100 [10x120mm fans] Logitech G9 X-Trac Pro 
  hide details  
Reply
post #9 of 283
Thread Starter 
Quote:
Originally Posted by DuckieHo View Post
Telnet needs to post here so he can receive his well-deserved rep!


You might want to make it a point to mention the Kingston Boot V-Series is an Intel 40GB X25-V with different firmware.
Thanks. I will do that. Yeah he should. I did advise Telnet of this guide.
post #10 of 283
I don't even have one of these but I think Telnet deserves a .....or 2!

Nice Job!
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel 920 Asus P6T + LSI 9240-4i SATA6GB/s card Nvidia 8800GTS Patroit Viper 6GB of D3-1600 
Hard DriveOptical DriveOSMonitor
Crucial C300 256GB Benq 1655 W7 Ultimate x64 NEC MultiSync LCD2470WNX 
KeyboardPowerCaseMouse
Logitech diNovo cordless Corsair 650HX Lian Li A10-B Logitech MX Revolution 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel 920 Asus P6T + LSI 9240-4i SATA6GB/s card Nvidia 8800GTS Patroit Viper 6GB of D3-1600 
Hard DriveOptical DriveOSMonitor
Crucial C300 256GB Benq 1655 W7 Ultimate x64 NEC MultiSync LCD2470WNX 
KeyboardPowerCaseMouse
Logitech diNovo cordless Corsair 650HX Lian Li A10-B Logitech MX Revolution 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: SSD
Overclock.net › Forums › Components › Hard Drives & Storage › SSD › How to get your Kingston 40GB SSD to support TRIM