#3339 - 2000-06-20 04:26 PM
Proper procedure for posting code
|
Shawn
Administrator
   
Registered: 1999-08-13
Posts: 8611
|
Gang:What is the proper procedure for posting code to this BBS ? I know about the code/slash-code syntax and that, but when one actually copies the code in, what's the proper way of doing it ? Cutting and pasting straight from notepad or write doesn't seem to work very well ( for me anyway ). When I try to copy/paste the code back into my machine, the crlf's get all screwed up ! Am I missing something here ? cj/bryce/mca/box: You guys seem to have a handle on it. How do you post code ? Shawn.
|
|
Top
|
|
|
|
#3344 - 2000-06-20 08:12 PM
Re: Proper procedure for posting code
|
Jochen
KiX Supporter
   
Registered: 2000-03-17
Posts: 6380
Loc: Stuttgart, Germany
|
just a guess...NON-TRUE-TYPE ????????? will try it with 'Fixedsys' ahhh,stop, by the way gang : what is the proper 'chr(xxx)' for © ???  Thanx Jochen
_________________________
|
|
Top
|
|
|
|
#3345 - 2000-06-20 09:57 PM
Re: Proper procedure for posting code
|
MCA
KiX Supporter
   
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Which font you are using is no problem at all, because during the save action it will be converted to an useful one for notepad. For example use select:
- font type: Arial (so you see the effects of a proportional font)
- font size: 8
Example of a font "Arial" with size "5": code:
? only encrypted code is located in the common folder (f.e. NETLOGON). code which is very hard to modify. during decryption you can check of code has been changed or becomes damaged. ? a kixtart script for decryption is very slow. by testing a short script it takes too must time and it is comsuming a great lot of CPU time. a short script for me is about 250 lines. by using another program language we get an enormous speed up. a script of 10.000 lines can be decrypted within 2 à 5 sec before starting running kix32.exe procedure. ? do not use only XOR encryption. we think about many elements: stripping Kixstart script first. f.e. delete empty lines, remove comment statements, remove print statements when you are only using WRITE statements, change nice variable names to meaningless variable names (f.e. $x1, $x2, ..., $x999), combining separate lines to one line. compress kixtart script. calculate CRC value of script. encrypt script by XOR and/or other encryption techniques with a dynamic password usage. a dynamic password means: each time you are running the encryption/compression procedure the password will be different, which means the encrypt output file contains NEVER the same contents. make it possible to run the procedure over and over, so cracking because harder and harder. Result of a script of 300.000 bytes is 40.000 bytes after using of compression and encryption techniques. Encryption cost about 10 à 20 seconds. Decryption cost about 2 à 5 seconds. The processor speeds influences these results.
Example of a font "Arial" with size "8": code:
? only encrypted code is located in the common folder (f.e. NETLOGON). code which is very hard to modify. during decryption you can check of code has been changed or becomes damaged. ? a kixtart script for decryption is very slow. by testing a short script it takes too must time and it is comsuming a great lot of CPU time. a short script for me is about 250 lines. by using another program language we get an enormous speed up. a script of 10.000 lines can be decrypted within 2 à 5 sec before starting running kix32.exe procedure. ? do not use only XOR encryption. we think about many elements:stripping Kixstart script first. f.e. delete empty lines, remove comment statements, remove print statements when you are only using WRITE statements, change nice variable names to meaningless variable names (f.e. $x1, $x2, ..., $x999), combining separate lines to one line. compress kixtart script. calculate CRC value of script. encrypt script by XOR and/or other encryption techniques with a dynamic password usage. a dynamic password means: each time you are running the encryption/compression procedure the password will be different, which means the encrypt output file contains NEVER the same contents. make it possible to run the procedure over and over, so cracking because harder and harder. Result of a script of 300.000 bytes is 40.000 bytes after using of compression and encryption techniques. Encryption cost about 10 à 20 seconds. Decryption cost about 2 à 5 seconds. The processor speeds influences these results.
Greetings. [This message has been edited by MCA (edited 20 June 2000).]
|
|
Top
|
|
|
|
#3348 - 2000-06-21 09:07 AM
Re: Proper procedure for posting code
|
Anonymous
Anonymous
Unregistered
|
Jochen, MCA,Your question: quote: -------------------------------------------------------------------------------- what is the proper 'chr(xxx)' for © --------------------------------------------------------------------------------
The standard ASCII table doesn't contain this symbol. so there is no CHR-code. Greetings. Chr(169)
Code _____________________________________________
Cls $Chr=0 :Start $Chr=$CHR+1 ? $CHR ? CHR($CHR) goto start :End Exit _____________________________________________ Jos 
|
|
Top
|
|
|
|
#3349 - 2000-06-21 10:45 AM
Re: Proper procedure for posting code
|
Jochen
KiX Supporter
   
Registered: 2000-03-17
Posts: 6380
Loc: Stuttgart, Germany
|
Jos,in the first i tried chr(169) [Yes,lads and lassies ; I got a charmap too ] but it returns only 'c' and NOT '©' .... please don't let me look like a 'dummass' , i am just a little 'confusiasted' Jochen [b.t.w.: Jos : Your code example will loop infinitely until it logs You OFF!!!] [This message has been edited by jpols (edited 21 June 2000).]
_________________________
|
|
Top
|
|
|
|
#3350 - 2000-06-21 11:01 AM
Re: Proper procedure for posting code
|
Anonymous
Anonymous
Unregistered
|
Jochen,Strange in my DOS box I'll get the right caracter. Maybe the Codepage is responsible for that. The code that I posted was to figure out the CHR string with the /d parameter. Jos
|
|
Top
|
|
|
|
#3351 - 2000-06-21 11:59 AM
Re: Proper procedure for posting code
|
Jochen
KiX Supporter
   
Registered: 2000-03-17
Posts: 6380
Loc: Stuttgart, Germany
|
Hi Jos,nice to hear something from You again, ehhh my fonts in my DosBox are Rasterfonts, hmm, codepage is German [IBM] (Yahh, it is a ThinkPad) NT=4.0;SP=6a (English). strange: on my 'BigBlue 300gl' i receive for chr (169) a '®' where NT=4.0 SP=5 (English) and codepage = German [Standard] ....  ¡I think this is getting babylonic! Yours etc. Confucius
_________________________
|
|
Top
|
|
|
|
#3352 - 2000-06-22 12:11 AM
Re: Proper procedure for posting code
|
Anonymous
Anonymous
Unregistered
|
Hi Jochen,I'll tested it on my Dutch Win95 machine ( Digital ) with dutch codepage 850 ( just typed chcp in the DOS Box ). Once again tested the 1 minute writen schript and i'm sure about CHR(169) on my machine. I Also Tested it on an Englisch NT 4.0 Server SP4 codepage 850. The result was the same as on my machine. My guess is it's the codepage. Jos [This message has been edited by Jos (edited 21 June 2000).]
|
|
Top
|
|
|
|
#3354 - 2000-06-21 03:38 PM
Re: Proper procedure for posting code
|
Bryce
KiX Supporter
   
Registered: 2000-02-29
Posts: 3167
Loc: Houston TX
|
Greetings!Posting/retrieving code from this BB system. :Posting I will type my message place the code /code And come back and paste from notepad between the two. Retrieving: I will copy all code between code /code, run wordpad(write.exe) and paste it into there. then I do a Ctrl-a, ctrl-x, close Wordpad with out saving, and paste it into notepad. don't know why it works this way......But it will preserve the formatting. Bryce
[This message has been edited by Bryce (edited 21 June 2000).]
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 2419 anonymous users online.
|
|
|