MikroC 5.0.2 Patch

[metal]

Hi

MikroC 5.0.0.2 patch can be downloaded form here

[gezgin]

crack not working for PIC16FXXX

[metal]

To All

Your problem is as usual Liker error: Routine too large Now I am really angry, and will say bad words.

I do have to say this now, although I do cracks for you guys, I don't have to teach you how to use the software I crack, or try to crack then fail. Bear in mind, if I see something like that in future, I can assure you guys it will be my last crack here on the forum. I am not responsible for the lack of manual reading, ignorance, or someone being an amateur, cause here on the forum, the number of times I read this word, exceeds the number of useful posts on the forum.

There is what I always talk about, PIC16 specifics in the damn manual, read it, and read how the code architecture should be in mikoelektronika products.

I see that you were trying to see if the patch works or not, just to fulfill your wishes, download this example and it will compile fine using delay_ms(1000) !!

BTW, gezgin, no need to post the same request 3 times on the forum, well ,as you can see, my eyes are as sharp as an eagle.

MetaL

[stroma]

Hi metal,
I’m sure that most of the guys there think that you are great. I appreciate all your efforts about the crack you’ve made and I understand your irritation. Don’t be so angry at these few guys who are so lazy and don’t read manuals.
Thanks metal!

[robertino]

metal, thx for your work.....

Bobbe

[gezgin]

Dear Metal, I dont say anything to you. Your helps and crack are very well, but I used old example: Led  blinking 2.

new example is working for 16FXXX at mikroc 5.0.0., 5.0.1, 5.0.2.

Thanks.

[pak]

Hi metal,
         I support all your work and thank you very much.
 
pak

[Faros]

Hi metal,

You have all the right to gnash your teeth … asking your self the most frequent question in the world …why?

Here is why:

-   Because it’s much easier to say it dose not work when the program is a cracked, much much easier than one trying to check his code writing for Syntax and logical errors.
Notes that the reply “crack not working “  is posted in the same day of crack release.

-   Most users think that software’s that took a year to protect could be cracked in 10 minutes, so no problem to complain. It’s a 10 minutes work after all.

-   Most users haven’t tried to crack before, so they don’t know how crackers always checks there work? …. They don’t that crackers are the most suspicious people in the world … “ that is way you descried your eyes as eagle’s  eye” … and that it takes you a lot of effort and time testing before you say that you are done and release the crack.

-   The hidden rule that says “you have the right to crack and we keep all the rights to criticize “must be changed. Crackers have upper hand and if there is an explanation needed then, I think its much better if we agree upon the following rules:

1-   The code must be revised for at least 10 times before posting it.
2-   An attachment of the code and the errors found must be attached, i.e. … the code must not be requested in another post.
3-   The posted codes must be as complete as possible with comments added as needed
4-   The one that cracks is not responsible for teaching others how to write codes for the cracked software … there are manuals for that.  
5-   The least manners, I think, a “thank you for the effort” should be issued ahead of the explanation, by the way “thank you” takes less typing than the “crack not working for xxxxxx”

I know that we are all trying to make this forum the best, thank you Metal for your tolerance as well as for your good work.

[msamar]

hi metal only me that undersand your  grate crack
i am working on c++ ,c , assembly during 10 years ago this crack is working unlimited
dont care if some body her are new student on programming
this crack is unlimited for MikroC compiler that  belong to mikroe.com
regards engineer msamar

[Yazi]

make a brogram up than 2k instruction for 16xxx pic with mikcro you must be divide your main program  in smal programs(function less than 2k), and use org directive:)
I have tested mikroc with program up than 7k with 16f877:cool:
best regards

[metal]

Hi

I think I have already posted a simple example explaining that, this is because PIC microcontrollers have paged memory mapping. Any way, if the code is writen using functions and procedures, then liker error will never appear, so writing large code is no big deal after all

[robban]

Hi MetaL!

Just kill'em!

[[email protected]]

metal, thx for your work..... It's works very well...

[Yazi]

Hi
I have tested the mikroc 5.0.0.0 with a big program up than 90%; but not work in the latest vesrion possible of bug in the latest versi:confused: n. exemple attached

