Ext2Fsd is an open source Linux ext2/ext3 file system driver for Windows systems (2K/XP/VISTA/WIN7/WIN8, X86/AMD64).
- htree index
Great savior tool!
Great software!!! It works perfectlty!!!
Love the humor: Mounted an OEM partition (backup partition) which was formatted as EXT2 (quite an old PC, late 2006, but only recently I've actually made a system backup using the OEM backup software), mounted it as readonly, then attempted to create a folder. The error message was a funny one: 0x8000FFFF (user mode error 65535): Catastrophic failure OK, leaving that aside, it is an useful program (being the only one of its kind that doesn't BSOD my Windows 8.1 and forces me to get to safe mode and forcibly remove it, since the ADD/REMOVE PROGRAMS one doesn't worn in safe mode :) Does it support EXT4? (even read-only, 'cuz I know how hard it is support EXT4 in Windows, just like NTFS in Linux or OSX :) ) I think it does, though I didn't actually try it. I made sure I mounted it as read-only, to avoid crippling my now-only backup of Windows -- if I break it, I'm practically screwed! 4 points for ease, since it's not very complicated but it's still not a granny-program -- but is it supposed to be? 4 points for features, due to lacking support for journaling (which makes some ext3 file systems unwritable -- nasty) 3 points for design: It couldn't blend into all versions of Windows anyway, the interface looks a bit "classic" to me but this is just user preference. 3 points for support -- default score. And a reply for electricprism's lowest rated review: Ext4 recognized as ext3 is actually a common thing in the Linux world itself, plus you might have had an older version that didn't (directly) support ext4 (ext4 without extents and journaling is simply ext3 with a new name, really, so read-only support was available before actual direct support) The BSOD might be a real issue back then (has it been fixed? hint: that large partition is more than 2^32 sectors, so don't mount filesystems that only work with 32-bit sector pointers and also do checkings -- doing some things in user space is a perfect way to avoid BSODs from ever occuring -- if the service crashes, then restart it and redo the mounting; you can also do separate daemons for each mount and unmount any filesystem that crashed -- that's a suggestion for special cases; in my case I've got none of these problems :) )