last updated at 24 Feb, 2007 22:56 (2 times)
Terry (01 Nov, 2006 17:06):[...]
The eCS IDE Channel => eComStation 1.2R (and the soon eCS 2.0)
will be HPFS-installed on a 60 gig hard drive (as primary) with a
200 gig hard drive (as secondary). Thus, the eCS install can be
within a primary partition on the 60 gig without a logical
partition. The 200 gig hard drive provides the expansion
flexibility for SVista, multimedia, etc.
The WinXP IDE Channel => An operational Win XP is on a
partitioned FAT 32 hard drive (for eCS file access) with 160 gigs
(as primary). WinXP is a "necessary occupational evil" due to
financial planning software apps.
You will avoid much frustration if you, as an instance, allocate
your first hard disk to WinXX primary partitions and (possibly)
LVM-enabled Boot Manager (BM); instead of allocating your second
IDE hard disk (whatever size it may be) to WinXX. OS/2 (and
Linux) will live "happy" on logical partitions.
Consequently, below is a suggestion that leaves the primary IDE
for your WinXX version(s) (and possibly Vista):
After you connect your hard disks, boot with your bootable media
to the LVM utility. You can do so by booting to a command prompt
and proceed to type F3. As mentioned to OriAl (<
http://www.os2world.com/cgi-bin/ultraboard/UltraBoard.cgi?action=Read&BID=61&TID=1712&P=1#ID1712 >), depending on where your manual LVM
files are located in your eCS bootable media, change directory to
that location and enter:
LVM.EXE /SI:FS/SIZE:120
Once inside of the LVM utility, observe the label at the top:
1) Logical Volume management Tool -Logical View
If your IDE (and or SCSI) hard disks have not been exposed to
LVM-enabled BM, you will simply see temporary placeholders for
removable media devices.
Pressing F5, you will be taken to the physical view of your
hardware. Note the emphasis label at the top:
2) Logical Volume management Tool -Physical View
Pressing TAB, a user will be taken to create an
3)
primary and/or logical partition.
It must be noted that when creating a Primary partition, the
default action is to allocate space from the beginning of the
first free space encountered; notwithstanding, when creating a
Logical partition, the default is to allocate from the end of the
free hard disk space. Consequently, if an user is to have more
control over the partitioning scheme, the physical view is the
way to go. Later the partitions can be assigned to a Logical
Volume as we will be doing.
4) Hence a Primary partition is selected
5)
...to be created at the beginning of the free space
6)
The partition is labeled and a
size for the primary partition is entered if
desired.
7) And we are done with the
first partition Note that since the physical partition has not been assigned to an LVM entity it is "Available."

