Damn you to hell, system commander. (help me)

Factual Questions
1

Here is the backstory:

I get partition magic, create a couple partitions. Install Red Hat Linux 7.1. It works, yay. Need more space in partition x. Resize, do a LOT of stuff, reboot. “Could not determine driver letters” Closes out. OK, so partition magic is screwed. At least my operating systems work.

grabs system commander 7.03

attempts to resize partition
Not enough ram? (PROBLEM #1). “upgrade to >64MB ram”. BUT I HAVE 256 MEGS. (this is PC133, btw)

OK, fine. So you don’t want to work either, eh? Then I’ll stab your heart. Or just uninstall. uninstall

reboot

Ahh, linux time. (PROBLEM #2) “partition is type 0” or something like that. “use partition manager for other OS to fix”.

:mad: does not describe my anger.

So how do I:
A) make system commander realize I have more than enough ram
B) make the partition type to 1 or something else.

2

No clue, sorry, but I’ll bump this from the bottom of page 2 for you. Good luck. :slight_smile:

3

Sorry buddy, you can see there have been a number of people who have opened this, but nobody really has an answer. The beauty of partition magic and system commander is a couple clicks and you can do all that you need. The horror of it is that a couple clicks and you can completely bugger your system.

I have used system commander 2000 on a computer that had windows/linux partitions. There was no problem resizing however I couldn’t boot into linux right away without changing a couple of things.

Maybe you could describe what is happening again. When you turn on your computer does it go into the system commander mini-os/boot loader or LILO or something else? Then you choose either windows or linux which it tries and fails to boot?

I’ll tell you my story and maybe you can glean some information from it. I had both windows and linux on partitions and was using system commander. When I chose windows it would go straight to windows. When I chose linux, it went to LILO which I had set to automatically go to linux (an artifact of having installed system commander after I had an up and running system which used LILO). I resized my partitions. Windows then booted fine, but linux didn’t boot right away. The problem was that linux was near the end of the disk so that after I resized, the boot partition had moved. What you have to do in this situation is boot into linux somehow and then run LILO on your hard drive which will reset LILO’s pointers (or however it does it) to the boot partitions correctly. The next time you start system commander, it still probably won’t find the boot partition when you select linux from the menu (because that still points to an incorrect place?). There is an option in system commander for it to automatically search for new boot partitions. Do this and it will add another linux to your menu, this one will be correct.

so my steps where

  1. resize
  2. boot into linux by alternative method (boot disk that you created before repartitoning and will load your full system) or other methods if you didn’t do this (let me know if this is a problem and I can tell you how to do this).
  3. run LILO from / and as root. It will say things like added windows, added linux. This will give LILO the proper boot partition position.
  4. reboot back into system commander, search for new boot partitions and add the new linux one that it finds, then remove the old one.

There are wizards here who may be able to help you rebuild partitions if that is required, but that is beyond me.