DIR and File Manager Show SFM Files with Wrong Size

Last reviewed: April 4, 1997
Article ID: Q112402

The information in this article applies to:
  • Microsoft Windows NT Advanced Server version 3.1
  • Microsoft Windows NT Server versions 3.5 and 3.51
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

The wrong file size will be displayed when you view a Macintosh System executable or font file on a Services For Macintosh (SFM) volume on a Windows NT Server computer.

This problem will occur in all versions of Windows NT when you use DIR from the command prompt or in File Manager. This will also occur when viewing a Macintosh executable file with Windows NT 4.0 Explorer. A Macintosh client shows the correct file size.

CAUSE

CAUSE

Macintosh files have both a Data Fork and a Resource Fork. Windows NT gets the file size info from the Data Fork. If no information is available in the Data Fork, the file size displayed is zero. Both Macintosh executable files and font files have 0 bytes listed in the Data Fork, so their size is displayed as 0 bytes.

STATUS

Microsoft has confirmed this to be a problem in Windows NT Server versions 3.1, 3.5, 3.51 and 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: prodnt Mac zero exe sfm
Keywords : kbbug3.10 kbinterop ntmac NTSrv
Version : 3.1 3.5 3.51 4.0
Platform : WINDOWS


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.

Last reviewed: April 4, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.