Yellow-SH said:
It does nothing... There isn't another way to do it ? :/
The patched ROM is zero because the patching failed. When you use a patching script or xDelta GUI, it won't tell you if it failed and won't display the error. If you patched with the normal release of the ROM, try the DSTT/TTDS version of the patch. People having issues with the regular one have been having better luck it.
I'm starting to wonder if the DSTT/TTDS patch doesn't care if the ROM has been patched before or not. Its the only explanation I can think of for it working when the normal ROM doesn't. Sadly can't find guaranteed clean dump to test my theory.
Also, YAY v3. I read a bit of the change log and like what I see. I wish I had the time to seriously play B/W as I really want to try it out (game and patch).
UPDATE: I tried patching a clean ROM with the normal patch and it didn't work. Again, unless something is wrong with the ROM (which I doubt at this point), the patch, xDelta, or some combination of the two is causing the problem. I don't understand how its either as people are using the same patch and version of xDelta (I think) to patch what should be the same ROM. I don't know if the OS you are running might cause the problem as I've tried patching on my Mac and Windows laptop (with the same ROM and patch using the xDelta scripts and GUI that have worked for other people) and had the same results (errors out and doesn't patch).
I've read that patching with xDelta changes stuff in the ROM file. That is why you can't patch a patched ROM (usually). Does anyone know how I check what has been changed? I think its the ROM ID but can't remember. Even if it is the ROM ID, not sure how to find out what it is.