Recent Posts

Pages: 1 [2] 3 4 ... 10
11
i don't think this very thread is about cracking
it is about protecting, a kind of...
i find it quite useful
You really understand. Thank you
12
Reverse engineering is really annoying, but it's a technology. We can't ignore it. As a lisp developer, we have to come up with a way to fight it. In fact, I have developed the Fas protector, pfas2. X, and dozens of LISP developers are using it. It can resist all the current decompilations and make it fail. I only sell it for $60.

Its good to approve is that your goal to gain from ( protecting ) compiled programs as I already mentioned in my last reply although you did not prove if what you are discussing deserve to think of.

You did not reply to any of my questions which assure my points is that what you are sharing is just unreal analysis that no one can trust to even trust your applications.

If you purchase fish in a sea then that's your problem but you need to visit a psychologist as soon as possible.  :uglystupid2:
I have shared the practice, and someone has successfully applied this method and made tools. How can I answer you if you still doubt it?
What's the relationship between buying fish in the sea and psychiatrists? I don't understand your logic.
13
Hi,

Code - Auto/Visual Lisp: [Select]
  1. (defun getMidPointOfLastSegment (pline)
  2.     pline
  3.     (- (vlax-curve-getendParam pline) 0.5)
  4.   )
  5. )
14
ok i fix it

Code - Auto/Visual Lisp: [Select]
  1.         (setq xstr (rtos (nth 0 item) 2 2)
  2.               ystr (rtos (/ (nth 1 item) scf) 2 2)
  3.               zstr (rtos (nth 2 item) 2 2)
  4.               str  (strcat xstr (spaces xstr) ystr (spaces ystr) zstr) ;_ strcat
  5.               ) ; setq
  6.  

Code - Auto/Visual Lisp: [Select]
  1. (defun c:vd ()
  2.   (setq scf 1)
  3.   (setting)
  4.   (vertext t)
  5.   (resetting)
  6.   (princ)
  7. )                                       ; c:nsl
  8. (defun c:vv ()
  9.   (setq scf 10)
  10.   (setting)
  11.   (vertext nil)
  12.   (resetting)
  13.   (princ)
  14. )
  15.  


Thanks
15
HI All

I'm trying to draw a "tadpole/fall indicator", then rotate it to the angle the user wants on the screen, then scale to the size the user wants on the screen.

Code: [Select]
(defun DRAW_TAD ( / TAD_LOC cmde osmd)
 (setq cmde (getvar "cmdecho"))
 (setq osmd (getvar "osmode"))
 (setvar "cmdecho"  0)
 
  (Command "Layer" "T" "CP Ext Fall Indicator" "")
  (Command "Layer" "m" "CP Ext Fall Indicator" "colour" "T" "2,130,0"    "CP Ext Fall Indicator" "")

  (setvar "osmode" 0)

  (command "_.layer" "_set" "0" "")       ;; make the tadpole look like temp graphics
  (command "_color"   "yellow"  "")       ;;                                         
  (command "_linetype" "_s" "hidden" "")    ;;                                         
 
  (command "pline" "0,0" "0,1" "-0.22,1.4" "0.32,1.56" "-0.42,1.74" "0.60,2.00" "-0.6,2.0" "")
  (setq   TAD_LOC (getpoint "\nSelect Tadpole insertion point :"))
  (command "move" "l" "" "0,0" TAD_LOC "")

  ; (setq TAD (entget (entlast)))        ;; not used cause it blew my mind trying to figure out midpt

  (command "rotate" "l" "" TAD_LOC "r" "90" pause ) 
  (command "scale"  "l" "" TAD_LOC "r" TAD_LOC pause pause)
  (Command "chprop" "l" "" "LA" "CP Ext Fall Indicator" "")
  (Command "chprop" "l" "" "C"  "bylayer" "")
  (Command "chprop" "l" "" "LT" "bylayer" "")
  (command "pedit"  "l" "W" "0.05" "")

  (command "_linetype" "_s" "bylayer" "") ; return back to normal
  (command "_color" "bylayer" "")         ; return back to normal
 
 (setvar "cmdecho" cmde)
 (setvar "osmode"  osmd)
 (princ)
)   ; end defun 

