OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Virtualization => Topic started by: Dan Eicher on July 19, 2025, 02:37:43 am
-
I would like an easy way to make files available on a Windows11 machine (running virtualbox) available to Arca OS 5.1.1 running as a VM under vitualbox.
What is the easiest way to make files available?
-
Virtualbox, and most other virtualization software packages, have a "shared folders" concept. This requires "guest additions" to be enabled on the os within the VM; as you are running ArcaOS, I believe the guest additions are already enabled.
You only need to go into Virtualbox, find and enable a shared folder for your ArcaOS VM, and it will then show up in ArcaOS.
Read more about this in the Virtualbox Administration Guide, available from the Virtualbox download website.
Hope this helps ...
-
Thanks, I've done that windows emulation (7/xp) on Win11 - but didn't know if it worked with AOS.
I will try it and report back.
-
Shared folders fails to copy files in some cases, leaving a 0 length file on the host system. WPS seems to have the defaults for move and copy swapped.
Other than that, it seems to work pretty well. I wish there was a pair of applications that would allow OS/2 associations to result in actions on the host system. For example, WPURL objects should open a browser tab on the host system web browser.
-
Hello
Shared folders fails to copy files in some cases, leaving a 0 length file on the host system. WPS seems to have the defaults for move and copy swapped.
It is on my TODO list to open a ticket about the VirtualBox guests on OS/2 have this issue.
-"Drag-drop+Ctrl" (copy action) from the guest to the host it give me that failure of a 0 length file on the host system. (ERROR)
-"Drag-drop+Shift" (move action) from the guest to the host it works as the expected "file move". (FINE)
- Only "Drag-drop" from the guest to the host works as a "file move". I'm not sure if that is fine between two different drives. (NOT SURE)
Regards
Regards
-
Virtualbox, and most other virtualization software packages, have a "shared folders" concept. This requires "guest additions" to be enabled on the os within the VM; as you are running ArcaOS, I believe the guest additions are already enabled.
You only need to go into Virtualbox, find and enable a shared folder for your ArcaOS VM, and it will then show up in ArcaOS.
Read more about this in the Virtualbox Administration Guide, available from the Virtualbox download website.
Hope this helps ...
This is true for file in partition formatted FAT32 or NTFS not in JFS, this partitions is not presented by a WIN system to virtualbox and so to ARCAOS that run on it. To view this type of partition in native mode virtual box use a new VMDK virtual disk that map all partition you want.
This type of Virtual Disk is active only under Linux under WIN is in test mode, not usable for more one test. By now I work on a Virtualbox version 714 that permit to create this VMDK disk but not to use it more than one time.
-
Good day today, first I went down a wrong path, I found some websites, that lead me down a road of copying a bunch of files from /os2 to /os2additions.
I guess that was for old versions of virtualbox, I'm using 7.0 release something or other.
Then I found ReadmeArcaos in c:\os2additions directory, lots of good information in the readme on vboxcontrol and the vboxservice
At first I was going to do like windows and map under c, but then I found, I could map a whole new drive letter (d:) which I did and it worked great.
I copied the watcom installer (from 88watts) to the shared folder and ran it.
Then I was able to compile and run mthread.c from the os/2 sample directory.
-
FYI
I created a buy report in the VirtualBox site.
- https://github.com/VirtualBox/virtualbox/issues/98
Any corrections to my English or redaction to make it more clear are welcome on the ticket.
Regards
-
You should add the output of help sys0266 to the bug report.
SYS0266: The specified file was not copied.
EXPLANATION: Either the source and target files are not in the same
file system or the operating system does not support COPY for this
file system.
ACTION: Check the source and target file names and retry the operation.