¿ªÔÆÌåÓý

  1. H390-Vm
  2. Messages
Single Messages Topics Expanded Polls

Re: Using Hercules version specific config file parameters with VM370CE

 

¿ªÔÆÌåÓý

Hi Bob, Fish and others,

Please note that I'm including information provided by Fish is a newer post than this one...

To summarize the posts and include additional information to the discussion.

??? Hercules 3.x knows nothing about the newer Hercules 4.x ARCHLVL and other configuration parameters.

??? Hercules 4.x will accept the older Hercules 3.x configuration parameters, but will issue a warning that are deprecated.

??? Fish's HercGUI (Windows only) currently rejects the Hercules 3.x configurations parameters (to be accepted in the next release) and INCLUDE statements.

??? Jacob Dekel's HercStudio (Linux and Mac) only supports Hercules 3.x only.? I'm not sure if it accepts INCLUDE statements.?

??? ??? I'm not sure that Jacob is maintaining this as the Yahoo group is no longer available.

??? None graphical interface users who are only affected by the differences between Hercules 3.x and 4.x.

I had thought that Bob's option 3 was the best and easiest to maintain, but given the above information, I would suggest a single file with both Herc 3.x and Herc 4.x statements commented out and include some sort of Installation/User document similar to Jurgen Winkelmann's TK4- document.?

Fish has suggested an configuration/installation script to make the necessary changes to the configuration file based on the version of Hercules installed or failing that to prompt the user for the Hercules version.?

I think that a good Installation/User manual would go a long way to making new users to VM/370 CE more comfortable and at ease with it no matter which Hercules version or direction is chosen by the maintainers.

As far as dropping support for older versions of Hercules, I would say not until there is a reliable way to get SDL Hercules 4.x installed on Linux and Mac either by the distro's Software Manager utility, a DEB/RPM file or a reliable Build/Make file from source option.? Otherwise, you will have done a disservice to the community.

Thanks for listening.

Regards,

Gary?


On 1/2/22 10:58 AM, Bob Bolch wrote:

I changed the subject line to be more specific.

I caused the existing difficulty with ARCHLVL -vs- ARCHMODE because I thought that 3.13 supported both. That was an error on my part. However, there are more incompatibilities than just ARCHMODE/ARCHLVL.? The currently available VM370CE release exposed bugs in ECPSVM support for Hyperion only. That bug is reported as fixed, but I have found new bugs in the operation of the CP PER command modification, when ECPSVM YES is present in the configuration file and Hyperion 4.4.0 is used.

I think saying that you cannot use VM370CE with HERCGUI is not desirable, when the change needed to allow that package to work is trivial for the end user.?

Which of these is the most acceptable?for VM370CE to supply?

1. A config file for each release.?
2. One config file with tailoring instructions for other releases.
3. A small config file for each release. Each has an INCLUDE statement to pull in the common elements. Most statements are common between releases and would be in this common section.
4. One config file for the oldest supported Hercules release with instructions for modifying it for other Hercules releases.?
5. Same as 4, but we supply one config file for the newest release.

A separate question is can we ever drop support for a Hercules release??

Another question is what happens when an "old" configuration statement like ARCHMODE stops being accepted by a newer Hercules?

Your thoughts would be appreciated.
Bob Bolch
Join [email protected] to automatically receive all group messages.