updated inf file and documentation

Ext4Fsd/Ext2Fsd.inf

@@ -16,14 +16,7 @@ InfVersion  = "01.03.00"
 Provider    = %Ext2Fsd*Author%
 Signature   = "$Windows NT$"
 DriverVer   = 03/04/2020,0.70
-CatalogFile = Ext4Fsd.cat
+CatalogFile = Ext2Fsd.cat
-
-;[ClassInstall32]
-;AddReg     = Ext2Fsd.Install.ClassReg
-
-;[Ext2Fsd.Install.ClassReg]
-;HKR,,,%REG_SZ%,"%Ext2Fsd*Class%"
-;HKR,,"Icon",%REG_SZ%,"-5"
 
 [DefaultInstall.NTx86]
 AddReg     = Ext2Fsd.Install.AddReg
@@ -125,7 +118,7 @@ HKR,,"TypesSupported",%REG_DWORD%,7
 [SourceDisksFiles]
 ; <filename> = <disk or cabinet number>,[<subdirectory>],[<filename>],[<size>],[<checksum>]
 ; Note: <filename> is neither on a disk nor in a cabinet if <disk or ;cabinet number> is 0
-Ext4Fsd.sys   = 1, "."
+Ext2Fsd.sys   = 1, "."
 
 [DestinationDirs]
 Ext2Fsd.CopyFiles.Drv.NTx86 = 12   ; %SystemRoot%\System32\Drivers
@@ -138,28 +131,28 @@ Ext2Fsd.CopyFiles.Drv.NTarm64 = 12   ; %SystemRoot%\System32\Drivers
 Ext2Fsd.DeleteFiles.Drv.NTarm64 = 12   ; %SystemRoot%\System32\Drivers
 
 [Ext2Fsd.CopyFiles.Drv.NTx86]
-Ext4Fsd.sys,,,%COPYFLG_NOPRUNE%
+Ext2Fsd.sys,,,%COPYFLG_NOPRUNE%
 
 [Ext2Fsd.DeleteFiles.Drv.NTx86]
-Ext4Fsd.sys,,,%DELFLG_IN_USE%
+Ext2Fsd.sys,,,%DELFLG_IN_USE%
 
 [Ext2Fsd.CopyFiles.Drv.NTamd64]
-Ext4Fsd.sys,,,%COPYFLG_NOPRUNE%
+Ext2Fsd.sys,,,%COPYFLG_NOPRUNE%
 
 [Ext2Fsd.DeleteFiles.Drv.NTamd64]
-Ext4Fsd.sys,,,%DELFLG_IN_USE%
+Ext2Fsd.sys,,,%DELFLG_IN_USE%
 
 [Ext2Fsd.CopyFiles.Drv.NTarm]
-Ext4Fsd.sys,,,%COPYFLG_NOPRUNE%
+Ext2Fsd.sys,,,%COPYFLG_NOPRUNE%
 
 [Ext2Fsd.DeleteFiles.Drv.NTarm]
-Ext4Fsd.sys,,,%DELFLG_IN_USE%
+Ext2Fsd.sys,,,%DELFLG_IN_USE%
 
 [Ext2Fsd.CopyFiles.Drv.NTarm64]
-Ext4Fsd.sys,,,%COPYFLG_NOPRUNE%
+Ext2Fsd.sys,,,%COPYFLG_NOPRUNE%
 
 [Ext2Fsd.DeleteFiles.Drv.NTarm64]
-Ext4Fsd.sys,,,%DELFLG_IN_USE%
+Ext2Fsd.sys,,,%DELFLG_IN_USE%
 
 [Strings]
 Ext2Fsd*Author      = "Matt Wu"

Ext4Fsd/Ext4Fsd.vcxproj

@@ -121,49 +121,57 @@
     <DebuggerFlavor>DbgengKernelDebugger</DebuggerFlavor>
     <OutDir>$(SolutionDir)Ext4Fsd\$(ConfigurationName)\x86\</OutDir>
     <IntDir>$(ConfigurationName)\x86\</IntDir>
-    <TargetName>Ext4Fsd</TargetName>
+    <TargetName>Ext2Fsd</TargetName>
+    <Inf2CatUseLocalTime>true</Inf2CatUseLocalTime>
   </PropertyGroup>
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
     <DebuggerFlavor>DbgengKernelDebugger</DebuggerFlavor>
     <OutDir>$(SolutionDir)Ext4Fsd\$(ConfigurationName)\x86\</OutDir>
     <IntDir>$(ConfigurationName)\x86\</IntDir>
