> Looking for feedback on creating a "software compatibility" list on > the FreeDOS wiki. Easy in ~2002. either software worked as well in freedos as in msdos, or it was a bug to be fixed.
first it was Bart and me fixing 16 Bit stuff (fixing 300+ bugs), later Michael Devore fixed a huge number of bugs for DPMI(32 Bit stuff), and Japheth clearing (most of) the rest. in ~2003, IMO most relevant bugs were fixed. > Sometimes, people say they have problems running some game or other > software on FreeDOS. sure as hell. sometimes people have even trouble to drive on the right side of the street. > Recent examples include Windows 3.11, it's not a recent example. Windows 3.11 requires some interfaces (APIs) that are a) mostly undocumented and b) neither Bart, me, or any follow up developer cared about to invest valuable lifetime. organize a 7 digit amount of $ and this might change. > and some CD-based games that use copy protection. cool. copy protection used more or less by definition undocumented/sparsely documented functions. I see no reason to invest time into this. recommend OAKCDROM instead. > What would be the best way to track these issues, and provide a way > for people to find a fix or workaround? track these issues in a single place. not scattered in a couple of non-searchable mailing lists, SLACK, or where ever... > I'm thinking of a "software compatibility" page on the wiki. I don't > think this should be a huge list of "this software works" but a > shorter list of "this software doesn't run (with default config?) on > FreeDOS" and some workarounds (if we know them). just go ahead Tom _______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
