Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 217171 - incompatible with System Commander 8
incompatible with System Commander 8
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i686 Windows
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
: 217172 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2006-11-24 11:42 EST by William Biesty
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-11-28 13:29:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description William Biesty 2006-11-24 11:42:02 EST
Description of problem:
Incompatible with system commander 8, the multiboot and partitioning software.

Version-Release number of selected component (if applicable):

How reproducible:
install system commander 8 (SC8) on windows xp sr2 with a separate hard disk 
for Fedora, install Fedora on partitioned and formatted second drive, boot 
from first drive, Fedora starts but Windows XP drive and partition is lost 
requiring a complete repartition and install.

If Fedora is installed with out the boot, SC8 complains it is not a valid 
linux and when selected the PC hangs but the windows xp drive and partition 
still works.

Steps to Reproduce:
Actual results:

Expected results:
Boot either Fedora or Windows xp.

Additional info:
I got Fedora core from the Mark Sobell book "A practical guide to RedHat Linux.
Comment 1 Jeremy Katz 2006-11-28 13:29:03 EST
This sounds like a bug with SystemCommander 8.  Unfortunately, we can't really
do much with proprietary apps like this
Comment 2 Jeremy Katz 2006-11-28 13:36:32 EST
*** Bug 217172 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.