Knowledge Base

Semicolon Not Processed Correctly in NetWare Login Script

Article ID: 147873

Article Last Modified on 11/15/2006

APPLIES TO

This article was previously published under Q147873

SYMPTOMS

When 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.

RESOLUTION

STATUS

This problem no longer occurs in Windows 98. To resolve this problem, install the current version of Windows. For information about the current version of Windows, visit http://www.microsoft.com/windows.

MORE INFORMATION

The 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."

Additional query words: user system tree

Keywords: kbnetwork kbpolicy kbprb KB147873


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.