Very Computer

Any idea on how to solve this problem?
cedric

The sys has two HD's.
A 16G and 30G
W98 was on 16G and had been for some time.
Installed MDK8.0 on 30G.
At boot up, 'LO' filled the screen in a loop.
Then there was nothing, no W98 or MDK.
I know, or think, the mbr of the 16G is corrupt.

I disconnected the 16G cable and reinstalled MDK.
It is working fine.
Now, how do I get W98 back and run dual boot?
Or, can I get W98 back and boot up to MDK using a floppy?

If I am able to fix the mbr using the W98 CD, will MDK be
there? If not, can I boot up to it using a floppy?

So if I misunderstand you correctly, you unplugged a disk
did the linux thing, installed the old drive. That would cause
the drive letters to change. Now linux cannot find where it was.

You can boot cd 1 mandrake and get into the rescue mode
find the new drive letter where linux is and change
the /etc/lilo.conf and /etc/fstab to match the new drive letters
where linux lives. You then have to install the lilo conf changes.

You might make a Rescue diskette:
http://www.toms.net/rb/home.html

Ok, you booted diskette or cd 1 in rescue mode

Change hda5 to your / partition location
        mkdir /mnt
        mount /dev/hda5 /mnt
        chroot /mnt
Made changes in /etc/lilo.conf and /etc/fstab
        /sbin/lilo -v              to install changes.

--
The warranty and liability expired as you read this message.
If the above breaks your system, it's yours and you keep both pieces.
Practice safe computing. Backup the file before you change it.
Do a,  man command_here or cat command_here, before using it.

Connect the windows drive as the primary drive /dev/hda.
Then install Linux on the second drive but leave the windows drive
connected and install linux to /dev/hdb or the correct device depending
where it is connected.

After you have linux installed then you can add the lines to the end of
/etc/lilo.conf to be able to boot windows if the install doesn't do it
for you.

other=/dev/hda1
label=win

--
   Confucius:  He who play in root, eventually kill tree.
Registered with the Linux Counter.  http://counter.li.org

Quote:> Why did you disconnect the windows drive to install Linux? Linux won't
> overwirte the windows drive/partition unless you tell it to.

> Connect the windows drive as the primary drive /dev/hda.
> Then install Linux on the second drive but leave the windows drive
> connected and install linux to /dev/hdb or the correct device depending
> where it is connected.

Quote:> After you have linux installed then you can add the lines to the end of
> /etc/lilo.conf to be able to boot windows if the install doesn't do it
> for you.

Using fdisk in DOS, I did a fdisk /mbr to repair the mbr. I now have W98.
That is what I'm using now.

What I need, I think, is to be able to boot to MDK on /dev/hdd via floppy
and leave W98 alone. Is there a lilo.conf on the boot floppy. If so, can I
set it up to look for MDK on /dev/hdd?

MDK does not seem to be able to correctly set up the mbr on /dev/hda to
allow LILO to work properly.

Quote:> other=/dev/hda1
> label=win

> --
>    Confucius:  He who play in root, eventually kill tree.
> Registered with the Linux Counter.  http://counter.li.org

Change your bios boot order and test diskettes after you create them.

lilo boot diskette:
        Load a blank floppy into drive and
        lilo -b /dev/fd0
Remove diskette and label it    lilo boot

image boot diskette:
        Load a blank floppy into drive and
        mkbootdisk --device /dev/fd0 $(uname -r)
Remove diskette and label it    image boot

Rescue diskette:
http://www.toms.net/rb/home.html

Replacing a wiped out mbr lilo using the Rescue diskette

Change hda5 to your / partition location
        mkdir /mnt
        mount /dev/hda5 /mnt
        chroot /mnt
        /sbin/lilo -v

Then, install Win, then  boot from your CD, hit F1 and type

rescue

then, at the prompt (it will look strange, something like "sh-2.05#"), type

mount /dev/hda5 /mnt
chroot /mnt
/sbin/lilo
reboot

Quote:> So if I misunderstand you correctly, you unplugged a disk
> did the linux thing, installed the old drive. That would cause
> the drive letters to change. Now linux cannot find where it was.

Quote:> You can boot cd 1 mandrake and get into the rescue mode
> find the new drive letter where linux is and change
> the /etc/lilo.conf and /etc/fstab to match the new drive letters
> where linux lives. You then have to install the lilo conf changes.

Quote:> You might make a Rescue diskette:
> http://www.toms.net/rb/home.html

Quote:> Ok, you booted diskette or cd 1 in rescue mode

> Change hda5 to your / partition location
> mkdir /mnt
> mount /dev/hda5 /mnt
> chroot /mnt
> Made changes in /etc/lilo.conf and /etc/fstab
> /sbin/lilo -v              to install changes.

> --
> The warranty and liability expired as you read this message.
> If the above breaks your system, it's yours and you keep both pieces.
> Practice safe computing. Backup the file before you change it.
> Do a,  man command_here or cat command_here, before using it.

Quote:> You can create a lilo diskette, an image boot diskette, and or
> a rescue diskette. Only the rescue diskette contains utilities.

Quote:

> None of these work using the MDK  CD1 in rescue mode.
> How do I do this since I can't get to Linux?

Rescue diskette:
http://www.toms.net/

Change hda5 to your / partition location
        mkdir /mnt
        mount /dev/hda5 /mnt
        chroot /mnt
        /sbin/lilo -v