-    <TargetName>Ext4Fsd</TargetName>
+    <TargetName>Ext2Fsd</TargetName>
+    <Inf2CatUseLocalTime>true</Inf2CatUseLocalTime>
   </PropertyGroup>
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
     <DebuggerFlavor>DbgengKernelDebugger</DebuggerFlavor>
     <OutDir>$(SolutionDir)Ext4Fsd\$(ConfigurationName)\x64\</OutDir>
     <IntDir>$(ConfigurationName)\x64\</IntDir>
-    <TargetName>Ext4Fsd</TargetName>
+    <TargetName>Ext2Fsd</TargetName>
+    <Inf2CatUseLocalTime>true</Inf2CatUseLocalTime>
   </PropertyGroup>
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
     <DebuggerFlavor>DbgengKernelDebugger</DebuggerFlavor>
     <OutDir>$(SolutionDir)Ext4Fsd\$(ConfigurationName)\x64\</OutDir>
     <IntDir>$(ConfigurationName)\x64\</IntDir>
-    <TargetName>Ext4Fsd</TargetName>
+    <TargetName>Ext2Fsd</TargetName>
+    <Inf2CatUseLocalTime>true</Inf2CatUseLocalTime>
   </PropertyGroup>
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|ARM'">
     <DebuggerFlavor>DbgengKernelDebugger</DebuggerFlavor>
     <OutDir>$(SolutionDir)Ext4Fsd\$(ConfigurationName)\arm\</OutDir>
     <IntDir>$(ConfigurationName)\arm\</IntDir>
-    <TargetName>Ext4Fsd</TargetName>
+    <TargetName>Ext2Fsd</TargetName>
+    <Inf2CatUseLocalTime>true</Inf2CatUseLocalTime>
   </PropertyGroup>
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|ARM'">
     <DebuggerFlavor>DbgengKernelDebugger</DebuggerFlavor>
     <OutDir>$(SolutionDir)Ext4Fsd\$(ConfigurationName)\arm\</OutDir>
     <IntDir>$(ConfigurationName)\arm\</IntDir>
-    <TargetName>Ext4Fsd</TargetName>
+    <TargetName>Ext2Fsd</TargetName>
+    <Inf2CatUseLocalTime>true</Inf2CatUseLocalTime>
   </PropertyGroup>
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|ARM64'">
     <DebuggerFlavor>DbgengKernelDebugger</DebuggerFlavor>
     <OutDir>$(SolutionDir)Ext4Fsd\$(ConfigurationName)\arm64\</OutDir>
     <IntDir>$(ConfigurationName)\arm64\</IntDir>
-    <TargetName>Ext4Fsd</TargetName>
+    <TargetName>Ext2Fsd</TargetName>
+    <Inf2CatUseLocalTime>true</Inf2CatUseLocalTime>
   </PropertyGroup>
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|ARM64'">
     <DebuggerFlavor>DbgengKernelDebugger</DebuggerFlavor>
     <OutDir>$(SolutionDir)Ext4Fsd\$(ConfigurationName)\arm64\</OutDir>
     <IntDir>$(ConfigurationName)\arm64\</IntDir>
-    <TargetName>Ext4Fsd</TargetName>
+    <TargetName>Ext2Fsd</TargetName>
+    <Inf2CatUseLocalTime>true</Inf2CatUseLocalTime>
   </PropertyGroup>
   <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">
     <ClCompile>
@@ -335,6 +343,9 @@
   <ItemGroup>
     <ResourceCompile Include="Ext4Fsd.rc" />
   </ItemGroup>
+  <ItemGroup>
+    <Inf Include="Ext2Fsd.inf" />
+  </ItemGroup>
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
   <ImportGroup Label="ExtensionTargets">
   </ImportGroup>

Ext4Fsd/Ext4Fsd.vcxproj.filters

@@ -291,4 +291,9 @@
       <Filter>Resource Files</Filter>
     </ResourceCompile>
   </ItemGroup>
+  <ItemGroup>
+    <Inf Include="Ext2Fsd.inf">
+      <Filter>Driver Files</Filter>
+    </Inf>
+  </ItemGroup>
 </Project>

Ext4Fsd/FAQ.txt

@@ -3,7 +3,7 @@
 ================
 
 -------------------------------------------------------------------------
-Q) What systems could Ext2Fsd 0.51 support
+Q) What systems could Ext2Fsd 0.53 support
 
 A) Windows 2000, xp, 2003, Vista, Win7 (X86, AMD64)
    Windows NT 4.0 is no longer supported.
