# OS2 World Community Forum

## OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: Valery Sedletski on November 02, 2018, 11:30:29 pm

Title: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 02, 2018, 11:30:29 pm
Hi, I'm currently developing a VBox shared folders IFS for OS/2 guest. It is not
finished, yet, and I'm adding the fixes currently to it. But it is mostly working
already, and copying files from/to shared folders works. The current link is here:

Many people needed the VBox additions, so it should be a
great help for them. So, if anybody wants the OS/2 additions,

You should add these statements to config.sys:

Quote
rem The main VBox additions driver
device=d:\os2\boot\VBoxGuest.sys

rem The shared folders IFS
ifs=d:\os2\boot\VBoxSF.ifs
run=d:\os2\VBoxService.exe

rem VBox Mouse driver
rem device=d:\os2\boot\mouse.sys
device=d:\os2\boot\VBoxMouse.sys

In case you have amouse.sys instead of mouse.sys, comment it out too.

Also, for video integration, there is a VBox GRADD driver, vbxgradd.dll. In case
you have SNAP installed, you should have the following lines in config.sys:

Quote
set greext=sddgrext

In case you have panorama installed, you should have these lines

Quote
set greext=panogrex

To install the VBox video driver, you need to comment the above lines out
and change them to the following ones:

Quote

Also, if you have SNAP installed, you can comment sddhelp.sys. But then, you
also need to comment out/remove the

Quote
#includecode "sddpmi.dll"

from \os2\svgadata.pmi file and change it to

Quote
#includecode "genpmi.dll"

Otherwise, sddpmi.dll will load, and try to open sddhelp.sys driver, and
fail, so, it will stop with an error message. To avoid this, you need to change
sddpmi.dll to genpmi.dll in svgadata.pmi file.

Alternatively, you can just set your video driver to GenGRADD first with
"setgradd" command in command line (you need to boot into command line
for this), or use corresponding menu item in Recovery choices screen.
Recovery choices appeared in eComStation, only. Older versions of OS/2
have setvga.cmd command and "Set video to VGA" option, only. But you
should use a GRADD video driver, so "Set video to VGA" option is not
suitable in this case.

VBoxService.exe should be on PATH, of course. Note that VBoxSF.ifs has the following
command line switches:

Quote
/V       verbose init (enable messages)
/Q       quiet init (disable messages)
/D       output debug messages to VBox log, and also to QSINIT/OS4/ArcaLDR built-in log.
In case QSINIT/ARCALDR or OS/4 kernel are not available, the messages are directed
directly to COM1
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on November 04, 2018, 03:38:07 am
Hi Valerius.

I'm trying it on a Windows 10 Host (VirtualBox 5.2.20) and ArcaOS 5.0.1 as a guest.  But I put all the files on C:\Programs\VBox2.

I used to get the trap I'm attaching when the PMSHELL loads.  But it got fixed when I updated to Panorama 1.11.

How is supposed to mount the drive on the OS/2 guest? Something like "net use x: \\vboxsvr\share" ? Which protocol is it needed for this, NETBIOS ?

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 04, 2018, 09:32:19 am
Hi, I'm currently developing a VBox shared folders IFS for OS/2 guest. It is not
finished, yet, and I'm adding the fixes currently to it. But it is mostly working
already, and copying files from/to shared folders works. The current link is here:

Many people needed the VBox additions, so it should be a
great help for them. So, if anybody wants the OS/2 additions,
………………………………………..

Good, Vbox guest additions for os2 is one of my unsolved task .  Tried to install the official ones I had an unrecoverable trap stop on rebooting similar to what shown by Martin here above, and would be nice having more luck with these.
Would you please provide more detailed installation instructions? I see some executable and some other system files in the two directories (I presume to be copied in respective OS2 root ones) plus you explaination on how to edit the config sys, but I'd need -and maybe others as well- a more comprehensive installation guide.  Thank you much
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 04, 2018, 01:37:45 pm
2Martin: You don't need Panorama, as VBox uses it's own video driver. Though,
you can install Panorama (or SNAP) first, and replace its GRADD driver with that
from VBox. VBox video driver can be installed over any existing GRADD driver,

So, you had that trap in PMDD if you install vbxgradd.dll without prior install
of Panorama?

Quote
How is supposed to mount the drive on the OS/2 guest? Something like
"net use x: \\vboxsvr\share" ? Which protocol is it needed for this, NETBIOS ?

Shared folders are attached like this:

Quote
VBoxSFAttach w: 1.-os2

in your case. Though, it is usually not required. All shared folders you specified
in the VM config will be mounted automatically.

NETBIOS has nothing common with shared folders. You don't need to install
any network protocols for them. Shared folders is the VM feature. The VM
exposes some host machine disks to the guest. To access them, the shared
folders IFS calls API's in VBox. So, the guest just communicates with the host
side. There are special services run on both, the guest side, and the host side.

PS: I tested it successfully with VBox 5.2.20 on Linux host. The additions are
built with 5.0.51.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 04, 2018, 01:55:33 pm
2mauro: There are the instructions in the official readme on Oracle's Additions ISO,
though, it is brief too. Mine is even more thorough :) Not sure, what's not clear for
you? You should copy all the files in respective directories (or somewhere to \programs,
or whatever directory you use for installing apps). Only vbxgradd.dll should be on the
LIBPATH. Any other programs can have arbitrary location. You should have any GRADD
good).

You need to use VBoxMouse.sys instead of mouse.sys (just comment it out). So all you
need is the following statements in config.sys:

Quote
device=\...\VBoxGuest.sys
device=\...\VBoxMouse.sys
ifs=\...\VBoxSF.ifs

You should comment out mouse.sys and the "set" line for your previous GRADD
driver. If something is not clear, please tell more specifically :)

PS: And yes (I forgot to mention), you need the latest kLIBC and libcx installed

> Tried to install the official ones I had an unrecoverable trap stop on rebooting
similar to what shown by Martin here above, and would be nice having more
luck with these.

The trap in PMDD usually means that you have your video driver misconfigured.
So, you only need to install it correctly.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on November 04, 2018, 03:11:54 pm
Hi Valery

Quote
VBoxSFAttach w: 1.-os2

The command mounts the W: drive, but it shows empty in the GUI (known issue #1, right?). On the command line it list something but without file names (Check picture)
I'm not sure if there is another requirement that I'm missing. Anyways, it looks very promising.

A thing that got broken with this version of "VBoxGuest.sys" is the bidirectional "Shared Clipboard" can you also check if it is working for you?

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 04, 2018, 03:54:20 pm
2Martin: Are you sure you started VBoxService.exe successfully? You should add it to
startup.cmd, otherwise Additions will not work. VBoxService.exe automounts all shared
folders, so you don't need to mount them manually. Also, it handles the shared clipboard
too. If shared clipboard is not working, then most probably, VboxService.exe is not
running.

> The command mounts the W: drive, but it shows empty in the GUI (known issue #1, right?). On the command line it list something but without file names (Check picture)
>I'm not sure if there is another requirement that I'm missing. Anyways, it looks very promising.

As I said, WPS Drives object is not working at the moment. CMD.EXE doesn't work too, indeed
(because not all DosFindFirst flags are working yet). But File Commander/2 and 4OS/2 work fine.
Also, command.com and Volkov Commander show file listings in a VDM (though, the file name
translation short <-> long is to be implemented, yet -- similar way as it's done in fat32.ifs for
exFAT).

PS: Hm, indeed, looks like shared clipboard is not working, even with VBoxService.exe running.

PPS: It appears that VBoxService.exe quits after it mounts the shared folders. Need to see why.
This is the reason why shared clipbord is not working -- it requires a running VBoxService.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 05, 2018, 09:05:41 pm
2mauro: There are the instructions in the official readme on Oracle's Additions ISO,
though, it is brief too. Mine is even more thorough :) Not sure, what's not clear for
you? You should copy all the files in respective directories (or somewhere to \programs,
or whatever directory you use for installing apps). Only vbxgradd.dll should be on the
LIBPATH. Any other programs can have arbitrary location. You should have any GRADD
good).

The trap in PMDD usually means that you have your video driver misconfigured.
So, you only need to install it correctly.

ok , understood.   Trying and see what happens is not a problem, in case of disaster I will revert to the stepback just saved.
Thank you, I'll let you know as I will take the time for doing this.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 06, 2018, 08:18:06 am
2mauro: There are the instructions in the official readme on Oracle's Additions ISO,
though, it is brief too. Mine is even more thorough :) Not sure, what's not clear for
you? You should copy all the files in respective directories (or somewhere to \programs,
or whatever directory you use for installing apps). Only vbxgradd.dll should be on the
LIBPATH. Any other programs can have arbitrary location. You should have any GRADD
good).

The trap in PMDD usually means that you have your video driver misconfigured.
So, you only need to install it correctly.

ok , understood.   Trying and see what happens is not a problem, in case of disaster I will revert to the stepback just saved.
Thank you, I'll let you know as I will take the time for doing this.

again: "the system detected an internal processing error".  Sorry, too tricky for me, hope wil find in the future an automated installation routine.  Thank you anyhow.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 06, 2018, 09:57:37 am
2mauro: No fully automated procedure. I'd avoid automated config.sys modifications.
It should be modified by hand, because it's easy enough. Uninstalling drivers in case of
problems is easy too. You can boot to command line and fix your config.sys. It is not
windows, everything is user-controlled. So, please set up your video driver correctly,
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 06, 2018, 01:15:09 pm
2mauro: No fully automated procedure. I'd avoid automated config.sys modifications.
It should be modified by hand, because it's easy enough. Uninstalling drivers in case of
problems is easy too. You can boot to command line and fix your config.sys. It is not
windows, everything is user-controlled. So, please set up your video driver correctly,

yes Valery, I agree with the OS2 system concept (since 1996, it was the preinstalled OS in my first pc) like I approve Linux philosophy using it as well.  I already have recovered the well working OS2 system version making an .ova backup just yesterday as I presumed this situation.  I'd like to manage something a bit less complicated when-where possible.  I'm getting a very precious help here and could configure some software with the users suggestions whom I'm happy to deal with.  Returning on this specific issue, believe the trouble consists in uncorrect editing of the config.sys and startup.cmd (I have a blank one, no script in it), even if your explaination appeared to be clear enough for that. I then feel confident to have positioned the files in the right paths, and also had created a C:\OS2\OS2Addition where to place the exe files as recommended by the original VBox Guest instructions.   The only way to resolve in my case, I think, would be submitting to you my config.sys and startup.cmd to be correctly edited, understanding meantime that it is not a simple favour to ask for.   ::)
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 06, 2018, 02:54:38 pm
2mauro: Why do you need to backup the VM as .ova? It can be fixed without that -- using the
same techniques you use with OS/2 on real hardware. So, all you need is return your config.sys
as it was before your modifications. You remember what did you modified, don't you? You can
always boot OS/2 to the "recovery choices" menu and go to the command line, and edit your
config.sys. (As always, press Alt-F1 when the white brick with the "OS/2" caption on right appears.
So, the "recovery choices" menu should appear. Then choose "F2" to boot in the command line.
Didn't you used it before? Once you're booted into the command line, you can start tedit, FC/2,
or any other text editor you like). And you return your video driver back to GENGRADD or VGA
from the "recovery choices" menu, in case of any video driver troubles. So, you could return
to a GENGRADD driver, then replace it to VBXGRADD, as I described before.

