The new version works good under 4DOS now!! 8) Thanks for the fix! No issues with creating/viewing/removing files. Unloading works like a charm (and unloading the packet driver afterwards as well)
Sounds great! I'm glad it works for you.
The only small issue I ran into:
- after copying lots of files and directories (+-200 files, 20 dirs), and wanting to remove them again in one go using "DELTREE /Y *.*", not all data is removed at once
I am aware of this. In fact, this is something I already fixed a week ago, but had no time to release it formally yet (and got temporarily distracted by another retro project). If you feel courageous, you might try upgrading to latest SVN version of ethersrv (no EtherDFS change is necessary). Latest SVN version of ethersrv is here:
https://sourceforge.net/p/etherdfs/code/HEAD/ … rv-linux/trunk/ (click on "download snapshot").
Furthermore: what about LFN support? (using DOSLFN ie) Is this on your wish list?
Not really in my plans, since I do not use it myself.
Right now when I copy files from Linux to my FAT32 drive with some or all capitals or files that do not meet the 8.3 character criteria, ethersrv shows: ERROR: invalid handle, when trying to access the files from MS-DOS (which shows "Access denied" by itself).
Just a hunch: isn't this because your Linux is (wrongly) treating the file system as case-sensistive? I think there are some options that need to be passed to mount, like "iocharset" or "charset", not sure which (myself I use the "msdos" mount filesystem which works properly out of the box, but I know that vfat is trickier). Last time I tried to mount a fat drive using the vfat driver I remember Linux shouting at me "warning, this filesystem will be case-sensitive" (not exact words), this appeared in the dmesg.
I understand that is currently not possible to create LFN files from EtherDFS, but perhaps it is possible to allow EtherDFS to access LFN files? (by stripping/ignoring LFN values on access, just like MS-DOS does when Windows is not loaded)
Yes, this is definitely something that needs to be addressed. Well, the "case sensitivity" issue is, I believe, a problem of your mount configuration, but "long filename to short filename" is a feature that ethersrv would need to perform on its own. I will think about how to address that.