The code doesn't actually care if an image is a floppy image or a hard
drive image; it's just a FAT12, FAT16, or FAT16B image and all are
supported.
There are two good use cases for floppy images:
- Mounting a driver disk temporarily over the network to copy something
from it without having to dig out physical media.
- Inspection:
- you can use the "read only " flag on the client or mark the disk
image read only on the server side to avoid accidental changes.
- You can use "session scoped writes" to simulate allowing writes and
changes, without actually changing the underlying disk image.
And don't forget ASSIGN.COM ... I've mounted a disk image using NETDRIVE
and then used ASSIGN.COM to remap the drive letter, allowing me to use
software that insisted on being run from drive A:
The journaling feature can also be used to avoid accidental changes to the
underlying image.
On Sat, Aug 17, 2024 at 1:59 AM Frantisek Rysanek <frantisek.rysa...@post.cz>
wrote:
> That's pretty cool :-)
> Needs much less conventional RAM compared to the MS LanMan.
> Resembles iSCSI or AoE or NBD, and even has "COW snapshot like"
> functionality, controlled from the client side... all of that in DOS.
> Priceless :-)
>
> The floppy emulation probably won't help in trouble cases where some
> obscure old software requires access to a physical floppy drive
> (that's where physical emulators come in handy) but even those
> marginal cases aside, this is very cool.
>
> Frank
>
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
