AFAIK, ddinstall cannot modify INI files,
This should be possible by adding a section :OS2INI to the DDP.
Oh, that's good. So, it looks like everything can be installed with ddinstall only.
but this could be done from REXX.
REXX has to be installed first. So it will not work early at installation time. But an option for OS/2 <2.1.
Why do you need it early at installation time? It can be installed after the completion of installation,
and it is done always this way. Why OS/2 < 2.1
Do OS/2 versions older that 2.1 miss ddinstall?
But yes, ddinstall can be used at any time -- so you're right
(I plan to move shared clipboard code to a DLL loadable from SYS_DLLS, so VBoxService
no more contains PM-related code, so I could move VBoxService.exe from startup.cmd to a run=... line in
config.sys).
There are enough other solutions for clipboard sharing that will work with a wider range of virtualized OS/2 products. The current additions require files that are simply not available on a fresh install and do not work under most versions of OS/2.
Other solutions for clipboard sharing? What do you mean? I know only about one program
written by dink, it has versions for OS/2 and win32, only. But what to do in case of Linux or
any other less widely used OS?
Current VBox Additions use KEE API's, that's why they require Aurora-level kernel. So yes, it will
not work with Merlin, or older OS'es. I don't like this too. But that's how VBox works. The drivers
from OS/2 additions are built with GCC and should be 32-bit. Writing 32-bit drivers for older OS-es
has big issues. Drivers from the additions use VBox runtime. It's problematic to use VBox runtime
in 16-bit drivers. So, no way.
Which files that are not available at fresh install are used by the Additions? Do you mean, kLIBC/libcx/
gcc runtime? Yes, of course, they are required, as VBox (including the additions) is built with GCC+NASM.
So, these files are required. But this cannot be avoided. No way to build the Additions with Watcom,
currently. Anyway, it's easy to install kLIBC/libcx/libgcc in a freshly-installed system. The additions
depend on a small number of libs, indeed. Here's the list:
libc066.dll
gcc1.dll
libcx0.dll
Nothing more is required, I only omitted standard OS/2 DLL's like tcpip32.dll, pmwin.dll, doscalls.dll.