CompuServe Messages

Mike, The issue of Ultracard's relationship with ARexx has me a bit confused also (and is one of two main reasons why I chose to return my purchase of UC to my dealer for refund). My understanding of UC's support of ARexx is that basically it can tell ARexx to execute a Rexx script via the AmigaDos Execute() function, where the command executed is basically the equivalent of "rx uc-arexx-file". Sometimes the 'uc-arexx-file' is an in-line ARexx string script (multiple ARexx statements, separated by semicolons) and sometimes it is an external file name. If that is in fact the level of ARexx support, then Ultracard is NOT functioning as an ARexx host, but is running an external, dis-connected ARexx host (the 'rx' command). This is very different to providing true ARexx support, in which the ARexx host passes a script (file or string) to ARexx (via RexxMast's public port) to execute, and which in turn, RexxMast turns around and passes back "atomic" commands to the Rexx Host program to process as appropriate. No where in the documentation did I see any reference to the "atomic" commands supported by UltraCard when functioning as an ARexx host. Is this a documentation problem? Or is it an implementation problem, which I suspect. In the latter case, I feel that claiming ARexx support is mis-leading, as any program that provides the capability to Execute() any DOS program could (falsely, IMHO) claim ARexx support. There is more to true ARexx support than that. <continued>