Hi, I suggest that you link or mirror the amendmend of case 2:96CV645B, MS <-> Caldera, about MS pushing DRI out of the market (and playing dirty tricks with Novell when they bought DRDOS, and so on, not to mention many other things like OEM tricks, vaporware, simulated incompatibility...). In the end, Caldera bought it, called it OpenDOS, got some cash from the court but never enforced the other things (no "per CPU even if it is not with MS DOS" OEM prices, no "MSDOS+Win3.1 cheaper than Win3.1+DRDOS, although DRDOS cheaper than MSDOS" OEM prices, no hidden APIs, no pretend- to-be-incompatible APIs, ...). Pity. Basically Win95 included DOS, so other DOSes got pointless. History is repeating with Netscape/MSIE and with Quicktime/ReapPlayer/MediaPlayer and with Java/NET, to mention only a few :-((.
http://www.maxframe.com/DR/Info/fullstory/amendment.html I found this page when trying to find out which parts of int 2f.???? are needed for Win/386 compatibility. - 2f.13 int 13 hooking: done in FDSHIELD, so "incompatible DOS" message fixed - 2f.1607.0006: does HIMEM have to provide this A20 change info service? On the other hand, Win ships with MS HIMEM (the deliberate DR incompatibilty is removed after the beta, only SETUP/SMARTDRV still contain AARD check, and WIN has the check disabled, HIMEM/MSD even removed -> http://fringe.davesource.com/Fringe/NonZen_Companies/Microsoft/Tactics/1993.09.0 1.Locks_Out_DrDOS.html ...). - 2f.1607.0015 kernel instancing: Seems to be needed in full form only for kernels which ident themselves as DOS 5+ (UMB, HMA support, some data structures). Alternative seems to be 2f.1603 style instancing? What happens if no instancing is supported at all? Simply DOS boxes broken? 2f.1607.0015 has 6 functions: query patch table, ask DOS to patch itself, ask it to unpatch itself, data structure size query, data structure bitmask query, driver size query. 2f.1603 only supplies a data structure which tells DOSMGR which areas in memory are relevant for instancing. If you can comment on this int 2f.1x function list, please do. Thanks. Eric. ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
