Jochem Peelen

The originally reported problem was no longer encountered when installing build 12079: - 32 bit ooRexx under Windows 8.1 as well as - 64 bit ooRexx under Windows 10 1909 A "quick upgrade" type of install was done; the uninstaller from build 12074 had no problem to remove rxapi and continue the uninstall. I did not systematically test this with the builds I installed over the 14 months since reporting the problem. Routinely, I logged off and on before installation to make sure rxapi did not run. Therefore...

Sorry for the confusion, the previous message was intended for bug #1627 (rxapi locked)

The reported problem was no longer encountered when installing build 12079 on - 32 bit ooRexx under Windows 8.1 - 64 bit ooRoss under Windows 10 1909 Doing a "quick upgrade" type of install, the uninstaller from build 12074 had no problem to remove rxapi. I did not systematically test this with the builds I installed in the 14 months since reporting the problem. Routinely, I logged off and on before installation to make sure rxapi did not run. Therefore I cannot tell which build brought the fix to...

The problem did not show up during a dozen installs of builds 11895 through 11926. I propose to close #1628 as a duplicate of #1641. Regards Jochem Peelen

After installation of builds 11891, 11892 and 11893 on three consecitive days, I can confirm that the behaviour as described in ticket 1628 did not show up on these three occasions and might have been solved by the fix to 1641. Regards Jochem Peelen

Rexx build 11861; everthing else unchaged compared to opening of this report. This evening the bug unexpectedly showed up during ordinary work (no new installation) after creating a new subdirectory and copying 12 files to it using the Windows Explorer: In an ordinary command line window, "the -p profile.the" resulted in the profile not being processed by ooRexx and THE error message 0052 as describe above. From an administrator command line, the same command was processed withou bug. The bug was...

When installing build 11861 I was able to reproduce the behaviour. Sequence of commands immediately after installing the new build: 1) open administrator command line and change to ooRexx installation directory 2) issue "the -p profile.the" to check that interaction with THE is ok (dir.dir shown in XEDIT mode) 3) leave dir.dir using qquit 4) issue "attrib -A rexxtry.rex" and "attrib -A oorexxtry.rex" to change somethig in the installation directory 5) close administrator command line window 6) open...

Typo: the word NOREXX of course is within a comment. This software edited out the asterisks.