MartMart KiX Supporter
Registered: 2002-03-27
Posts: 4673
Loc: The Netherlands
Originally Posted By: Ruud van Velsen
Dear KiXtart supporters,
attached to this email is RC 1 of KiXtart 2010 4.61…
If you get a chance, please have a look at this build and let me know what you think!
This update contains the following fixes & enhancements:
• Fixed issue with handling of EXIT codes • Fixed issue with COPYing files to a directory (without specifying a backslash) • Fixed issue with writing large DWORD values to the registry • Updated @PRODUCTTYPE to correctly report Server 2008(R2) & Windows 7 • Added REPLACE function • Fixed @LOGONMODE (yes, finally!) • Fixed BREAK “0”
Check out KIX2010.TXT for more detail on the enhancements.
Please feel free to share this build on your websites or via email.
NTDOCNTDOC Administrator
Registered: 2000-07-28
Posts: 11634
Loc: Space
Not a bug Glenn and Ruud previously said (somewhere) that this would always be the case.
I don't think backwards compatibility is in the plans for this part, but that is just my take on it and at least good to have you post about it so it is known and Ruud can respond on it.
Glenn BarnasGlenn Barnas KiX Supporter
Registered: 2003-01-28
Posts: 4402
Loc: New Jersey
I understand it isn't really a bug, but my tokenized scripts run the same with 4.53 and 4.60, but fail immediately with 4.61. More of a heads-up that if you use tokenized scripts (we use them for 90+% of our tools) then you'll need to consider updating your scripts when you update Kix to 4.61.
Glenn
_________________________ Actually I am a Rocket Scientist!
Registered: 1999-05-06
Posts: 391
Loc: Amsterdam, The Netherlands
Verrrry good call...
Actually, you are both right: downward compat is not always garantueed. This is why I store a versionnumber in the tokenized scripts. If a new version of KiXtart needs to make some change in the tokenstream, I update the versionnumber and the new version of KiXtart will only run with newly tokenized scripts.
However, I didn't change anything the tokenstream in 4.61 (or at least, I didn't intend to...), so 4.61 should really run 4.60 scripts just fine.
Turns out I broke something...
Fixed in the next build (which I hope to send out asap).
I can't tell you how good it makes me feel to see 1) Ruud here working on the next release, and 2) everyone chipping in to test the rc and posting back their results.