2Doug Bissett: No, no LFN API in OS/2 VDM, so I'm not going to provide LFN to VDM. I'm just shorten filenames, so that they will be available
to DOS/win16 programs, and convert short filenames back to long ones, so they could be accessed. Why it could lead to problems? This feature in fact, was ported from fat32.ifs, where I added the similar code for exFAT. Now I adapted the same code for vboxfs.ifs. As far as I can see, I don't see any problems it may cause, so far.
2Dave Yeo: Yes, I plan to make a command line switch to disable that in the future, but not yet. Just in case someone does not like this. So far, I saw only one reason to not do that. Imagine, you have both "My documents" and "Mydoc~3D" directories in the root directory. Then under DOS, the first one will be abbreviated to the second name, and the second name will be inaccessible. If that's not desired, you'd better avoid creating file names ending at ...~<Number>. But such names are usually not needed. So, it is unlikely if you'd ocassionally create such a file/dir.
2Martin Iturbide: So, DOS window works for you, but "winfile" traps? Strange, because "winfile" works fine for me. Could you provide
any logs? (Enable logging with "/d" switch to vboxfs.ifs, redirect COM port to a host pipe, and connect with a terminal emulator. So far,
I only aware of "putty" being able to connect to a named pipe, but Putty does not seem to have output saved into a log file. But you can
try). I start "progman" first, and run "winfile" from a Program Manager icon. Works fine for me.
PS: So far, command.com and Norton Commander work fine for me. Though, when I try to start Volkov Commander,
I get an IPE in OS/2 kernel. Seems to be a VBox bug.