| Eduard |
| (Fresh Scripter) |
| 2011-08-25 10:59 PM |
Version 4.62: not supported on Windows 2000 anymore?
|
Hi,
The doc's still state that 4.62 is supported under Windows 2000, but it doesn't work for me anymore: "KIX32.EXE is not a valid Win32 application".
Can someone else please confirm this problem?
Allen
|
| (KiX Supporter) |
| 2011-08-25 11:05 PM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
You might redownload it. I think that is a different error than the one you get when it is not supported.
| Eduard |
| (Fresh Scripter) |
| 2011-08-25 11:14 PM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
No, the same binary does work OK on other OS'es, so it's not broken in that sence.
The error message is translated from Dutch, so might be somewhat different in English then shown. But it doesn't work on Win 2000.
Just doing "KIX32.EXE /?" in a command prompt already gives the error.
|
Allen
|
| (KiX Supporter) |
| 2011-08-25 11:30 PM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
I don't have 2k to test on... Ruud said he would be unavailable for comment for a couple of weeks... so hopefully someone else can confirm this. In the mean time you could do something like this in a bat file:
Code:
@echo off ver | find "2000" > nul if %ERRORLEVEL% == 0 goto oldkixexe 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 ::For all other OSs :start kix32.exe scriptname goto exit :oldkixexe kix32_453.exe scriptname :exit
| Les |
| (KiX Master) |
| 2011-08-26 02:16 AM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
I concur that it doesn't work on W2K.
KIX32.EXE is not a valid Win32 application.
|
Allen
|
| (KiX Supporter) |
| 2011-08-26 05:38 AM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
Here's a more updated version of the bat file... covers all OSs...
Code:
@echo off
ver | find "95" > nul
if %ERRORLEVEL% == 0 goto oldkix
ver | find "98" > nul
if %ERRORLEVEL% == 0 goto oldkix
ver | find "NT" > nul
if %ERRORLEVEL% == 0 goto oldkix
ver | find "2000" > nul
if %ERRORLEVEL% == 0 goto oldkix
for /f "tokens=2*" %%i in ('reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v ProductName') do set OS=%%j
echo %OS% | find "XP" > nul
if %ERRORLEVEL% == 0 goto currentkix
echo %OS% | find "2003" > nul
if %ERRORLEVEL% == 0 goto currentkix
echo %OS% | find "Vista" > nul
if %ERRORLEVEL% == 0 goto currentkix
echo %OS% | find "2008" > nul
if %ERRORLEVEL% == 0 goto currentkix
echo %OS% | find "Windows 7" > nul
if %ERRORLEVEL% == 0 goto currentkix
echo Unknown OS
pause
goto exit
:currentkix
kix32.exe scriptname
goto exit
:oldkix
kix32_453.exe scriptname
:exit
| Eduard |
| (Fresh Scripter) |
| 2011-08-26 10:40 AM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
Thanks Les for the confirmation, and thanks Allen for your work-around.
Of course Win 2000 is very old now, and not supported by Microsoft anymore.
But we still have some systems running it, and these do what they need to do, so why replacing them?
The work-around is possible, but will still need a lot of scripts to be modified for this.
So first I would like to be sure whether it was intentional to not support Win 2000 anymore with version 4.62.
If yes, then the doc's should be updated to reflect this.
If not, then wasn't this tested during the beta?
|
Allen
|
| (KiX Supporter) |
| 2011-08-26 01:57 PM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
Quote:
The work-around is possible, but will still need a lot of scripts to be modified for this.
Curious, how so?
| Les |
| (KiX Master) |
| 2011-08-26 02:05 PM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
Originally Posted By: Eduard
If not, then wasn't this tested during the beta?
The liner notes only mentions it no longer working with NT4. No mention of W2K.
We too still have a few W2K around with no immediate plans to upgrade them.
| Eduard |
| (Fresh Scripter) |
| 2011-08-26 05:24 PM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
Originally Posted By: Allen
Quote:
The work-around is possible, but will still need a lot of scripts to be modified for this.
Curious, how so?
Sorry that was bad wording. I meant to say that we have to modify the way the scripts are called. Now most of the scripts are called directly, and this has to go through the batch file now.
| Eduard |
| (Fresh Scripter) |
| 2011-08-26 05:28 PM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
Originally Posted By: Les
Originally Posted By: Eduard
If not, then wasn't this tested during the beta?
There is a mention of a beta test by a limited group of users in the August 12 post from Allen in the Lounge forum.
|
Allen
|
| (KiX Supporter) |
| 2011-08-26 05:31 PM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
That was the release notes from Ruud, I just posted it. I don't think anyone here (kixtart.org) tested the beta.
|
Allen
|
| (KiX Supporter) |
| 2011-08-26 05:35 PM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
As a side note... Oh how I used to love Batch files, but if I had to write that ugly crap now, after using kix all these years, I think I would want to shoot myself.
|
NTDOC
|
| (KiX Master) |
| 2011-08-26 08:39 PM |
|
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
I've just kept 4.53 in place. Don't have any systems or code that requires stuff from 4.62 yet.
| Mart |
| (KiX Supporter) |
| 2011-09-01 03:49 PM |
|
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
We get no messages on the two Win2K servers we have left but the logon script does not start automatically. Starting it manually works just fine.
| Ruud van Velsen |
| (Hey THIS is FUN) |
| 2012-09-10 05:31 PM |
|
Re: Version 4.62: not supported on Windows 2000 anymore?
|
Ah yes, the issue here is that recent versions of Visual Studio no longer support NT and Windows 2000 (that is: the runtime that comes with VS 2010 and up no longer supports these OS's, and that's where the error message comes from).
KiXtart itself could run fine, but it would have to be built using an old (unsupported) version of Visual Studio, which is undesirable as there have been quite a few (security) fixes in the runtime since then.
Ruud