SFM Time and Date Stamp Change Copying Between Volumes Locally
This article was previously published under Q170965 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. RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 (http://support.microsoft.com/kb/152734/EN-US/) How to Obtain the Latest Windows NT 4.0 Service Pack
For your convenience, the English version of this post-SP3 hotfix has been posted to the following Internet location. However, Microsoft recommends that you install Windows NT 4.0 Service Pack 4 to correct this problem. ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40
/hotfixes-postSP3/sfm-fix/ (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.
STATUSMicrosoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4. MORE INFORMATION
For more information, please see the following articles in the Microsoft
Knowledge Base:
166571 (http://support.microsoft.com/kb/166571/EN-US/) Creating an SFM Volume on Large Partition Causes a Stop 0x24
172511 (http://support.microsoft.com/kb/172511/EN-US/) Stop 0x0000000A w/ Services for Macintosh & McAfee Anti-Virus 177644 (http://support.microsoft.com/kb/177644/EN-US/) Commenting Macintosh File Changes Date and Time Stamp 178364 (http://support.microsoft.com/kb/178364/EN-US/) Macintosh Clients See Files on WinNT Server Constantly Moving 180622 (http://support.microsoft.com/kb/180622/EN-US/) STOP:0x0000001E with STATUS_INSUFFICIENT_RESOURCES in Sfmsrv.sys 180716 (http://support.microsoft.com/kb/180716/EN-US/) SFM Fails to Accept Associations with Two-Character Extensions 180717 (http://support.microsoft.com/kb/180717/EN-US/) SFM: File Date and Time Stamp Change with Get Info 180718 (http://support.microsoft.com/kb/180718/EN-US/) SFM: Disconnect Macintosh Clients before Dismounting Volume 185722 (http://support.microsoft.com/kb/185722/EN-US/) SFM Rebuilds Indexes upon Restarting of Windows NT APPLIES TO
| Article Translations
|

Back to the top
