For reasons related to work, I use one box that used to (and still needs to ) dual boot with win98se. A few days ago the 98 side went totally south, and cannot even be fiddled with in safe mode. Thus I need to reload 98 which will over write the LILO boot loader. No problem except that I can't find any way to actually reload LILO. I've tried to make a set of boot disks but can't find any means for doing it and even so all those I've made in the past with later versions of SuSE have failed to work. I just created a boot floppy from the YaST2 menu from the Custom LILO screen, but it fails to boot at all even with the bios set to boot from legacy floppy first. What I'm looking for is a method by which I can re-install LILO as the boot loader AFTER the re-install of 98se has restored the MBR. tia, dave -- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1 People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
On Sat, 2004-05-15 at 01:43, David Johanson wrote:
For reasons related to work, I use one box that used to (and still needs to ) dual boot with win98se. A few days ago the 98 side went totally south, and cannot even be fiddled with in safe mode. Thus I need to reload 98 which will over write the LILO boot loader. No problem except that I can't find any way to actually reload LILO.
What I do is to boot from CD (or DVD) and select boot installed system. THen you choose your root partiion, and Linux starts... Once you got Linux up and running, you can reinstall LILO with the standard commands... Hope this helps Jerry
Jerome R. Westrick wrote:
On Sat, 2004-05-15 at 01:43, David Johanson wrote:
For reasons related to work, I use one box that used to (and still needs to ) dual boot with win98se. A few days ago the 98 side went totally south, and cannot even be fiddled with in safe mode. Thus I need to reload 98 which will over write the LILO boot loader. No problem except that I can't find any way to actually reload LILO.
What I do is to boot from CD (or DVD) and select boot installed system. THen you choose your root partiion, and Linux starts... Once you got Linux up and running, you can reinstall LILO with the standard commands...
Hope this helps Jerry
I can do just that with versions later than 7.x, but 7.x doesn't appear to offer that option. Perhaps I should just insert an 8.x Cd and see if that works. dave -- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1 People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
Jerome R. Westrick wrote:
On Sat, 2004-05-15 at 01:43, David Johanson wrote:
For reasons related to work, I use one box that used to (and still needs to ) dual boot with win98se. A few days ago the 98 side went totally south, and cannot even be fiddled with in safe mode. Thus I need to reload 98 which will over write the LILO boot loader. No problem except that I can't find any way to actually reload LILO.
What I do is to boot from CD (or DVD) and select boot installed system. THen you choose your root partition, and Linux starts... Once you got Linux up and running, you can reinstall LILO with the standard commands...
Hope this helps Jerry
This "how to recover my 7.1 system" has been bothering me for quite some time. Your suggestion of trying to re-load from another CD was something that had crossed my mind earlier but for some reason I just never bothered to try it. Not sure what had caused that mental block because with an earlier install of 8.1 that I was playing around with I actually did just what you suggested but somehow never considered using anything other than the 7.1 CDs. DUH! Yesterday when playing around with the 7.1 installation I tried making a boot CD from YaST -- YaST2 | control Center | Misc | configure Bot-Mode and selected "Create a boot floppy." After so doing I tried booting with the newly created floppy in the "A" drive but didn't notice any drive "A" activity and the system booted as usual. This, erroneously, led me to believe that the disk was a failure and I just set it aside. Today when I booted into the system it failed to boot giving me screen full after screen full of . . . . . following the line looking for a boot image. I tried booting several times always getting the same results. I was getting rather frustrated when I decided to put in the boot disk made yesterday, just because I could think of nothing else to do. Again there was minimal boot activity, almost none save for a couple of early on blinks of the drive "A" light, and this very early in the start phase, almost at BIOS start time, but the system booted as usual. I then tried without the disk in the drive and once again the series of . . . I then put the disk back in the drive and everything worked as desired. This time I went back into YaST and opted for a write to the boot disk MBR and let that run. Viola, system again booted from the hard drive. So I now realize that not only did I create a functional boot floppy, but that by doing so with YaST I altered the system. Learned something new today. Next I tried booting from the 9.1 Disk #1 and found that, of course, that works also, although it failed to find and setup the eth0 connection. But who cares, once booted, sbin/lilo should be able to take care of that. Thanks for your suggestion; made put think a little which proved fruitful! dave -- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1 People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
David Johanson wrote: <snip>
I decided to put in the boot disk made yesterday, just because I could think of nothing else to do. Again there was minimal boot activity, almost none save for a couple of early on blinks of the drive "A" light, and this very early in the start phase, almost at BIOS start time, but the system booted as usual. I then tried without the disk in the drive and once again the series of . . . I then put the disk back in the drive and everything worked as desired. This time I went back into YaST and opted for a write to the boot disk MBR and let that run. Viola, system again booted from the hard drive. So I now realize that not only did I create a functional boot floppy, but that by doing so with YaST I altered the system. Learned something new today.
Next I tried booting from the 9.1 Disk #1 and found that, of course, that works also, although it failed to find and setup the eth0 connection. But who cares, once booted, sbin/lilo should be able to take care of that.
<snip> Well, it proved to get more interesting after I tried a re-install of windows (it failed) and I tried to reboot 7.1. The boot disk didn't work giving only LIL- and stopping after that. I guess you set 7.1 to boot from one specific site be it a drive or a floppy disk, but not both. So I tried a couple of versions of SuSE just for kicks getting successful only with the 9.1 version the others not providing mouse support. So I'm still in the dark as to how one actually makes a boot disk(s) that work when the normal MBR approach doesn't work. dave -- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1 People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 16 May 2004 10:18, David Johanson wrote:
David Johanson wrote:
<snip>
I decided to put in the boot disk made yesterday, just because I could think of nothing else to do. Again there was minimal boot activity, almost none save for a couple of early on blinks of the drive "A" light, and this very early in the start phase, almost at BIOS start time, but the system booted as usual. I then tried without the disk in the drive and once again the series of . . . I then put the disk back in the drive and everything worked as desired. This time I went back into YaST and opted for a write to the boot disk MBR and let that run. Viola, system again booted from the hard drive. So I now realize that not only did I create a functional boot floppy, but that by doing so with YaST I altered the system. Learned something new today.
Next I tried booting from the 9.1 Disk #1 and found that, of course, that works also, although it failed to find and setup the eth0 connection. But who cares, once booted, sbin/lilo should be able to take care of that.
<snip>
Well, it proved to get more interesting after I tried a re-install of windows (it failed) and I tried to reboot 7.1. The boot disk didn't work giving only LIL- and stopping after that. I guess you set 7.1 to boot from one specific site be it a drive or a floppy disk, but not both. So I tried a couple of versions of SuSE just for kicks getting successful only with the 9.1 version the others not providing mouse support.
So I'm still in the dark as to how one actually makes a boot disk(s) that work when the normal MBR approach doesn't work.
dave
-- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1
People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe If I understand your post & you're running WindozeXP on a dual-boot you first have to run 'fixmbr' from the 'Repair' function on your XP installation disk. That'll put the mbr back to rights so that you can boot your OS. Then, if your SuSE7.1 disk is like the later ones, you can use it to boot your SuSE & rewrite the mbr w/the boot loader. Been there a couple times, or so, myself. ;-)
HTH... - -- ...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAp5No1rD/PgIdojIRAt37AKCsVrdFVILWnEvJvc2hLrICf1bdmQCfVFLQ +F7eerhwQWatI/S0dcqc3+o= =dWrs -----END PGP SIGNATURE-----
C Hamel wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday 16 May 2004 10:18, David Johanson wrote:
David Johanson wrote:
<snip>
<snip>
<snip>
Well, it proved to get more interesting after I tried a re-install of windows (it failed) and I tried to reboot 7.1. The boot disk didn't work giving only LIL- and stopping after that. I guess you set 7.1 to boot from one specific site be it a drive or a floppy disk, but not both. So I tried a couple of versions of SuSE just for kicks getting successful only with the 9.1 version the others not providing mouse support.
So I'm still in the dark as to how one actually makes a boot disk(s) that work when the normal MBR approach doesn't work.
dave
-- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1
People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
If I understand your post & you're running WindozeXP on a dual-boot you first have to run 'fixmbr' from the 'Repair' function on your XP installation disk. That'll put the mbr back to rights so that you can boot your OS. Then, if your SuSE7.1 disk is like the later ones, you can use it to boot your SuSE & rewrite the mbr w/the boot loader. Been there a couple times, or so, myself. ;-)
HTH... - -- ...CH
Thanks for the suggestion, but the windoze side is 98se. dave -- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1 People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
C Hamel wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday 16 May 2004 10:18, David Johanson wrote:
David Johanson wrote:
<snip>
<snip>
<snip>
Well, it proved to get more interesting after I tried a re-install of windows (it failed) and I tried to reboot 7.1. The boot disk didn't work giving only LIL- and stopping after that. I guess you set 7.1 to boot from one specific site be it a drive or a floppy disk, but not both. So I tried a couple of versions of SuSE just for kicks getting successful only with the 9.1 version the others not providing mouse support.
So I'm still in the dark as to how one actually makes a boot disk(s) that work when the normal MBR approach doesn't work.
dave
-- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1
People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
If I understand your post & you're running WindozeXP on a dual-boot you first have to run 'fixmbr' from the 'Repair' function on your XP installation disk. That'll put the mbr back to rights so that you can boot your OS. Then, if your SuSE7.1 disk is like the later ones, you can use it to boot your SuSE & rewrite the mbr w/the boot loader. Been there a couple times, or so, myself. ;-)
HTH... - -- ...CH
Thanks for the suggestion, but the windoze side is 98se.
dave
-- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1
People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe Okay! If you can get to your partition via a floppy boot disk (borrow one if you have to! <G>) then perform the following: 'fdisk /mbr' & you will find
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 16 May 2004 13:43, David Johanson wrote: that (1)your MBR is fixed; (2)grub/lilo is gone (but that is fixable, too). HTH... - -- ...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAp9ZZ1rD/PgIdojIRAhe9AJ9P2oP3kN6Sk0gGHpzOfGmatzreGgCfWDKH ctLqk7pp3+U4XXJE1oiqrvo= =B+32 -----END PGP SIGNATURE-----
participants (3)
-
C Hamel -
David Johanson -
Jerome R. Westrick