Ext2fsd 0.50 is a professional, elegant and handy application which brings you an ext2 file system driver for windows (2k, xp, vista and win7). It’s a free software. Anyone can modify or distribute it under gpl2. Major features:Features ext2fsd supports:Ext2/ext3 volume reading & writingExt3 journal replay when mountingVarious codepage: utf8, cp936, cp950 …Mountpoint automatical assignmentLarge inode size: 128, 256, …Large file size bigger than 4gCifs sharing over networkHtree directory indexingExt4 extent read-only, no size truncating and expanding supportFast fsck (uninit_bg) and group block checksum support64k block-size, support compatible to linux ext4 and e2fsprogsOs: 2k, xp, vista, server 2003/2008, win7Features ext2fsd doesn’t support:Fully ext3 journal supportExt4 extent supportLvm and linux raid (md)Nt4 is no longer supported.Supported ext3/4 features :Flexible inode size: > 128 bytes, up to block sizeDir_index: htree directory indexFiletype: extra file mode in dentryLarge_file: > 4g files supportedSparse_super: super block backup in group descriptorUninit_bg: fast fsck and group checksumExtent: reading, writing with no extending.Journal: only support replay for internal journalUnsupported ext3/4 features:Journal: log-based operations, external journalExtent: size truncating & expanding, file deletionFlex_bg: first metadata groupEa (extended attributes), acl supportEnhancements:Ext4 extent readonly support by bo branten. Writing is possible but with no size-extendingExt3 directory index (hash-tree) supportFast fsck (uninit_bg) and group block checksum supportExt4 64k block size supportSymlink/special inodes open/read/deletion supportBuffer head implemented over cache pagesMemory allocation optimization for flexible-size inodesImprove file deletion: don't grab global lock when deletingFixme: return zero-content for sparse file gapsFixme: check available spaces before blocks allocationFixme: refresh stale root dir content after journal replayFixme: incompatible dentry management for 64k block sizeFixme: don't do journal replay for devices set as readonlyFixme: win7 cmd.exe always reports file sizes as zeroFixme: win7 memory throttling issue calling ccpinreadFixme: ext3fsd build issues (slist/div64 for win2k, browser files)Fixme: compiling test failure (fastio doesn't update i_size)Fixme: possible mcb memory leak for symbolic linksRequirements:Windows (2k/xp/vista/win7)