Sorry for the delayed reply ... time is lacking.
Anyway, if you assigned the unused 105G as a primary
NTFS partition, this would be the end result (assuming
as I stated, that NT* follows the same enumeration
rules as MS-DOS) :
Drive 0 (250G) =
C: Primary/Active FAT32 35G (Both O/S)
D-F: Extended/Logical FAT32 33, 30, 30G (Both O/S)
K: Primary NTFS 105G (Normally, NT* only)
Drive 1 (40G) =
G-J: Extended/Logical FAT32 10, 10, 9, 9G (Both O/S)
You will notice how the K: partition is enumerated last,
so that even for O/S (that is, MS-DOS and W98) that can't
see this partition (being NTFS), all other partitions get
assigned the same drive letter. Beware that F: is partly
beyond the 128/137G limit for LBA32, so you need to ensure
LBA48 solutions are in place lest you corrupt C: due to
LBA wrap-around! Same applies for K: which is entirely
above this limit.
Now, as for the W9* IO.SYS patch, this is for a separate
problem. If you have a mixture of CHS and LBA partitions,
MS-DOS 7.XX (W9X) and 8.00 (WME) will sometimes use CHS
addressing for partitions beyond 7.8G, which must use LBA
addressing, since otherwise CHS wrap-around will occur. In
your case, all partitions will have been LBA types, which
should mean you are safe from this bug. However, if you
were to choose slightly smaller partitions on your second
hard drive, you might still be vulnerable to this bug.
As for the various service packs and updates from MGDx and
other sites, beware some of these will restore the standard
(ie. buggy) version of 'IO.SYS', so (if you had a mix of
CHS and LBA partitions types) you would need to restore the
patched version PRIOR to rebooting.
I have 2 hard drives in my computer and 2 DVD's. Both hard drives are EIDE/PATA. Right now I am running win98se and I want to install XP pro sp3 so it will dual boot both OS. Drive 0 is 250gb and Drive 1 is 40gb. Drive 0 has 5 partition volumes. C drive is primary/active with win98se installed on it. My other volumes have other programs installed into them except G drive, which I left empty. All volumes are FAT32 on both hard drives. So I have:
(Drive 0) ---------------------------------------------- (Drive 1) is extended partition with 4 volumes.
C:\ primary/Active win98se 35gb ------------- H:\ programs installed 10gb
D:\ programs installed 33gb -------------------- I:\ programs installed 10gb
E:\ programs installed 30gb -------------------- J:\ programs installed 9gb
F:\ programs installed 30gb -------------------- K:\ programs installed 9gb
G:\ empty 105gb
The order in which MS-DOS (*) enumerates partitions is :
a) First primary partition of each drive, in turn
All extended partitions of each drive, in turn
c) All remaining primary partitions of each drive, in turn
Drives that are not recognized are not enumerated.
* At least as far back as version 7.0, perhaps even 6.22
(earlier than that, only one primary partition was supported).
Assuming NT uses the same rules, what you should do is make
that 105G partition a primary partition. Then it will get
enumerated last for NT, & ignored for DOS/W9X. So all other
partition drive letters will match between the two O/S.
BTW, if you get phantom drive enumeration or other LBA problems
in W9X, you might want to try my revised patch for V7.10 'IO.SYS'
(based on original patch by Steven Saunderson), available at :
Thank you JDS (Joe) This sounds interesting to me, but am still a little confused here. If I make my G volume into a primary partition, then install NTFS on it, win98 won't see it, so then win98 will change the drive letters on my second hard drive, because there won't be a G volume on my first hard drive. Then what happens when I boot into XP, where it can see all volumes, to the letter assignment? Do you know if XP has to be installed on a primary partition? I have read XP will run from a logical drive as long as it can install it's drivers in the first primary partition of the hard drive.
Another question, what is this V7.10 - IO.sys patch for? I downloaded all the win98 updates from MDGx web site and installed them in order to get my 250gb hard drive to run win98se, and so far everything is working great.