Hi, Massimo...

On 08/27/24 12:52 pm, Massimo S. wrote:

Il 26/08/2024 07:01, Steven Levine ha scritto:

In <list-10700090@2rosenthals.com>, on 08/25/24
    at 02:40 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:

Hi,

the warpin os2.ini entry points to the directory C:\VAR\TEMP but that
directory is invalid, to avoid forther  problems the warpin os2.ini entry
has been deleted..

That's odd.  How did you make that happen?

Lewis, see if the ANPM installer should be fixed or not if someone is not
using the workplace shell

You can submit a mantis ticket.  It's up to AN if they wish to support a
configuration like yours.

Hi,

my one is just a feedback

luckily i found a work-around to install ANPM

if they are interested* they can answer my email and i will open a ticket

thank you

massimo

*i agree that my one is a "rare" setup/configuration

What is the issue with ANPM?

I've read this entire thread, and yet I see nothing which could be classified as an issue to be addressed in ANPM. If you are going to open a ticket, please be clear in the ticket as to how a change in ANPM could address your problems. Remember that ANPM has nothing to do with your WarpIN INI entries (it only calls WarpIN to handle WarpIN installers). ANPM only presents errors reported to it from yum and/or rpm, so unless it is *not* outputting an error message which it should, that's not an issue for ANPM. ANPM does indeed require a minimum WarpIN version of 0.9.14, but that is due to the multilingual installer and the unicode handling in the WarpIN script (which Paul R worked very hard to address - at my specific request - and to whom I shall be forever grateful for that work).

I'm just not seeing a failure of ANPM anywhere, here, regardless of your unique configuration. I see other things which don't look right, but nothing which could be handled by ANPM (bypass the environment validation, somehow? would that be wise?).