PS: You can post your config.sys, i could look at it. Startup.cmd doesn't matter, most probably.
I doubt it can make any troubles. All you need from it is start VBoxService here. It looks like you
have video driver troubles. So, revert to GENGRADD and try installing the additions again.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 06, 2018, 08:41:21 pm
2mauro: Why do you need to backup the VM as .ova? It can be fixed without that -- using the
same techniques you use with OS/2 on real hardware. So, all you need is return your config.sys
as it was before your modifications. You remember what did you modified, don't you? You can
always boot OS/2 to the "recovery choices" menu and go to the command line, and edit your
config.sys. (As always, press Alt-F1 when the white brick with the "OS/2" caption on right appears.
So, the "recovery choices" menu should appear. Then choose "F2" to boot in the command line.
Didn't you used it before? Once you're booted into the command line, you can start tedit, FC/2,
or any other text editor you like). And you return your video driver back to GENGRADD or VGA
from the "recovery choices" menu, in case of any video driver troubles. So, you could return
to a GENGRADD driver, then replace it to VBXGRADD, as I described before.

PS: You can post your config.sys, i could look at it. Startup.cmd doesn't matter, most probably.
I doubt it can make any troubles. All you need from it is start VBoxService here. It looks like you
have video driver troubles. So, revert to GENGRADD and try installing the additions again.

ok, I sent to you my config,sys lines in a private message, thank you.
I keep my mind that saving the machine status in .ova format (if you work in Virtual Box) just before a system update that could prevent to reboot it again, is the more pratical way to obtain the machine as it was before the change.  3 minutes to create the .ova image, 2 minutes for restoring it, if necessary. I know how to go in OS2 recovery menu, I did once, then I do not know how to operate for editing by command line.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 07, 2018, 02:00:20 am
2Mauro:

> ok, I sent to you my config,sys lines in a private message, thank you.

Your config.sys looks ok. But I asked for a modified config.sys which causes your system to trap.
So, it's bad that you have it restored to the previous state. Did you BTW commented the

Quote
set greext=panogrex

line? It can cause a trap in PMDD too, because panogrex.dll is a Panorama part,
you should disable it if you use another video driver.

Quote
I keep my mind that saving the machine status in .ova format (if you work in Virtual Box) just before a system update that could prevent to reboot it again, is the more pratical way to obtain the machine as it was before the change.  3 minutes to create the .ova image, 2 minutes for restoring it, if necessary. I know how to go in OS2 recovery menu, I did once, then I do not know how to operate for editing by command line.

Don't you know how to start FileCommander/2 or another VIO-based file manager? Having it in your
system is a must. It's possible to use a command line, only ("cd" and "dir" commands are all you need),
then use "tedit" text editor, which is present in every system (just run "tedit c:\config.sys"), but FC/2 is
easier. You just add it to PATH and all you need to do, once in the command line, is to start "fc".

Too bad that you cannot use simple shell commands. I thought, every OS/2 user knows them. It's
the basic skills every user should know. If you don't know it, I could not help you :(
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 07, 2018, 06:57:29 am
Ok, I take your recommendation to get FC/2. Yes, I commented 'set greext=panogrex' as 'rem set greext=panogrex' , like I did the rest of the editing in the config.sys.
As necessary, if you say so, I would also repeat my editing and send you the modified config.sys.
Thank you
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Doug Bissett on November 07, 2018, 11:04:57 pm
I gave this a quick try. It is certainly not ready for "prime time", but it is a decent start. It will deserve more test time.

The biggest thing, that I see so far, is that a DIR command (in CMD.EXE) is totally unusable. Using packages like 4OS2, or FC/2, in a VBox system, is far from ideal., but it is okay for testing something like this. The final product must use the basic OS/2 programs, with no extras.

I will comment about testing software, If you are going to test software, be sure that you understand what you are testing, and how to recover from a user error, or a software error. Working with VBox makes it much easier to recover, because you can copy the VDI file somewhere safe, and simply copy it back over the damaged VDI file. The instructions, at the top of this thread, assume that the user knows how to modify CONFIG.SYS, and put files in the proper place (even when they are locked by the running system). If you don't know those basics, I would suggest that you don't waste your time, or the time of the developer, because he doesn't have the time to teach you those basics. Perhaps, open a new thread, asking how to do whatever you need to do, then come back to the testing thread, with proper feedback.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 08, 2018, 12:24:29 am
2Doug Bissett: Yes, file listings in WPS Drives object and CMD.EXE doesn't work yet. Use 4OS/2 and FC/2 for now.
Anyway, FC/2 and 4OS/2 are not "extras" but are "must have" programs. Of course, it should work in standard
programs like CMD.EXE and WPS, but not all at once. It will work later. It is just easier to make FIL_STANDARD
and FIL_STANDARDL DosFindFirst options work first. WPS does also require EA's to work, it seems. But no EA's
support in VBox, AFAIK. So, it is more difficult to make WPS and CMD.EXE working. But it will work later.

PS: Yes, agree with the 3rd paragraph, too. What I could add here is except for backing up the .vdi file,
or exporting it to .ova and then reimporting, in case of problems, there is also a snapshots feature in VBox. You
can take a snapshot of a VM (just like checkpoints in windows restore), then revert to any checkpoint.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 09, 2018, 07:02:08 am
…….. in case of problems, there is also a snapshots feature in VBox. You
can take a snapshot of a VM (just like checkpoints in windows restore), then revert to any checkpoint.

Valery, afaik,  you can resume from a snapshot only once you are in the working system, so it is not for a non-booting system recovery.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Doug Bissett on November 10, 2018, 05:35:35 am
Quote
Anyway, FC/2 and 4OS/2 are not "extras" but are "must have" programs

They are "extras", and neither one is a "must have". IMO. They are not part of OS/2, they are added later. I usually install 4OS/2, but I never use it. I haven't even thought about FC/2, for a number of years. I wasn't impressed with it then, and I see no good reason to try it now.

I will wait for you to fix your program, there are other ways to accomplish what shared folders does.

As I said, it looks like a good start, but it certainly isn't ready for general use.

Quote
there is also a snapshots feature in VBox.

There are a few ways to do that. I find it easiest, to just copy the VDI file, and copy it back if something goes wrong. Snapshots are too permanent, and end up taking up space in my backups. Export/Import has a few problems too, like converting VDI files to VMDK files, which work okay, but if I wanted VMDK files, I would have made the disk image use that format initially. I am not saying that either method is wrong, or bad, I am just saying that copying the VDI file is easier.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 10, 2018, 07:43:23 am
2Doug Bissett:

Quote
They are "extras", and neither one is a "must have". IMO. They are not part of OS/2, they are added later. I usually install 4OS/2, but I never use it. I haven't even thought about FC/2, for a number of years. I wasn't impressed with it then, and I see no good reason to try it now.

OS/2 without FC/2 and 4OS/2 is non-usable. CMD.EXE has a lot of limitations, and it does even not support
command autocomplete. It has only basic  required features. So, 4OS/2 should be used instead. It is free,
open source and no reason not to use it by default. It was included into eCS by default too.

WPS is not at all intended to be a file manager. It only serves as a convenient program launcher, using a desktop.
Copying files with WPS is slow and inefficient. So, it anyway requires an external file manager. But GUI file managers
like Larsen Commander and File Manager/2 are even less usable that Norton Commander clones, like File Commander/2
is. FC/2 has very optimized and convenient hotkeys and using it instead of GUI file managers is far more efficient.

And FC/2 can be started from command line, when booting into Recovery Choices menu. So, it is very useful
and convenient for system repair too. In my opinion, Norton-like file managers are most usable ones, so I use
File Commander/2 and Dos Navigator/2 in OS/2, Volkov Commander, DOS Navigator and Norton Commander
in DOS, Midnight Commander under Linux, and Far Manager is the best under Windows.

Quote
There are a few ways to do that. I find it easiest, to just copy the VDI file, and copy it back if something goes wrong. Snapshots are too permanent, and end up taking up space in my backups. Export/Import has a few problems too, like converting VDI files to VMDK files, which work okay, but if I wanted VMDK files, I would have made the disk image use that format initially. I am not saying that either method is wrong, or bad, I am just saying that copying the VDI file is easier.

Snapshots can be deleted, if not required anymore. And the space used by them can be freed by compacting
the disk image. There is a "compact disk image" feature for that.

2Mauro:

Quote
Valery, afaik,  you can resume from a snapshot only once you are in the working system, so it is not for a non-booting system recovery.

You can restore from a snapshot any time. You can do it with VBoxManage:

Quote
https://www.vleeuwen.net/2012/12/virtualbox-snapshots-using-the-cli

Also, IIRC, this is possible to do the same from GUI. Just start the VM and "restore from a snapshot"
can be choosen from its menu.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Doug Bissett on November 10, 2018, 07:56:55 pm
Quote
OS/2 without FC/2 and 4OS/2 is non-usable.

Sorry, but I don't agree with any of this.  FC/2 and 4OS/2 are no better than CMD.EXE, and the WPS. RSYNC can be useful, but it has a different purpose. If you like them, by all means use them. I will use what I find works best, for me. This is OS/2, after all.

I avoid anything that even hints that it is like a NORTON program. Many years ago, when antivirus was a new thing, I found that NORTON was causing more problems than it fixed, or prevented. From what I have seen, over the years, that hasn't changed. Clones, of course, should not have those problems, but I avoid them anyway.

BTW, 4OS/2 doesn't display directory information (for a shared drive) any better than CMD.EXE does (that is, no file names). At least CMD.EXE formats what is shown, in a more readable way. I find the 4OS/2 DIR to be distracting, on normal directory displays. I do hope that you an come up with something that works better than what SAMBA does.

Quote
Snapshots can be deleted, if not required anymore. And the space used by them can be freed by compacting the disk image. There is a "compact disk image" feature for that.

True, but it is all time consuming maintenance, that needs to be done before I can do a backup. At least OS/2 doesn't use up large amounts of disk space for garbage, like windows does, so compacting doesn't need to be done as often (after spending a lot of time cleaning out the garbage), when you don't use Snapshots. Copying the file, to a place that doesn't get backed up, is still much easier.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: OS4User on November 10, 2018, 09:40:28 pm
OS/2 without FC/2 OS/2 is non-usable

I agree,  if one needs to manege files fast and often FC/2 is  the best choice.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 11, 2018, 01:21:56 am
2Doug Bissett:

Quote
I avoid anything that even hints that it is like a NORTON program. Many years ago, when antivirus was a new thing, I found that NORTON was causing more problems than it fixed, or prevented. From what I have seen, over the years, that hasn't changed. Clones, of course, should not have those problems, but I avoid them anyway.

Norton causing problems? I did not saw any problems with Norton. So, what do you mean? So, is there any alternative
for Norton clones? Do you think that using a bare command line is better and more efficient? I doubt that.

Quote
BTW, 4OS/2 doesn't display directory information (for a shared drive) any better than CMD.EXE does (that is, no file names). At least CMD.EXE formats what is shown, in a more readable way. I find the 4OS/2 DIR to be distracting, on normal directory displays. I do hope that you an come up with something that works better than what SAMBA does.

??? My version displays directory listings fine. I'm using 4OS/2 OSE, osFree version. Maybe, your version is different
and it uses different switches for DosFindFirst?

