In a message to William White  Jonathan De Boyne Pollard
wrote:

JD>   A much better solution would be to use 4OS2, the replacement command
JD>   interpreter from JP Software (see the FIDONET 4DOS echo), and use the
JD>   enhanced /DOS= switch to the START command.

JD>   To encapsulate everything in one file (4OS2's START /DOS= command
JD>   requires a second file to hold the settings), the best solution is to
JD>   use REXX.

JD>   Fortunately, the example code given for SysCreateObject (in the REXX
JD>   reference in your Information folder) is just about all there is to
JD>   running desktop icons.  The only missing parts are that you need
JD>   "Update" as the option, "OPEN=DEFAULT;"
prepended to the setup string,
JD>   and SET statements for any non-default VDM settings.  i.e.


JD>       result = SysCreateObject("WPProgram",
JD>                               ,"A Virtual DOS Machine",
JD>                               ,",
JD>                               ,"OPEN=DEFAULT;PROGTYPE=VDM;",
JD>                               ||"SET DOS_AUTOEXEC=C:\MYAUTO.BAT",
JD>                               ,"Update")

JD>   No, there aren't too many commas in the above.  In REXX files, the
JD>   comma is also the line continuation character.

   If I read this right, using a REXX, I gather from the above you can
start a session from a predefined icon on your desktop ?? I figured there
must be a way to do it, but never quite figured it out. So far, I've been
using the 4OS/2 "start" command (works great), just think it would be a
bit slicker to use an already defined icon on the desktop, then you can
go in and alter settings, etc.

Catch you later, Mike (mjh{at}rvrsd.mmbbs.mn.org)

 * WCE 1.5/2049 * God created women 'cause sheep can't cook

--- WILDMAIL!/WC v4.11a