SCOUG-HELP Mailing List Archives
Return to [ 03 |
September |
2003 ]
<< Previous Message <<
>> Next Message >>
5
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Content Type: text/plain
Content-Transfer-Encoding: 7bit
Peter:
If you try my GUI program (I E-Mailed it to you yesterday), it may or may not work for
you. I cannot really test it out on my system. The problem is that inside the program the
code refers to another file, "CR", which is an ASCII file. That file holds the Carriage
Return-Line Feed characters for use in the REXX program, RUN.EXE. VisProRexx
says that all I have to do is compile the RUN.EXE executable as "self contained" and
that's all there is to it. I can then distribute it to anyone else and they can successfully
use it. I'm not so sure that's correct in this case, because of the the need to use this
ASCII file.
Why don't you try the RUN.EXE out on your system. If it does not work do the following:
1. Attached is the ASCII file, "CR"
2. Place that file in a folder named, "SubProcs"
3. Place the "SubProc" folder inside the same folder that contains the
RUN.EXE program.
4. Invoke the RUN.EXE program
That should work!
HCM
Content Type: application/octet-stream
File attachment:
CR
Content Type: application/octet-stream
File attachment:
PETER.cmd
Content Type: application/octet-stream
File attachment:
PETER.dll
Content Type: application/octet-stream
File attachment:
RESOURCE.VPR
<< Previous Message <<
>> Next Message >>
Return to [ 03 |
September |
2003 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
|