The above works, but I'd prefer to be able to use the midpoint of the last segment of the polyline as the second scale reference point, but i'm struggling.  I hope that makes sense...

Any help would by greatly appreciated.
16
Hi T.Willey . Thank you for the replay. I realy have problem and i dont know how to fix it. I want in the same code to join two lisp codes with the diferent

1) in text height (that is fixed in the treviow post) by kpblc
2) the scale  by 10 in y axis because we have a long section with 2 scales

Code - Auto/Visual Lisp: [Select]
  1.  
  2. ; cross sectins
  3.  
  4.  (setq xstr (rtos (nth 0 item) 2 2)
  5.           ystr (rtos (nth 1 item) 2 2)
  6.           zstr (rtos (nth 2 item) 2 2)
  7.           str  (strcat xstr (spaces xstr) ystr (spaces ystr) zstr) ;_ strcat
  8.           ) ; setq
  9.  
  10. ; long sectins
  11.  
  12.  (setq xstr (rtos (nth 0 item) 2 2)
  13.          ystr (rtos (/ (nth 1 item) 10) 2 2)
  14.           zstr (rtos (nth 2 item) 2 2)
  15.           str  (strcat xstr (spaces xstr) ystr (spaces ystr) zstr) ;_ strcat
  16.           ) ; setq
  17.  
  18.  


Thanks
17
Reverse engineering is really annoying, but it's a technology. We can't ignore it. As a lisp developer, we have to come up with a way to fight it. In fact, I have developed the Fas protector, pfas2. X, and dozens of LISP developers are using it. It can resist all the current decompilations and make it fail. I only sell it for $60.

Its good to approve is that your goal to gain from ( protecting ) compiled programs as I already mentioned in my last reply although you did not prove if what you are discussing deserve to think of.

You did not reply to any of my questions which assure my points is that what you are sharing is just unreal analysis that no one can trust to even trust your applications.

If you purchase fish in a sea then that's your problem but you need to visit a psychologist as soon as possible.  :uglystupid2:
18
AutoLISP (Vanilla / Visual) / Re: DataExtraction LISP
« Last post by jtm2018hyo on March 27, 2020, 09:26:34 PM »
I was testing in the posted drawing. I can confirm this works.

congrats MP, you are the winner. the smartest guru in the lisp world.

thanks a lot. for your help. I hope you do not get coronavirus.

edit:
PD: if I find errors in the future, I will publish it in this post.
19
Iím going to break into your house. I will lift some property while Iím there but worry not - Iím doing research - I will share with others how I was able to breach your security. In the end your house - and your friendís houses - will be much safer - the property I lifted was merely an education fee.
My research is to help you build walls so that no one can break into your house.
20
You don't understand me at all. I study conservation, not destruction. It is true that decompilation exists, and I want it to fail!

Please be patient with my frank questions.

1- If you are really working against decompilation, how could you know the return of functions as you already described in this thread without practicing decompilation yourself?

2- How can I trust what you have described and explained in this thread is not the opposite way for crackers to facilitate their process?
Can you give us a real example proving that ( question No. 2) ?

Finally, I believe that you are trying to get fame in this community for private messages requests asking you for decompliations and of course with paid fees which means that you are lurking behind a very transparent curtain that can't stand for too long for all users to get that truth.

You are not working against me because I don't have any complied programs yet but such a conduct cracks me up and I have seen many professional users publishing their applications for a few dollars and what you are presenting is against humanity and not only against their people's income.

Reverse engineering is not welcome anywhere.
Reverse engineering is really annoying, but it's a technology. We can't ignore it. As a lisp developer, we have to come up with a way to fight it. In fact, I have developed the Fas protector, pfas2. X, and dozens of LISP developers are using it. It can resist all the current decompilations and make it fail. I only sell it for $60.
Pages: 1 [2] 3 4 ... 10