1.32

[Astronauticus]

Hallo,

Das 1.32 Update ist verfügbar. Mehr weiß ich auch noch nicht.

[ja45]

Hier ist's offiziell klick

[Serdar]

Vielen Dank für den Link.

[Holsteiner]

Funktioniert auch mit der Toolbox.

mfg Holsteiner

[JAMIMAMU]

keine schlafende hunde wecken*g
--
tip top fw. bessere werte hatte ich noch nicht!

[Maeckes]

N'Abend,

wo genau bekommt man denn die "neue" Toolbox 2.33, denn mit der 2.31 geht es bei mir (noch) nicht.

Gruß Maeckes

[ja45]

wo genau bekommt man denn die "neue" Toolbox 2.33

http://www.ocztechnologyforum.de/for...t-zu-25nm-SSDs

[Meteorman]

Hallo

Geht das auch wieder mit der win7 reperatur cd?

meteorman

[Astronauticus]

Das mag ich jetzt gar nicht kommentieren.

Issues resolved since version 1.29

•Improved read disturb handling at the end of life of the NAND flash

•Corrected the SMART attribute range floor to be set to 1 for all attributes

•Reduced the time required to wake up from sleep & standby

•Fixed an issue that required the first non-data command after reset to be IDENTIFY

•Increased the number of bad blocks that can be handled, thus improving NAND flash end of life behavior

•Fixed ClearSMARTbehavior to match the description in the SRM

•Added Enhanced Security Erase methods supporting military erase protocols

•Fixed a rare condition that could cause the drive to reset and clear the data

•Fixed a condition in which a drive could hang if repeatedly rebooted without sufficient time to recover between cycles

•Updated flash configuration settings for Intel/Micron 25nm flash support

•Improved the SATA behavior with respect to the CONT signal in order to work around limitations with some hosts

•Reduced the drive boot time when it was shutdown using the STANDBY IMMEDIATE command

•Improved FW efficiency for performance improvements of up to 5%

•Fixed SMART Attribute 194 to correctly display negative numbers in the normalized data field

•Added the capability to force the drive into a “read only mode, via GPIO 14

•Enable 3K PE Cycle Micron 25nm MLC NAND firmware configurations

•Fixed an issue where an internal task could be scheduled during p-Fail handling and cause a panic

•Fixed an issue with read disturb handling for single-plane programmed flash devices

•Fixed the firmware to respond to a non-responsive die without panicking

•Updated DIAG FORMAT READ command response to return the active format values

•Modified Set Features to maintain the DMA mode selection when PIO is enabled

•Improved the process for creating the Root File system such that it will still function if low-numbered blocks are marked bad. Block 0 still must be good

•Fixed a panic condition by improving map handling & recycling

•Modified FW to return uncorrectable error when an internal data CRC error is detected instead of panicking

•Added an option to turn off all ATA security

•Modified the Diagnostic Unlock command to UNFREEZE the drive in order for the firmware update tool to function properly on systems that use the FREEZE state for extra protection

Known open issues:

•Extreme use of LBASetErrorappears to have a problem

•SMART command B0 occasionally returns incorrect status

•TRIM command response times are longer than desired

•Receipt of the Read Verify command does not change power mode to active

•Intermittent panic while testing Diagnostic API command

•Can’t write-same (SCT command) the whole drive

•Resetting SMART PHY event counters has no effect

•Time for windows format of RAID volume on PMC-Sierra maxRAIDBR5225-80 RAID HBA is longer than desired

•Drive may fail to boot within 5 seconds with continuous rapid power cycles

•Compatibility issue with LSI SAS-to-SATA interposer when used with LSI 1078

•Drive hangs on Write Long with illegal command parameter

•Compatibility issue during Red Hat 5.4 Linux boot on nVidiaMCP55 chipset

•Sleep followed by non-data commands can sometimes cause the drive to fail to respond to the non-data command

•Under benchmarking scenarios with IOMETER 2006, 60GB drives that use Hynix32nm MLC (1024 blocks, 8KB pages) can impose long latencies

•In very rare situations, after boot up from an unsafe power cycle (not sleep or standby immediate),the drive may lose some of the last written data to the drive and return some previously valid data instead

•ATA Power states are not properly placing the drive into the low power state in Iddle, Standby, and Sleep causing higher than expected power consumption

[NicoOCZ]

Ja, das ist die vielfach besprochene FW, die die "Energiesparprobleme" lösen soll. Meine Vertex2 und -LE lassen sich damit problemlos "hibernaten"