Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Valery Sedletski

Pages: 1 ... 3 4 [5] 6 7 ... 24
Hi all again!

I fixed the trap in TranslateName function (in code translating filenames short <-> long). Now it seems to be stable.
The  link is:

2Martin: does this build trap for you, when you using windows file manager?

Hi all!

I uploaded the new version:

Since now, you can disable the file name translation feature short <-> long with the "/h" or "-h" flag:

ifs=d:\os2\boot\VBoxFS.ifs /h

If "/h" or "-h" is set, long file names are just skipped in DOS sessions (the same behaviour like in HPFS/JFS).
Just in case someone likes this behaviour more, or just disable file name translation for stability (I have a bug
somewhere which can cause traps, in filename translation feature, So, if you add the "/h" switch, it should be
more stable until I fix the bug) and performance (file name translation use some CPU time) reasons.

2Martin Iturbide: Of course, I have some documentation on debugging, in docs/debug.txt file on the Additions ISO. It is unfinished, though.
But here is described, how to setup a log buffer in ArcaOS. If you have windows host, you'll need Putty:

Then you need to set up a COM port emulation in VBox, with mapping to a host-side named pipe. You can use this tutorial:

And also, you need to add the "/d" switch in VBoxFS.ifs, to enable COM port logging.

PS: I'm sorry, but your trap screens are useless, because this is a trap in 32-bit code, so I cannot determine, in which segment this code is located (like in 16-bit case). For having additional info, please install a debug kernel (e.g., OS/4 kernel), together with .sym files for that kernel and VBoxFS.ifs/VBoxGuest.sys. (The symbol files should be supplied together with the kernel. Also, there are .sym files for the Additions on the Addiitions ISO).

If something is not clear, feel free to ask me :)

Quote from: Martin
Now it also seems that my VM got worst, now even on OS/2 when I try to access the shared file it traps (trap2).

You have a trap even in OS/2 on the real hardware? Which file and what it is shared with?

Utilities / Re: Create an ISO from a CD
« on: July 05, 2019, 11:36:07 pm »
No, this is wrong froloff. Frolloff should be Dmitry, not Leonid

Utilities / Re: Create an ISO from a CD
« on: July 05, 2019, 09:31:47 pm »
2Doug Clark: BTW, you can use VBox with WinXP guest to run Nero, and grab and burn CD's and DVD's from it. As latest OS/2 version of
VBox has support of CD/DVD pasthrough, and CD-writing software should work fine. Anybody tested that, except me? ;)

PS: PowerDVD should work too, though, I didn't tried it.

Utilities / Re: Create an ISO from a CD
« on: July 05, 2019, 09:22:14 pm »
Yes, the latest one available from Froloff and Nickk (until they left OS/2 and didn't gave the sources to the community. Disappeared in
the unknown direction ;()

PS: BTW, this version of CDRTools supports USB CD/DVD/BD disks (tested well with my Hitachi-LG BP50NB40 Blu-ray/DVD/CD writer).
Though, better use the os2cdrom.dmd version from IBM's UDF filesystem (included in latest versions of eCS and ArcaOS), instead of
the version included in CDRTools.

PPS: On Blu-ray disks, UDF cannot format such disks as a "big disktette". UDF format just returns an "unknown medium" error. I use fat32.ifs for creating "big diskettes" with FAT/FAT32/exFAT filesystem on CD/DVD/BD rewritable disks. Just format such disks with the included FAT utility DLL  with /fs:<FAT16|FAT32|EXFAT> parameter:

format w: /fs:fat32 /v:fat32dvd

And you should be able to use such disks as "big diskettes". I reused here the CDRW read/write code from VBox. So, the same
routines are used in both programs.

2Lars Erdman: This is how file name shortening algorithm works: It removes first several leading dots from name, and leaves three characters
after last dot as an extension (and skips characters in between). So, thanslation algorithm does not misinterpret anything.

It is safe to use extension for directories in DOS. Yes, originally, there were a convention that directories doesn't have an extension. But that convention was widely "violated". "Violated" is not anything bad. Directory, in any file system, including FAT, is a file, containing the list of directory entries (excluding some exotic file systems, which don't include FAT). So, any directory can have any name, with or without extension. This is safe, because there is no difference, how files and directories are stored on the file system. And I used DOS and never saw any problems when having directories with extension. :-)

PS: Lars, this is not my own algorithm, it was invented before me by Henk Kelder and Ko Myung Hun. It was worked for at least, a decade before I joined the fat32.ifs project. Nobody still complained, so far. I only enhanced this algorithm for exFAT (as exFAT, opposite to VFAT, does not contain short file names along with long ones. So, I added a bit of new code, generating the short file names from long ones, and restoring them back. The idea was got from -- see "Fabricating a short file name").

2Martin Iturbide: I just found that if I start "svn up" in the VBox source directory, and then enter the same directory with FC/2, I get
a trap. Maybe, you have the same with "winfile.exe", so you're accessing the same directory with some other program at the same
time? Also, please check that it doesn't trap if opened with "winfile.exe" only. You can try several times, to discard false results.

Utilities / Re: Create an ISO from a CD
« on: July 05, 2019, 03:02:44 pm »
2Andre Heldoorn: No, on Hobbes I see an older version. This one is uploaded at

Storage / Re: changing USB volume letter
« on: July 05, 2019, 01:02:10 pm »
Also, you can try a shared folder "drive letter pinning" feature:

Just create a vboxfs.cfg file in your \os2\boot directory, with the following contents:

exch            e:
os2f             f:
valerius       m:

etc. So, format is "<shared_folder_name>     <drive_letter>:".
So, all specified shared folders will take a specified drive letter. So, you could assign them the way they will not conflict.

Utilities / Re: best process killer application
« on: July 05, 2019, 12:48:39 pm »
2Dave Yeo: WatchCat works fine with both PS/2 and USB keyboards with a wccall.exe utility from ErOS2. If someone interested, I can share it.

Utilities / Re: Create an ISO from a CD
« on: July 05, 2019, 12:38:31 pm »
Me, together with Rich Walsh, would also suggest to use "readcd f=iso_image.iso dev=HOST,ID,LUN -retries<NUM>", which
is the easiest way to grab CD's to an ISO image. Probably, you'll need the latest CDRTools to support DVD's and BD's.

I have CDRTools version 2.01.01a59. I see an older version at Hobbes. So, maybe I should upload it somewhere?

PS: DVDToys are just a frontend to CDRTools, and cost some money. So, I'd better use CDRTools directly.
PPS: Though, I own a DVDToys license :)

BTW, you'd better use this build:

It contains a small fix for a starting point for a counter which is after a tilde. It was zeroed-out sometimes incorrectly, so
some dirs or files were inaccessible (ERROR_PATH_NOT_FOUND). Now it should work.

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, 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.

Hi all!

I added a new release:

The feature added is path translation: long <-> short filenames for OS/2 VDM. Now for DOS processes,
paths are abbreviated as 8.3 file names. Each name is abbrevited, plus a dir entry number is added after
a tilde, so using that number, names can be converted back to long ones.

So, now all file names are accessible from DOS.

Please test.

Pages: 1 ... 3 4 [5] 6 7 ... 24