View Single Post
Old 04-27-2018, 09:36 PM   #41
dmapr
Evangelist
dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.
 
Posts: 469
Karma: 600816
Join Date: Sep 2009
Device: Kobo Aura HD, Kobo Aura One
Quote:
Originally Posted by jackie_w View Post
Wouldn't that be less flexible? The FindBaseAddress is used to get you to the vicinity of where the patching needs to happen and needs to be unique. Depending on the specific patch, using the Offset value, the Find/Replace values may (sometimes) be much shorter strings and more specific
Sorry, I didn't make my intent clear. I was thinking that it could be an optional field which would allow both the use case that you're describing and the one I was referring to. Basically "only provide it when it's different from the FindBaseAddress".
dmapr is offline   Reply With Quote