Known Problems of KiXtart on Windows 9x

The following is a list of known issues that may be encountered when using KiXtart on Windows 9x:

·  If KiXtart is used on systems that are configured to run both Microsoft Networking client software and Novell Netware client software, compatibility issues can cause KiXtart to fail to retrieve network information and/or find any script. If these problems occur, make the following change in the registry of the affected clients:

 

HKEY_LOCAL_MACHINE

   System

      CurrentControlSet

         Services

           MSNP32

              Network Provider   CallOrder              [00 00 00 40]  >change to> [00 00 00 20]

           NOVELLNP

               Network Provider  CallOrder              [00 00 00 20]  >change to> [00 00 00 40]

·  When text is output to bottom-right position of the screen, the screen scrolls.

This issue is related to the Console API on Windows 9x.

·  Color is sometimes garbled when the screen is scrolled.

This problem is caused by the way Windows 9x handles color attributes.

·  On Windows 9x, SAVEKEY produces a hidden, read-only system file in the Windows System directory. On Windows NT, the same command produces a normal file in the current directory.

 

In either operating system, the file can be used with LOADKEY (after it has been made visible using ATTRIB).

·  On Windows 9x, if a network drive is removed that was redirected from My Computer or Windows Explorer, the drive remains visible in the Windows interface as a disabled or ghosted drive, and the drive is reconnected when the user clicks it.

 

This scenario can be prevented with an additional step. After the drive has been removed, delete the corresponding subkey from the registry. For example:

USE E: /d

DELKEY("HKEY_CURRENT_USER\Network\Persistent\E")

 

·  The logon script is sometimes skipped completely.

 

This problem can be caused by a sharing bug in Msnet32.dll. The bug was fixed in version 4.00.951 of Msnet32.dll. The latest version of this file is available from your local MicrosoftÒ Product Support Services contact (refer to Q150589).

Another reason for the logon script to be skipped on Windows 9x is a space in the logon script field in NT User Manager. Although NT User Manager accepts multiple strings (and spaces) in the logon script field, Windows 9x fails to run the logon script.

·  The ShutDown function does not work reliably.

This problem is caused by the underlying Windows API. It may be fixed in a future version of Windows 9x. As a workaround, try the following command :

SHELL "%windir%\RUNDLL32.EXE user.exe,ExitWindows"