I suppose kix32.exe ?

W9x have some problems if the kix32.exe file is in use by an other user that logs in.

Solution 1

This is most often caused by an older version of MSNET32.DLL on Pre-OSR2 Windows 95 systems. More detailed information on the symptoms and cause can be obtained from Microsoft's KB Article Q150589.

MSNET32.DLL 4.00.951, dated 4/18/96 (60,416 bytes) fixes the problem.

Solution 2

With Windows 95, another possible cause is that the Workgroup Name configured in the Information Tab of Network Settings does not match the Domain Name that the authenticating Domain Controller belongs to. In this case, often the ($Priv) field will report (Guest) instead of (User) or (Admin) when reviewing the log files. Either change the Windows 95 Workgroup name to match the Domain Name or install the latest W95 updates, including: DCOM95.exe, VTCPUP20.exe, VIPUP20.exe and W95WS2SETUP.exe.

Solution 3

Create an eight character .bat file.
Let the user execute the batch file instead of the kix32.exe file.

sample...

echo off
cls

if exist c:\winnt\*.* goto winnt

echo Loading NTscript

start /min /wait %0\..\kix32.exe kixtart.kix
exit

goto end

:winnt
Rem Make sure this a Windows 95 or NT client
if "%WINDIR%"== goto end

echo Loading NTscript

start /min /wait %0\..\kix32.exe
exit

goto end

:end

gr.

Olly V