Hi Pat,
> If you folks were to extend the DOS API, in which direction would you
> take it?
none at all
> Would you go with POSIX/UNIX/Linux, win32 or simply provide
> the same API with extensions for modern functionality and platforms?
the same good old API.
The reason is quite simple: virtually no new DOS software is written
in these days, so it wouldn't be used anyway.
And even iff new software is written, probably noone would limit the
program to FreeDOS only (with the possible exception of freedos people
themselves)
the last guys who tried that was DR, when they made a new API (in
their EMM386) with multitasking, TSRs/drivers in RAM beyond the first
megabyte, etc.
While it was nice (for DR users), that drivers would take less RAM, I
doubt anybody outside DR ever used this API.
certainly there's a lot to be done, like
support for UDF CD/DVD
support GPT disks ( >2TB partitioning, but this is worked on
already, coming soon) (actually that's fairly easy)
Robert mentioned a better (open-source) SMB/CIFS client
USB disk drivers that don't kill the USB keyboard/mouse
(read only) support for EXT3/NTFS/Reiser/Apple HFS
DOS on an Itanium (is that possible ?)
DOS on an iMAC (this might be possible)
and probably much more.
but none of this would require the change/extension of the DOS API,
and all of that would profit both new and old software.
Tom
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
