patch for Hitech picc std v9.60pl2

[mitsos]

hi

get from:
http://rapidshare.com/files/129138596/Patch.exe.html

regards
mitsos

[xxtigerxx]

can anyone link 9.60 of the demo..

:-)

[omni]

Is this patch for a demo or for the update version ?

If for the update version, where can we get it?

[mitsos]

hi

it is for the "downloadable" demo from hitech site.

mitsos

[0sLtEd43bZ5z]

Hi, does anyone know if this patch works also for HI-TECH C PRO for the PIC10/12/16 MCU Family ANSI C COMPILER v9.60PL2?

[robban]

No, it doesn't..... but someone may fix it?

[wessoms]

Have not tried 100%


http://rapidshare.com/files/133398949/PICC_PRO_9_6_0.rar.html


enjoy..

Posted on: July 29, 2008, 09:30:48 21:30 - Automerged
Password Sonsivri

[robban]

Seems to work OK. But it reports the version to be 9.60PL3. Never mind.
Thanx...

[edalab]

only work at lite mode.

Posted on: July 30, 2008, 03:07:27 03:07 - Automerged
please continue to work for crack picc pro for pic16

[robban]

It's working for me. What's the problem?

[0sLtEd43bZ5z]

robban are you sure, it's not working in lite mode?

[robban]

I think You must have enabled "Operate in lite mode" when You set up the compiler. Use 45 days evaluation instead.

[mbandala]

Have not tried 100%
http://rapidshare.com/files/133398949/PICC_PRO_9_6_0.rar.html
enjoy..

Posted on: July 29, 2008, 09:30:48 21:30 - Automerged
Password Sonsivri

Guys!
You have not noticed it? wessoms indeed uploaded PICC v9.60pl3 but it is the PRO version. I have fully tested and works OK. This is really something and I am very satisfied...

I just uninstalled my STD v9.60pl1 installation, installed this one and didn't have to change anything in MPLAB. I was able to compile my codes by just clicking the BUILD button.

Posted on: July 30, 2008, 01:58:31 13:58 - Automerged

I think You must have enabled "Operate in lite mode" when You set up the compiler. Use 45 days evaluation instead.

Yes, better try the 45 days evaluation mode. Though I tried the Lite mode and it worked. At least you should be able to compile any existing work in either Lite or evaluation modes. The problem has to be related to the configuration of the compiler in MPLAB. You should probably get a source file successfully compiled with a previous version of PICC and then try this new version with your working code.

[0sLtEd43bZ5z]

Hi,

i tried to install this cracked PL3 version, however at installation, I get feedback "Your evaluation period has expired (139402)". I actually did use up 45 days on older (not cracked) version of the compiler. This feeback appears after checking (connecting with Hi-tech server) in installation mode. I cannot proceed with instalation even if I disconnect computer. Does anybody know based on which property, Hi-tech checks which computer am I using. MAC or hard disk serial number or something else. I'm pretty sure Hi-tech has some kind of database, based on which it checks from which computer installation is runned.

Can perhaps anybody crack installation file, not to check online for previous installations?

[wessoms]

For the PICC PRO 9.60PL3 :

If your 45 day period has been previously used then install the lite version, copy the file over and it will work in PRO mode. If you have the picc pro 9.60PL3 version already installed just copy the picc.exe in the download over the one installed.

[robban]

The only thing I can think of is that Yr. time and calendar is not updated, or Yr. registry is clogged up.You can manually remove any entries by searching it for "HI-TECH" or use a registry cleaner that remove any void entry.
... good luck.

[mitsos]

hi

I think the only feature of the cracked picc.exe is to hide the lite mode when executed.
By no way works at the pro mode with ocg enabled.

I notice the following (using command line, I choose 16f877)
compiling the led.c from the samples folder
on picc pro 9.60pl3 compiler
with the genuine picc.exe I take a hex file that waste 69 memory places (lite mode)
with cracked picc.exe      I take again a hex file with 69 memory places   ("virtual" pro mode)
on picc std 9.60pl2 compiler (cracked)
without optimization I take a hex file that waste 49 memory places
with full otimization I take a hex file that waste 25 memory places

