Hello. Oh, what fun it's been.
I HAD two hard drives. They *both* went bad. I buy
two New hard drives, both Seagate. One is 8.4 Gb and the other is 4.3 Gb. I format the first into FOUR FAT16 partitions using the FORMAT.COM which comes with WIN98 after
booting into single-task (DOS) mode. I install Windows98.
So far, so good. I also buy a ZIP drive. OK. I also have been using System Commander version 3.01 (now outdated Windows tells me when I try to take advantage of FAT32).
The second new Seagate drive arrives. I decide to install
my Windows NT 4.0 Workstation as an NTFS into this *slave*
hard drive. NT Setup cannot do this. It refers to drive 'C'
only and wishes with all of its heart to destroy (format)
drive C:, which is where Windows98 resides. I say NO.
The only way NT's setup program is to work is if I go into
BIOS and (changing cables and jumpers) and make this
4.3 Gb HD the only one, the primary master drive.
I now install NT 4.0 with the filesystem, NTFS. It works.
I now change the BIOS (AGAIN) to where the WIN98 drive is
the primary master and NT 4.0 is residing on the Seagate 4.3
Gb primary slave.
WHEW!
I re-boot the PC, for about the 155th time now. System Commander reports an error. It's an error in the first
sector of the slave drive containing NT 4.0 NTFS. I ininstall SCommander. I then re-install it brand new.
The results are the same. THEN, I go back into BIOS and
set up the 8.4 Gb Seagate where WIN98 resides and fire up
WIN98. SURPRISE!! I had partitioned this drive into 4
partitions, NOW 2 are not reported from within Explorer.
I work some more, cursing Bill Gates BIG TIME. I use
FDISK and FORMAT to lose everything that was there and
give me back another, larger partition.
WHAT GIVES Microsoft!?!?!?
QUESTION: (Worth extra point due to the excessive number
of words and runon text)
Given the above system configuration, how can I get both
of these Microsoft products to work independently of one another?
I wish to have a System Commander boot-up menu to do this.
I am well aware that FAT16 and FAT32 cannot be seen
from NTFS and vice versa.
JIM NOWLIN