My version of 4OS/2 uses FIL_QUERYEASIZE == 2, and FC/2 uses FIL_STANDARDL == 11. command.com
and Volkov Commander in a DOS session use FIL_STANDARD == 1. These do work.

CMD.EXE uses FIL_QUERYEASIZEL == 12, WPS uses FIL_QUERYEASFROMLIST == 3 -- these won't
work, yet.

PS: just checked another version of 4OS/2 (version 4OS2 3.08.3-shl), it uses FIL_QUERYEASIZEL,
like CMD.EXE. So, it doesn't display file names too. Probably, you have the same problem.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 11, 2018, 02:25:52 am
PS: BTW, I fixed FIL_QUERYEASIZEL now, so file listings in CMD.EXE and some versions of 4OS/2
are working now. The problem was very simple. It was a oNextEntryOffset field in the beginning of
FILEFINDBUF4L structure. DosFindFirst returns it, but an IFS should omit it, it is added later by the
kernel. It was returned by FIL_QUERYEASIZEL, but was ommited by FIL_QUERYEASIZE, so the
latter worked, and the former didn't work. Now FIL_QUERYEASFROMLIST/FIL_QUERYEASFROMLISTL
are in the queue. Should be fixed soon. (The layout of data returned by these two options is the
most complex, so it's harder to implement it).
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Doug Bissett on November 11, 2018, 07:34:05 am
Quote
PS: just checked another version of 4OS/2 (version 4OS2 3.08.3-shl), it uses FIL_QUERYEASIZEL,
like CMD.EXE. So, it doesn't display file names too. Probably, you have the same problem.

I have 4OS/2 3.08.4-shl, which is the officially supported version, that comes with ArcaOS 5.0.3.

Quote
I fixed FIL_QUERYEASIZEL now, so file listings in CMD.EXE and some versions of 4OS/2
are working now.

Wonderful. I am looking forward to your corrected program.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 12, 2018, 06:58:48 am
I Valery, this is the screenshot of the two error message when try to open the shared folder E from WPS:

(https://ibb.co/k9CYQA)

https://ibb.co/k9CYQA (https://ibb.co/k9CYQA)

but, as you specified to me, I have found the E drive and its contained files using FC2.

Thank you
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on November 13, 2018, 04:42:56 am
Hi

I wonder what which video drive would be better for a VirtualBox ArcaOS guest. Panorama, SNAP or the include gengradd.dll on the addons? which one provides better performance for a guest machine?

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Doug Bissett on November 13, 2018, 06:32:41 am
Sort of off topic, but...

Quote
I wonder what which video drive would be better for a VirtualBox ArcaOS guest. Panorama, SNAP or the include gengradd.dll on the addons? which one provides better performance for a guest machine?

I have no doubt that SNAP and Panorama, do nothing in VBox, except take up memory space and machine cycles. The video information is passed to the host video driver by the gengradd.dll supplied by the extensions. The host video driver does all of the fancy stuff.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 13, 2018, 02:25:29 pm
Hi all

I uploaded a new build of VBox OS/2 Additions to my ftp:

Quote

For convenience, I built them as an ISO image, so it can be easily attached to the VM.
are unavailable) now contain buildlevel information. I also included the readme from
the Oracle additions (though, it is a bit not in sync with current state, and I need to
write my own readme in the future) and all required DLL's from kLIBC (in case they
are missing in your system. If they are present, use the versions from your system,
but update from repository, first).

Also, things that were fixed in this version include correct handling of directory listings
in CMD.EXE and 4OS/2 (though, FIL_QUERYEASFROMLIST[L] option in DosFindFirst
is not yet working. I need to generate correct FEALIST structure with empty EA's for
WPS Drives object to be working correctly).

Also, I noticed an error in previous version, which was fixed too: I renamed gengradd.dll
from official Oracle Additions to vbxgradd.dll, but forgot to change the internal module
name to VBXGRADD too (it remained to be GENGRADD as is). So, I discovered that
is unavailable). So, this is why Mauro got VGA mode with 16 colors. He has no gengradd.dll
in his system, but has vgagradd.dll, so it was loaded as a fallback.

Also, new features include support for UNC pathnames. So, paths like

Quote
\\vboxsrv\shared_folder_name\path\to\somefile

or

Quote
\\vboxsvr\shared_folder_name\path\to\somefile

now are working. Though, it appears that an UNC IFS can be only one in the system, so
if you have ifs=netwksta.200 from Peer/LAN Server installed, only last UNC IFS in config.sys
will work. So, currently, you need to comment out the second IFS, if you want to try this.

2Mauro: So, you have VGAGRADD loaded. So, update to the new version, it should work now.
It looks like you had amouse.sys and VBoxMouse.sys loaded at the same time, that's why you
had a trap. All other your settings seem to be ok. I only don't know why you have this error:

Quote
https://ibb.co/k9CYQA

I dont have it in my system. I only see an empty drive for each shared folder I have. No errors
at all.

2Martin Iturbide: It's best to use VBXGRADD. SNAP or Panorama work in VESA mode anyway.
So, they should be slow. VBXGRADD seems to call VBox video functions from host directly, so it
should be better. Though, I don't know exactly what it does as I don't have its sources. And previously,
between vbxgradd and gengradd until Mauro said he has started in VGA mode.

2Doug Bissett: So, now I have CMD.EXE working. So, WPS should be working soon too.

PS: I updated the first message of this topic, now it contains the latest link to binaries,
and some new tips.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on November 13, 2018, 04:11:15 pm
Hi

Sorry for more off topic and basic things. How do you configure a custom video resolution (1,920x1,080) with vbxgradd or GENGRADD ? I used to have the procedure with SNAP, but I want to follow your advice.

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on November 13, 2018, 04:41:25 pm
Ohh. I just found it. It was almost same thing that I was doing with SNAP.

On the host:
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" setextradata "ArcaOS 5.0.3" "CustomVideoMode1" "1920x1080x32"

And the resolution started to show on the Screen options.

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 13, 2018, 05:38:57 pm
2Martin Iturbide: Yes, this works for me too, just tried. Switched to full screen successfully, but can't
switch back because the Host key doesn't work for some reason in VBox version 5.2.20 (Linux host).
Too bad. Needed to kill the VM.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on November 13, 2018, 09:58:23 pm
Hi

2Martin Iturbide: Yes, this works for me too, just tried. Switched to full screen successfully, but can't
switch back because the Host key doesn't work for some reason in VBox version 5.2.20 (Linux host).
Too bad. Needed to kill the VM.

I'm using VBOX 5.2.22 on Windows (host). The Host+F works fine for me on the ArcaOS guest, my host key is the right control key.

I still need to do more testing with the IFS and also find out why the "birectional clipboard" is not working anymore.

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 14, 2018, 06:59:21 am
2Martin Iturbide: I updated to 5.2.22 too, but it didn't helped (I have VBox under Linux on my
laptop. Maybe, it's working for you because you have Windows). It seems, if the host key is
Right Ctrl, it doesn't work. But when I tried to change it to Right Alt, it worked. so, it finally
works for me.

Shared clipboard doesn't work because VBoxService.exe quits after it has shared folders mounted.
Shared clipboard service is a part if it. So, I need to fix VBoxService first.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 14, 2018, 08:19:05 am
Hi, with some trouble but much effort (and questions too) I did the installation of these guest additions, and think I moved some steps ahead from zero.

after placed the files in their respective working directory and modified the config.sys as written, here's how it works now:

-Mouse integration works
-Shared folder works in FC/2, I didn't catch immediately that I had to find it there

-non need to modify the Startup.cmd file, I just copied a shadow of VBoxService.exe  in the Startup folder contained inside OS/2 System utilities, it does its job.

Then initially I could reboot the system but only VGA resolution (640x480 16 colors) was possible, no other parametres to set in the System Panel. This because I renamed Gengradd.dll and Panogrex.dll, thinking that at this point Vbxgradd.dll should take their place.
But the video settings/resolution/colors came back working with its parameters as before as I decided to restored gengradd.dll .
So I do not see Guest Addition video driver action by now .

Just like to ask if this indication here below is valid when you tell to comment out 'set gradd_chains=c1'  but after that this line has to be rewritten again same it was:

…….
Quote
set greext=panogrex

To install the VBox video driver, you need to comment the above lines out
and change them to the following ones:

Quote

my guest system is OS2 Warp 4.52, hosted in Windows 10, VirtualBox v 5.2.18 and I have not installed before the Guest additions officially provided with it

Thank you
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 14, 2018, 10:16:28 am
2Mauro:

> -non need to modify the Startup.cmd file, I just copied a shadow of VBoxService.exe  in the Startup folder contained inside OS/2 System utilities, it does its job.

Yes, this should work both ways. No big difference.

No need to comment the

Quote

line, and add it again. The position of that line in config.sys doesn't matter. So, you returned
because it is faster and it provides support for extra video modes, as Martin said about adding
the 1920x1080x32 mode.

And no need to rename gengradd.dll and panogrex.dll files. You only need to comment the respective
config.sys lines out.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Doug Bissett on November 15, 2018, 05:58:29 am
Quote
I uploaded a new build of VBox OS/2 Additions to my ftp:

I finally found some time to try this. First, I don't like the way it is packaged. It is difficult to easily transfer the files to the final locations, but I am sure you can do better (possibly by packaging it as an RPM, or WPI, package). Even a ZIP file, that could be unzipped over the boot drive, would be better (of course, that assumes that files are where they are expected to be). I don't know how you would handle the LIBC stuff though. That should be done with ANPM (RPM/YUM) anyway.

It is MUCH better. At least I get, what appears to be, good information when I do DIR in CMD.EXE, or 4OS/2. Even a DOS or WinOS2 window works, within the limits of what DOS does. I still do not get anything, but a blank folder, when opening the WPS drive object, and that folder does not close properly, every time.

In CMD.EXE, I cannot copy a file to another drive. It says that it cannot find the specified drive (not clear on which drive, the source, or the target). Copying a file to a new name on the source drive (no drive letters used) seems to work okay, but it said that 2 files were copied. I don't see a second file. Deleting the copied file works.

I am not sure what to make of vbxgradd.dll. I did not change the line in CONFIG.SYS, but the file is locked, so I assume that your replacement gengradd.dll is using it. I don't notice any difference in the video stuff.

I am testing in VBox 5.2.22, under win 10 1803 host, with ArcaOS 5.0.3.3 (test version) as guest. The shared folder is a directory on a FAT32 drive (no EAs, as OS/2 knows them). I use the same shared folder with XP, and win7, guests.

Another good step forward, but still not ready... :)
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 15, 2018, 09:59:39 am
2Doug Bissett:

Quote
I finally found some time to try this. First, I don't like the way it is packaged. It is difficult to easily transfer the files to the final locations, but I am sure you can do better (possibly by packaging it as an RPM, or WPI, package). Even a ZIP file, that could be unzipped over the boot drive, would be better (of course, that assumes that files are where they are expected to be). I don't know how you would handle the LIBC stuff though. That should be done with ANPM (RPM/YUM) anyway.

I put it into the ISO image for easier mounting under a VM. So, you mount the ISO image under your
OS/2 VM and copy files to respective directories. Just copy them by your file manager. I use FC/2 for
that. In the future, I plan to create also an RPM package for it, so it could be easily installed from the
yum repository. So, I plan to distruibute  the additions by two ways: 1) As an usual additions ISO
2) As an RPM package. This sould be more convenient. RPM is better for newer OS/2 installations,
which have UNIX ports installed. If they are not installed, it's better to use the ISO image.

