I shall be truly a 30ina not know which post, and then you still advice to a range not protected, at least we avoid the splash of SS that is, placing a range unprotected automatically when I compile the file with the sign SIS me also and being an unprotected range does not serve either move from SS then once created just run it in the mob.

Another thing, I do not know what you're uid, but I for the first tests I put to shakeme and I noticed that gave me the certificate error while accepting the plea was that two applications can not have the same uid, it is as short want to go in two conteporan in a large 1 meter and a half, who is still first and the other not, then anyone who might give a different look at the file to read the table below carry over and use a uid unprotected those V9 Unprotect uid allocation.

enclosed two rotateme changed, I just noticed that there are two things that I did not come back ... 1 package complete with sis saw sisxplorer in Size from changing every time you make a change, which could be assumed that invalidate a control of the changes since the code that tries somehow package file .
2nd that the check is always that the exe file, oh shit I'm writing while I relate! 99 out of 100 I found the error! Bischeri of us! check in the exe file is the original, while the package system changes! in the original package you check the system and that of the same! as I did not see it! member, even you, that I with decimals not find me there! 2 are the solutions, check or change the whole package system once created by a hex editor, or the change to ex!

then you always do when I write a check on the starboard

changes in the various uid here and there, even in creating the package, then as we were doing so far, once the packaging with the laws sisxplorer you say what is the check of the package, in short, changing the uid nell'header he will automatically re check but not the same and the result are in conflict, then just take the package that you just completed hex are open the exe and recompiling again!


Related Posts :



0 comments