DOCUMENT:Q143472 13-FEB-1999 [winnt] TITLE :FPNW Blue Screens Accessing or Creating Folders with Long Paths PRODUCT :Microsoft Windows NT PROD/VER:3.51 4.0 OPER/SYS: KEYWORDS:kbnetworkkbbuglist kbfixlist ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft File and Print Services for NetWare versions 3.51, 4.0 ------------------------------------------------------------------------------- SYMPTOMS ======== If your network client uses Novell's MS-DOS real-mode redirector, NETX, you may experience one of the following problems: - When you attempt to create a directory where the total path length is greater than 255 characters on a FPNW server, you may experience a blue screen error. - When you attempt to access a directory where the total path length is greater than 128 characters on a FPNW server, FPNW becomes unstable and a blue screen error normally occurs during the shut down of FPNW. CAUSE ===== You experience a blue screen error when you attempt to create a folder with a path greater than 255 characters because FPNW does not perform limit checking on the path length when the request is made. This problem only affects NETX clients because all other Novell NetWare clients perform limit checking before they submit the request to the server. You experience a blue screen error when you attempt to access a folder with a path greater than 128 characters due to problems converting the folder path string to Unicode within the FPNW server. This only affects NETX clients because all other Novell NetWare clients' use different NCP's (Network Control Protocol) which do not experience this problem when they submit a change directory request. RESOLUTION ========== Perform one of the following steps to resolve these problems: - Obtain the hotfix mentioned below. - Use a Novell's VLM client on MS-DOS-based computers instead of NETX. - Do not create folders with paths greater than 128 characters. STATUS ====== Microsoft has confirmed this to be a problem in Windows NT 3.51 and 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the Following word in the Microsoft Knowledge Base (without the spaces): S E R V P A C K Additional query words: prodnt 4.00 csnw ====================================================================== Keywords : kbnetwork kbbuglist kbfixlist Technology : kbServicesNetwareSearch kbFPNW351 kbFPNW400 Version : 3.51 4.0 Issue type : kbbug ============================================================================= 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. Copyright Microsoft Corporation 1999.