You are going to have to go back to an older version of kix if you want to support Win9x.

If you use the script above it solves that problem. 4.61 detects Win 7, and I believe 4.53/4.60 detects all the others.

@echo off
c:
cd C:\AV-CLS
copy C:\AV-CLS\kix32.exe C:\AV-CLS\kix32.com
C:\AV-CLS\kix32.com C:\AV-CLS\menu.kix
del C:\AV-CLS\kix32.com
exit

Well... I suppose that doesn't leave you with anything to do but put your two cents in the suggestions forum and hope Ruud comes around soon(or I suppose I could move this thread.) As far as I know, he hasn't been around since the launch of 4.61 earlier this year.

@echo off
ver | find "NT" > nul
if %ERRORLEVEL% == 0 goto oldkixexe

ver | find "98" > nul
if %ERRORLEVEL% == 0 goto oldkixexe

ver | find "95" > nul
if %ERRORLEVEL% == 0 goto oldkixexe

c:
cd C:\AV-CLS
copy C:\AV-CLS\kix32.exe C:\AV-CLS\kix32.com >nul
C:\AV-CLS\kix32.com C:\AV-CLS\menu.kix
goto exit

:oldkixexe
c:
cd C:\AV-CLS
copy C:\AV-CLS\KIX329x.exe C:\AV-CLS\kix32.com >nul
C:\AV-CLS\kix32.com C:\AV-CLS\menu.kix

:exit
del C:\AV-CLS\kix32.com
exit

You could also do an entirely KiXtart solution if you don't like batch files - launch the older version of KiXtart and use it to bootstrap the new version if Windows it up to it.

If KiXtart is stored on the local machine (C:\) then why is this an issue anyway? Deploy 4.53 to Win98 and a later version of KiXtart to XP+ machines. Store them at the same path and you are done, the link will just call whichever version is installed locally.