Preparing a New HD for Win2K?

[Bill]

Hi, I'm preparing a new laptop HD for Win2K.

Initially, I want two disks: C: (30G) with Win2K & programs, and D: (25G) for data. C:
and D: will be NTFS.

but... I *MIGHT* have to install Win98SE for a dual-boot configuration later, I don't
know, (depends on if all programs install over correctly). I'm leaving lots of free
space. Using V-COM's SystemCommander, I can dual-boot Win2K and Win98SE if C: is NTFS.

Thing is, it's been so long since I've set partitions on a new hard drive.

Do I:
- Make C: in a 30G primary partition,
- then make a 25G extended partition and create a logical partition inside that called
D:?

or something else...

THANKS!

Bill.

 

[Pegasus \(MVP\)]

Hi, I'm preparing a new laptop HD for Win2K.

Initially, I want two disks: C: (30G) with Win2K & programs, and D: (25G) for data. C:
and D: will be NTFS.

but... I *MIGHT* have to install Win98SE for a dual-boot configuration later, I don't
know, (depends on if all programs install over correctly). I'm leaving lots of free
space. Using V-COM's SystemCommander, I can dual-boot Win2K and Win98SE if C: is NTFS.

Thing is, it's been so long since I've set partitions on a new hard drive.

Do I:
- Make C: in a 30G primary partition,
- then make a 25G extended partition and create a logical partition inside that called
D:?

or something else...

THANKS!

Bill.

A couple of comments:

- 30 GBytes for a primary partition sounds overly generous if
you intend to store your data on a separate partition (which would
be a good idea). I would select 10 GBytes for Win2000 or
15 GBytes for WinXP.

- My boot manager lets me boot into an OS installed on any
partition on any disk. You need to find out if System Commander
has this capability too or if it only boots into OSs installed on
primary partitions on the primary master disk.

 

[R. C. White]

Hi, Bill.

Using V-COM's SystemCommander, I can dual-boot Win2K and Win98SE if C: is
NTFS.

Are you sure? I've not run either Win2K or Win9x in several years, but I
well remember the mantra: Win9x cannot read, write, or even SEE an
NTFS-formatted partition. Therefore, it certainly cannot boot from such a
partition. And, since it cannot boot from any but the System Partition
(Active primary partition on the drive designated as the boot device), this
almost always means that C: must be FAT(x).

Has this changed? Or has V-COM figured out a way around it?

The archives of this NG are full of messages from several years ago from
folks who wanted to add Win9x to a system that already had C: formatted as
NTFS. We usually referred them to sites such as this one by MVP Doug Knox:
http://www.dougknox.com/xp/tips/xp_repair_9x.htm

Doug wrote this one for WinXP, but it's an update of the earlier Win2K
version, so it should still work with Win2K.

Since you are just now setting up a virgin disk, you might consider
formatting C: as FAT32. And, if you expect to access any files on D: from
Win9x, then D: also must be FAT32. Except for the System Partition (C,
neither Win9x nor Win2K will care whether its "boot volume" is a primary
partition or a logical drive.

Dual-booting with Win9x is (almost) the only reason I know of to use FAT
these days. But it is an absolute requirement to run those older Windows
versions which cannot deal with NTFS.

RC

 

[Bill]

Hi, Bill.


Are you sure? I've not run either Win2K or Win9x in several years, but I
well remember the mantra: Win9x cannot read, write, or even SEE an
NTFS-formatted partition. Therefore, it certainly cannot boot from such a
partition. And, since it cannot boot from any but the System Partition
(Active primary partition on the drive designated as the boot device), this
almost always means that C: must be FAT(x).

V-COM SystemCommander 8 replaces the boot loader with their own custom boot loader.
According to their docs, they will dual-boot Win98SE even if c: is NTFS - it's a selling
point. Their manual explains how to do it.

 

[R. C. White]

Hi, Bill.

Thanks for the update. Please report back and let us know how it works for
you.

RC