SCOUG-Programming Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Fri, 3 Aug 2001 02:41:15 PDT
From:	<leganii@surfree.com >
Reply-To:	scoug-programming@scoug.com
To:	scoug-programming@scoug.com
Subject:	SCOUG-Programming: Boot drive ? / Homework results

Content Type: text/plain

On Fri, 03 August 2001, Peter Skye wrote:

> Sender: scoug-programming-owner
> To: scoug-programming@scoug.com
> Subject: SCOUG-Programming:
> Boot drive ?
> From: Peter Skye
> Reply-To: scoug-programming@scoug.com
> Date: Fri, 3 Aug 2001 00:41:53 PDT
>
> Steven Levine wrote:
> >
> > He's already got it under the name CREXX.INF.
>
> Well, Mr. Steven "Typo" Levine, I grepped and pmsearched all over the
> place looking for CREXX.INF to no avail.
>
> Finally found OREXX.INF (in \OS2\BOOK\). Next time, raise those eyelids
> a tad so the "C" doesn't look like an "O" and the proper key gets
> pressed, eh?
>
> Mr. Quackles says you did it on _purpose_ just to harass me.

No, I think one is *O*bject Rexx, the other *C*lassic Rexx.
I don't really know, but I'd guess one is called REXX.INF
if it is for the active interpreter - I've go that one on my system.
If I installed ORexx, this one would get renamed to
CREXX.INF when ORexx was activated as the active interpreter.

> _____
>
> Now then, I want my Classic Rexx programs to use the Object Rexx
> function calls (such as "SysBootDrive()"):

I did my home work assignment on this the other night.
I don't have the 'exehdr' (I think that was the name Steven L.
referred to.) utility Mr. Levine referred to, but I did run the
EMX 'strings' utility on c:\os2\dll\rexxutil.dll, and a large
chunk of the output was obviously the function name information.
(This is for Warp 3 / Fix Pack 35 by the way.)
I found that it had *all* of the Rexxutils listed
in Dick Goran's book (4th edition), whether they were listed in his book
for Classic or Object Rexx.
In fact it had in the header area SysGetEA listed twice
for reason's unknown to me, and two other functions
not listed in Goran's book,
SysQueryExtLIBPATH and SysSetExtLIBPATH.
If anyone has any info on these two in particular to fill me in
on, I'd appreciate it.
(I can take good guesses on them, but exact confirmable
information would be appreciated just for future reference.)
And, yes, I checked, there were no files 'crexx*' or 'orexx*'
incase I installed orexx years ago and forgot about it.

As for all the stuff below, it sounds like a good experiment,
and I for one would like to know what happens if you try
any of it. :-)

>
> -- 1. Do I need to update my .INF and .DLLs? Here's what I have:
>
> [G:\OS2\BOOK]dir *rex*
> 8-12-96 1:35a 790930 0 OREXX.INF
> 6-14-96 10:45a 203855 0 REXX.INF
>
> [G:\OS2\DLL]dir *rex*
> 8-09-96 12:25a 156291 49 NAMEREXX.DLL
> 11-20-98 3:58p 33725 0 OREXUTIL.DLL
> 11-20-98 3:58p 489013 0 OREXX.DLL
> 7-22-96 7:33p 43858 0 OREXXSC.DLL
> 7-22-96 7:33p 76878 0 OREXXSOM.DLL
> 7-22-96 7:33p 4002 0 OREXXWPS.DLL
> 6-14-96 10:45a 49189 0 PMREXXIO.DLL
> 12-16-97 1:09p 266047 0 REXX.DLL
> 7-23-98 3:54p 29603 0 REXXAPI.DLL
> 3-31-97 5:35p 61195 0 REXXCRT.DLL
> 8-01-96 1:53p 8360 0 REXXINIT.DLL
> 11-20-98 3:58p 49229 0 REXXUTIL.DLL
>
> -- 2. When I do a SysLoadFuncs() should I use "OREXUTIL.DLL" instead of
> "REXXUTIL.DLL"? I currently do this:
>
> rc = rxFuncAdd( "SysLoadFuncs", "RexxUtil", "SysLoadFuncs" )
> ...
> rc = SysLoadFuncs()
>
> I *presume* I'm supposed to use "ORexUtil" instead of "RexxUtil" when I
> call rxFuncAdd() because the DLLs are named REXXUTIL.DLL and
> OREXUTIL.DLL. Yes?
>
> -- 3. Since ORexUtil.dll is smaller than RexxUtil.dll, I'm wondering --
> am I supposed to rxFuncAdd() them *both*? Is there any reason I should
> continue to use RexxUtil? Is there any functionality in RexxUtil that
> isn't in ORexx? Does ORexUtil.dll load RexxUtil.dll by itself without
> me explicity doing so?
> _____
>
> Now, if I just swap the "C" and "O" key caps . . .
>
> - Confused In Rexx Land
> (He's confused everywhere else too. - Mr. Quackles)
>
>
>
> =====================================================
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-programming".
>
> For problems, contact the list owner at
> "rollin@scoug.com".
>
> =====================================================

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 03 | August | 2001 ]

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.