Hi Bernd,

> On Feb 9, 2024, at 3:00 PM, Bernd Böckmann via Freedos-devel 
> <freedos-devel@lists.sourceforge.net> wrote:
> 
> Hello,
> 
> I uploaded Willis recent changes containing the HTML help 1.1.0 (English) to 
> the unstable Gitlab repo [1]. The other languages are still shipped in 
> version 1.0.8. This also contains version 5.3.6 of the HTMLHELP.EXE with 
> several bugs fixed. Crashes and display corruptions should hopefully not 
> occur anymore.

Awesome! Thanks.

> 
> Can someone please alter the interim build process, so that HTMLHELP is the 
> default help viewer, and this gets a little testing? I would do it by myself 
> but have no overview over the build process and probably not the permissions 
> needed.

The build process used by RBE (Release Build Environment) is a rather complex 
spaghetti monster. But, it is fully automated and minor changes like this are 
fairly easy to implement. 

When the RBE is putting together the Interim Test Build release, it pulls the 
lists of packages for the different media from the two installer projects on 
GitHub. 

Primary Installer Settings:
https://github.com/shidel/FDI/tree/master/SETTINGS 
<https://github.com/shidel/FDI/tree/master/SETTINGS>
(or, the unstable branch if it exists)
https://github.com/shidel/FDI/tree/unstable/SETTINGS 
<https://github.com/shidel/FDI/tree/unstable/SETTINGS>

Floppy Edition Settings:
https://github.com/shidel/FDI-x86/tree/master/SETTINGS 
<https://github.com/shidel/FDI-x86/tree/master/SETTINGS> 
(or, the unstable branch if it exists)
https://github.com/shidel/FDI-x86/tree/unstable/SETTINGS 
<https://github.com/shidel/FDI-x86/tree/unstable/SETTINGS>

(unlike Version Release Builds that always pull from the master branch, Test 
builds always pull from unstable branches when they exist)

So, the first step is to verify that the Package for HTMLHELP is included in 
the release and installed. 

The two sets of package lists are similar. But, have a couple big differences. 

The sets from the Primary Installer include simple expansion macros. For 
example, the PKG_FULL.LST includes a $PKG_BASE$ macro. That tells the installer 
to also include everything in the PKG_BASE.LST file. 

So for main installer, it would probable be good to install it with BASE and 
have it “Live” on the LiveCD. A minor change to PKG_BASE.LST. Since, the LiveCD 
always tries to make all the packages in BASE live, no change will be needed to 
the PKG_LIVE.LST. 

( the current PKG_BASE.LST has a reference to HTMLHELP commented out. just need 
to uncomment it for inclusion during install )

The Floppy Edition package lists are a little different. There is only a “BASE” 
for the install called X86_ALL.LST. It does not have any macros. But, it does 
contain platform specific switches for creating the install media archive. 
Those switches resemble comments with a “tag” direction. Individual tags are 
turned off and on in the list file. It starts by turning all tags on. Then, 
when software is not compatible with specific hardware, that tag is turned off. 

Since HTMLHELP should run on the lowest supported hardware, It would be in 
section with most of the BASE packages. 

( note: there is an old reference to base\help commented out. When AMBHELP was 
added, the package for “help” was renamed to htmlhelp)

Once HTMLHELP has been added to the install list, AMBHELP and probably AMBREAD 
should be commented out for the floppy version. Possibly for the main installer 
package list as well.

That will take care of making sure new test version of  HTMLHELP gets installed 
in the next interim build. 

But, there is one more thing we may wish to do…

We probably want to update the HELP.BAT file to prefer HTMLHELP over AMBHELP. 
That will require simply updating the HELP.BAT file in the FDHELPER package on 
GitLab. https://gitlab.com/FreeDOS/base/fdhelper/-/tree/unstable/BIN 
<https://gitlab.com/FreeDOS/base/fdhelper/-/tree/unstable/BIN>

All fairly simple to do. 

If you want to issue some pull requests with the changes thats fine. 

Otherwise, I’ll get to it sometime over the next few days. 

:-)

Jerome

Oh BTW... If your interested in seeing the RBE in action, or making builds 
locally, it’s very easy to install and create builds. You can read the 
instructions for installation into a virtual machine at 
https://gitlab.com/FreeDOS/OS/builder/-/wikis/home 
<https://gitlab.com/FreeDOS/OS/builder/-/wikis/home>

It’s been a while since I did a fresh install of the RBE. So, hopefully newer 
versions of the OS that runs the RBE haven’t broken the install or build 
process. 



> 
> Thanks! Bernd
> 
> [1] 
> https://gitlab.com/FreeDOS/base/htmlhelp/-/commit/621b781ee2bedc777dcf6f2c86065002f6d48000
> 
> 
> 
> 
> _______________________________________________
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel

_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to