Operating Systems > Linux and UNIX

Mandrake was a fatal mistake

(1/3) > >>

Ice-9:
I had my SuSe installed, everything was running fine except for hardware 3D support, apparently there are some conflicts between the NVidia driver and XFree86 .....
A friend of mine told me that his Mandrake 8.2 was running very well so I decided to give it a try, wiped my Linux partitions and installed Mandrake.
Install went well but after using it for a while I didn't like it as much as SuSe.
So what did I do?  I wiped my Linux partitions again and decided to install Suse again.
Man, man, man, what a mistake ......
I had nothing but trouble since.
First I received a "Cannot write to LILO boot" message, after that I couldn't even boot Windows anymore, did a fixboot and a fixmbr from the recovery console and Win boot was ok.
Installed Suse again, again the same LILO message, except after that I couldn't restore my mbr anymore so no Win2K!!!!
Re-installed Win2K and Suse, SuSe install going smooth, LILO installs but doesn't let me boot Windows anymore and 3D support is not configurable  :( .
Jeez, spent the last 24 hours to install, re-install, uninstall, configuring, cursing.
I'd like to go Linux-only but I feel I still lack some knowledge to do everything I did in Windows.
 :(
Maybe I should try Redhat?

TheQuirk:
I posted this in a different thread, but this seems what exactly he needs..

open /etc/lilo.conf

I'm guessing you know where windows is..
anyway, add this:

other=/dev/hda1
table=/dev/hda
label=Windows

Replace "hda1" with where windows is, then change "hda" to the hard drive it's on.. If you don't know, just run cfdisk/fdisk and it will tell you. I'm pretty sure it's hda1, though.

Ice-9:
Thanks, but already did that, I found reference tot that in SuSe's support database and it leaves me with an "Unexpected error in LILO"!!!!!!
I'm getting pretty desperate since it's at least my 10th install since yesterday.
Fucking Mandrake, overwrote SuSe's LILO but apparently overwriting Mandrake's own LILO is a no-go!
Restoring the mbr from Win2K rescue disc resulted in a loss of FATs.
Anyway, I'm giving up for now, I'm gettin a headache just by looking at my pc.
I'm gonna give Redhat a try later today but I'd really like to get SuSe going again.
I can't stand it when something refuses to work when it previously worked fine!!!!!!

And Randy Rhoads was so ahead of his time, completely off topic I know but I had to share this  

TheQuirk:
run fdisk/cfdisk, erase *everything* and then reinstall. i know it doesn't make sence, but it sometimes works miracles, just like changing the number address thingies in SCSI devices :-p

dbl221:
use the fdisk from Dos/windows and at the command prompt type:  fdisk /mbr

This overwrites the Master Boot Record.  The MBR is composed of 0-446 Bytes boot-strap code + 64 Bytes(4*16) for the 4 entry partition table plus 2 Bytes for the signature AA55.

fdisk from linux will not work...use the Dos version.

Navigation

[0] Message Index

[#] Next page