the other goals of its W32 counterpart are left to be successfuly handled
by UNIX OS in much more efficient way.</p>
- @{[ doc_img 'dia/cache-manager',
+ @{[ doc_img 'dia/cache-manager.dia',
'<span class="productname">NT Cache Manager</span> Architecture' ]}
<p>Cache Manager objects are always bound to
subsystems. It was chosen as easier way to trace it instead and validate
all the Cache Manager assumptions by Cache Manager simulator.</p>
- @{[ doc_img 'dia/TraceFS','TraceFS Hooking' ]}
+ @{[ doc_img 'dia/TraceFS.dia','TraceFS Hooking' ]}
<p>You must prepare your driver to be hooked
(<span class="fname">ntfs.sys</span> in this case):</p>
from <span class="productname">WinDbg</span> by
@{[ a_href 'Reverse.pm#WinDbg','W32 remote kernel debugging' ]}:</p>
- @{[ doc_img 'ntdebug-windbg-boot','Successfuly connected <span class="productname">WinDbg</span>' ]}
+ @{[ doc_img 'ntdebug-windbg-boot.png','Successfuly connected <span class="productname">WinDbg</span>' ]}
<p>The resulting trace file should be processed by
@{[ captive_srcfile './src/TraceFS/checktrace.pl' ]} Perl Cache Manager