It's better to handle kLIBC dependencies with RPM, but in case RPM is not present in your system,
it can be copied manually from the ISO. Also, each RPM package has the same files zipped. So, you
can use a ZIP file as a third installation method.

Quote
It is MUCH better. At least I get, what appears to be, good information when I do DIR in CMD.EXE, or 4OS/2. Even a DOS or WinOS2 window works, within the limits of what DOS does. I still do not get anything, but a blank folder, when opening the WPS drive object, and that folder does not close properly, every time.

Yes, CMD/4OS2/DOS session should work now, but WPS still doesn't, as all required DosFindFirst
options are implemented, except for FIL_QUERYEASFROMLIST[L]. It requires more work, as I should
properly return an empty FEALIST structure (which contains an empty EA'S) for WPS to be working.
DOS also requires more work, as I need to implement filename translation short <-> long, as it's
done by FAT32.IFS. So, some long file names are not yet accessible to DOS/Win16 programs.

Quote
In CMD.EXE, I cannot copy a file to another drive. It says that it cannot find the specified drive (not clear on which drive, the source, or the target). Copying a file to a new name on the source drive (no drive letters used) seems to work okay, but it said that 2 files were copied. I don't see a second file. Deleting the copied file works.

Yes, I know about that, too. The "copy" and "cp" commands still don't work as required. It tries
to create a destination file and returns "File not found" error. Need to fix this too.

Quote
I am not sure what to make of vbxgradd.dll. I did not change the line in CONFIG.SYS, but the file is locked, so I assume that your replacement gengradd.dll is using it. I don't notice any difference in the video stuff.

What do you mean, you left GENGRADD in config.sys as is, but VBXGRADD is used, and

PS: I also fixed VBoxService.exe, so it no more quits after mounting all shared folders. So,
shared clipbord should work now. I also will add an option to explicitly assign drive letters
to shared folders, instead of using the first available ones. Will release it soon.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 15, 2018, 04:37:47 pm
2Mauro:

No need to comment the
line, and add it again. The position of that line in config.sys doesn't matter. So, you returned

yes, otherwise I had to "work" with a 640x480x16colors only resolution

Quote
because it is faster and it provides support for extra video modes, as Martin said about adding
the 1920x1080x32 mode.

Quote
And no need to rename gengradd.dll and panogrex.dll files. You only need to comment the respective
config.sys lines out.

ok
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 16, 2018, 04:15:09 am
2Mauro:

I updated the link in the first message of this thread. And the message itself, so that it
contains the actual information. So, you need to reupload it and try.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 17, 2018, 08:44:34 am
I have copied the new version files in their respective directories, but nothing new happens, same gengradd settings resolutions+colors in the system->screen panel, and no shared clipboard working.
Strange… Repeat, it is at least better than when I could not afford for having some guest additions working functions.
Thank you.

PS I'm sure 100% I'm doing something wrong but you have well expained to me what to do
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 17, 2018, 01:33:44 pm
2Mauro: Is it indeed the version r179? Its version of vbxgradd.dll should load ok, it's fixed.
Though, VBoxService fix was in r180, so I didn't uploaded the fix, yet. So VBoxService.exe

Quote

This version contains more fixes. Both vbxgradd.dll and VBoxService.exe now are
working. SO, shared clipboard should work too.

Also, now I fixed UNC pathnames, so, it now should work if any other UNC IFS is
installed, except for vboxsf.ifs (like the IFS from Peer/LAN Server).

Also, a new feature is added: If \os2\boot\vboxsf.cfg file is present, having lines
like the following:

Quote
share1       <driveletter1>
...
shareN       <driveletterN>

Then drive letters can be pinned. If vboxsf.cfg file is not present, a first available drive
letter is used.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 17, 2018, 03:23:11 pm
2Mauro: Is it indeed the version r179? Its version of vbxgradd.dll should load ok, it's fixed.
Though, VBoxService fix was in r180, so I didn't uploaded the fix, yet. So VBoxService.exe

Quote

This version contains more fixes. Both vbxgradd.dll and VBoxService.exe now are
working. SO, shared clipboard should work too.

ok, got the r183 files and moved them in my C:\ respective directories, replacing the existing ones and adding the new ones.  But it is still like before, no Guest Additions video driver working.  The only thing I've never touched are the three .dll files in USR->LIB.  I understood that if I already have them recently installed in the system  (with rpm-yum manager from Netlab repository) then the already existing ones should be ok, right?
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 17, 2018, 03:36:29 pm

ok, got the r183 files and moved them in my C:\ respective directories, replacing the existing ones and adding the new ones.  But it is still like before, no Guest Additions video driver working.  The only thing I've never touched are the three .dll files in USR->LIB.  I understood that if I already have them recently installed in the system  (with rpm-yum manager from Netlab repository) then the already existing ones should be ok, right?

update: shared clipboard works! It was just disabled in VBox guest settings. My mistake, excuse me.

And, opened C:\OS2\INSTALL\GRADD.LOG  I found the following:
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 17, 2018, 06:15:12 pm
2Mauro:

Yes, as it was written above, if you have the \usr\lib\*.dll files already installed, no need to install them

Quote
And, opened C:\OS2\INSTALL\GRADD.LOG  I found the following:

So, it loaded ok. Did you checked System Setup->System->Screen ? Does it show all
usual video modes? If so, enable the video mode you need and reboot.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 18, 2018, 10:35:59 am
2Mauro:x

So, it loaded ok. Did you checked System Setup->System->Screen ? Does it show all
usual video modes? If so, enable the video mode you need and reboot.

System Setup shows same resolutions given with Panorama drivers , no 16/9 options given, no 1920x1080x32 mode in the options, in the screenshot here below I find the highest possile resolutions:

(https://ibb.co/hkvDN0)
https://ibb.co/hkvDN0 (https://ibb.co/hkvDN0)

I then believed that it was because of the monitor model choosen which is a LCD display 1024x768, but also in its higher res (till 1600x1200x32) there are no 16/9 value

(https://ibb.co/e5FBaL)
https://ibb.co/e5FBaL (https://ibb.co/e5FBaL)

as you see, in the 'Adapter Name' field it shows Virtual Box VESA Bios
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 18, 2018, 04:33:30 pm
2Mauro:

So, you have all video modes in the list. I have no display selected here at all. Yes, these
modes are shown by VBox VESA BIOS. I have the same. What else do you want?

No 16x9 value? Then add it with VBoxManage command, as Martin did before.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 18, 2018, 07:36:03 pm
2Mauro:

So, you have all video modes in the list. I have no display selected here at all. Yes, these
modes are shown by VBox VESA BIOS. I have the same. What else do you want?

No 16x9 value? Then add it with VBoxManage command, as Martin did before.

Done, this is what I missed.  As said at the beginning, I'm not so smart to catch all of those details myself (that's why I had preferred a self-installing routine like in other VB guest OS), but I can go to the end with a patient navigator.  Thank to you and Martin as well in this last case   :D
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on November 20, 2018, 03:48:47 pm
Hi Valerius.

I just made a new test today.
Using "VBoxAdditions-os2-x86-5.0.51.r183.zip" with Windows 10 Host (VirtualBox 5.2.22) and ArcaOS 5.0.3 as guest.
I located all files on "C:\Programs\Vbox" as personal preference with the exception of the vbxgradd.dll that goes on C:\OS2\DLL

- Bidirectional clipboard works
- Mouse integration works
- Video works with 1,920x1,080 (setting the custom resolution on the VM).

This are my comment with Vbox.IFS:
1) It does not auto-mount with "start /n vboxservice.exe" on startup.cmd. I had to run like "VBoxSFAttach w: OS2Temp" to mount the drive. Was an auto-mount supposed to happen, or did I get it wrong? I have no problem adding "VBoxSFAttach w: OS2Temp" on the startup.cmd.
2) It is "Read only" I can not copy a file from and to the same mounted drive using 4OS2 or CMD. (but the good thing is that now CMD sees the files and I can copy those to other drives like C:).
3) WPS integration is not working.
a) I open e.exe and looked at the W: drive and worked (E Running W.png)
b) I open W: from the "Drives" icon and get a OS2KRNL trap (See OS2KRNL- Trap.png or video (https://youtu.be/ZTbCMzdtWt0))

Let me know if this limitations are expected since I got lost since the thread is getting bigger.
Anyways it is great to be at least able to read the folder and copy files from the host.

Regards

Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: roberto on November 20, 2018, 06:57:34 pm
Using "VBoxAdditions-os2-x86-5.0.51.r183.zip" with Windows 10 Host (VirtualBox 5.2.22) and ArcaOS 5.0.3 as guest.
Here you say you have arcaos503, but in the trap error version 14.200_W appears, and I see in my computer the 14.201_SMP in arcaos503, something does not fit.
saludos
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 20, 2018, 08:49:19 pm
2Martin Iturbide:

Quote
1) It does not auto-mount with "start /n vboxservice.exe" on startup.cmd. I had to run like "VBoxSFAttach w: OS2Temp" to mount the drive. Was an auto-mount supposed to happen, or did I get it wrong? I have no problem adding "VBoxSFAttach w: OS2Temp" on the startup.cmd.

Is your \programs\VBox directory on PATH? If not, you need to specify the full path:

Quote
start /n c:\programs\vbox\VBoxService.exe

It automounts ok on mine, and several other users machines. Did you checked the
"Auto-mount" checkbox in shared folder settings?

Quote
2) It is "Read only" I can not copy a file from and to the same mounted drive using 4OS2 or CMD. (but the good thing is that now CMD sees the files and I can copy those to other drives like C:).

Do you have "read only" checkbox set on your shared folder in VM settings? If so, remove it. The "copy" command does not yet work ok, as I already mentioned above. e/ae editors should work. I have no problems saving files with them.
Note that read only shared folders are not tested at all -- used r/w ones only so far.

Quote
3) WPS integration is not working.
a) I open e.exe and looked at the W: drive and worked (E Running W.png)
b) I open W: from the "Drives" icon and get a OS2KRNL trap (See OS2KRNL- Trap.png or video)

E.exe is not the WPS drives object. It is Drives object did not work. File dialog should work. But now I
added support for WPS Drives object, will upload a new version soon. From your trap screen it is
hard to tell where it trapped. Somewhere in the kernel. You'll need to retest with the newer version
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 20, 2018, 09:44:09 pm

Quote

Now WPS Drives object should work ok, as I implemented creating the empty EA's
structure. Also, I fixed FS_VERIFYUNCNAME, so it now should work, when two UNC
IFS-es are installed. The "dir \\vboxsrv\sharename" now works ok with CMD.EXE.
Previously, this command gave an error.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on November 20, 2018, 11:22:45 pm
Using "VBoxAdditions-os2-x86-5.0.51.r183.zip" with Windows 10 Host (VirtualBox 5.2.22) and ArcaOS 5.0.3 as guest.
Here you say you have arcaos503, but in the trap error version 14.200_W appears, and I see in my computer the 14.201_SMP in arcaos503, something does not fit.
saludos

Hi Roberto.

It seems to me that ArcaOS 5.0.3 installs the  14.200_W kernel when you have only once processor/core. I installed this VM with only one core, any tip to update/change to the 14.201_SMP from the kernel that I have is welcome.

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on November 20, 2018, 11:51:43 pm
Hi

