INI File Sizes Become 0 Bytes After Starting WinLogin

Last reviewed: November 21, 1994
Article ID: Q88099
The information in this article applies to:
  • Microsoft Windows operating system versions 3.1, 3.11
  • Microsoft WinLogin version 1.0.

SUMMARY

In WinLogin 1.0, if the fallbackdir= entry in the [WINLOGIN] section of the WINLOGIN.INI file is incorrectly set to the Windows directory, .INI files in the WINDOWS directory may become 0 bytes in size.

The fallbackdir= entry should be set to the Windows \FALLBACK subdirectory.

MORE INFORMATION

If problems occur when running the WinLogin Client software and the .INI files in the WINDOWS directory have become 0 bytes, the fallbackdir= line in the [WINLOGIN] section of the WINLOGIN.INI may be set incorrectly. It should NOT be set to the local WINDOWS directory. Instead, it should be set to WINDOWS\FALLBACK or any other directory that did not already contain the .INI files listed in the WLMERGE.INI file.

Edit WINLOGIN.INI and set fallbackdir= correctly,then replace the lost .INI files with backup copies, provided they are available.

This information applies to version 1.0 of Microsoft WinLogin. For information about ordering Microsoft WinLogin, call the Microsoft Sales Information Center (MSIC) at (800) 426-9400, or mail the form supplied with the Windows Resource Kit (WRK) for the Microsoft Windows operating system version 3.1.


KBCategory: kbnetwork kb3rdparty
KBSubcategory: win31
Additional reference words: 1.00 1.0 3.10 3.1 LAN Manager
LANman remove novell network share winlog


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