The same procedure is applied
to the remaining section of the hard disk
9)
Hence the physical aspect
for the first hard disk entity is done Reiterating, both primary partitions are "Available" because they have not been assigned to an LVM entity.
10) Now, pressing F5 again, we are returned to the logical
view --Boot Manager needs to be installed if not already
done-- and it can be seen that we still need to
assign the primary partitions we created to the Logical Volume
Manager. This situation is analogous to that where there were
previous partitions in the hard disk and we needed to have LVM
"see" those.
11)
Noting that BM intrinsic properties
guide it to be installed on the first free space it encounters,
it installs itself at the beginning of the second IDE hard
disk since ALL of the first IDE hard disk is taken. The assertion can be verified by pressing F5 again to return to the Physical View and proceeding to select D1, i.e., the second IDE hard disk.
12)
We press F5 again and
proceed to assign the first primary partition to an LVM
entity
13)
The LVM entity has to be
Bootable, a drive letter is assigned to it, and also a
label
14)
The utility prompts us
for the physical hard disk unit to be selected.
15)
Needless to say, we
select D0, since there is the first (or existing) primary
partition that we want to add.
16)
Since we are selecting
an existing partition we simply verify that the default
information is correct.
Terry (01 Nov, 2006 17:06):
Question #1: What bootloader tips are appropriate?
Leverage the intrinsic qualities of each operating system you
may already have and/or will be installing.
As mentioned previously, WinXX can best be accommodated in
primary partitions -as Tex an Flywheel asserted. Consequently,
if you will be installing Vista later, allocate with your OS/2
LVM utility two primary Volumes in your first hard disk for those
--either the 60Gb or the 200Gb.
Leaving those two predatory operating systems in your first hard
disk will avoid you potential headaches later as you require more
flexibility.
Note that the flexibility provided by the OS/2 LVM-enabled Boot
Manager can allow you mostly any combination but consider
candidly your technical proficiency. By reading some replies, it
appears to me that not many people appreciate the power of the
OS/2 LVM-enabled Boot Manager.
Consequently, and placing emphasis on the intrinsic qualities of
the OS/2, think about placing it in a logical partition on your
secondary IDE attached hard disk. From there you can manage all
your first IDE primary partitions and allocate space for their
needs using LVM from within OS/2.
For instance, (unless you were
JoannaRutkowska, of course) due to the tendency for
infection/corruption of the MS offerings, from your OS/2 second
IDE hard disk you might recover when WinXX/Vista go down with
viruses/rootkits/hijackings and/or, of course,
Joanna's anticipated Blue Pill attacks.
Terry (01 Nov, 2006 17:06):
Question #2: What dual-booting tricks would you offer?
You may install OS/2's LVM-enabled Boot manager at the start of
your first hard disk. It may be installed at the end of your
first hard disk or at the beginning of your second hard disk.
Notwithstanding, consider seriously your technical abilities and
--to make your future manipulations easier-- put it at the
beginning of your first hard disk.
If you already have a WinXX partition covering the start of your
hard disk you might consider installing BM on the second hard
disk or even at the end of your first hard disk.
Leveraging the OS/2 LVM-enabled Boot Manger intrinsic tendency to
install itself on the first free space it encounters, you might
"trick it" to install on the second hard disk if you first create
(even if temporarily) a partition(s) covering your whole first
hard disk.
Terry (01 Nov, 2006 17:06):
Question #3: Does it matter whether WinXP is on IDE1 or IDE2?
As mentioned previously by several people, you will make your
life easier if you install it on the first hard disk on a primary
partition.
Terry (01 Nov, 2006 17:06):
Question #4: Will there be any LVM problems to recognize the
WinXP hard drive?
If your WinXX is an already existent entity in your hard disk you
may add it to LVM-enabled BM by the procedure stated throughout
this post. And it will boot from your BM.
If you will be installing your WinXX AFTER you have installed
your OS/2, you need to make some changes to the WinXX hidden
file BOOT.INI
As some people noted in this thread, even if you allocate the
WinXX primary partition from your LVM utility, on the reboot for
the second phase of the WinXX installation the WinXX install
utility will sometimes/often refuse to proceed.
This is one of the reasons that even if a user is to have an NTFS
WinXX in a multiboot environment, s/he needs to format in FAT32
initially, so as to have easier access to modifying the file
BOOT.INI in the root directory of their WinXX drive.
Opening that file in a text editor on the first phase of the
WinXX installation, you will see something like:
---------------------------------------------------------
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="MicrosoftWindowsXPProfessional"/fastdetect/NoExecute=OptIn
----------------------------------------------------------
Note especially the timeout= directive and if needed increase the
time in seconds to allow you to select which partition to boot
upon your second phase of the WinXX installation.
Additionally, note the partition(1) under [operating systems]
It is often the case that on the WinXX reboot to proceed to the
second phase of installation, Boot Manager will be assigned that
partition(1) and WinXX partition will become partition(2).
Consequently, an user will not be able to continue the second
phase of the WinXX installation.
A workaround is to modify the BOOT.INI file BY ADDING that second
partition after the initial partition(1) as follows:
--------------------------------------------------------------
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="MicrosoftWindowsXPProfessional"/fastdetect/NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="MicrosoftWindowsXPProfessional"/fastdetect/NoExecute=OptIn
---------------------------------------------------------------
With this change, an user will be able to continue her/his WinXX
second phase installation by selecting from her/his ensuing WinXX
menu partition(2) --of course, after OS/2's BM. Note that after
the WinXX installation is complete, the user simply edits the
WinXX BOOT.INI file to reflect the partition where WinXX is
residing.
A word of warning: Often (if not always) on the initial reboot after your WinXX has completed its installation onto your hard disk --yes, even if you allocated its primary partition with LVM-enabled OS/2 Boot Manager-- OS/2's Boot manager will not be there upon rebooting your machine; you will see that WinXX will restart into its partition but BM will be nowhere to be seen.In that case, all that needs to be done is reboot with the OS/2 bootable media again, enter into the LVM utility once again (as explained priorly) and --note carefully:
A1) Remove the Boot Manager, press F3 and save your changes.
A2) Reboot once again with your OS/2 bootable media and into your LVM utility and reinstal your BM. Note that you may need to add once again your bootable physical partition to an LVM entity from the logical view of the LVM utility (as shown on #12 and #13 above).
Possible shortcut to A1 & A2 above:
Often the rebooting procedure is not a necessary condition to bring back your OS/2 BM to manage your hard disk.
It is sufficient to redefine A1 above as follows:
Subsequently press F3 and reboot your system. Quite possibly your BM will appear showing the menu of bootable LVM entities...and you are done!
On the other hand, if WinXX starts up instead of OS/2's BM then go back and implement the full procedure stated in the section "A word of warning."
Needless to say, the short cut to the A1 & A2 mentioned above will avoid you the extra step of assigning once again your bootable partitions to LVM units. Moreover, it saves one the trouble of reassigning to LVM units even those non-bootable Compatibiliy (read FAT, FAT32, NTFS, etc.) and JFS volumes.