Click here to return to the KiXtart HelpDesk main page...

Known Problems of KiXtart on Windows 9x

The following is a list of known bugs and other issues you might encounter running KiXtart on Windows 9x:

  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.

  The LockLog utility (shipped with the MS-DOS – based version of KiXtart) does not work on Windows 9x.

  The SET and SETM commands do not work on Windows 9x.

As a work around run Winset.exe (available on the Windows 9x CD) from within KiX32 using the SHELL command.

  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 you have made it visible using ATTRIB).

  On Windows 9x, if you remove a network drive 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.

You can prevent this scenario with an additional step. After you remove the drive, delete the corresponding subkey from the registry. For example:

USE E: /d


  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. You can get the latest version of this file from your local Microsoft Product Support Services contact (refer to Knowledge Base article 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”