Hi! > the code patterns which Windows 3.1 looks for that Eric > mentions will NEVER be there, nor should they be there, of course.
This depends a lot on WHY the patterns are searched / patched by Win3.1 ... For example the "mov ...,dx" might be to make something partially relocateable or to trap / buffer some data for partial reentrancy. The mov [...],ds ...,bx is probably similar. No idea yet what the cmp al,7 ...,9 ... is supposed to be, but it involves storing some pointer-ish data at a fixed location. The dx=ax=0 bx=di ds=es call somewhere code is probably to hook that call in question, and the last chunk is again an access to the fixed ss:2ea location, I really wonder what data is stored there. Even if FreeDOS will never contain the code as real code, it could still be added as dummy code which makes Win3.1 look at the right FreeDOS places to hook in some way - or FreeDOS could detect that it is being patched by Win3.1 and enter a "more compatible" mode then (e.g. start checksumming SFT entries to make sure that SFT and f_nodes stay in sync, or sync segment and stack values in some places if the patches mean that Win3.1 attempts to backup or relocate parts of DOSes state / code / data structures / stack / ... Please refer to the > Win3.x /3 investigations, /s ones, cool 386SWAT debugger thread for a detailled description of the pattern matching done by Win3.1 /3. Eric ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
