LMSCRIPT.PIF and the SMSLS logon scriptLast reviewed: April 22, 1997Article ID: Q126159 |
The information in this article applies to:
SYMPTOMSThe SMSLS logon script stop responding (hangs) when used with some Windows 3.1 and Windows for Workgroups 3.1 or 3.11 configurations.
CAUSEWhen a Windows system logs on to a network, LMSCRIPT.EXE is run on the client to parse and run the logon script. Under some Windows configurations, applications run from the logon script can cause LMSCRIPT.EXE to hang. This problem usually occurs due to a timing problem with the background and foreground processes. Since LMSCRIPT.EXE is an MS-DOS-based program, a LMSCRIPT.PIF file is used to describe it's required environment. Other drivers or processes running under Windows can take processor cycles away from LMSCRIPT.EXE. This can hang the LMSCRIPT process or cause applications that are running within the logon script to fail.
RESOLUTIONYou may be able to reduce or eliminate this problem by modifying the \WINDOWS\SYSTEM\LMSCRIPT.PIF file or by creating a batch file:
Modifying LMSCRIPT.PIF
Creating Batch FileCreate a batch file called NTLOGON.BAT with the following entries:
Net Time Net Use <network drive>: \\<ServerName>\<SMS Share> <network drive>: SMSLS.BAT (SMSLS logon script) <local drive C>: |
Additional query words: sms prodsms wfw wfwg program information file
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |