OS/2, eCS & ArcaOS - Technical > Setup & Installation

VirtualBox and Warpin (wic.exe)

<< < (2/4) > >>

Andreas Schnellbacher:
You can use my DOSBox installer as a huge example for using REXX to extend WarpIN. Beneath extracting the files README.OS2, inst\* and the .wis file from Jochen's package, there exists dosbox-createwpi.cmd.

The REXX .cmd files contain tons of examples. The createwpi script allows for using either extracted files (from an older package) or include files. Jochen always builds his files with recent DOSBox files, directly from its repository, so for me remained only to download recent NLS files and convert their numerous encodings.

Special about the REXX code in the DOSBox WarpIN installer is: It downloads missing .rpm packages, edits a config file, removes all kinds of old DOSBox files and uses dynamic WarpIN page contents.

It's surely much to big to start with wic. But I can sent it to you if you want. I rarely watch my os2world.com PM area, so please drop me a note here, in case.

BTW: WarpIN has several flaws. Many of them can be worked around with WarpIN REXX. Christian had made 2 presentations about advanced installations. One is how to automate uninstall (quite complicated, implemented now by Alex) and the others I remember are how to debug contained REXX code and how to dynamically build installer pages (e.g. his genmac installer). For NEPMD he had created a preprocessor that expands vars in the .wis file. Furthermore, I have added to the NEPMD installation to rename old NEPMD entries in the WarpIN database. All these are very special and require some experience.

Some tips:


* Use Christian's Initialize_GetTitle method for REXX code executed on starting WarpIN.
* The names of the packages should be fix. Changing them later should better be avoided.
* Use the GROUP tag for subpackages.
* Folders created by the installer should not have the REPLACE flag for CREATEOBJECT. That allows for moving them manually. REPLACE may be useful for all other objects.
* HTML comments are not allowed within tags.
* For updates, allow for installing it over the existing files, without uninstall for convenience.

Alex Taylor:

--- Quote from: Bennie Nelson on December 29, 2021, 04:13:00 pm ---So I extracted the install script (wic -X) from the VirtualBox WPI file and listed the package (wic -l), but I have not found a way to list the specific files in the package other than extracting them with wic -x. It looks like I should be able to delete the 9 files, add the newer versions from the Guest Additions ISO, update the script (see below), and add that, as well.

Archive: "vboxadd.wpi"
WPI revision: 3
Stub size: 0 bytes
Package 1
     9 files, size:  5,107,122 bytes original
                     1,694,924 bytes compressed (67% compression)
Summary: 1 package(s), 9 files total
     5,107,122 bytes original
     1,694,924 bytes compressed (67% compression)

--- End quote ---

Put a package number at the end of the command line to see the files in that package.

Or you can use my ARCVIEW program, it will display WPI file contents.


--- Quote ---The version string for the PACKAGEID in the install script would need to be changed:
<PCK INDEX=1 PACKAGEID="Oracle\VirtualBox\Client Additions\6\1\12"

What am I missing?

--- End quote ---

Other than updating the changed files, not much. Unless, of course, the actual required install logic needs to be changed, in which case you'll need to figure that out.

Neil Waldhauer:
If you can find a readme, you might add a note to it explaining your change.

jailbird:
A dumb question..

Are the OS/2 Additions even really changed that often, or does their build system just automatically bump the release version every time they cut a new one?

I’m basically wondering if it’s even worth updating them, really?

Doug Bissett:

--- Quote from: jailbird on December 30, 2021, 11:08:09 pm ---A dumb question..

Are the OS/2 Additions even really changed that often, or does their build system just automatically bump the release version every time they cut a new one?

I’m basically wondering if it’s even worth updating them, really?

--- End quote ---

From what I have seen, the date, and time, on the files gets changed, at every release, but if you compare them to the previous ones, they are not really changed very often. They do get changed sometimes, but the only way to find out is to do a compare on the files. The safe, and easy, way is to always update, whether the files were actually changed, or not.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version