🚀 go-pugleaf

dic5340@hertz.njit.edu (David Charlap) writes:

> In article <92283.195245RONY@awiwuw11.wu-wien.ac.at> RONY@awiwuw11.wu-wien.ac
> >Larry:
> >
> >We are backlogged a week, so you might know the answer already.
> >
> >Create e.g. an OS/2-window-object, open the object-menu, choose open
> >settings, choose program.
> >
> >Save the settings.
> >
> >Move or shadow the object to the Startup-folder.
> 
> You can also create a file called STARTUP.CMD in the root of your boot
> volume.  This is the old (OS/2 1.2) way of starting up apps, but it
> works.  You just "start" or "detach" apps from it.  Be sure to end the
> file with an "exit" statement or the window will remain open at a
> prompt.
> 
> -- 
> David Charlap         |"there aren't 50,000 things for which it's worth writi
> dic5340@hertz.njit.edu| software; and the computer industry doesn't have enou
> ----------------------+ programmers to create that much good software.
> Therefore, most of it must be worthless" -- Boris Beizer "The Frozen Keyboard

I have a STARTUP.CMD file with the code from one of the redbooks that's
supposed to keep programs and stuff from starting.  The OS/2 Command
Window stays open even though the file ends with EXIT.  What am I
missing here:   Code follows
/* Clear startup programs from OS2.INI */            
 call RxFuncAdd 'SysIni','RexxUtil','SysIni'         
 call SysIni,'PM_WorkPlace:Restart','DELETE:'        
 call SysIni,'FolderworkareaRunningObjects','DELETE:'
 exit                                                

Rob Rittenhouse
                                                     
Rob@cybernet.cse.fau.edu
RITTENHO@acc.fau.edu