SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 03 | August | 2001 ]

>> Next Message >>


Date: Fri, 3 Aug 2001 00:41:53 PDT
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: Boot drive ?

Content Type: text/plain

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.
_____

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

-- 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".

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


>> Next Message >>

Return to [ 03 | August | 2001 ]



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.