From 00bc325219e9035b8f90b4e50c152314b89b8306 Mon Sep 17 00:00:00 2001
From: short <>
Date: Thu, 2 Oct 2003 14:29:36 +0000
Subject: [PATCH] +TraceFS known bugs

---
 project/captive/doc/Index.html.pl | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/project/captive/doc/Index.html.pl b/project/captive/doc/Index.html.pl
index acac424..40adf0c 100755
--- a/project/captive/doc/Index.html.pl
+++ b/project/captive/doc/Index.html.pl
@@ -1185,7 +1185,7 @@ print <<"HERE";
 		postpones Pin mapping destroy to later time but it does not matter.</p>
 
 
-		<h3>TraceFS NT Cache Manager Tracer</h3>
+		<a name="TraceFS"><h3>TraceFS NT Cache Manager Tracer</h3></a>
 
 			<p>@{[ a_href '#cache_manager','Cache Manager behaviour' ]} would be hard
 			to analyze just by @{[ a_href '#reverse','reverse engineering' ]} as it
@@ -1228,6 +1228,17 @@ print <<"HERE";
 			Any seen incompatibilies will be reported &mdash; your target is to reach
 			as few error messages as possible.</p>
 
+			<p>KNOWN BUGS: Combination of message synchronization primitives and
+			implemented refusal to create journalling thread of
+			<span class="fname">ntfs.sys</span>
+			causes fatal system lockup in several advanced operations
+			such as setting compression attribute. Despite it more common operations
+			can be successfuly traced during the whole
+			<span class="productname">Microsoft Windows</span>
+			session including its final shutdown and such traces provide enough
+			material to be food to
+			@{[ captive_srcfile './src/TraceFS/checktrace.pl' ]} Perl Cache Manager
+			validator.</p>
 
 			<h4>TraceFS for general API tracing</h4>
 
-- 
1.8.3.1