2Martin Iturbide:

Quote
1) It does not auto-mount with "start /n vboxservice.exe" on startup.cmd. I had to run like "VBoxSFAttach w: OS2Temp" to mount the drive. Was an auto-mount supposed to happen, or did I get it wrong? I have no problem adding "VBoxSFAttach w: OS2Temp" on the startup.cmd.

Is your \programs\VBox directory on PATH? If not, you need to specify the full path:

Quote
start /n c:\programs\vbox\VBoxService.exe

It automounts ok on mine, and several other users machines. Did you checked the
"Auto-mount" checkbox in shared folder settings?

I confirm that C:\Programs\vbox was on the path and libpath. And the auto-mount checkbox is enabled on the host.

Quote
Quote
2) It is "Read only" I can not copy a file from and to the same mounted drive using 4OS2 or CMD. (but the good thing is that now CMD sees the files and I can copy those to other drives like C:).

Do you have "read only" checkbox set on your shared folder in VM settings? If so, remove it. The "copy" command does not yet work ok, as I already mentioned above. e/ae editors should work. I have no problems saving files with them.
Note that read only shared folders are not tested at all -- used r/w ones only so far.

It is not read only on the options.. I have "Auto-Mount" and "Make Permanent". I also found out that when the VM guest is turned on it shows the "Make Permanent", when it is off it does not show it.

By turning off the "Make Permanent" and turning it on, on the next boot it auto attached.

I need to keep testing it further.

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 21, 2018, 12:07:52 am
2Martin:

Quote
It seems to me that ArcaOS 5.0.3 installs the  14.200_W kernel when you have only once processor/core. I installed this VM with only one core, any tip to update/change to the 14.201_SMP from the kernel that I have is welcome.

Just search \os2image for SMP kernel (It should be in \os2image\debug\smp, I think).
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Dave Yeo on November 21, 2018, 12:13:46 am
I installed this VM with only one core, any tip to update/change to the 14.201_SMP from the kernel that I have is welcome.

The SMP stuff is in x:\os2\install\smp. Just replace your kernel, unlock and replace doscall1.dll and I guess harderr.exe. The other stuff is only for debugging tracing and such. Usually you also replace os2ldr but I don't think it is necessary with ArcaOS.
The W4 kernel will give about 10% better performance on a single core machine so unless you need the SMP support...
Changing back is the same except the files are in x:\os2\install\w4
x: of course is your boot drive
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 21, 2018, 06:40:21 pm

1) It does not auto-mount with "start /n vboxservice.exe" on startup.cmd. I had to run like "VBoxSFAttach w: OS2Temp" to mount the drive. Was an auto-mount supposed to happen, or did I get it wrong? I have no problem adding "VBoxSFAttach w: OS2Temp" on the startup.cmd.

if you think that issue might be a wrong script in the the startup.cmd, I would suggest to place a shadow copy of vboxservice.exe in the Startup folder (inside OS2 System folder in my OS2 Warp 4.52 machine), don't know if ArcaOS has same folder function.
It has worked for me.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on November 23, 2018, 06:58:43 am

Quote

Now WPS Drives object should work ok, as I implemented creating the empty EA's
structure. Also, I fixed FS_VERIFYUNCNAME, so it now should work, when two UNC
IFS-es are installed. The "dir \\vboxsrv\sharename" now works ok with CMD.EXE.
Previously, this command gave an error.

in my OS2 Warp 4.52 guest, WPS shared folder drive containing files has appeared and worked just at first time of system reboot after the new GA r184 version installation, no more on further sessions.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Moritz on November 23, 2018, 03:05:46 pm
It works mostly good for me but i noticed some things using the lateste 184 build.

DOS window does not show folders but shows files some files double
Command window shows some folders double

FC/2 shows everything correct.

System ArcaOS 5.03, packages from netlabs-exp repository

Thanks for the work!

Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 23, 2018, 05:01:50 pm
2Moritz:

Interesting effect that it displays some files twice. Are you sure they are the same?
Maybe, this is two different files with long name, truncated to the same short name?
I don't have this on my VM. Also, directories are shown ok in my case.

PS: File names in DOS are not yet ready, because file name translation short <-> long
is to be implemented, yet.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 23, 2018, 05:40:17 pm
PS: This is in DOS (command.com):

Quote

The volume label in drive L is os2l.
Directory of L:\TMP

0075_01  TRP      5866  14.11.18 13:51
3        10  <DIR>      23.12.15 23:45
acpi-3   22.    129939  23.12.15 23:39
acpi-man ger    118667   4.08.08 19:48
acpi-too kit    241070  14.12.15 10:23
acpi     psd    220275  28.11.13 11:02
acpi32   dll     15631  28.11.13 11:00
acpi4    bpd    112959  20.12.15 22:56
acpi4    rar    109184  23.12.15 22:29
AcpiInfo dat    452032  24.12.15  1:31
AcpiLstI fo.     37748  24.12.15  1:31
AcpiMana er.    201794  12.03.07 17:12
AcpiMana er.      2822  24.12.15  1:31
dos      txt        40  23.11.18 16:51
DosSysCt _IP     22112  18.11.16 22:12
freeShar dMe     14385   7.01.16 14:58
g        img  33162240  30.09.17  6:22
gnufu    dll     24445  31.03.98 18:22
gnuintl  dll      6203  31.03.98 18:22
o        img 181485568  29.09.17  8:58
PMGPI    DLL    248446  16.10.01 13:31
PMGPI    txt    117246   7.03.17 18:45
yum_save tx-     12815  21.05.17  7:53
yum_save tx-     20325   3.04.18 23:31
yum_save tx-     20325   3.04.18 23:33
0
31 file(s)  223235866 bytes used
371965952K bytes free

The same directory shown in 4OS/2:

Quote

Volume in drive L is os2l
Directory of  L:\tmp\*

23.11.18  16:54         <DIR>        0   _H__D  .
23.11.18  16:52         <DIR>        0   _H__D  ..
23.12.15  23:45         <DIR>        0   ____D  3.10
12.11.18  11:32         <DIR>        0   ____D  additions
0      0   _____
23.11.18  16:54              38      0   _____  4os2.txt
14.11.18  13:51           5 866      0   _____  0075_01.TRP
23.12.15  23:39         129 939      0   _____  acpi-3.22.03.rar
4.08.08  19:48         118 667      0   _____  acpi-manager-20070312.zip
14.12.15  10:23         241 070      0   _____  acpi-toolkit-3.22.zip
28.11.13  11:02         220 275      0   _____  acpi.psd
20.12.15  22:56         112 959      0   _____  acpi4.bpd
23.12.15  22:29         109 184      0   _____  acpi4.rar
28.11.13  11:00          15 631      0   _____  acpi32.dll
24.12.15   1:31         452 032      0   _____  AcpiInfo.dat
24.12.15   1:31          37 748      0   _____  AcpiLstInfo.lst
12.03.07  17:12         201 794      0   _____  AcpiManager.exe
24.12.15   1:31           2 822      0   _____  AcpiManager.log
12.11.18   9:50         692 493      0   _____  additions.zip
18.11.16  22:12          22 112      0   _____  DosSysCtl_IPI.exe
7.01.16  14:58          14 385      0   _____  freeSharedMem.exe
30.09.17   6:22      33 162 240      0   _____  g.img
31.03.98  18:22          24 445      0   _____  gnufu.dll
31.03.98  18:22           6 203      0   _____  gnuintl.dll
29.09.17   8:58     181 485 568      0   _____  o.img
16.10.01  13:31         248 446      0   _____  PMGPI.DLL
7.03.17  18:45         117 246      0   _____  PMGPI.txt
17.11.18  18:26       1 422 919      0   _____  VBoxAdditions-os2-x86-5.0.51.r183.zip
20.11.18  15:54       2 818 048      0   _____  VBoxAdditions-os2-x86-5.0.51.r184.iso
21.11.18   2:34       1 519 757      0   _____  VBoxAdditions-os2-x86-5.0.51.r184.zip
21.05.17   7:53          12 815      0   _____  yum_save_tx-2017-05-21-07-53nopywb.yumtx
3.04.18  23:33          20 325      0   _____  yum_save_tx-2018-04-03-23-33cvthgo.yumtx
3.04.18  23:31          20 325      0   _____  yum_save_tx-2018-04-03-23-315o16h2.yumtx
223 235 352 bytes (212MB) in 29 files and 4 dirs

223 297 536 bytes (212MB) allocated
307 888 103 424 bytes (286GB) free

As can be seen above, the names shown are the same for "yum_save tx-", "VBoxAddi ion",
but the files are different. Also, as it can be seen, "addition" ("additions" in fact) subdirectory
is shown here. Both listings contain 29 files and 2 directories.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 23, 2018, 06:51:01 pm
2Moritz:

> Files/directories skipped/repeated twice

I have no idea why they could repeat twice, but they can be skipped because file
attributes are not matched. Maybe, they have hidden/system/readonly/archive
attributes set? Can you check which attributes these files/directories have? DOS
could skip files with system/hidden/readonly attributes. You could try removing
these attributes with FC/2 and see. You can also try Norton/Volkov Commander/
DOS Navigator -- they should not skip files with special attributes set.

