Very Computer

I happened to take a look at
ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/ and noticed
an nt40 folder that contains a hot-fix for the nt 4.0 kernel. I haven't
installed it yet but was wondering if anyone has used the hot-fix yet.

Thanks,
martin

DOCUMENT:Q78303  24-Sep-1996  [winnt]
TITLE   :Windows NT File Corruption Problem
PRODUCT :Microsoft Windows NT
PROD/VER:  4.00
OPER/SYS:WINDOWS
KEYWORDS:kbnetwork kbbug4.0

--------------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Windows NT Workstation version 4.0
 - Microsoft Windows NT Server version 4.0

--------------------------------------------------------------------------

SYMPTOMS
========

If files are rapidly accessed on a Windows NT File server,
intermittent data corruption may occur.   Microsoft Internet News
Server data files may exhibit these symptoms.   The problem is more
likely to be observed on a Multiprocessor system.

CAUSE
=====

If an application is performing a write-extend of a file, the cache
manager read ahead thread is also reading the current last page of the
file as part of a larger read.  The read ahead thread issues the read
and the write is blocked waiting for the read to complete.   Due to a
timing problem that may occur, the memory manager wakes the write
thread associated with the IO operation.  This thread will place null
characters in the last page which is beyond the current file size and
then write the new data into the page.  The read thread wakes up and
also zeroes the last page after the write thread has written the new
data.  The update to the page is lost and null characters are appended
in the file instead of the data which should have been committed for
the IO operation.

RESOLUTION
==========

Obtain the fix mentioned below or wait for the next Windows NT service
pack.

STATUS
======

Microsoft has confirmed this to be a problem in Windows NT version
4.0. A supported fix is now available, but has not been fully
regression-tested and should be applied only to systems experiencing
this specific problem. Unless you are severely impacted by this
specific problem, Microsoft recommends that you wait for the next
Service Pack that contains this fix. Contact Microsoft Product Support
Services for more information.

This hotfix has been posted to the following Internet location:

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotf...

Ed

c];^)

There was a not-so-final release of NT4 that, on the blue boot screen,
read like this:

blah blah blah.... (Build 1381)

and that was it...the REAL final version read like this:

blah blah blah... (Build 1381).

note the trailing period.  Apparently there was some kind of security
or kernel problem with the first release (of which only about 50 to
100 copies made it out--I got ahold of one!) which was quickly fixed.
I don't know if this hotfix also addresses other bugs, considering NT4
was pretty hastily put out and I've been experiencing pretty quirky
behavior lately.

My guess would be that it couldn't hurt to install thehotfix.  Worst
case the program doesn't fix anything and you feel much better anyway!
:)

Hope that helps!

Josh Anderson

SYMPTOMS
========

If files are rapidly accessed on a Windows NT File server, intermittent
data corruption may occur.   Microsoft Internet News Server data files
may exhibit these symptoms.   The problem is more likely to be observed
on a Multiprocessor system.

CAUSE
=====

If an application is performing a write-extend of a file, the cache
manager read ahead thread is also reading the current last page of the
file as part of a larger read.  The read ahead thread issues the read and
the write is blocked waiting for the read to complete.   Due to a timing
problem that may occur, the memory manager wakes the write thread
associated with the IO operation.  This thread will place null characters
in the last page which is beyond the current file size and then write the
new data into the page.  The read thread wakes up and also zeroes the
last page after the write thread has written the new data.  The update to
the page is lost and null characters are appended in the file instead of
the data which should have been committed for the IO operation.

RESOLUTION
==========

Obtain the fix mentioned below or wait for the next Windows NT service
pack.

STATUS
======

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A
supported fix is now available, but has not been fully regression-tested
and should be applied only to systems experiencing this specific problem.
Unless you are severely impacted by this specific problem, Microsoft
recommends that you wait for the next Service Pack that contains this
fix.

"If you don't know where you're going, any road will take you there"