My computer system (Is important for the performance improvement of the system after the conversion, the maximum speed of the SSD will also depend of course heavily on the performance of the rest of the PC's off.): RAM currently: 12 GB with Windows Experience Index 7.5; Processor 7.4; Windows 7 Pro (64 bit), dual boot with Linux / Ubuntu on a separate hard drive. The SSD I have acquired, in order to make for the 6Gb / s performance area, the 10-year warranty and the reasonable price and 'last but not least' my fast PC even faster. The claim made by some critics that the Kopiieren / clones of the old C: drive is on the SSD with a SATA to USB Adapter possible only applies in the case that only 1 SATA connector is present (eg Notebook). The enclosed CD V.4.5 Samsung has queried after starting these two possibilities. To ensure that the clone operation works, I have my old hard drive C: treated Disk Cleanup, Disk Defragmenter, and a very good debugger with Windows programs and the AHCI mode enabled. The SSD I have installed on 3 positions for cloning. All hard disks were connected to the simplicity at first to the board's SATA II controller. Since the clone program also wanted additional clone Linux disk in the SSD into it, I have this disabled. Then the Clone operation was performed without error, the hard drives were then reconnected in order SSD, Linux disk and old drive C: (this safety still in its original state, should later serve as a Windows data storage). Computer rebooted, Windows came very quickly (after the announcement of "loading Windows" in less alls 10 s). The dual-boot menu was gone and damt no access to Ubunzu longer possible. I then to backup the boot loader of SSD and old Drive C :, the boot loader of the SSD with the old disk C: eye exchanges. Everything was fine when you reboot. Dual boot went back. My review has, however, revealed that the bootloader altte the C: drive has alls selected boot disk because the boot loader nor the old disk identifiers were included. So hung Linux disk and rebooted. Then the computer is "suspended", the reason was that in this bootloader, the old 20-digit hard disk IDs were listed. Well I had 7 CD Repair to hand a one Windows. With it I was able to repair the boot area again, but only for Windows, not for dual boot. For this purpose, a remark: With the boat programs BCDedit and EasyBCD that disk identifiers can not change, unfortunately. The problem for the dual boot I have therefore firstonce returned to it later to discuss with the relevant forums.
Here the performance results (according to Samsung program) for the SSD drive, even without SATA III controller (see my review on the Assmann DS-30104-1 Digitus PCI Express Card, 4-pin, SATA III) and activated with Rapid MOde : Sequential Read 2801 MB / s, sequential write 507 MB / s, Direct reading 79348 / OPS, Direct writing 67483 / OPS Windows Experience Index 7.8 The performance data after installation of Digitus card see my Digitus review. There you can also be seen what the purchase of this brings SATA III controller performance standard.
Resumé: The SSD is very fast and after connection to the Digitus SATA III controllers and other Optimierungsmaßnahnen a little faster (See Digtus-review). The current dual-boot failure can not be blamed on the SSD. Therefore 5 stars. Samsung should point out that problems in dual boot systems are to be expected in its user manual but. A proposed solution, as they have to be eliminated would be most welcome.