PS: Indeed, as it can be seen, your files have "archived" bit cleared, except for
those two "sav_*.ice" files. So, it's because of this.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 23, 2018, 09:48:28 pm
Hm, but I cannot reproduce your situation on my machine. I have OS/2 or Linux
hosts, and OS/2 guest. On OS/2 host, I set "archive" bit in DOS file attributes, but
via a shared folder, I see this bit cleared on that file. You seem to have Windows
host (is it true?), and see "archive" bit set on some files via shared folders. Too bad,
I have no windows on my test machine :( I have WinXP host on a third machine, though.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: ivan on November 30, 2018, 02:39:16 pm
Maybe this is the wrong place but...  Does anyone know where I can get VBox for an OS/2 host with all the necessary dependencies that will work on ArcaOS running on an AMD Ryzen G processor?
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on November 30, 2018, 03:39:35 pm
2ivan:

Quote

?

This is the latest available version.There is also the older official version 5.0.6 of VBox on Herwig's page.
Not sure, what do you need for "AMD Ryzen G" processor. Never had such processor. And I doubt
that other VBox versions are available. The required dependencies are described here:

Quote
http://trac.netlabs.org/vbox/

PS: Why do you need the version with all the dependencies? Manually picking all versions of all required
libs is not recommended because it is tricky and causes library versions conflicts, which can cause problems.
It is recommended to have a single version of each library in the system, to avoid situation, when different
programs want different versions of a library, and thus, crashes happen. Also, having a single library in the system
consumes less memory. This is very important on a 32-bit system, which is limited with the < 4 GB limit
of its address space. To achieve this, there is a package manager, like yum. It should care about all
dependencies, updating each library to the latest version, and all programs being dependent from the
same version of each library. So, why not just use the package manager as it's designed?

PPS: For AMD Ryzen processors (not sure about "Ryzen G"), Arca OS kernels was not known to work/boot
ok. Though, on unofficial OS/4 kernels, there are some users which had successfully using OS/4 kernel
with AMD Ryzen processors (though, I'm not sure about what Ryzen variants they are). But it makes sense
to contact OS/4 developers and try being a tester. Also, as a bonus of an OS/4 kernel, you'd have a
possibility to use hardware virtualization (AMD-V/VT-x) with OS/2 version of VBox. This is an unfinished
feature, yet, but it is mostly working. I am even able to run OS/2 guest on top of OS/2 host.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: ivan on November 30, 2018, 05:00:58 pm
Thank you.

To answer your questions.  The Ryzen G processor is the 4 core version with the built in Vega graphics.  I asked about all the dependencies because I remember when the first OS/2 version came out there was quite a scrabble to find everything needed - some from hobbes and some from other places.

From what I have seen any problem between ArcaOS and Ryzen processors is in the install.  For some reason the memdisk does not work because it throws a 'not enough memory' fault, even in cases where there is a minimum of 4Gb RAM.  There is a workround - install using an AMD A10-9700 processor then replace the processor with the Ryzen. Once there is a working ArcaOS on the hard disk it boots up and runs without any problems except that the built in to the motherboard USB does not work - no USB 3 (XHCI) driver.  Other than that ArcaOS boots as if using a SSD drive.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on December 22, 2018, 01:07:16 pm
Hi

I noticed that VirtualBox 6.0 for Windows was released. On the change log (https://www.virtualbox.org/wiki/Changelog) you can find:
- "OS/2 Guest Additions: initial shared folder support "

Valerius: Are those your changes going into the official code stream?

Regards

Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on December 24, 2018, 06:13:10 pm
2Martin: No, this is Knut's version of OS/2 additions. I told Knut that my version is almost ready,
then he immediately flushed his last version (previously unpublished). It appears that he had almost
working version, but did not committed it to official repository, until now. My version is based on
his early version, which was available in Oracle's repository. I thought, it was abandoned.

So, now we have two versions of OS/2 additions -- mine and Knut's. Mine has some features,
missing in Knut's version (his version has non-working WPS Drives object, for example. And
automount won't work, only manual mount. Plus no drive letter pinning support).
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on December 25, 2018, 06:52:46 pm

So, now we have two versions of OS/2 additions -- mine and Knut's. Mine has some features,
missing in Knut's version (his version has non-working WPS Drives object, for example. And
automount won't work, only manual mount. Plus no drive letter pinning support).

Hi Valery, did someone else than me reported he has issue for shared folder to be handled in wps, as advised you some posts before? No problem with fc/2, but in wps it shows as an empty drive even if it contains some folder and file,
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Oliver Cremer on December 25, 2018, 09:47:12 pm
Quote
Hi Valery, did someone else than me reported he has issue for shared folder to be handled in wps, as advised you some posts before? No problem with fc/2, but in wps it shows as an empty drive even if it contains some folder and file,
I did not read the whole thread, but I have the same WPS-problem with shared folders. I use VirtualBox 6.0.0 with Ubuntu 18 (host) and ArcaOS (guest). The additions are "VBoxGuestAdditions.iso ; 6.0.0r127566". Where did you post the probelm? Trac on Netlabs? forums.virtualbox.org? https://www.virtualbox.org/wiki/Bugtracker?

Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on December 25, 2018, 09:54:29 pm
Quote
Hi Valery, did someone else than me reported he has issue for shared folder to be handled in wps, as advised you some posts before? No problem with fc/2, but in wps it shows as an empty drive even if it contains some folder and file,
I did not read the whole thread, but I have the same WPS-problem with shared folders. I use VirtualBox 6.0.0 with Ubuntu 18 (host) and ArcaOS (guest). The additions are "VBoxGuestAdditions.iso ; 6.0.0r127566". Where did you post the probelm? Trac on Netlabs? forums.virtualbox.org? https://www.virtualbox.org/wiki/Bugtracker?

no, I've reported it in this thread since Valery is the developer of the G.A. version that I've installed, and this topic (started by Valery) was for giving feedback on testing.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Andreas Schnellbacher on December 26, 2018, 12:05:34 am

I use VirtualBox 6.0.0 with Ubuntu 18 (host) and ArcaOS (guest).
That's apparently Knut's version, not Valery's.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on December 26, 2018, 01:31:48 pm
Quote
That's apparently Knut's version, not Valery's.

Yes, It is important not to confuse that. Knut St. Osmundsen (https://www.os2world.com/wiki/index.php/Knut_St._Osmundsen) is the guy doing the VirtualBox official OS/2 Guest addons for the VirtualBox project, I really didn't know he was active until this (version 6.0 guest addons) update. Tickets should be open on: https://www.virtualbox.org/wiki/Bugtracker (https://www.virtualbox.org/wiki/Bugtracker)
By my ticket haven't been replied in 5 years (https://www.virtualbox.org/ticket/12106). Time flies.

It would be great if both streams can be merged together, but sometimes it is hard to make two developers agree in his way of doing things.

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on June 24, 2019, 08:46:51 pm
Hi, Martin.

> It would be great if both streams can be merged together, but sometimes it is hard to make two developers agree in his way of doing things.

The two versions are very different, so no way to merge them. And I want a bit different features, which are unlikely to be implemented by Knut
and Oracle. And it seems, Knut does not like to include other people's code. (Look at BWW and their libc fork called libcn -- the same situation).

Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on June 24, 2019, 08:55:20 pm
Quote from: mauro
Quote from: Valery Sedletski
So, now we have two versions of OS/2 additions -- mine and Knut's. Mine has some features,
missing in Knut's version (his version has non-working WPS Drives object, for example. And
automount won't work, only manual mount. Plus no drive letter pinning support).

Hi Valery, did someone else than me reported he has issue for shared folder to be handled in wps, as advised you some posts before? No problem with fc/2, but in wps it shows as an empty drive even if it contains some folder and file,

I have mostly implemented returning empty EA list in some IFS functions, so, in theory, WPS should show a folder listing in "Drives" object.
In practice, it shows it sometimes, and sometimes it shows a "No objects were found that matched the specified match criteria" dialog. Some
other problem occurs. No idea yet, why. Need to look at it closer. If you try to open a WPS window from FC/2 with Ctrl-W, it often works, but
if you try opening the root directory of a shared folder from Launchpad->Drives->..., then it fails often.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on June 24, 2019, 09:08:11 pm
BTW, I released a new r199 version of VBox Additions today:

Quote

Many fixes were added, including timestamp fixes: now "touch" utility gives the current time as a timestamp
for affected files. "Make" utility no more loops around, so that, building sources with "make" should work
correctly. Also, I adjusted returned file listings, so file find operation (with DosFindFirst/Next API's) no more
returns an empty filename, so now "copy" command works correctly in both CMD and 4OS/2. Also, now
ZIP and WIC utilities work correctly, so that I was able to create ZIP and WarpIN archives over a shared
folder. Also, I fixed some traps and memory leaks, so now I was able to check out VBox and fat32.ifs and
osFree sources, and build them over a shared folder without any problems. VBox sources take about
1 GB of space on disk, and compile for about 6-8 hours in a VBox machine under a Linux host. So,
no memory leaks occured that time and everything was built without problems. Git and Svn clients
work fine over a shared folder too.

So, I'll appreciate any testing.

PS: This version also has fixed wildcard matching, the DOS way (instead of the UNIX way).

PPS: Now timestamps are adjusted to local timezone. For that, TZ environment variable in config.sys
is parsed to calculate a time zone offset. Time zone offset calculating is done in VBoxService.exe
"Timesync" service, and set a "timezone" field in Global infoseg (via DosSetDateTime/DosGetDateTime
API's). Currently, only simple syntax like "TZ=MSK-3" works. (I'll implement a full timezone parser in the future)

PPPS: Also, I implemented logging to OS/4 / QSINIT / ArcaLDR log buffer. There are unfinished docs (README
buffer etc.).
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: ivan on June 24, 2019, 09:49:17 pm
Now all we need is a vBox host for OS/2 that works as well as your additions.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on June 24, 2019, 09:59:27 pm
OS/2 host? It works, isn't it? OS/2 guest over OS/2 host with hardware-assisted virtualization works fine on my machines, too.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Rich Walsh on June 24, 2019, 10:19:22 pm
I have mostly implemented returning empty EA list in some IFS functions, so, in theory, WPS should show a folder listing in "Drives" object. In practice, it shows it sometimes, and sometimes it shows a "No objects were found that  matched the specified match criteria" dialog. Some other problem occurs. No idea yet, why.

Just to confirm: if your IFS receives a request for the total size of all EAs (FIL_QUERYEASIZE), and you want to indicate that their are no EAs, are you returning '4' (and not '0')? Returning zero is the most common coding error when handling EAs.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on June 24, 2019, 11:13:20 pm
Quote from: Rich Walsh
Just to confirm: if your IFS receives a request for the total size of all EAs (FIL_QUERYEASIZE), and you want to indicate that their are no EAs, are you returning '4' (and not '0')? Returning zero is the most common coding error when handling EAs.

What do you mean? cbList field? It is always returned to be 0. (It is so in vboxfs.ifs, fat32.ifs and ramfs.ifs/emsfs.ifs). Why it should be 4?

I used the working code from fat32.ifs as a template, so it should work. I see no problems with displaying disks with Drives WPS object
in fat32.ifs. So, the problem is with something other.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Rich Walsh on June 25, 2019, 04:01:08 am
Quote from: Rich Walsh
Just to confirm: if your IFS receives a request for the total size of all EAs (FIL_QUERYEASIZE), and you want to indicate that their are no EAs, are you returning '4' (and not '0')? Returning zero is the most common coding error when handling EAs.

What do you mean? cbList field? It is always returned to be 0. (It is so in vboxfs.ifs, fat32.ifs and ramfs.ifs/emsfs.ifs). Why it should be 4?

First, I assume that the 'cbList' field you are referring to is the one at the end of the FILESTATUS4 structure. In a properly functioning IFS, the following call will return a value of 4 in 'cbList' if 'pFilename' refers to a file with no EAs:

DosQueryPathInfo(pFilename, FIL_QUERYEASIZE, &fs4, sizeof(FILESTATUS4));

The documentation for this function and DosQueryFileInfo() is misleading. You would think it says that the size of the EAs will be returned - but that is incorrect. It actually returns the size of the FEA2LIST structure that is needed to hold all EAs. That structure is the size of all EAs *PLUS* a ULONG (named 'cbList') that identifies the total size of the variable-length structure. Thus, the correct size of an FEA2LIST for a file with no EAs is 0 + 4.

I knew this is a common error because I had to fix it in ISOFS in order to install ArcaOS from an ISO image file. The problem showed up when the installer tried to run IBM's ancient 'unpack.exe'. Even though it knew a given pack file had no EAs, it still queried them using the undocumented Level 4 argument (FIL_QUERYALLEAS). It interpreted a value of zero as 65536 and complained that the EAs were too large (since they can be no more than 65535 bytes). I doubt anyone had ever seen this error before because I know of no other program stupid enough to ask for something it knows doesn't exist.

Quote
So, the problem is with something other.

That may be true, but returning 0 in cblist is still incorrect. Write a simple test program and point it to a file on a JFS, HPFS, or even FAT drive to confirm this. BTW... AN's version of FAT32 also returns 4.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Lars on June 25, 2019, 06:51:26 am
Oh yes, EAs.

That's the worst designed programming interface I have ever come across. I am sure MS invented this bullshit in its darkest days. It's a steady resource of misinterpretation (as we all can see from this discussion).

But wait, parts of MMPM are just as bad.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Lars on June 25, 2019, 07:03:36 am
By the way: how does this go together with the fact that if you ask for a specific EA that then, the IFS does have to return an FEA(2) structure, basically returning the EA name that was requested (that is: szName is filled and cbName properly set to the length) but with EMPTY content (that is: cbValue is 0) ?
Returning nothing in this case is definitely WRONG.

That's why in the past I suggested to return a "sensible" size for exactly that FEA(2)LIST structure that would allow to return at least a couple of empty FEA(2) structures but Gregg stated that 0 should be returned.

As I said: a horrible programming interface.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Lars on June 25, 2019, 10:30:01 am
I just checked the FAT32 source code:

FS_FILEINFO (that should cover API DosGetFileInfo) returns 4 (for FIL_QUERYEASIZE and FIL_QUERYEASIZEL) if there are no EAs.

FS_PATHNFO (that should cover API DosGetPathInfo) returns 4 (for FIL_QUERYEASIZE and FIL_QUERYEASIZEL) if there are no EAs.

FS_FINDFIRST/FS_FINDNEXT (that should cover APIs DosFindFirst/DosFindNext) return 0 (for FIL_QUERYEASIZE and FIL_QUERYEASIZEL) if there are no EAs. This latter one was what Gregg requested as the response for files that do not have EAs.

<quote>
For Level 2 File Information (ulInfoLevel == FIL_QUERYEASIZE) : On output, pfindbuf contains the FILEFINDBUF4 data structure without the last two fields: cchName and achName. This is used with EAs.

The cbList field contains the size, in bytes, of the file's entire EA set on disk. You can use this field to calculate the maximum size of the buffer needed for Level 3 file information. The size of the buffer required to hold the entire EA set is less than or equal to twice the size of the EA set on disk.
</quote>

Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on June 25, 2019, 11:28:46 am
2Rich Walsh & Lars Erdmann:

vboxfs.ifs was created looking at fat32.ifs and ramfs.ifs. So, they should behave similar way. Looking at fat32.ifs, I see:
1) In FS_PATHINFO and FS_FILEINFO: filestatus.cbList = sizeof(filestatus.cbList); (i.e., 4 for one ULONG).
2) In FS_FINDFIRST worker,

Code: ("C") [Select]
                     if (!f32Parms.fEAS || !HAS_EAS( pDir->fEAS ))                        /* HACK: what we need to return here                           is the FEALIST size of the list                           that would be produced by usGetEmptyEAs !                           for the time being: just tell the user                           to allocate some reasonably sized amount of memory                        */                           pfFind->cbList = 0;                     else                        {                        rc = usGetEASize(pVolInfo, pFindInfo->pInfo->rgClusters[0], NULL,                                         szLongName, &pfFind->cbList);                        if (rc)                           /* HACK: what we need to return here                              is the FEALIST size of the list                              that would be produced by usGetEmptyEAs !                              for the time being: just tell the user                              to allocate some reasonably sized amount of memory                           */                              pfFind->cbList = 0;                        rc = 0;                        }
so, in absence of EA's, it returns cbList = 0; Yes, I looked primarily at FS_FINDFIRST. Rich, you seem to be right.
At least, FS_FILEINFO and FS_PATHINFO do thye same.

Quote
Quote
So, the problem is with something other.

That may be true, but returning 0 in cblist is still incorrect. Write a simple test program and point it to a file on a JFS, HPFS, or even FAT drive to confirm this. BTW... AN's version of FAT32 also returns 4.

Yes, but the error occurs when FS_FINDFIRST (but not FS_FILEINFO / FS_PATHINFO) is called. It returns 0 in cbList in both vboxfs.ifs and fat32.ifs. Though, I see no problems at all
with fat32.ifs.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Lars on June 25, 2019, 02:34:33 pm
ok, FS_FINDFIRST / FS_FINDNEXT should therefore also return pfFind->cbList = sizeof(pfFind->cbList) in case of no EAs (!HAS_EAS(pDir->fEAS)) or not activated EAs (!f32Parms.fEAS).

And then, I also wonder if "usGetEASize" returns the correct size. My gut feeling is that you will also need to add 4 on top of what it returns. And I have not yet understood if it really counts the bytes of all the FEA structures (appended by the EA name and the EA data) that it needs to create or only the bytes of the "naked" EA data which, again, would be wrong.

By the way: FS_PATHINFO and FS_FILEINFO do not honour the (!HAS_EAS(pDir->fEAS)) case (that is: the case where no EAs exist).
Unless "usGetEASize" properly handles this case ...

Here is the back and forth discussion regarding FS_FINDFIRST/FS_FINDNEXT:
http://trac.netlabs.org/fat32/ticket/55
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Rich Walsh on June 25, 2019, 07:35:51 pm
Here is the back and forth discussion regarding FS_FINDFIRST/FS_FINDNEXT:
http://trac.netlabs.org/fat32/ticket/55

It's hard to understand why there should ever have been a "back and forth" in the first place: none of this is subject to debate.

You write a test program that incorporates the various scenarios, run it against one or more files on an *HPFS* formatted disk, then alter your own IFS to produce the same results as HPFS. Period, end of discussion. It doesn't matter if the results you get are good, bad, or just stupid - they are what the OS and programs like 'unpack.exe' were built to expect.

Note: I consider HPFS to be the reference IFS as it is the only filesystem that is pure IBM and has not been altered by well-meaning but potentially ill-informed third parties.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Lars on June 26, 2019, 07:18:04 am
It's hard to understand what good it does to return "4 Bytes" on a FIL_QUERYEASIZE if the return value is to serve as a measure of how many bytes you need to allocate when you want to actually request an EA.
As I said, you need an FEALIST with at least one entry plus the extra space for the requested EA Name to return the result. even if the EA is empty/does not exist. That is most certainly more than 4 bytes.

And guess what: obviously JFS.IFS returns 0 bytes on a DosFindFirst with FIL_QUERYEASIZE (that's what I read from Gregg's comments). But seemingly it would return 4 bytes on a DosQueryPathInfo with FIL_QUERYEASIZE. In short: the results are not even consistent in itself.

Who is using HPFS (and therefore testing with it) these days ? Nobody.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Rich Walsh on June 26, 2019, 10:54:28 am
It's hard to understand what good it does to return "4 Bytes" on a FIL_QUERYEASIZE if the return value is to serve as a measure of how many bytes you need to allocate when you want to actually request an EA. As I said, you need an FEALIST with at least one entry plus the extra space for the requested EA Name to return the result. even if the EA is empty/does not exist. That is most certainly more than 4 bytes.

How is the OS supposed to know that you're going to waste your time requesting some EA when it's telling you that there are NO EAs?? Returning '4' says "Ain't nothin' here, don't bother". If you're going to ignore what it says, then you'll just have to put forth some effort to calculate the appropriate size because it won't assist you in pursuing something that's pointless.

Quote
Who is using HPFS (and therefore testing with it) these days ? Nobody.

What kind of excuse is that for not bothering to find out how things are supposed to work? I have no use for willful ignorance, so I *did* try to find out. These are the results I got from running a simple DosFindFirst() against files with no EAs on various filesystems. The number is the value of FILEFINDBUF4.cbList:

FAT - 4
HPFS - 4
CDFS - 4
ISOFS - 4
JFS - 0
FAT32 - 0

You know what this shows? JFS & FAT32 are BROKEN. There was a _reason_ I suggested using HPFS as a reference: "[it] has not been altered by well-meaning but potentially ill-informed third parties" the way bootable JFS has been.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on June 26, 2019, 03:52:20 pm
2Rich Walsh:
Yes,  indeed. I created the test example for DosFindFirst, and now see that different IFS'es return the following results:

HPFS - 4
JFS - 0
FAT32 - 0
RAMFS/EMSFS - 0
CDFS - 4
NDFS32 - 0

So yes, original IBM's IFS-es return 4, you're right
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Rich Walsh on June 26, 2019, 07:49:32 pm
NDFS32 - 0

Valery, which NetDrive plugin were you using when you tested NDFS32?

My _guess_ is that the plugin, not the generic filesystem, supplies EA information. I know for certain that the ISO plugin returns '0' for DosQueryFile/PathInfo() (I never tested DosFindFirst()). It may be that other plugins return the correct value. I'm especially curious about the SMB plugin since that's the one that is most often used. I'd test it myself but I don't have a network set up right now.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on June 28, 2019, 04:42:54 pm
2Rich Walsh: My most used plugins for Netdrive are FTP and ISOFS plugins. I have no SMB shares in my flat, so
nothing to test on. At least, when FTP plugin is active, It shows 0 in DosFindFirst. Also, I checked ISOFS plugin,
it shows 0 too.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: R.M. Klippstein on June 29, 2019, 03:46:28 am
Hi valery, trying to compile r-199 on ArcaOS 5.0.3 craps out on Vboxacpi. (Thats probably normal!) I'm guessing you are compiling with eCS. r-199  compiling with eCS-B2 gives the same RC error "RC: error - only interger type allowed ()." that earlier revisions gave. it then deletes the compiled virtualbox.exe. I still haven't been able to figure out a fix for this, any suggestions?

Thanks klipp
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on June 29, 2019, 02:31:02 pm
2R.M. Klippstein: I'm compiling with both MCP2 and eCS 2.2, and I see no problems. VBoxACPI -- what do you mean? IASL errors?
RC error? Hm. Is it somewhere complained about that error already? I don't remember what's the problem already. A week ago,
I compiled the VBox sources in eCS 2.2 VM under Linux host -- no problems, all build time dependencies were the latest from the Netlabs-exp
repository. I don't have ArcaOS, so no idea. Maybe, you're using Netlabs-rel?

PS: in r199, only Additions were updated, so you'll not get any advantages compiling all VBox sources.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: R.M. Klippstein on June 29, 2019, 08:24:35 pm
@valery, It looks like the RC error is caused by encountering a negitive value while doing the final (ibelieve it's the final)  compile of virtualbox.exe I'm really dumb on this error, I've been trying to solve it since r-155 ! Its obviously something messed up in my area.
I do my compiling on AMD boxes, I guess I'll try to do it on my Intel based server next, but I bet I get the same results.
As far as ArcaOS compiling , it can be done and gets the same results but not worth the hassel withACPI.

Good to see you back working on Virtualbox, Thanks for all the excellent work and effort.

klipp
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Dave Yeo on June 29, 2019, 09:31:01 pm
Which rc is being used? WRC and the various IBM RC's seem to behave differently in some circumstances. Here Mozilla only compiles with rc ver 5 IIRC and gets errors with wrc. IIRC, some of the IBM rc's don't like slashes as path separators.
Running emxomfld without parameters will show the relevant environment variables.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: R.M. Klippstein on June 30, 2019, 01:00:57 am
Hi Dave, It I'm TOTALLY lost when it comes to anything pertaining to RC! When compiling Valery's virtualbox source code the EMXOMFLD TYPE uses WLlink . It looks like WRC is used as OPEN WATCOM is needed for the compile. I'm not smart enough to add anything that might be termed as intelligent! Sorry, But thanks for any additional suggestions.

klipp
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Dave Yeo on June 30, 2019, 01:56:17 am
So the compiler is OpenWatcom? In that case ignore what I said about rc.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on June 30, 2019, 03:15:49 pm
2rklipp: Can you show which "rc" and "iasl" versions do you have? What "which wrc", "which  iasl" commands say? Start them and show
which versions they show?
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: R.M. Klippstein on June 30, 2019, 11:47:30 pm
2valerius
rc is in H:\OS2\rc.exe  (88041)
iasl  vboxtools\os2x86\bin\iasl.exe   (533548)
wrc h:ºwatcom\binp\wrc.exe   (250515)

It turns out I didn't have bison installed, I installed it and re-compiled and now iI get:

weakld error: Unresolved symbol (UNDEF)  '_yydebug'.
The symbol is rferenced by-.
H:\199-VBox\out\os2-x86\release\object\VboxDTraceCmd\src\VBox\ExtPacks\VBoxDtrace\generated\dt_lex.o

do I need sometthing else installed?
Thanks for the help.  klipp
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 01, 2019, 02:05:06 am
wrc should be version from the yum repository, not from your version of OpenWatcom. You should install gcc-wrc. Please install all
build time dependencies from here: http://trac.netlabs.org/vbox/.

Quote
iasl  vboxtools\os2x86\bin\iasl.exe   (533548)

What is 533548? This does not seem to be a valid date. I'm using the version

Quote
20170119

It is in my d:\ecs\bin directory. I can share it with you if you need. It should be on PATH when you're running configure.

Quote
weakld error: Unresolved symbol (UNDEF)  '_yydebug'.
The symbol is rferenced by-.
H:\199-VBox\out\os2-x86\release\object\VboxDTraceCmd\src\VBox\ExtPacks\VBoxDtrace\generated\dt_lex.o

I have no out\os2-x86\release\object\VboxDTraceCmd\src\VBox\ExtPacks\VBoxDtrace\generated\ directory in my
build at all. What is your kBuild version BTW? Mine is:

Quote
kmk -v

kmk - kBuild version 0.1.9998 (r118688303)
Built Jul 26 2017 20:41:48

Something is wrong in your environment.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: R.M. Klippstein on July 01, 2019, 08:23:11 pm
2valerius, I appologize for taking up so much of your time over the years, I will bother you no more!
Happy Birthday

klipp
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 01, 2019, 10:10:59 pm
R.M.Klippstein: No, no problem. I'm happy to help, if I can :) But better ask in Slack (as here is the topic on VBox Additions, not VBox in general).
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 04, 2019, 03:43:12 pm
Hi all!

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.

Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Doug Bissett on July 04, 2019, 05:04:47 pm
Quote
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.

Wow. That is a feature that is going to cause problems. PLEASE, if DOS can't read a long file name, don't show the file, at all (just like DOS in OS/2 does).
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on July 05, 2019, 01:00:20 am
The feature added is path translation: long <-> short filenames for OS/2 VDM.

I found that feature very interesting for testing purposes. If it causes problems, it would be more useful to document the problems instead of just fearing the worst.

I'm attaching a screenshot of a shared folder on virtualbox from a Windows host. OS/2 sees the files, and DOS also sees the abbreviated as 8.3 file names.

But opening "winfile" is a different story for me. If I run winfile (WinOS2 session) and point it to the W: drive (The one shared from the VirtalBox host) it will trap OS/2.

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Dave Yeo on July 05, 2019, 03:05:16 am
Simplest would be some type of switch, parameter or environment variable to enable/disable the long name conversion.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 05, 2019, 08:41:06 am
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.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 05, 2019, 12:03:26 pm

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.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 05, 2019, 03:10:55 pm
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.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Lars on July 05, 2019, 05:14:07 pm
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.

I can see another problem as documented in the screenshots that Martin provided:
there is a directory called "VBoxAdditions-os2-x86-5.0.51.r200". This directory name is "shortened" to "VBOXA~29.R20".
Obviously, the translation algorithm misinterprets everything after the last dot as a filename extension even though it is a directory. Additionally, the "extension" r200 is clipped to r20 because for a DOS filename extension only 3 characters are allowed.

I'd say that for a directory name, there should NEVER be an extension (but I am not sure how DOS handles a dot in a directory name). No matter what DOS does it would be much safer to never assume that a directory name has an extension and handle dots in directory names just as an ordinary character.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 05, 2019, 05:35:56 pm
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 http://freedos-32.sourceforge.net/lean/specification.php -- see "Fabricating a short file name").
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on July 05, 2019, 10:22:56 pm
Hi Valerius

I updated to r203 and still get a trap on winfile. I rebooted, open the WinOS2 program manager, run the winfile from the icon, selected the E: drive (that was automounted) and trap (attached screenshot).

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

I want to do logging to the COM port  but I don't know how to do it.
Quote
(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).

Do you have some documentation/link on how to do that??

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 05, 2019, 11:51:02 pm
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:

https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

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:

https://stackoverflow.com/questions/37728628/connection-through-com-port-between-host-and-guest-in-virtualbox

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?
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on July 06, 2019, 04:20:11 pm
Hi

I will check the documentation to produce a better log.

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?

I was not clear enough with this. Before, my VM only trapped with WinFile, now it also traps on the OS/2 command line (inside the same VM).

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 06, 2019, 07:23:50 pm
Hi all!

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

Quote
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.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 07, 2019, 01:37:00 am
Hi all again!

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

2Martin: does this build trap for you, when you using windows file manager?
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on July 11, 2019, 06:10:06 pm
Hi Valery, I've one among others who appreciated your job in these OS2 Guest Addition, fighting a little bit to install it due to my poor knowledge, but arrived to the end also thanks to your patient help.
I dealed with one previous version, think r204, and fighted a lot only for understanding what to do, the final result fitted enough my expectations except for the shared folder handling, which is then possible to me only acting from FC2 while it does not appear in WPS.
Reading here that you made some steps forward, I wonder if you suggest to try the latest version in case might have solved the WPS shared folder display (resulting empty in his WPS volume pane). I would try only if you believe this could solve the case, otherwise I keep the version that have installed months ago, also giving enough on my need.
Thank you
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 11, 2019, 10:11:46 pm
2mauro: The problem with empty WPS folder didn't solved yet, so far. Though, last versions stability was enhanced since "months ago". So, some traps and hangs were fixed. Also, some new features were added, like shortening file names for VDM. So, I'd recommend to update your version to the latest one.  Updating always doesn't hurt. If you see something bad, you always have option to roll back to the previous version.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: mauro on July 12, 2019, 09:18:54 am
if it will be only a matter of file replacing from old to new or some among them, without editing again the config.sys,  I'll try.
Thank you
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 12, 2019, 12:33:55 pm
Hi all! (especially, Martin).

I fixed stack overflows in filename translation (short <-> long) code, occuring on IBM's kernels. On OS/4
kernels all was ok, because they have twice more stack. So, trap 0008 occuring when selecting the shared
folder in windows file manager, may be fixed too, as I suspect that it is the same (I observed trap 0008 too).

Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Martin Iturbide on July 13, 2019, 12:27:34 am
Thank you Valery for the update. It is going to take me sometime to test it, like one week.
I will get back to this post once I try it.

Regards
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 13, 2019, 10:27:26 pm
Hi all!

There were some forgotten changes in previous release I added here. For example, forgotten memory release
in some places. So, now these memory leaks are fixed. Martin, please better use this version.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: ivan on July 21, 2019, 05:46:51 pm
Hi Valery,

I'm still trying to get vBox working on OS/2 on my Ryzen based computer.  I downloaded the vbox-os2-v5.0.51 and followed the instructions for installing but all I get when I try to run it is an error (see attachment).

I therefore have some questions.
1) does the vboxdrv.sys give any indication when it loads?  I see nothing when config.sys lists drivers, top and other process viewers don't show it either.
2) do you think I am missing something obvious?  If so what should I be looking for?

Any suggestions or other ideas.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 22, 2019, 09:34:10 am
2ivan: No, VboxDrv.sys does not write any messages during the boot. The message you posted can mean different things. It means that it fails
to create the XPCOM object. Something got wrong. The reasons can be different. It usually just fails to load some libraries. Usually, some of the
required libs is missing, or outdated. Or, it fails to loads a library because of a shared memory problems. May also loading libraries to high memory
help. Or, some libraries are missing or outrdated. Are you sure you installed all needed libraries? The download page lists all the dependencies.
You'd better use yum/rpm to install dependencies, because installing everything manually is tricky and not supported.

PS: What VIRTUALADDRESSLIMIT do you have? (it may be too low)
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Doug Bissett on July 22, 2019, 04:53:37 pm
Quote
I'm still trying to get vBox working on OS/2 on my Ryzen based computer.  I downloaded the vbox-os2-v5.0.51 and followed the instructions for installing but all I get when I try to run it is an error (see attachment).

That problem is caused by LIBC. If you use DragText (part of ArcaOS), you can go to the Environment tab, in the VirtualBox icon, and add "LIBCX_HIGHMEM=2", and it will probably work. If you don't use DragText, you can add "SET LIBCX_HIGHMEM=2" to CONFIG.SYS (affects ALL programs that use LIBC), or wrap VirtualBox.EXE so it sets that before starting.

I have no idea what it really does, but it works, for me.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 22, 2019, 11:24:58 pm
2Doug Bissett: You're right. Another cause of this error could be libcx allocating buffers in high memory. Some OS/2 API's doesn't
like when buffers are in high memory, so they need to use them in lower memory. To use buffers in lower memory, IIRC, LIBCX_HIGHMEM=2
option can be used.
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: ivan on July 23, 2019, 02:54:01 pm
Thank you Valery and Doug for trying to help but after more reboots and chkdsk in the last two days than the preceding nine months I have decided to go the hardware route and have ordered the necessary KVM and PS/2 to USB adapters to make it work.

Yes, I did get vBox to limp along on OS/2/ArcaOS but the fact that I couldn't get it to install the latest Linux ZorinOS because it appears that vBox doesn't like 64bit OSs running on OS/2.

Apart from very frequent vBox crashes causing hard reset and chkdsk (3TB takes a loooong time), I was experiencing problems with several of the programs I run as standard.

Having now removed vBox and its driver from my main computer all appears to be back to what it was before I started the exercise and hopefully tomorrow (when Amazon delivers) I will be able to call up Zorin at the press of a button (it gives me firefox 60.8.0esr and direct access to my met station) all I have to do is work out how to share files between the two.

Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: Valery Sedletski on July 23, 2019, 04:34:32 pm
ZorinOS? What's it? Linux distro? Never used it. Yes, 64-bit guests currently don't work. Yes, some Linux distros
haven't a 32-bit version. The work on hardware virtualization is being worked on, but not yet. It should
work, in theory. At least. I ran Ubuntu 64-bit guest on WinXP 32-bit host, so it can be done on OS/2 too,
but not yet. Why do you need necessarily the exotic ZorinOS, why not e,g, Debian,
which has a 32-bit version?

PS: I have Debian on a bare hardware too (two separate machines and a ssh session from one
to another)
Title: Re: Shared folders IFS for VBox Additions, the test version
Post by: ivan on July 23, 2019, 05:41:17 pm
ZorinOS because I use it for teaching transition from Windows to Linux.  For some reason most people don't see it as 'threatening' or 'difficult' as other Linux versions.

I also have Linux Mint on a small form factor unit (ITX) that is the termination of my met station which feeds daily data to a couple of NAS boxes to allow for monthly data analysis using Mesa on OS/2.

Again, thank you for your help.