[metal]

yazi,

I have already compiled your code as is and have not modified it using v5.0.0.2, the result was success: 7477 words used. I attached your compiled project with hex files. I have also attached an image for you to re-focus your eyes my friend.

Back to your code, although your code compiled fine, but I don't see it necessary to use org directives here, any way, it compiled fine for me wether the org directives exist in your code or not, but this makes me feel as if you are looking for compiler bugs or trying to say the crack doesn't work, rather than trying to develope a useful project here. The org directive is usually used to tell the compiler that a routine is starting at a predefined location in the program ROM, thats all, no magic !!

I consumed all patience I got to reply to your claim, people, use your minds, come on, these mikroelektronika compilers have excellent promising future, use it the right way, and you will see that they worth every effort I did to crack them. To be honest, this forum is starting to make me sick, I can see that the power has been lost already, and never be back as long as I see lots of members think this way.

When some one has such a problem, why don't they post it on a new thread asking for help, rather than behaving this way, or at least send me a private message, I have received plenty of such messages, and solved 'em all. Shall I start throwing tutorials about the art of problems solving now ?

Sorry to say this yazi, but you disappointed me in deeed, you were the last person I expected to post such a reply

[Yazi]

HI metal.
I say that the compiled result not work on hard whene you use the 5.0.0.2. but it work fine on hard whene you compile it with the 5.0.0.0
do you have tested this on hard or on proteus simulator?
I dont say that your patch not work:) I say there is possibilite of bug in 5.0.0.2 version
For me all mikroelektronica compiler are  a lot of asm bug and result hex file is verry big compared to hitech ccs or IAR compiler
Best regards

[metal]

Yazi,

I am not expert at C, nor a software bug finder, your code worked on PIC16F876/77/77A when I removed the org directives, but have you tried the compiled code without org directives on the hardware like I did.

I also wrote a small code in order to check wether there is a bug regarding the org directive, the resulted hex code was correct, and it started where I wanted it to be, it worked on hardware too.

You seem to have overlaped something in your code, I have not checked that yet.

BTW, it you feel that mikroelektronika products are for you, then why do you bother your self and try them, or try to crack them, if you are soooo good, then why don't you make us a better C compiler than MikroC ?

Another thing, if someone has a problem like this that occured to yazi, post it on a separate thread, ok.

[gezgin]

Dear members of Sonsivri,

MikroC 5.0.0.1 compile correctly my project code or Led blinking and these codes correctly running in Proteus 6.7 and development boards, but when MikroC 5.0.0.2 compile these codes but not working.

MikroC 5.0.0.2 compile but compiled code not working.

I didnt succeeded I tryed every way.  (Page

 MikroC 5.0.0.2 compile this code, but why not working this compiled code?

Best regards.

[Yazi]

asm file is good but hex file is encrypted, when you compil program up than 2k

[metal]

What do you mean by encrypted...

I attached the HEX file for your project, and it seems ok to me...

Any way, I have noticed that there is a stack overflow in your code, also there is a possibility of cracking failure, I have not examined this yet.

[robban]

Hi all!
 
Quite a good compiler, that MikroC. At least it conforms to0 ANSI-C so You can for example
port code from CCS_C or HI-TECH with minor or no changes at all.
Thanx for the patch...

[Fallout]

Hello everyone...  i'm new in PIC but i already like MikroC as for me it is very usefull.... but have 2k limit...  i write Keygen for MikroC 5.x.x simply generate key and have fun with fully working version....

offcourse working on all 5.x.x version's ) key size is always 666byte's do not ask about it.... you do not need patch , modify or something else... use only clear install and key ) like other officialy registered user's

p.s: after key will be created (MikroC.key) put it in MikroC install dir... for me it is "C:\Program Files\Mikroelektronika\mikroC"

p.s.s
Sorry for bad English... i'm from Russia )

Enjoy with FXD Team

[koky]

thanks Fallout, great work!
I have tested now with 5.0.0.3 and work

[sly_fox_2006]

Hi,

Fallout that's a great job you've done!

Thanks a lot man!

 

[Yazi]

Very nice work, can you do it for the micropascal and micropascal dspic?

best regards