Page 1 of 1 1
Topic Options
#198174 - 2010-03-24 06:00 PM Tokenization Compatibility Problem
groon Offline
Just in Town

Registered: 2010-03-10
Posts: 4
Loc: Canada
I found a thread from June 2006 regarding this issue, in which Ruud said it was fixed in version 4.52, yet here I am, seeing the problem again in versions 4.60 and 4.61

The issue is this: tokenized scripts from one version of KiXtart throw errors when executed by a later version. (Obviously, we shouldn't expect an earlier version to be able to understand a script tokenized by a later version.)

To demonstrate the problem, save this script:
 Code:
@kix ?
$ExplorerKey="HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer"
$value=readvalue("$ExplorerKey","EnableAutoTray")
if @error=0
  $rcode=writevalue("$ExplorerKey","EnableAutoTray","$value","REG_DWORD")
  "Wrote enableautotray=$value" ?
endif
$ProfilesKey="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList"
$value=readvalue("$ProfilesKey","ProfilesDirectory")
if @error=0
  $rcode=writevalue("$ProfilesKey","ProfilesDirectory","$value","REG_EXPAND_SZ")
  "Wrote profilesdirectory=$value" ?
endif


Tokenize the file using KiX32.exe version 4.60, and confirm that it works, then run it under version 4.61. (Note: this script will not make any changes to your system. The script uses readvalue and writevalue commands, as well as the @kix macro, for illustrative purposes, as these were the lines which were certain to cause problems in the scripts I was testing.)

I've tried this on five different computers, running Windows XP, Windows XPx64 and Windows 7x64, and the problem occurs under all OSes.

I've already begun distributing version 4.61 to clients and am now afraid I'm going to be breaking stuff I've had in place for a couple years. Yikes.

Is there anything I can do, apart from un-distributing the new version?

Top
#198175 - 2010-03-24 06:23 PM Re: Tokenization Compatibility Problem [Re: groon]
Glenn Barnas Administrator Offline
KiX Supporter
*****

Registered: 2003-01-28
Posts: 4400
Loc: New Jersey
This is a known issue with 4.61. \:\(

I have been distributing code tokenized with .k53 and .k61 extensions, and have renamed the executables so that I can associate the extensions with the particular executables.

Here's the weird thing.. MOST of the functions and commands in 4.53 are compatible in 4.61, but when something isn't, you get a totally strange and unrelated error.. often something like "missing argument" or "invalid parameter" on a line that's correct, or even a comment!

Ruud said that nothing in the tokenizer changed, but clearly something's amiss. Aside from registering unique extensions to the correct executables, there isn't a lot we can do at this time.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D

Top
#198176 - 2010-03-24 06:50 PM Re: Tokenization Compatibility Problem [Re: Glenn Barnas]
groon Offline
Just in Town

Registered: 2010-03-10
Posts: 4
Loc: Canada
Thanks for the quick reply. If Ruud says nothing's changed, does that mean he's not going to be looking at the issue? Is there a bug report forum where we could formalize this question?
Top
#198178 - 2010-03-24 09:38 PM Re: Tokenization Compatibility Problem [Re: groon]
Glenn Barnas Administrator Offline
KiX Supporter
*****

Registered: 2003-01-28
Posts: 4400
Loc: New Jersey
You could add something to the Suggestions forum, and reference a link to this post.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D

Top
Page 1 of 1 1


Moderator:  ShaneEP, Arend_, Jochen, Radimus, Glenn Barnas, Allen, Ruud van Velsen, Mart 
Hop to:
Shout Box

Who's Online
1 registered (Allen) and 633 anonymous users online.
Newest Members
min_seow, Audio, Hoschi, Comet, rrosell
17881 Registered Users

Generated in 0.051 seconds in which 0.022 seconds were spent on a total of 13 queries. Zlib compression enabled.