it seems that hitech to give a good impession about the ocg optimiser, "destroy" the picc pro compiler to produce larger size of code comparing to std version without optimization.

regards
mitsos

ps I hope kappa do the right job

[mbandala]

with the genuine picc.exe I take a hex file that waste 69 memory places (lite mode)
with cracked picc.exe      I take again a hex file with 69 memory places   ("virtual" pro mode)
on picc std 9.60pl2 compiler (cracked)
without optimization I take a hex file that waste 49 memory places
with full otimization I take a hex file that waste 25 memory places

I just tried led.c and got this from the compiler using 16F873 in MPLAB

Memory Summary:
    Program space        used    15h (    21) of  1000h words   (  0.5%)

It used only 21 bytes. It looks like my copy of PICC PRO 9.60pl3 is working with OCG. Am I wrong?

[mitsos]

hi

can you give us more info about what mplab version you have, what settings in build options are you use as here with mplab v8.1 and various compilers from hitech installed I take a hex with 77 memory places with the 16f873. Something going wrong so I must solve it.

regards
mitsos

[robban]

I just tried the LCDemo in samples folder(where do You find the LED example?) and the PRO version used roughly 20 % lower hexfile than the standard version...

[0sLtEd43bZ5z]

Hi, I tried compiling one of my small projects with lite and cracked PL3 version and noticed a slight difference in code size. It changed from 476 bytes (lite) to 461 (cracked pro).
Not much difference, however project is very simple (1 source file, no interrupts...).
I have installed compiler in lite mode, because I used up 45days in evaluation pro mode...
So I guess crack works also in lite mode.

[mitsos]

hi

I try everything in my place:
I try mplab version 8 and 8.1, I install the picc pro 9.60 pl3 by all ways eval 45,lite then with doctor cleaner I clean registry errors (is there a better program for this job?) but everytime I take a hex file with 69 memory places to 16f877 against 25 with picc std 9.60pl2 with full optimization, when compiling the led.c in the misc folder of samples

Can you tell me which mplab are you using, what type of installation you choose at the picc pro as the problem is not solved.

regards
mitsos

[robban]

Well, this needs to be solved...

Which environment are Yr. machine running on? The problem is not obvious to me, at least. Remember though, if You have PIC:s as a hobby, optimization is for those who need to upgrade an existing PIC where a change of MCU will be costly. Someone else mentioned a pro uninstaller which could be handy in this case since some fragments still linger in Yr. temp folders.
Myself I don't care much for Vista since it's not a significant change from XP(only mor RAM and CPU power needed). I think You need to tell us Yr. environment and the steps toward failure.

Another thing: If you are able to port HI-TECH code to Knudsen CC5X(red edition, found elsewhere in this forum) You'll be amazed how compact the code will be.

[0sLtEd43bZ5z]

I don't think registry(or any other installation traces) has anything with detecting previous installations. Hi-tech has some kind of database, with some of comuter unique values (MAC or HD ID) so at each installation it checks this database (as far as I noticed, you cannot install evaluation version without net access). But if you install in lite mode, you should be able to use cracked version. I did anyway.

[mbandala]

hi

can you give us more info about what mplab version you have, what settings in build options are you use as here with mplab v8.1 and various compilers from hitech installed I take a hex with 77 memory places with the 16f873. Something going wrong so I must solve it.

regards
mitsos

Sorry you are struggling with this. I suppose I was lucky anyway. I just installed the 45-day trial and applied the crack. Then created a new project in MPLAB 8.0 (Device=16F873), selected the HI-TECH Universal Tool Suit and added LED.c (which is located in C:\Program Files\HI-TECH Software\PICC\PRO\9.60\samples\misc). I did not change anything in the build options, just clicked the "rebuild" button and got the screen I am attaching. You can clearly see that OCG seems to work for me. I hope you can reproduce this result. Just keep trying.

Posted on: August 01, 2008, 07:03:02 19:03 - Automerged
I honestly don't think that the MPLAB version matters. Just remember to crack the 45-day trial. I tried the Lite mode and that didn't work... I'm using XP SP2 if it helps...

[mitsos]

hi
and my last action was to format my hdd to install the windows xp pro with last sp3, I try the mplab 8 and 8.1 nothing changes, I get very bigger files than std version.
I notice that speed and debug options are impossible to check/uncheck, the change in the optimization settings does not alter the size of the created hex file and the installations of the two versions differ in size by a factor 2, std(9.60pl2) wastes almost 30MB and pro(9.60pl3) wastes 13.50MB.

regards
mitsos

ps I can live without pro for the time...

[mbandala]

You still having that problem is unbelievable specially after formatting your HDD. Have you tried in another PC? Any chances that the patch only worked for XP SP2? You never know... these things happen.

I hope more people here can confirm that the crack worked for either XP SP2, XP SP3 or other Windows versions. Mine is Windows XP Build 5.1.2600.2 Service Pack 2.

Posted on: August 03, 2008, 01:32:57 01:32 - Automerged
I just tried to install the PRO compiler in another computer. It worked. I just did what I describe above. I must point out that I did id without internet connection and choosing not to install the HI-TIDE IDE.

[mitsos]

hi mbandala

previous I have the same with you windows version (I mean xp pro with sp2), I run several times the doctor cleaner and I notice strange things in my pc and the known problem with pro compiler, I decide to clean my hdd and, as I wrote, I setup the xp pro with sp3.
Only one thing I have in my mind if the patched picc.exe wants a particular version of .net framework, I remember that the keygen for fastavr compiler v4.3 working correctly if you have installed the .net framework 2. On the other side I compare the genuine and patched picc.exe and differ only at two bytes.
At your place, the installation of the versions std and pro differ so much in the wasted size as I wrote in previous post?

regards
mitsos

[mbandala]

hi mbandala

previous I have the same with you windows version (I mean xp pro with sp2), I run several times the doctor cleaner and I notice strange things in my pc and the known problem with pro compiler, I decide to clean my hdd and, as I wrote, I setup the xp pro with sp3.
Only one thing I have in my mind if the patched picc.exe wants a particular version of .net framework, I remember that the keygen for fastavr compiler v4.3 working correctly if you have installed the .net framework 2. On the other side I compare the genuine and patched picc.exe and differ only at two bytes.
At your place, the installation of the versions std and pro differ so much in the wasted size as I wrote in previous post?

regards
mitsos

Well I don't have the STD version installed right now but the PRO version is about 13.5 MB. The size is weird but the compiler performs better that the STD version. The only .net framework I have installed is version 2.0. I don't know if this install (HI-TECH PRO) has something to do with either Visual Basic or Visual Studio. I have Visual Basic 6.0 Pro, and the redistributable versions 2005 and 2007 of Visual C++. Probably these added a feature that is required by the crack, I don't know. Something I can also thing of is that despite of having a genuine Windows license, I never run Windows Update, in fact I have disabled these two services "Security Center" and "Automatic Updates". I think I don't need them and besides my old Gericom Laptop runs faster without them. Probably a recent Microsoft hot fix is preventing you from using the crack with success.

It might be very interesting to find a solution for this problem. Unfortunately, not many have reported a successful installation of HI-TECH PRO and no one else has reported the same problem you have. Probably not many people out there care for using this PRO version or probably not many have realized it is available in the forum. Hence, the title of this topic should be changed to "HI-TECH PICC PRO v9.60 PL3 crack testing" or something like that...

[mitsos]

hi
today I test the functionality of the cracked picc.exe in a different way.
During installation of picc pro 9.60pl3 I was connected to net and I get an activation for 45 days.
Then I try the led.c to pic16f873 and in the output window of MPLAB I see the:
HI-TECH C PRO for the PIC10/12/16 MCU family  V9.60PL3
Copyright (C) 1984-2008 HI-TECH SOFTWARE
licensed for evaluation purposes only
this licence will expire on Thu, 25 Sep 2008

Memory Summary:
    Program space        used    15h (    21) of  1000h words   (  0.5%)


Next I replace the original picc.exe with the cracked one and when I rebuild in the output window of MPLAB I see the:(the evalution expiry disappeared)
HI-TECH C PRO for the PIC10/12/16 MCU family  V9.60PL3
Copyright (C) 1984-2008 HI-TECH SOFTWARE

Memory Summary:
    Program space        used    15h (    21) of  1000h words   (  0.5%)

I think the cracked piccc.exe foul the program by extending the activation period to unlimited.
So the question is: in order to the cracked picc.exe working correctly, is it needed to setup the compiler with an valid activation (like the 45 days) or not?

regards
mitsos

[mbandala]

Looks like it.

[omni]

Hmm that's not so good then...

What do you do when you are not on the Net or have access to it?

I'm guessing that this activation is linked to the computer hardware in some way so copying registry keys would probably not work, or wherever it sets the evaluation data.

[mitsos]

hi

I do some simple tests:

1. I change one of activation bytes and then I build a project with original and cracked picc.exe
in both cases compiler works at lite mode and I get a big hex file

2. I finish the 45 days evalutation period by changing the date in my pc
the activated compiler returns to lite mode and by using the cracked picc.exe remains at lite mode
big hex file again

I think that is a half of a full crack. Kappa's cracks patch two exe files the picc and cgpic as you see in other versions.

waiting for a complete crack

regards
mitsos

[mbandala]

Mitsos

What you just did is giving you a false indication. In the HI-TECH website, it is said that if you change your computer's date in order to "extent" your trial period the compiler would know it and turn itself into lite mode. It doesn't matter whether you change the date back or forward, it is a change and the compiler will detect this and go to lite mode automatically. I am not making assumptions or guessing, this info is in the compiler's website. Look for it if you don't believe me.

In other words, the change of date indeed will spoil the installation. I think that the crack doesn't override the change of date. But this situation doesn't necessarily means the crack will stop working after 45 days. There is not way to say that, is there? The PL3 was released on the 29th of July.

I strongly suggest you enjoy the compiler as it is. So far the crack seems to work, doesn't it? Just apply the crack and wait. I don't know, maybe the crack doesn't work at all and we have been using the trial license since we got the compiler installed. If the compiler stops working after 45 days, the we will see what to do next. So, changing the date here is nonsense...

Right now, my installation is less than two weeks old. It means that in about a month I will really be able to drop a conclusion on the crack. In the meanwhile, I am enjoying the compiler and having fun reducing the program space of my previous projects...

[kcsoft]

I had installed and expired picc pro 9.60. When i tried to install again, at the activation page the message "Activation expired" poped-up.
Offline activation or lite mode installs ok but the produced hex file is larger than with the std version.
The workaround for this is to modify one digit in the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductID key, with regedit
then install the picc pro, activate evaluation online, copy patched picc.exe.
Until now, it works ok, windows doesnt seem to care about this registry key. I have XPSP2.
If you change the ProductID key back, picc pro will generate big hex file again.
Hope this works for mitsos too.

Maybe somebody will use this info in a patch.

[dabi]

hi kcsoft
  Do you means delete the productID key or how to modify the value?

[kcsoft]

hi kcsoft
  Do you means delete the productID key or how to modify the value?

Read carrefully:
The workaround for this is to MODIFY ONE DIGIT in the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductID key, with regedit

[hosmis]

with std9.60 PL2 :



with pro9.60.PL3 :



http://www.4shared.com/file/62030229/fc4ee43/HiTide_Error.html