> Also, a thought on the topic of Windows 3.1 drivers: what is the > feasability of reverse-engineering an existing video driver to work > out what the interface is? I guess the interface would be simple, at > least relative to Windows XP :) I guess it may still be quite hard. > Of course this requires the developer to live in a country where > reverse engineering is allowed. At least this is one of those cases - > for the purposes of making interoperable software - that laws often > permit.
Maybe it would be easier to create a opensource Windows 3.xx clone from the beginning. ReactOS and WINE code are available to download and these have implemented the Win 16 API. > Finally, is anyone else concerned about links to illegally-copied > software being posted on this mailing list? Perhaps it is bad for > FreeDOS's reputation? Perhaps we could get in trouble with the > SourceForge folks? Sorry if I am speculating about things that are > none of my business! I just note that in some countries and with some > service providers/sites you can get in trouble just for posting links > to things. You are right, I'm sorry for my post. I won't repeat any similiar subject anymore. By the way, could anybody explain me the differences between the 2 versions of PTS-DOS 32 existing nowadays? Another question, has the FreeDOS beta 0.9 cd lite version drivers for USB, network and DHCP? ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
