SCOUG-HELP Mailing List Archives

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

Date:	Fri, 8 Mar 2002 12:16:29 PST7
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: IFS= sequence (was: basedev lines not found)

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

In <3C884C22.1061@peterskye.com>, on 03/07/02
at 09:29 PM, Peter Skye said:

>In CONFIG.SYS, must IFS= appear before certain other lines?

It's an old wives tale best I can tell. The kernel makes multiple passes
through config.sys during loading. From my config.sys notes:

REM --> Load order BASEDEV (SYS BID VSD TSD ADD I13 FLT DMD) IFS DEVICE
REM --> CALL waits for completion, RUN does not ===

BASEDEV's come first with the sub-ordering show above. Then IFS's. Then
DEVICE's. Once the all device driver initialization completes (i.e. the
init complete strategy routines are called) RUN's and CALL's are done in
the order found.

I've always gone under the assumption that keyword commands (KEYS=ON etc)
and SET statements are processed in the first pass through config.sys.
However, since drivers can't access the environment, this could be delayed
until just before the RUN's and CALL's are invoked.

>I notice, for example, that the IFS=...CDFS.IFS line is before
>BASEDEV=IBMATAPI.FLT in my CONFIG.SYS. Is this sequence required?

Nope.

>I'm unclear on when (which scan of CONFIG.SYS) the IFS= lines are
>processed and what other lines are processed on that same scan.

See above. The answer is NONE.

>documentation), and that BASEDEV= lines are processed before DEVICE=
>lines. But I've never seen any documentation on when IFS= lines are
>processed.

I've read it. It's hidden somewhere in cmdref.inf.

>There must be a reason that the Warp developers have us use
>IFS=...HPFS.IFS instead of DEVICE=...HPFS.IFS. Darned if I know what
>that reason is; I'm guessing it has something to do with the load
>sequence.

The kernel state is in a different state when loading IFS's, so I suspect
it was done to make this obvious. When loading IFS's, all BASEDEV's are
loading and running. When loading DEVICE's, all IFS's are all loaded and
running.

Steven

--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.31a #10183 Warp4/FP15/14.085_W4
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
---------------------------------------------------------------------

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

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 [ 08 | March | 2002 ]

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.