they might be on to you already , if you download ver 1.33 from the archive you now get ver 1.32b
and the hack does not fit the latest. which is ver 1.34
they might be on to you already , if you download ver 1.33 from the archive you now get ver 1.32b
and the hack does not fit the latest. which is ver 1.34
Warning I'm not a teacher
I’ll have to get that!
Meanwhile, can you back up a version from 1.32b to 1.32?
Windows:
Same file location in Windows directory structure.
Find file offset 0x1623AE, change 0x85 to 0x84.
For them to have truly deliberately blocked a weakness, the new version would not have the 0x85 value in a close location (for the new version),
and/or changing it to 0x84 would have no effect. There’s a completely different method though, they would have had to stop both.
It’s probably best if certain words are never mentioned in this thread to it isn’t found,
such as the word that describes what happens to an egg shell when you hit it.
You should have a message Richard, but the second method might also break XC8 (untested).
All integrity would be lost if that was posted in public.
If you can determine that is also GCC compiler it doesn’t matter, but I seriously doubt it.
If that no longer works, they have definitely found it, and I guess I can’t update![]()
In their archive (http://www.microchip.com/development...nloads-archive) there are all software versions available since 1.0 for all software packages.
But I wonder, what are they doing? Is it legal to grab an open source and sell it 1K?
Ioannis
It’s not illegal to include it in your own project and sell it so long as you provide the source (which Microchip do).
That part is still moral thuggery, but technically there’s nothing wrong with it.
But you must also provide full source and any modification made to it for your project, and any scripts required for anyone else to compile it themselves,
and must not take any steps to make it difficult for anyone else to compile.
This has occurred at least twice in the history of Microchip distributed GCC, and that is illegal.
Richard is saying if you download the v1.33 package right now, you actually get v1.32b in it.
The first part Ioannis, you can liken that to you writing some program for free, and giving it away to everyone including source.
Then I take it, deliberately cripple it (disable some nice features), and charge people a fee to un-cripple it for them, all without your knowledge.
Unfortunately GNU licensing didn’t really accommodate this situation, and it's legal, but you wouldn’t think much of me for doing it if you found out.
Last edited by Art; - 28th April 2018 at 09:55.
Hi
For help with latest versions:
github.com/cv007/XC3216
XC8 is definitely not GCC.
The Mac OS version is missing form the document on Github, and I have found it myself:
XC16 v1.34: offset: 0x64D8E7. Change 0x85 to 0x84.
Cheers![]()
Bookmarks