> To: scoug-help@scoug.com
> Subject: SCOUG-Help: IFS= sequence (was: basedev lines not foun
> --------------------------------------------------------------------
>
> =====================================================
>
> > [BASEDEV=] are loaded before the IFS's are running.
>
> In CONFIG.SYS, must IFS= appear before certain other lines?
>
> I notice, for example, that the IFS=...CDFS.IFS line is before
> BASEDEV=IBMATAPI.FLT in my CONFIG.SYS. Is this sequence required?
No. See below.
>
> 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.
>
> I know that BASEDEV= lines are processed based on the extension of each
> driver (the specific sequence is given in the BASEDEV= online
> documentation), and that BASEDEV= lines are processed before DEVICE=
> lines. But I've never seen any documentation on when IFS= lines are
> processed.
According to 'The OS/2 Warp Survival Guide', by Azzarito and Green,
Chapter 10, the order can be at least be resolved to
1) BASEDEV=
(other references, as Mr. Skye points out, detail the order of these
being loaded.)
2) DEVICE=
3) Various 'Performance Statements'
(Which they specificly state includes IFS=)
From what I can tell, this group includes everthing
that does not fit in the other four groups I list here
or REM statements.
4) Environmental Variable Statements
(SET .....)
5) They don't mention them, but CALL
statements are executed after the SET commands.
I can verify this by personal experience.
There are also RUN statements that are not mentioned by A&G,
But I think they happen sometime before #5) above, probably after
#4) Someone who knows all can probably get more specific about this.
According to 'Your OS/2 Warp VERSION 3 Consultant', 2nd edition
by Herb Tyson, pages 317-318, all Run statements are launched
simultaneously, and order of execution cannot be guaranteed.
I know from many bootups with various CALL statements that
the sequence they are run in is always the order they are in
in the CONFIG.SYS file.
A&G state explicitly on page 440 that the statements in each
group above are processed in order they encountered, with a single
pass for each group.
>
> 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.
>
> - Peter
Probably something to the effect that access to the hardware
has to be established before abstract stuff like
organizing the data on the hardware into a filesystem
can be done. Just a guess.
Regards,
Dallas E. Legan II / leganii@surfree.com / dallasii@kincyb.com
Powered by......Lynx, the Internet at hyperkinetic speed.
=====================================================
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".
=====================================================
>> Next Message >>
Return to [ 08 |
March |
2002 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
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.
