How to Format Directory Output with FTP Server

Last reviewed: May 8, 1997
Article ID: Q103075

The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

WARNING: Using Registry Editor incorrectly can cause

    serious, system-wide problems that may require you to
    reinstall Windows NT to correct them. Microsoft cannot
    guarantee that any problems resulting from the use of
    Registry Editor can be solved. Use this tool at your own
    risk.

Some File Transfer Protocol (FTP) client software makes assumptions based on the formatting of directory list information. The Windows NT FTP server provides some flexibility for client software that requires directory formatting similar to UNIX systems.

To set the default for the format of directory listings for new FTP users, change the value of MsDosDirOutput using the Registry Editor (REGEDT32.EXE). MS DOS-style listings are a value of 1 (the default), and UNIX-style listings are a value of 0.

The path to the MsDosDirOutput entry is as follows:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FtpSvc
   \Parameters

Users can toggle this setting with the site-specific command DIRSTYLE. On most FTP client implementations (including the Windows NT FTP client), users enter a command similar to

   quote site dirstyle

to get this effect.


Additional query words: prodnt
Keywords : kbnetwork NTSrvWkst nttcp
Version : 3.1
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: May 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.