The information in this article applies to:
SYMPTOMSWhen you are using the Microsoft Client for NetWare Networks or the Microsoft Service for NDS, a semicolon (;) in a SET statement in a NetWare login script may be parsed as a character, rather than as a join parameter, by the login script processor. RESOLUTIONThis issue is resolved by the following updated file for Windows 95 and OEM Service Release 2 (OSR2), and later versions of this file:
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95 and
OEM Service Release 2 (OSR2). An update to address this problem is now
available, but is not fully regression tested and should be applied only
to computers experiencing this specific problem. Unless you are severely
impacted by this specific problem, Microsoft does not recommend
implementing this update at this time. Contact Microsoft Technical Support
for additional information about the availability of this update.
MORE INFORMATIONThe Novell login script processor requires a semicolon in SET statements to concatenate an environment variable and a string. For example: set <a>=<b>;"text string"If <b> = "this is a ", <a> is set to "this is a text string." The Windows 95 login script processor would set <a> to "this is a ;text string." For additional information about issues resolved by updates to this component, please see the following articles in the Microsoft Knowledge Base: Q152401 Problems If NetWare Server Allows More Than 256 UsersFor additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base: Q161020 Implementing Windows 95 Updates Additional query words: user system tree
Keywords : kbnetwork kbpolicy win95 |
Last Reviewed: June 30, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |