patch for Hitech picc std v9.60pl2

[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