Page 1 of 1 1
Topic Options
#46163 - 2003-09-29 10:54 PM Kixcrypt Question
JohnQ Offline
Starting to like KiXtart

Registered: 2003-03-04
Posts: 171
I am attempting to use kixcrypt and having some minor difficulties. Kix32.exe is not in the path on the machines that will be executing the script. The executable resides in "c:\kix\kix32.exe". I thought that I could specify this using the -E switch but I guess not. I don't want to include the kix executable in the package. Is there a way to specify a path to kix32.exe?

Also, when executing an unencrypted script, you can call your script and pass it an environment variable -- is this not possible once the script has been encrypted?

Top
#46164 - 2003-09-30 10:50 AM Re: Kixcrypt Question
Richard H. Administrator Offline
Administrator
*****

Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
You may include the full path to the KiXtart executable, indeed it is recommended.

If you are not sure what is going on, use the "-d" switch to create a debug version. This will output some useful information, including the execution path at both the encrypting and decrypting phase. When you are happy that all is running as expected, create a production version without the "-d" flag.

Note, you will of course not see any output if you use the console-less version.

You may set an environment variable before calling the encrypted script, and this will be available when the unencrypted script executes.

Top
#46165 - 2003-09-30 02:22 PM Re: Kixcrypt Question
JohnQ Offline
Starting to like KiXtart

Registered: 2003-03-04
Posts: 171
Thanks Richard.

I don't know what I did differently, but it is working now.

One other question. Say you have 2 scripts and both are encrypted. I assume that you cannot call the second one from the first. At least I couldn't get it to work. I had to execute the first script from the initiating batch file, wait for it to complete and then execute the second script from the same batch file. Is this correct behavior or is there a way to call one script from the other?

Top
#46166 - 2003-09-30 02:36 PM Re: Kixcrypt Question
Richard H. Administrator Offline
Administrator
*****

Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
Yes, you can call one script from another.

To be certain that it will work as you expect, you need to be sure to qualify the path. The directory that the scripts are unloaded into is available in an environment variable %KIXCRYPTDIR%

To make your script portable you could do something like:
code:
If %KIXCRYPTDIR%
$sScriptPath=%KIXCRYPTDIR%+"\"
Else
$sScriptPath=".\"
EndIf

...later in your script...

Call $sScriptPath+"part2.kix"
Call $sScriptPath+"part3.kix"

The only script you won't be able to call is the "master" script, as although the file name is available in %KIXCRYPTFILE% the script is overwritten and deleted as soon as possible after the primary command begins to execute.

Top
#46167 - 2003-09-30 10:35 PM Re: Kixcrypt Question
JohnQ Offline
Starting to like KiXtart

Registered: 2003-03-04
Posts: 171
Thanks Richard.

One last question. Reading some previous posts regarding kixcrypt, I think I read where you said that some of the command line parameters would not work with Win9x. Is this true? I'm using your latest gui to create the encrypted files.

I know you probably want to say "just test it" but unfortunatley I don't have any antiques to test it on and I know that we still have some Wintendo left in our environment - I just don't know where in the country they are which makes it kind of hard to test.

Thanks for your help and great tool!

Top
#46168 - 2003-10-01 09:46 AM Re: Kixcrypt Question
Richard H. Administrator Offline
Administrator
*****

Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
I don't recall the thread - if you know what it was about I may be able to answer specifically.

KiXcrypt has gone through major code changes, including using a new compiler, and as far as I am aware there are no outstanding problems running on any Wintel platform.

KiXtart was in fact developed on a Win95 platform, so it was more stable there than on WinNT+. It is now developed on XP.

The only issue that I can recall was that malloc()ed memory on Win95 was zeroed by the OS, and not on WinNT. This meant I missed a school-boy error where I didn't explicitly zero the memory myself. As I has no access to WinNT it was a bastard to track down. I've switched to statically allocated buffers in most cases now. This makes the code slightly less efficient (I allocate a few KB more memory than I actually need), but it means that the code is simpler and less prone to stupid errors.

I still have a Win9x box on my desk for debugging, although I don't know how long I'll be able to keep it, so if you do experience a problem let me know.

quote:
we still have some Wintendo left in our environment - I just don't know where in the country they are which makes it kind of hard to test.
You'll want to include an OS check in your script that fires off an email alert when it's run on a Win9x machine.

Amongst the machines I support I know of at least 2 Win3.11 machines and one Win3.1 machine still in production use for office applications [Roll Eyes]

Top
Page 1 of 1 1


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

Who's Online
0 registered and 1471 anonymous users online.
Newest Members
Viginette, ManuvdWielNL, Sir_Barrington, batdk82, StuTheCoder
17888 Registered Users

Generated in 0.189 seconds in which 0.165 seconds were spent on a total of 12 queries. Zlib compression enabled.

Search the board with:
superb Board Search
or try with google:
Google
Web kixtart.org