Quote:> when you are in the rescue mode, you are in linux.
> You have to mount the partition to do the work in. When you want to
> use the system from that partition you have to do a
>   chroot <partition_mount_point_here>

> Rescue diskette:
> http://www.toms.net/

Quote:> Change hda5 to your / partition location
> mkdir /mnt

Quote:> mount /dev/hda5 /mnt

Quote:> chroot /mnt

Quote:> /sbin/lilo -v

Quote:

>> mount /dev/hda5 /mnt
> /dev/hda5: success
> mount: you must specify the filesystem type

>> chroot /mnt
> no such file or directory

>> /sbin/lilo -v
> no such file or directory

Now listen up, where I said

Quote:>> Change hda5 to your / partition location

You might try running      fdisk /dev/hdd   to see partition numbers.

--
The warranty and liability expired as you read this message.
If the above breaks your system, it's yours and you keep both pieces.
Practice safe computing. Backup the file before you change it.
Do a,  man command_here or cat command_here, before using it.

Everything is here as before.
Linux boots up from floppy.
W98 as per normal

Is it a big deal to set up lilo so it boots off /dev/hda as
usual without loosing W98 again?

Thanks again,
cedric

Quote:> And, Thank You!!!

Quote:> Everything is here as before.
> Linux boots up from floppy.
> W98 as per normal

Quote:

> Is it a big deal to set up lilo so it boots off /dev/hda as
> usual without loosing W98 again?

You have to test the lilo boot to verify it boots windoze
correctly before the mbr install.

I would think that a  /sbin/li/o -v /dev/hda
would install into the mbr correctly unless your bios has
virus protection turned on.

--
The warranty and liability expired as you read this message.
If the above breaks your system, it's yours and you keep both pieces.
Practice safe computing. Backup the file before you change it.
Do a,  man command_here or cat command_here, before using it.

Quote:>> Everything is here as before.
>> Linux boots up from floppy.
>> W98 as per normal

> Are you indicating that you can boot windoz from the
> lilo menu?

Quote:

>> Is it a big deal to set up lilo so it boots off /dev/hda
>> as usual without loosing W98 again?

> I do not have problems with w98 or XPee.

Quote:

> You have to test the lilo boot to verify it boots windoze
> correctly before the mbr install.

Quote:

> I would think that a  /sbin/li/o -v /dev/hda
> would install into the mbr correctly unless your bios has
> virus protection turned on.

boot=/dev/hdd
map=/boot/map
install=/boot/boot.b
default=linux
keytable=/boot/us.klt
lba32
prompt
timeout=50
disk=/dev/hdd bios=0x80
message=/boot/message-graphic
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
        label=linux
        root=/dev/hdd6
        initrd=/boot/initrd.img
        append=" hdb=ide-scsi quiet"
        vga=788
        read-only
image=/boot/vmlinuz
        label=linux-nonfb
        root=/dev/hdd6
        initrd=/boot/initrd.img
        append=" hdb=ide-scsi"
        read-only
image=/boot/vmlinuz
        label=failsafe
        root=/dev/hdd6
        initrd=/boot/initrd.img
        append=" hdb=ide-scsi failsafe"
        read-only
other=/dev/fd0
        label=floppy
        unsafe

Quote:> Actually, I would prefer to trash all MS products.
> I run AutoCad and DairyQuest, therefore I need W98.

Quote:

>>> Is it a big deal to set up lilo so it boots off /dev/hda
>>> as usual without loosing W98 again?

>> I do not have problems with w98 or XPee.

> What is XPee?

Quote:

>> You have to test the lilo boot to verify it boots windoze
>> correctly before the mbr install.

> How do you test the lilo boot.

You put you changes in lilo.conf and and write to the test lilo
diskette. Shutdown the system and boot from the test floppy.
If all is well then you install normally.

Quote:

>> I would think that a  /sbin/li/o -v /dev/hda
>> would install into the mbr correctly unless your bios has
>> virus protection turned on.

> I'll check the virus thing in bios asap.
> Here is /etc/lilo.conf
> It is what came with MDK8.0
> What would be needed to boot from /dev/hda mbr?

other=/dev/hda1             <======= change this to match your install
        label=win98
        table=/dev/hda      <======= and this

Quote:> boot=/dev/hdd
> map=/boot/map
> install=/boot/boot.b
> default=linux
> keytable=/boot/us.klt
> lba32
> prompt
> timeout=50
> disk=/dev/hdd bios=0x80
> message=/boot/message-graphic
> menu-scheme=wb:bw:wb:bw
> image=/boot/vmlinuz
>         label=linux
>         root=/dev/hdd6
>         initrd=/boot/initrd.img
>         append=" hdb=ide-scsi quiet"
>         vga=788
>         read-only
> image=/boot/vmlinuz
>         label=linux-nonfb
>         root=/dev/hdd6
>         initrd=/boot/initrd.img
>         append=" hdb=ide-scsi"
>         read-only
> image=/boot/vmlinuz
>         label=failsafe
>         root=/dev/hdd6
>         initrd=/boot/initrd.img
>         append=" hdb=ide-scsi failsafe"
>         read-only
> other=/dev/fd0
>         label=floppy
>         unsafe

Quote:> other=/dev/hda1             <======= change this to match
> your install
>         label=win98
>         table=/dev/hda      <======= and this

cedric