SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Mon, 12 May 2003 08:10:50 PDT7
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Startup options (was: More on setting clock from startup.cmd)

Content Type: text/plain

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

Harry Motin wrote:
>
> > . . . *should* work okay from STARTUP.CMD
>
> I believe that you can place shadows of PM program objects
> in the startup folder and they should work just fine.

Mornin', Harry,

There seems to be some confusion about STARTUP.CMD versus the Startup
Folder.

They are two different things. STARTUP.CMD is a command file in the
root directory of your boot drive. The Startup Folder is a Workplace
Shell object.

> I have JunkSky, StealthMonitor and the
> WPS Taskbar in the OS/2 startup folder.

JunkSpy, not JunkSky. Please! :-))

What is StealthMonitor?

Do you mean the WPS Taskbar from Warp 3?

> XWorkplace as a startup folder (and a shutdown
> folder) is more versatile.
> -- In XWorkplace you can set the order of the
> different programs that will run.
> -- You can set a time delay for the startup of
> the first program.
> -- You can set another (but single) time delay
> between all the remaining programs in the folder.

This is valuable info about XWorkplace, thanks.

In STARTUP.CMD you can also set the order in which the various programs
will run. A major difference is that in STARTUP.CMD the programs
execute one-after-the-other unless you specifically tell them to execute
in parallel (using the START command). In the Startup Folder and
apparently in XWorkplace as a startup folder the programs all start in
parallel.

In general, I don't like time delays because you never know if the task
you're waiting on has actually completed. (The hard drive could do a
thermal recalibration at that moment, for example.) It's better to put
the task you're waiting on in a wrapper that sets a flag when done, and
wait for the flag.

> Conceivably, you could set the order and timing of the
> NTP program such that the TCPIP SETUP.CMD has been
> executed and your system is properly setup for TCP/IP.

SETUP.CMD is run from CONFIG.SYS via CALL MPTSTART. SETUP.CMD completes
before CONFIG.SYS processing terminates, thus both STARTUP.CMD and the
Startup Folder have network access instantly.

The TCP/IP Startup object in the Startup Folder runs TCPSTART.CMD which
starts various network daemons, servers and functions you may have
selected. Review the file \tcpip\dos\bin\TCPSTART.CMD to see all the
options -- the functions you haven't selected are REM'd out. To select
any of these functions, the preferred method is OS/2 System -> Setup ->
TCP/IP Configuration and then choose the Autostart tab.

- Peter

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

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

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

Return to [ 12 | May | 2003 ]

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.