Need a new Boot manager

[Splork]

Hi,

I am building a new system. Will use XP and eventually install
Win7 on another partition.

I like keeping things separate. Previously used FAT32 and
System Commander. System Commander requires a fat partition.

If I create a fat partition, above or below the target
partition, XP installs it's boot files there and labels it
drive C: D: gets the windows install.

Leaving all the unused space on the drive
unpartitioned/unformatted I get XP properly installed on the
Second partition area. System Commander will not function
though. I suppose I could try adding the fat partition after
the OS install, but that gets cumbersome when it comes time to
install Win7. Deleting the dos partition to install Win7 makes
the boot manager fail. Would be lots of creating and deleting
that partition if it succeeds at all.

Is there a boot manager that you folks know about that will
allow me to have the booted OS show up as drive C:

Win 98 and WinXP coexisted well and behaved under system
commander. Can I get this functionality back for NTFS OSs

Suggestions welcome

 

[Trimble Bracegirdle]

Its best to have different O/S's on different Physical drives
then switch between them by selecting in the Motherboard BIOS the disk
to boot first.

You will have to find a new Boot Manager but bear in mind that Windows 7
own boot manager can competently cope with Multi-boot
with other older O/S's.

Install the newest system first then older onto that.
All versions of Windows ever, require use of the first part of a HD
Boot Sector (shared or not) to start.

Do you really need FAT32 ???? convert to NFTS if possible.
Remember FAT32 can not do files larger than 4 GB & cannot
manage large modern disc capacities over 32GB with out problems.
(\__/)
(='.'=)
(")_(") mouse

 

[Doum]

Its best to have different O/S's on different Physical drives
then switch between them by selecting in the Motherboard BIOS the disk
to boot first.

You will have to find a new Boot Manager but bear in mind that Windows 7
own boot manager can competently cope with Multi-boot
with other older O/S's.

Install the newest system first then older onto that.
All versions of Windows ever, require use of the first part of a HD
Boot Sector (shared or not) to start.

(\__/)
(='.'=)
(")_(") mouse

I was always told to install the OLDEST OS first and it has always worked
for me.

On one system, XP was installed first and when I installed Seven, its boot
manager was installed and it works perfectly.

When I boot in XP, the drive where XP is installed shows up as "C" and when
I boot in Seven the drive where Seven is installed shows up as "C". I don't
need to go to the BIOS. I think the Seven boot manager is installed on the
XP drive since it's the first hard disk in the BIOS.

 

[Seth]

Install the newest system first then older onto that.
All versions of Windows ever, require use of the first part of a HD
Boot Sector (shared or not) to start.

Oldest first. If you install Win7 first, the XP boot menu won't recognize
it. Install XP first and the Win7 boot menu will.

 

[Ken Blake]

Do you really need FAT32 ???? convert to NFTS if possible.

I agree.

Remember FAT32 can not do files larger than 4 GB

True.


& cannot
manage large modern disc capacities over 32GB with out problems.

But not true.

Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003

 

[Trimble Bracegirdle]

"& cannot

manage large modern disc capacities over 32GB with out problems

....not true." ?????

Really ?! I mean would it really be sensible & problem free to format
a 1TB drive with FAT32 ??? (one single partition)
(\__/)
(='.'=)
(")_(") mouse (I Like Girls With Big Clusters)

 

[Ken Blake]

...not true." ?????

Really ?! I mean would it really be sensible & problem free to format
a 1TB drive with FAT32 ??? (one single partition)

LOL! You are equating "disc capacities over 32GB with "1TB"?

Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003