Installation on a faster system: Wrong REXX SysIni write process can lead to malfunctioning NEPMD.INI

[Andreas Schnellbacher]

After installation of NEPMD the EPM doesn't start with NEPMD settings. In contrast, the NEPMD program object 'Standard EPM' starts.

Renaming myepmd\bin\NEPMD.INI is a workaround for that. A new one is created on the next EPM start. The malfunctioning NEPMD.INI contains the entry:

RegDefaults -> \NEPMD\User\MovedUserFiles

while the correct temporary entry would be:

Install -> \NEPMD\User\MovedUserFiles

That explains why the RegDefaults? application wasn't written. It already contains (wrong) data. As a result, EPM won't start.

Additionally, that temporary entry is normally only written if the install script has copied previous files to a backup directory. The backup directory exists with the files etke603.dll and copydll.cmd. Normally they were deleted afterwards.

It seems as if patching etke603.dll to apply the NEPMD colors has failed at the end.