Eddy L O Jansson wrote:
ELOJ> Have you actually found a file which needed multiple patches? As
ELOJ> we're patching the CRT-initcode that would be kind of strange...
ELOJ> Multiple occurences would indicate redundant code _OR_ an unsafe
ELOJ> searchstring.
KF> And you would want to handle redundant code properly, wouldn't you?
ELOJ> Actually, no. I haven't done any real research, but my intuition and
ELOJ> experience tells me that the CRT.init-code (which is the one we want
ELOJ> to patch) is very likely to be located at the top of the file, and
ELOJ> thus it seems most probable that the first occurence is the only one
ELOJ> you want to patch.
KF> It's still capable of executing, after all.
ELOJ> I assume you don't 'speak' assembly, because your statement is quite
ELOJ> irrelevant. Study the searchstring and the context in which it
ELOJ> operates and you should get it.
Well then, forgive me for not understanding, but what exactly does that
string of machine code do that would only make a difference in that one
place and wouldn't matter anywhere else? And how can you be sure that
the Crt unit will always be linked in first?
Kim Forwood
---------------------------------------
Internet: kim.forwood@elab.canbbs.net
FidoNet: Kim Forwood, 1:153/831
---------------------------------------
--- Blue Wave/DOS v?.??
---------------
* Origin: The Eclectic Lab (1:153/831)
|