A word of caution. I have had major problems when attempting to relocate a Windows 2000 hard drive to either a different location in the same computer (changing from master to slave, or from IDE0 to IDE1), and even more problems when attempting to move it to different box completely. If possible, I would leave the windows 2000 hard drive where it was, and repair GRUB (I know that this configuration will work using LILO - windows on IDE0 master, linux on IDE0 slave, as that is what I run most of the time) At this time, I am unable to assist with the SUSE issue (I run Mandrake), and I have had to repair the bootloader on occasion by re-running the Linux installation, and selecting upgrade, but not selecting any pacakges to install
Darcy Brodie
Mike Fitton wrote:
On Fri, 2004-04-09 at 20:00, CAMERON NIKITIUK wrote:
From the advice I am given am I correct in assuming that I should be taking the following steps in the following order. Any further suggestions on other steps or a change in order would be excellent:1) Reinstall Suse 9 from CD and change bootloader (GRUB or LILO) to hdb (160GB).
2) Failing 1, remove 20GB & change 160 GB to master and repeat 1 with bootloader loaded on hda.
3) Check BIOS and see if drive recognized properly. If not, flash BIOS and check again.
4) Run fdisk /mbr and see if that corrects problem.
5) Use Recovery Console to try and correct issue.
6) Give up on the whole damn thing...become a budist monks and swear off on the evils of technology!!!
Any thoughts?
I have a different order in mind, just to retain the integrity of the 20gb drive, since there is important stuff you'll need off it.
1) I would try to make sure the BIOS recognizes the 160gb drive first and foremost as Curtis suggested.I haven't ever had the luxury of anything bigger that a 10 gb drive. <gb envy> ;=)
2) Retain the 20GB as a slave(hdb) & change the 160 GB to master(hda) and install Linux and the bootloader on hda.I don't think loading GRUB on hdb(win2k) will boot up.(Can anyone confirm this?)I have never tried it.
3) If you need to get your 20gb win2k back to a bootable condition on its own,as a standalone drive, you will need to run fdisk /mbr from a win2k boot disk.That should replace any GRUB bootloader info that was written to it previously.If you are running this as a slave to the 160gb then it shouldn't matter.
4) I have never needed to run Partition Magic so far, and haven't tried "Recovery Console". I'm not sure that would do anything to help here.
5) If all else fails, then I would say Join the monks and enjoy the winemaking and gregorian chants ;=) and don't forget to invite me for a drink!! sorry, I don't chant in tune...:=)
hope it helps Cameron
--mike
------------------------------------------------------------------------
_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
