Problem Renaming Files on a UNIX-based DEC Pathworks Server

 Last reviewed: January 28, 1998
Article ID: Q178271
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SUMMARY

You cannot rename a file that is located on version 6.1 or earlier of a UNIX-based DEC Pathworks server to a name that has more characters than the current file name.

MORE INFORMATION

This behavior is only seen under the following conditions:

  • The files are located on a UNIX-based DEC Pathworks server, version 6.1 or earlier.
  • The client exhibiting the behavior is a computer running Windows NT 4.0 Server or Workstation, any service pack level.
  • The client is using Windows NT Explorer to rename the file.
  • The client has a drive letter mapped to the Pathworks server.

Under the above conditions, the file rename will not allow you to extend the name of the file. If attempted at an MS-DOS prompt, or through Windows NT Explorer by means of a UNC connection, you can rename the file normally as expected.

The reason for this behavior is that the Pathworks server reports its maximum allowed file name length incorrectly.

The third-party product discussed here is manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this products' performance or reliability. 

Keywords          : NTSrvWkst
Version           : WinNT:4.0
Platform          : winnt
Issue type        : kbinfo

================================================================================

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: January 28, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.