🚀 go-pugleaf

Scott Mattes (Mattes@navsealog.i-net.com) wrote:

:   A couple of weeks ago I asked about a utility to open folders from 
: startup.cmd. I finally found one on a local BBS and I want to give it to a 
: wider audience. Where is the best FTP site to put it on?

The best place on the Internet for such a utility would be:

	hobbes.nmsu.edu : os2/incoming

This site, and its most popular mirror, ftp.cdrom.com, are the best 
places on the net to find OS/2 related software.  Put it there.  You 
might also email Dave Tholen, the moderator of the comp.os.os2.announce 
newsgroup, and tell him to post an announcement for all to see.  Include 
the text of the announcement in your post to him.

---

Larry R. Tubbs Jr.                    ltubbs@netcom.com
Team OS/2                             Author of PM Attrib and File Info
              -----PGP PUBLIC KEY AVAILABLE-----

Scott Mattes <Mattes@navsealog.i-net.com> writes:

>  A couple of weeks ago I asked about a utility to open folders from 
>startup.cmd. I finally found one on a local BBS and I want to give it to a 
>wider audience. Where is the best FTP site to put it on?

If you just want to open the folder on boot, why not simply drag a
shadow of the folder into the startup folder, the same way you would get
anything else to start up on boot? The 'startup.cmd' folder is there for
compatability reasons with old OS/2 1.x programs, and is executed before
the WPS starts up. You should always use the startup folder, if possible.
Handy hint - if you want items in the startup folder to launch in a
specific order, open the folder up in 'flowed' or 'details' view and
drag the objects inside to the order you want them to start up...


				Andrew Williams,
				Physics, Uni of Western Australia.

andreww@uniwa.uwa.edu.au (Andrew Williams) writes:

>If you just want to open the folder on boot, why not simply drag a
>shadow of the folder into the startup folder, the same way you would get
>anything else to start up on boot? The 'startup.cmd' folder is there for
>compatability reasons with old OS/2 1.x programs, and is executed before
>the WPS starts up. You should always use the startup folder, if possible.
>Handy hint - if you want items in the startup folder to launch in a
>specific order, open the folder up in 'flowed' or 'details' view and
>drag the objects inside to the order you want them to start up...

Actually, there still are good and solid reasons for maintaining the
STARTUP.CMD in addition to the STARTUP folder.

The STARTUP Folder is great, but it has no mechanism for ensuring that one
job is completed before the next job starts.  Admittedly, you can place a
.CMD file in the STARTUP folder, but STARTUP.CMD makes more sense.

STARTUP.CMD is almost always used by networking software such as Lan
Server/Lan Manager when there needs to be an established order to loading
programs.  It's easier for STARTUP.CMD to be managed by script-driven
installation programs, too.

Albert
--
Albert Crosby          | Microcomputer & Network Support | IBM Certified
acrosby@comp.uark.edu  |   University of Arkansas        |  OS/2 Engineer &
1 501 575 4452         |     College of Agriculture And  |   Lan Server 
=======Team OS/2=======|       Home Economics            |    Administrator*