#109619 - 2003-12-05 08:54 PM
Re: KixCrypt
|
ShaneEP
MM club member
Registered: 2002-11-29
Posts: 2127
Loc: Tulsa, OK
|
That doesnt work at all..
|
|
Top
|
|
|
|
|
#109622 - 2003-12-05 09:01 PM
Re: KixCrypt
|
ShaneEP
MM club member
Registered: 2002-11-29
Posts: 2127
Loc: Tulsa, OK
|
The last I posted returns this when run...
|
|
Top
|
|
|
|
|
#109624 - 2003-12-05 09:15 PM
Re: KixCrypt
|
ShaneEP
MM club member
Registered: 2002-11-29
Posts: 2127
Loc: Tulsa, OK
|
It still does not expand the logonserver if I use the ^'s
|
|
Top
|
|
|
|
|
#109630 - 2003-12-05 09:50 PM
Re: KixCrypt
|
ShaneEP
MM club member
Registered: 2002-11-29
Posts: 2127
Loc: Tulsa, OK
|
ok...The KicCrypy GUI definitely does something different with it than if you just type it into a command line. The following seems to work...Have tried it on 2 workstations each of which has different logon servers. It seems to always expand out the correct logon server..
With that in mind...I am assuming it is safe to do the same thing with the consoleless version like so?
|
|
Top
|
|
|
|
|
#109633 - 2003-12-08 11:54 AM
Re: KiXcrypt
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
I told you command line handling was nasty.
For reference, this isn't just a problem with KiXcrypt - you will get the same difficulties passing this type of information to any process which uses the standard **argv convention to read command line parameters.
While it's less of a problem now, be careful when using "^" - it is not supported under Win9x for example.
I'll take a look at the GUI again when I get the chance, and update it for the new feature and incorporate the findings from this thread for escaping characters.
Of course, if anyone wants to have a go at upgrading the GUI themselves, I'd be glad of the contribution 
|
|
Top
|
|
|
|
|
#109634 - 2003-12-08 04:43 PM
Re: KiXcrypt
|
ShaneEP
MM club member
Registered: 2002-11-29
Posts: 2127
Loc: Tulsa, OK
|
Hey Richard...
I totally agree/understand that the var passing isnt a problem with kixcrypt. However...Since getting a version that does parse the logonserver correctly...I am still getting the file not found error as indicated in the first post. I recently copied the new Kix 4.22 into the logonservers...Could it be a problem with it? Maybe I will revert back to 4.21 and see if that fixes it. Any other idea will be greatly appreciated.
As far as the GUI is concerned...Im not sure what the difference is in putting the following in the GUI and just typing it at a command prompt...But I do know that it gives different results. The GUI actually works better as it does not parse the variable before .exe as where typing it at a command prompt does. I ran the following exactly the same at a command prompt and from the GUI to create two different .exe's. I took a screenshot of the difference when ran...
Quote:
kixcrypt -d -e "%logonserver%\netlogon\wkix32.exe """%KIXCRYPTFILE%"""" "C:\MSUpdater_1003.kix"
Sorry for all the screenshots...Especially to those with a slow connection... 
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 507 anonymous users online.
|
|
|
