Adding a W98SE Hard Drive to Mdk9.2

[DeeJayBump]

I recently re-loaded one of my spare hard drives with Windows98SE. When I boot Mdk9.2, I can't get it to add this drive. The ls -l /dev/hd* command will list this drive (slave on the primary IDE) as "hdb" however I can't get it to mount or get HardDrake to list it either.

 

Any help in walking me through this would be appreciated.

 

BTW, the drive with w98SE works, because I can shut down, connect it as the master on the primary IDE and it will boot fine.

Edited September 2, 2004 by DeeJayBump

[Ixthusdan]

First make a mount point in /mnt. I would use /mnt/windows. Then add a line to fstab that reads

 /dev/hdb1 /mnt/windows vfat  umask=0, iocharset= iso8859-1, codepage=850 0 0

 

Edit lilo with a line that says

other=/dev/hdb
       lable="windows"
       table=hdb

 

Don't forget to leave a blank line at the end of the file. After saving and exiting lilo run lilo -v on the command line. Reboot, and you're done.

[DeeJayBump]

I followed your instructions. When I typed lilo -v on a command line, this was the result:

 

LILO version 22.5.7.2, Copyright © 1992-1998 Werner Almesberger

Development beyond version 21 Copyright © 1999-2003 John Coffman

Released 20-Aug-2003, and compiled at 16:45:54 on Sep 18 2003

 

Reading boot sector from /dev/hda

Using GRAPHIC secondary loader

Calling map_insert_data

Mapping message file /boot/message -> message-graphic

Calling map_insert_file

 

Boot image: /boot/vmlinuz -> vmlinuz-2.4.22-10mdk

Mapping RAM disk /boot/initrd.img -> initrd-2.4.22-10mdk.img

Added linux *

 

Boot image: /boot/vmlinuz -> vmlinuz-2.4.22-10mdk

Mapping RAM disk /boot/initrd.img -> initrd-2.4.22-10mdk.img

Added linux-nonfb

 

Boot image: /boot/vmlinuz -> vmlinuz-2.4.22-10mdk

Mapping RAM disk /boot/initrd.img -> initrd-2.4.22-10mdk.img

Added failsafe

 

Boot other: /dev/hdb, on hdb, loader CHAIN

Fatal: open /dev/hdb: No such file or directory

 

So, where do I go from here? Thanks for the help thus far.

[DeeJayBump]

Anyone? Or am I wrong in thinking that the folllowing line is a problem that needs to be rectified?

 

Boot other: /dev/hdb, on hdb, loader CHAIN

Fatal: open /dev/hdb: No such file or directory

 

Any further help in resolving this would be appreciated.

[bvc]

bios settings right?

[spinynorman]

Don't you have to change the 'dev/hdb' in lilo.conf to match 'dev/hdb1' in fstab? :unsure:

[DeeJayBump]

I don't know--that's why I ask. The BIOS reads the drives correctly, so the problem is not the BIOS.

[spinynorman]

I'm no expert, but I think it's worth a try. Just edit and run lilo -v again... :)

[DeeJayBump]

Okay, it simply would not work when connected as the slave drive (/dev/hdb)on the primary IDE channel, however when I switched it to the slave drive (/dev/hdd) on the secondary IDE, I got Mdk to notice it and mount it at /mnt/windows so that part is taken care of. The /etc/fstab modifications have been made, however when I run lilo -v I still get:

 

LILO version 22.5.7.2, Copyright © 1992-1998 Werner Almesberger

Development beyond version 21 Copyright © 1999-2003 John Coffman

Released 20-Aug-2003, and compiled at 16:45:54 on Sep 18 2003

 

Reading boot sector from /dev/hda

Using GRAPHIC secondary loader

Calling map_insert_data

Mapping message file /boot/message -> message-graphic

Calling map_insert_file

 

Boot image: /boot/vmlinuz -> vmlinuz-2.4.22-10mdk

Mapping RAM disk /boot/initrd.img -> initrd-2.4.22-10mdk.img

Added linux *

 

Boot image: /boot/vmlinuz -> vmlinuz-2.4.22-10mdk

Mapping RAM disk /boot/initrd.img -> initrd-2.4.22-10mdk.img

Added linux-nonfb

 

Boot image: /boot/vmlinuz -> vmlinuz-2.4.22-10mdk

Mapping RAM disk /boot/initrd.img -> initrd-2.4.22-10mdk.img

Added failsafe

 

Boot other: /dev/hdd1, on hdd1, loader CHAIN

Fatal: open hdd1: No such file or directory

 

SO my LILO boot config is still incorrect. What am I doing wrong? Once again, thanks for the help thus far.

 

EDIT: my /etc/lilo.conf reads:

boot=/dev/hda

map=/boot/map

default="linux"

keytable=/boot/us.klt

prompt

nowarn

timeout=100

message=/boot/message

menu-scheme=wb:bw:wb:bw

image=/boot/vmlinuz

label="linux"

root=/dev/hda5

initrd=/boot/initrd.img

append="devfs=mount hdc=ide-scsi hdb=ide-scsi acpi=ht resume=/dev/hda6 splash=silent"

vga=788

read-only

image=/boot/vmlinuz

label="linux-nonfb"

root=/dev/hda5

initrd=/boot/initrd.img

append="devfs=mount hdc=ide-scsi acpi=ht resume=/dev/hda6"

read-only

image=/boot/vmlinuz

label="failsafe"

root=/dev/hda5

initrd=/boot/initrd.img

append="devfs=nomount hdc=ide-scsi acpi=ht resume=/dev/hda6 failsafe"

read-only

other=/dev/hdd1

label="windows"

table=hdd1

other=/dev/fd0

label="floppy"

unsafe

 

while my /etc/fstab reads:

/dev/hda5 / ext3 defaults 1 1

none /dev/pts devpts mode=0620 0 0

/dev/hda7 /home ext3 defaults 1 2

/dev/hda1 /home/djbump1 ext3 defaults 1 2

none /mnt/cdrom supermount dev=/dev/scd0,fs=udf:iso9660,ro,--,iocharset=iso8859-1 0 0

none /mnt/cdrom2 supermount dev=/dev/cdrom2,fs=auto,ro,--,user,unmask=0,iocharset=iso8859-1,ide-scsi 0 0

/dev/scsi/host0/bus0/target1/lun0/cd /mnt/cdwriter auto ro,noauto,user,exec 0 0

/dev/hdd1 /mnt/windows vfat umask=0, iocharset= iso8859-1, codepage=850 0 0

none /proc proc defaults 0 0

Edited September 3, 2004 by DeeJayBump

[Ixthusdan]

Would you look at the drive using harddrake and see if the partition lable is correct? Make sure that windows is indeed on the first partition of the secondary slave.

[DeeJayBump]

Would you look at the drive using harddrake and see if the partition lable is correct? Make sure that windows is indeed on the first partition of the secondary slave.

<{POST_SNAPBACK}>

 

Double-checked it, and yes, Windows is on the firts partition of the secondary slave. In fact, there is only one partion on this drive.