On 2/20/2023 1:03 PM, Eric Auer wrote:
Hi! As we have various drivers which use the network redirector API,
CD/DVD redirector API or both, including drivers which use those for
different purposes, which advantage do we expect from using a special
IFS API which is both "more on topic" and "less existing", as in only
very specific DOS versions may have supported it? My impression was
that things like vmsmount and etherdfs work fine without that API :-)
Also note that the low-level format is not visible through IFS, so it
does not matter whether you use FAT32, FAT16 or NTFS. However, it may
matter whether you want long file names or files > 2 GB. For those,
I hope that the usual Win9x DOS 7.x int 21 calls have counterparts in
the network and CD redirector API space of the same DOS generations.
Yes, the network redirector "hides" the actual implementation of the
remote/server side. For example, Novell Netware had a totally different
file system, with very granular permissions and longer file names than
DOS (and early Windows 95) supported. And as I mentioned in an earlier
reply to Aitor, I just can't recall right now how this was handled in
Novell. I would have to try and dig out some of my old sources for some
utilities that I wrote for Novell under DOS, including a revision
control system that we used at a former employer.
And yes, it would be interesting to check how vmsmount handles that, but
as I mentioned, that MSCDEX specification is the only "official" source
that I can find still. Unless someone can dig out anything else on any
of the multitude of MSDN CDs, which I think might be the only other
possible source. I checked (before Aitor's question) for some info on
this and could not find anything on Microsoft's web site anymore, only
404s...
Ralf
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