@@ -12,9 +12,9 @@ A) Windows 2000, xp, 2003, Vista, Win7 (X86, AMD64)
    Win7 AMD64/X86, Vista AMD64, XP pro X86, Win2k SP4
 
 -------------------------------------------------------------------------
-Q) How to install ext2fsd version 0.51
+Q) How to install ext2fsd version 0.53
 
-A) Just click the file of ext2fsd-0.51.exe. It will guide you for all.
+A) Just click the file of ext2fsd-0.53.exe. It will guide you for all.
    and writing on ext3 partition:
 
    Senior users can try the setup.bat or registry manually editing.
@@ -167,10 +167,9 @@ A) Add a parameter "/quiet" in command when executing Ext2Mgr, like
 -------------------------------------------------------------------------
 Q) How to build Ext2Fsd package ?
 
-A) You need Winddk (sold by Microsoft) and use the gnu ntifs.h header file.
+A) You need downlaod WDK (provided by Microsoft), then select a build
-   But you have the ifskit if you want building for X86_64 systems. Then
+   environment (such as Win7 X64 free), then execute "build" under
-   you just select a build environment (such as windows 2003 free), and
+   the root directory of Ext3Fsd source code.
-   then execute "build" under the root directory of Ext2Fsd source code.
 
 
 Matt <mattwu@163.com>

Ext4Fsd/notes.txt

@@ -1,43 +1,43 @@
-==================================
+==================================
-Release Notes for Ext2Fsd V0.69
+Release Notes for Ext2Fsd V0.69
-==================================
+==================================
-
+
-Features implemented or bugfix:
+Features implemented or bugfix:
-
+
-    1, FIXME: superblock corruption of EXT4 volumes with 64BIT mode enabled
+    1, FIXME: superblock corruption of EXT4 volumes with 64BIT mode enabled
-    2, FIXME: possible corruption by race conditions in buffer-head reapering
+    2, FIXME: possible corruption by race conditions in buffer-head reapering
-    3, FIXME: possible deadlock issues (when flushing) caused by BCB locks
+    3, FIXME: possible deadlock issues (when flushing) caused by BCB locks
-    4, FIXME: miscellaneous minor updates of Ext2Fsd code base
+    4, FIXME: miscellaneous minor updates of Ext2Fsd code base
-
+
-Supported Ext3/4 features:
+Supported Ext3/4 features:
-
+
-    1, flexible inode size: > 128 bytes, up to block size
+    1, flexible inode size: > 128 bytes, up to block size
-    2, dir_index:    htree directory index
+    2, dir_index:    htree directory index
-    3, filetype:     extra file mode in dentry
+    3, filetype:     extra file mode in dentry
-    4, large_file:   > 4G files supported
+    4, large_file:   > 4G files supported
-    5, sparse_super: super block backup in group descriptor
+    5, sparse_super: super block backup in group descriptor
-    6, uninit_bg:    fast fsck and group checksum
+    6, uninit_bg:    fast fsck and group checksum
-    7, extent:       full support with extending and shrinking.
+    7, extent:       full support with extending and shrinking.
-    8, journal:      only support replay for internal journal
+    8, journal:      only support replay for internal journal
-    9, flex_bg:      first flexible metadata group
+    9, flex_bg:      first flexible metadata group
-   10, symlink and hardlink
+   10, symlink and hardlink
-
+
-Unsupported Ext3/4 features:
+Unsupported Ext3/4 features:
-
+
-    1, 64BIT mode (to support 2^64 blocks)
+    1, 64BIT mode (to support 2^64 blocks)
-    2, journal: log-based operations, external journal
+    2, journal: log-based operations, external journal
-    3, EA (extended attributes), ACL support
+    3, EA (extended attributes), ACL support
-
+
-Features to be implemented in next release:
+Features to be implemented in next release:
-    1, Extents management improvement
+    1, Extents management improvement
-    2, EA and ACL security checking (WIP)
+    2, EA and ACL security checking (WIP)
-
+
-WARNINGS:
+WARNINGS:
- 
+ 
-    The driver may crash your system and ruin your data unexpectedly,
+    The driver may crash your system and ruin your data unexpectedly,
-    since there might be software conflicts and I could only test it
+    since there might be software conflicts and I could only test it
-    on some of the popular platforms. You should use it with care and
+    on some of the popular platforms. You should use it with care and
-    use it at your own risk!
+    use it at your own risk!
-
+
-Matt <mattwu@163.com>
+Matt <mattwu@163.com>
-http://www.ext2fsd.com
+http://www.ext2fsd.com