#31589 - 2002-10-30 08:26 PM
KixCrypt Issue
|
Austin
Seasoned Scripter
Registered: 2002-01-24
Posts: 439
|
I am using kixcrypt to encrypt a file but I am having a little difficulty. It seems that my @ScriptDir macros are not working because I am not giving a full path when I just double click the exe or even give the full path to the exe in the cmd prompt.. is there a way around this?
Thanks so much for any advice...
_________________________
Austin Henderson
|
|
Top
|
|
|
|
#31591 - 2002-10-30 08:49 PM
Re: KixCrypt Issue
|
Austin
Seasoned Scripter
Registered: 2002-01-24
Posts: 439
|
I tried the @StartDir but I am getting nothing in return for it.. I need to come up with a way to make it use it.. it is looking for an ini file and some other things that are going to be in the same directory... I wonder if I could just remove the reference to it all together and it will use the current path? I will give it a shot.
Thanks
_________________________
Austin Henderson
|
|
Top
|
|
|
|
#31593 - 2002-10-30 08:58 PM
Re: KixCrypt Issue
|
Austin
Seasoned Scripter
Registered: 2002-01-24
Posts: 439
|
Yeah I just found that... well I dont know that to do.. I am packaging this thing with a little installer and need to make the call using the full paths to get any of the macros to work.. but I dont knwo where it will be installed.. directory wise.. any thoughts?
_________________________
Austin Henderson
|
|
Top
|
|
|
|
#31595 - 2002-10-30 09:05 PM
Re: KixCrypt Issue
|
Austin
Seasoned Scripter
Registered: 2002-01-24
Posts: 439
|
My understanding is that those macros only work if you give the full path in the command..
Like
C:\KixDev\kix32.exe C:\kixDev\KixScript.kix
So my problem is that they will not work because when you run the crypted exe you are just clicking the exe??
AM I missing something?
_________________________
Austin Henderson
|
|
Top
|
|
|
|
#31596 - 2002-10-30 09:08 PM
Re: KixCrypt Issue
|
Austin
Seasoned Scripter
Registered: 2002-01-24
Posts: 439
|
It returns NULL there is nothing in there I added a simple check and "crypted" it.
"SCRIPTDIR: "@ScriptDir
I get nothing..
_________________________
Austin Henderson
|
|
Top
|
|
|
|
#31598 - 2002-10-30 09:12 PM
Re: KixCrypt Issue
|
Austin
Seasoned Scripter
Registered: 2002-01-24
Posts: 439
|
Yes... well I think I have. I added the above code and it is nto putting anything out for ScriptDir... but it works just fine in a non-crypted script when I call
C:\KixDev\Kix32.exe C:\KixDev\Script.kix
So I think I am right.. but I am the first to admit I dont know everything..
_________________________
Austin Henderson
|
|
Top
|
|
|
|
#31599 - 2002-10-30 09:22 PM
Re: KixCrypt Issue
|
Austin
Seasoned Scripter
Registered: 2002-01-24
Posts: 439
|
I got the newest version of kix32.exe and the problem went away... thanks for the motivation guys...
; )
_________________________
Austin Henderson
|
|
Top
|
|
|
|
#31601 - 2002-10-30 09:32 PM
Re: KixCrypt Issue
|
Austin
Seasoned Scripter
Registered: 2002-01-24
Posts: 439
|
4.0.2.0
_________________________
Austin Henderson
|
|
Top
|
|
|
|
#31603 - 2002-10-31 02:21 PM
Re: KixCrypt Issue
|
Austin
Seasoned Scripter
Registered: 2002-01-24
Posts: 439
|
Actually what I did was crypt the code and put the new version of kix in the SAME directory as the crypted exe file. This directory we will call it C:\Something has the ini file necessary for my script and two tmp files used by the script. Works just fine like this so is it possible that the first place it will look it the current directory?
Thanks for your help.
_________________________
Austin Henderson
|
|
Top
|
|
|
|
#31605 - 2002-10-31 02:54 PM
Re: KixCrypt Issue
|
Richard H.
Administrator
   
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
quote: Works just fine like this so is it possible that the first place it will look it the current directory?
Yes, and no.
Without the extra secure settings the KiXcrypt simply calls %COMSPEC% with the executable name, and I guess the spawned interpreter will conform to the DOS convention of locating the executable including the brain-dead "look in the current directory first"
However, the kix32.exe executable is not compiled into crypted.exe. What this means is that it won't (necessarily) use the executable in your C:\Something directory when it runs, it will use the first one that it finds on the client PC. This is by design.
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 2220 anonymous users online.
|
|
|