SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 04 | October | 2007 ]

<< Previous Message <<


Date: Thu, 4 Oct 2007 23:46:42 -0700
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: IFS load

In <4705922E.70703@charter.net>, on 10/04/07
at 06:24 PM, Ray Davison said:

Hi,

>But it seems like catch 22. If OS/2 cannot access X: HPFS without
>loading the IFS, and you tell it to get the IFS from X:, how does it
>find X: to get the IFS to load?

The same what that is have been since OS/2 was invented. Also, the same
way the BASEDEVs are loaded.

>For the BASEDEVs does it do a "get from this partition"?

Sorta. I've discussed this before, but basically, drive letters don't
exist until late in the boot process. The MBR code used the partition
table to find the location that contains the first boot sector of the
partition/volume. The boot sector code know how to load the rest of the
bootloader. The bootloader contains the microFSD. This FSD is has enough
smarts to allow the bootloader to load os2boot (the miniFSD), os2ldr and
os2krnl. The bootloader passes control to the kernel which continues the
boot process. The kernel use the miniFSD to load the basedevs. The
kernel also asks the miniFSD what drive letter the boot volume is. After
the basedevs are loaded, the kernel enables the drivers and continues the
boot process. One part of this is the verify that the boot drive letter
known to the miniFSD matches what the DMDs know it as. This is really
where drive letters start to exist. Eventually hpfs.ifs is loaded. Once
loaded, it takes over from the miniFSD.

>Every partition has a letter and they are in order.

They always will be on single drive system when running Warp4. Does the
boot partition have the expected drive letter?

You do need to make sure you are asking dfsee to display the Warp4 style
drive letter assignements.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 3.00 beta 08pre #10183 eCS/Warp/DIY/14.103a_W4 etc.
www.scoug.com irc.ca.webbnet.info #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
"postmaster@scoug.com".

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


<< Previous Message <<

Return to [ 04 | October | 2007 ]



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.