Hello Eric, > I am actually surprised that nobody seems to care about the > buggy int 15.87 simply because HIMEM accidentally hides that > bug. because noone is allowed to use int 15.87 after HIMEM took complete control over it.
> Would be very strange if ALL XMS drivers out there, there aren't that many XMS drivers in the freedos world > except FD*XMS*, would explicitly set DS=ES before calling > int 15.87, because they knew that FD EMM386 would have a bug. it's unlikely that HIMEM.EXE was changed due to buggy EMM386 ;) > PS: I assume that only certain exotic DOS extenders and maybe some DR DOS > tools (which you can configure for 1. XMS, 2. EMS and 3. INT15 usage) would > be affected by the int 15.87 bug AFTER loading a bug-bug-compatible HIMEM / > EMM386 pair, EMM386 won't even load without HIMEM present. thus noone is allowed to call int 15.87 when emm386 is loaded. > simply because many programs stop using int 15.87 as soon as > more DOSy memory types like EMS, XMS or VCPI become available. and the int 15 memory isn't available any longer tom ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
