Hi Paul, > SMB/CIFS client would be very nice, it would be nice if it also > provided some sort of standard TCP/IP implementation as well ...
The other way round - you need TCP/IP to have a network file system client like SMB/CIFS. And because a client like Samba would be TSR, you are right that it would be nice if other clients could re-use the TCP/IP stack as long as it is in RAM anyway. Yet I still think that Wattcp is a nice / widespread implementation, maybe it could be extended to do that re-use thing to save some RAM. I would not try to save disk space, though: People who run, say, LYNX for DOS should not be forced to load Samba to make their Lynx work, so I would still keep the full Wattcp stack in the Lynx binary... > 1. Trumpet TCP for DOS. > 2. Novell LAN Workplace for DOS > 3. FTP software's PC/TCP > There is also WATTCP, but that's linked directly to the application > and does not work as a TSR like the above. Eric ------------------------------------------------------------------------- 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
