AvdP

FWIW, my output on WIN10 64-bit with a recent oRexx 32-bit seems ok: REXX-ooRexx_5.1.0(MT)_32-bit 6.05 19 Sep 2024 value 0.00000000000000016666666666666666667 format 0.00000000000000016666666666666666667 plus 1 1.00000000000000016666666666666666667

SEEK does not affect WRITE position

What version ooRexx have you installed? Note similar bug report 1529: https://sourceforge.net/p/oorexx/bugs/1529/

typo in rexxref.pdf - wrappered or wrapped

rexx.dll locked error message, still there: - ooRexx-5.0.0-12558.windows.x86_32 - on a clean WIN10 system that has no previous ooRexx installation It is not the error itself that concerns me (I know the solution), it is the misleading error message: .. this indicates that not all Rexx programs have been halted.

Hi Glenn, If you add a file with code to reproduce this error, and also mention your oRexx and Windows versions you will probably get quicker and better response to your questions.

Erich, Works fine. I built a 32bit installer with my VS2019 + CMake v3.20 and reverted to line cmake_policy(VERSION 2.8...3.3) Then executed the installer in a virgin WIN7 32-bit and rexx -v did not generate MSVC errors.

This code is apparantly supposed to replace /MD by /MT. But if the flag strings do not contain /MD (as it is in my local build environment) nothing changes to /MT. You mention a better solution for recent CMake. Care to share? I wish to force /MT for some tests.