This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages) (Learn how and when to remove this message)
|
Enhanced Write Filter (orEWF) is a component ofWindows XP Embedded andWindows Embedded Standard 7 which storesvolume changes on another medium instead of applying them to the original volume. Later it was renamed toUnified Write Filter (orUWF).[1] EWF allows the writes to be discarded or committed to the original volume later (either directly or through inaction based on the configuration). As this minimizes writes to a specified hard disk, EWF and FBWF (File-Based Write Filter)[2] have become popular inenthusiast computing as a way of decreasing wear ofsolid-state drives onnetbooks andCarPCs.
EWF has three main operating modes:EWF Disk,EWF RAM, andEWF RAM Reg. In each mode, the location of the EWF volume (which stores the configuration) and the overlay volume (which stores file changes) is different.EWF Disk stores the overlay data outside the primary disk, allowing an external disk such as aCompactFlash to be used as an overlay. The EWF volume is stored in anunpartitioned space on the disk.EWF RAMstores the overlay data in theRAM and the EWF volume in an unpartitioned space on the disk.EWF RAM Regis same as EWF RAM except the EWF volume is stored inWindows Registry.
As is the case with the appropriation of EWF in CarPCs, which are more often based on Windows XP because of its smaller "footprint," it has been used with similar effect in Windows Vista NetBooks to diminish write activity to, and so enhance the lifespan ofsolid-state drives (SSD). Due to changes in Windows Vista, however, the Disk Mode can not be used.
Unlike most commercialRAM disks, EWF cannot reclaim the RAM after files have been deleted from it. In EWF RAM (and EWF RAM Reg) mode, the memory consumed only ever increases. Eventually the system will have no more free space and will crash.[3]
Automatic adjustment of daylight saving time is not compatible with EWF, causing incorrect time settings at each reboot.[4]