DOCUMENT:Q170965
TITLE   :SFM Time and Date Stamp Change Copying Between Volumes Locally
PRODUCT :Microsoft Windows NT
PROD/VER:4.00
OPER/SYS:WINDOWS
KEYWORDS:kbbug4.00 kbfix4.00 kbfile
---------------------------------------------------------------------------
The information in this article applies to:

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

SYMPTOMS
========

When copying folders and files from one volume to another volume using a
Macintosh, the time and date stamps of the folder and files will change to
the date and time of the copy. This should not occur when doing a copy as
the data of the file has not changed.

This problem does not occur when copying files from Macintosh-accessible
volumes over the network. The problem only occurs when copying files and
folders on volumes residing on the same server.

CAUSE
=====

The problem was caused by Services for Macintosh (SFM) having multiple data
streams open on a file. Each stream has its own last modified time, and SFM
had only changed one of the stream times. Because NTFS stores a last
modified time on a per-file basis, not per-stream basis, the time that was
written to the file was not always the one that SFM had set.

This has been addressed by closing all of the data streams except one, and
then setting the time on that one stream, resulting in the time and date
being set to the last modified time, which will be the same as the original
file being copied from.

RESOLUTION
==========

To resolve this problem, contact Microsoft Technical Support to obtain the
following fix, or wait for the next Windows NT service pack.

This fix should have the following time stamp:

   02/03/98  02:10p               130,352 Sfmsrv.sys (Intel)
   02/03/98  03:07p               234,064 Sfmsrv.sys (Alpha)

This hotfix has been posted to the following Internet location:

   ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/
   hotfixes-postSP3/sfm-fix/

NOTE: The above link is one path; it has been wrapped for readability.

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 Technical Support for more information.

MORE INFORMATION
================

For more information, please see the following articles in the Microsoft
Knowledge Base:

   ARTICLE-ID: Q166571
   TITLE     : Creating an SFM Volume on Large Partition Causes a Stop 0x24

   ARTICLE-ID: Q172511
   TITLE     : Stop 0x0000000A w/ Services for Macintosh & McAfee Anti-
               Virus

   ARTICLE-ID: Q177644
   TITLE     : Commenting Macintosh File Changes Date and Time Stamp

   ARTICLE-ID: Q178364
   TITLE     : Macintosh Clients See Files on WinNT Server Constantly
               Moving

   ARTICLE-ID: Q180622
   TITLE     : STOP:0x0000001E with STATUS_INSUFFICIENT_RESOURCES in
               Sfmsrv.sys

   ARTICLE-ID: Q180716
   TITLE     : SFM Fails to Accept Associations with Two-Character
               Extensions

   ARTICLE-ID: Q180717
   TITLE     : SFM: File Date and Time Stamp Change with Get Info

   ARTICLE-ID: Q180718
   TITLE     : SFM: Disconnect Macintosh Clients before Dismounting Volume

   ARTICLE-ID: Q185722
   TITLE     : SFM Rebuilds Indexes upon Restarting of Windows NT

Additional query words: 4.00 macfile mac
============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.