SCOUG-HELP Mailing List Archives
Return to [ 08 |
May |
2003 ]
<< Previous Message <<
>> Next Message >>
6
=====================================================
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.
=====================================================
This is a MIME encapsulated message.
Content Type: text/plain
Content-Transfer-Encoding: 7bit
>>/**/
>>call RxFuncAdd 'SysLoadFuncs', 'REXXUTIL', 'SysLoadFuncs'
>>call SysLoadFuncs
>>call SysCreateObject 'LSPeerWorkstation',,
>> 'Shared Resources and'd2c(10)'Network Connections',,
>> '', 'OBJECTID='
>>I get error messages:
>>REX0003E and REX0200E
>>"Failure to Initialize"
>Attach the full script to a message. It's not obvious what you are doing
>wrong, but you are getting closer.
Hi Steven,
That is the full script. Here is the original message, and attached is my
file: peer.cmd.
> >>My Connections-NetWork-Network Services does not have the 'Shared Resources
> >>and Network Connections' Folder, only 'Logons' and 'Lan Server
> >>Administration'.
> >>
> >>How can I recreate it?
> >
> >Using this bit of REXX:
> >
> >/**/
> >call RxFuncAdd 'SysLoadFuncs', 'REXXUTIL', 'SysLoadFuncs'
> >call SysLoadFuncs
> >call SysCreateObject 'LSPeerWorkstation',,
> > 'Shared Resources and'd2c(10)'Network Connections',,
> > '', 'OBJECTID='
> >
> >If that doesn't work, then try replacing WC_NETSERV with WP_DESKTOP. That'll
> >create the object on the desktop and you can then move it to wherever you
> want.
Sandy
Content Type: application/octet-stream
File attachment:
peer.cmd
<< Previous Message <<
>> Next Message >>
Return to [ 08 |
May |
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.
|