For god's sake stop posting huge images, just resize them. Your problem is obvious, see attached image.
In windows explorer, Tools->Folder Options->View and uncheck "Hide extensions for known file types" (of course you will have to translate that for your language )
Then you will see the file you created is named 658597E2.pnach.txt so just remove the .txt at the end and it will work.
(08-04-2010, 09:18 AM)Bositman Wrote: For god's sake stop posting huge images, just resize them. Your problem is obvious, see attached image.
In windows explorer, Tools->Folder Options->View and uncheck "Hide extensions for known file types" (of course you will have to translate that for your language )
Then you will see the file you created is named 658597E2.pnach.txt so just remove the .txt at the end and it will work.
08-05-2010, 04:46 PM (This post was last modified: 08-05-2010, 04:50 PM by Saiki.)
.Hack/Infection (supposedly the other 3 as well, as the data may not move, NOT tested)
Important note: DISABLE CHEATS when loading this patch, it will produce TLB miss errors upon boot.
to use this patch do the following:
Open infection WITHOUT CHEATS, get to the title screen, PAUSE emulation, apply cheats, resume, enjoy.
Drain count and Experience cheats recommended to be used in phast/artmoney or another program and injected, these codes are correct, but untested in the patch engine.
08-05-2010, 05:17 PM (This post was last modified: 08-05-2010, 05:19 PM by vsub.)
Um...so does pcsx2 actually work this way(not using the whole value 8 digits value but only 2 digits value).
And if it does,then why did you use short?
byte - 2 digits value
short - 4 digits value
word - 8 digits value
08-05-2010, 05:48 PM (This post was last modified: 08-05-2010, 06:22 PM by nosisab Ken Keleh.)
Yes, and probably it's the reason for the TLB error. But not the only error, the addresses are meaningful too: Byte addresses can go anywhere, short must be in multiples of 2 and word in multiple of 4 address.
Even if it is possible to dispense the leading zeros the 'short' where it's effectively a byte (the address offset sequence lets no doubts about that) it erases the next, that's less perceptible because the sequent code corrects the error introduced by the former... but not in the last.
Does not matter, it's always an error, it becomes still more perceptible if you comment one or some those codes, for instance.
There is an easy way to certify the correct length to use, that's verify the leftmost digit in the original code address field.
if it is 0 the length is byte. If 1 the length is "short" and if it's 2 the length is "word", if any other value it must be used "extended" although not warranties the actual code works.
By the other hand, it's possible to use "extended" for every code but in this case that leftmost digit in the original code is meaningful and must NOT be replaced by 0.
to be in the secure side, always use the four bytes (complete word) with all the leading zeroes, despite the actual operand length.
PS: although not meaningful information afaik for pnach files, this may be useful information for those that uses cheat engines and hex editing. As already told the byte is represented by 2 hexadecimal digits. Now, each the digits is named a nipple and some actual implementations in a game may use nipples as the actual storage area length. BTW the nipple is half a byte, a four bits length value and can be in either half of the byte. Extending yet more the concept we come to the lesser degree of digital information is the bit and when used this way they form the 'flags'.