LinuxQuestions.org - Bootable USB Device with USB-ZIP BIOS

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Bootable USB Device with USB-ZIP BIOS (https://www.linuxquestions.org/questions/slackware-14/bootable-usb-device-with-usb-zip-bios-752269/)

Just to document everything, I did try placing 64M, rather than 4GB, on the USB but still no bootable USB:

Quote:

$> makebootfat -o /dev/sda -Y -Z -b ldlinux.bss -m mbrfat.bin -F -c ldlinux.sys -c syslinux.cfg -c vmlinuz -c initrd.gz image
$> fdisk -l /dev/sda
Disk /dev/sda: 4009 MB, 4009754624 bytes
84 heads, 22 sectors/track, 4237 cylinders
Units = cylinders of 1848 * 512 = 946176 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 * 1 4238 3915745 b W95 FAT32

This time only read 64M:

Quote:

$> dd if=/dev/sda1 of=usb.img bs=64M count=1

Create proper geometry for the USB disk:

Quote:

$> fdisk -H64 -S32 /dev/sda

The number of cylinders for this disk is set to 3824.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sda: 4009 MB, 4009754624 bytes
64 heads, 32 sectors/track, 3824 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 4
First cylinder (1-3824, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-3824, default 3824):+64M

Command (m for help): t
Selected partition 4
Hex code (type L to list codes): b
Changed system type of partition 4 to b (W95 FAT32)

Command (m for help): a
Partition number (1-4): 4

Command (m for help): p

Disk /dev/sda: 4009 MB, 4009754624 bytes
64 heads, 32 sectors/track, 3824 cylinders

Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda4 * 1 65 3915760 b W95 FAT32

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.

Writing everything back on USB:

Quote:

$> dd if=usb.img of=/dev/sda4

And a million dollar question:

Quote:

FDD
No Operating System

Dissolving in immense sorrow...

Quote:

Originally Posted by oxblood (Post 3669752)

Still not having a bootable USB. Let me go through the steps one by one:

I'm sorry, there shouldn't be any MBR in a "superfloppy".

I have tried on a 1GB and a 8GB stick which both works. See below.

1 GB - USBest Technology
-----
Plugin

# dmesg

sb-storage: waiting for device to settle before scanning
usb 2-1.3: New USB device found, idVendor=1307, idProduct=0163
usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.3: Product: USB Mass Storage Device
usb 2-1.3: Manufacturer: USBest Technology
usb 2-1.3: SerialNumber: 00000000000321
scsi 9:0:0:0: Direct-Access UDISK PDU20_1G 6AC2.0 0.00 PQ: 0 ANSI: 2
sd 9:0:0:0: [sdc] 2015231 512-byte hardware sectors (1032 MB)
sd 9:0:0:0: [sdc] Write Protect is off
sd 9:0:0:0: [sdc] Mode Sense: 00 00 00 00
sd 9:0:0:0: [sdc] Assuming drive cache: write through
sd 9:0:0:0: [sdc] 2015231 512-byte hardware sectors (1032 MB)
sd 9:0:0:0: [sdc] Write Protect is off
sd 9:0:0:0: [sdc] Mode Sense: 00 00 00 00
sd 9:0:0:0: [sdc] Assuming drive cache: write through
sdc:
sd 9:0:0:0: [sdc] Attached SCSI removable disk
sd 9:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete

# mkdosfs -IF32 /dev/sdc
mkdosfs 2.11 (12 Mar 2005)

# sync

Unplug-replug

# dmesg

usb-storage: waiting for device to settle before scanning
usb 2-1.3: New USB device found, idVendor=1307, idProduct=0163
usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.3: Product: USB Mass Storage Device
usb 2-1.3: Manufacturer: USBest Technology
usb 2-1.3: SerialNumber: 00000000000321
scsi 10:0:0:0: Direct-Access UDISK PDU20_1G 6AC2.0 0.00 PQ: 0 ANSI: 2
sd 10:0:0:0: [sdc] 2015231 512-byte hardware sectors (1032 MB)
sd 10:0:0:0: [sdc] Write Protect is off
sd 10:0:0:0: [sdc] Mode Sense: 00 00 00 00
sd 10:0:0:0: [sdc] Assuming drive cache: write through
sd 10:0:0:0: [sdc] 2015231 512-byte hardware sectors (1032 MB)
sd 10:0:0:0: [sdc] Write Protect is off
sd 10:0:0:0: [sdc] Mode Sense: 00 00 00 00
sd 10:0:0:0: [sdc] Assuming drive cache: write through
sdc:
sd 10:0:0:0: [sdc] Attached SCSI removable disk
sd 10:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete

# mount /dev/sdc /mnt/tmp

# mkdir /mnt/tmp/syslinux

# cp /boot/initrd.gz /mnt/tmp/syslinux
# cp /boot/vmlinuz /mnt/tmp/syslinux

# kedit /mnt/tmp/syslinux/syslinux.cfg

Put into syslinux.cfg: default vmlinuz initrd=initrd.gz

# umount /mnt/tmp

# sync

# syslinux /dev/sdc

# sync

Looks like a USB-ZIP drive in the system with picky BIOS. Looks like a USB-FDD in another system. Selecting boot from "Removable" works in picky system. Selecting boot from USB-FDD works in the other.

8 GB - Sony
------

Plugin

# dmesg

usb 2-1.3: New USB device found, idVendor=054c, idProduct=0243
usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.3: Product: Storage Media
usb 2-1.3: Manufacturer: Sony
usb 2-1.3: SerialNumber: 2A080922E7563
scsi 12:0:0:0: Direct-Access Sony Storage Media 0100 PQ: 0 ANSI: 0 CCS
sd 12:0:0:0: [sdc] 15663104 512-byte hardware sectors (8020 MB)
sd 12:0:0:0: [sdc] Write Protect is off
sd 12:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 12:0:0:0: [sdc] Assuming drive cache: write through
sd 12:0:0:0: [sdc] 15663104 512-byte hardware sectors (8020 MB)
sd 12:0:0:0: [sdc] Write Protect is off
sd 12:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 12:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1 sdc2
sd 12:0:0:0: [sdc] Attached SCSI removable disk
sd 12:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.

# mkdosfs -IF32 /dev/sdc
mkdosfs 2.11 (12 Mar 2005)

# sync

Unplug-replug

# dmesg

usb 2-1.3: New USB device found, idVendor=054c, idProduct=0243
usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.3: Product: Storage Media
usb 2-1.3: Manufacturer: Sony
usb 2-1.3: SerialNumber: 2A080922E7563
scsi 14:0:0:0: Direct-Access Sony Storage Media 0100 PQ: 0 ANSI: 0 CCS
sd 14:0:0:0: [sdc] 15663104 512-byte hardware sectors (8020 MB)
sd 14:0:0:0: [sdc] Write Protect is off
sd 14:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 14:0:0:0: [sdc] Assuming drive cache: write through
sd 14:0:0:0: [sdc] 15663104 512-byte hardware sectors (8020 MB)
sd 14:0:0:0: [sdc] Write Protect is off
sd 14:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 14:0:0:0: [sdc] Assuming drive cache: write through
sdc:
sd 14:0:0:0: [sdc] Attached SCSI removable disk
sd 14:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete

# mount /dev/sdc /mnt/tmp

# mkdir /mnt/tmp/syslinux

# cp /boot/initrd.gz /mnt/tmp/syslinux
# cp /boot/vmlinuz /mnt/tmp/syslinux

# kedit /mnt/tmp/syslinux/syslinux.cfg

Put into syslinux.cfg: default vmlinuz initrd=initrd.gz

# umount /mnt/tmp

# sync

# syslinux /dev/sdc

# sync

Looks like a USB-ZIP in system with picky BIOS. Looks like a USB-HD in another system. Works in both.

Quote:

Originally Posted by uppman (Post 3672934)

I'm sorry, there shouldn't be any MBR in a "superfloppy".

8 GB - Sony
------

Plugin

# mkdosfs -IF32 /dev/sdc
mkdosfs 2.11 (12 Mar 2005)

# sync

Unplug-replug

# mount /dev/sdc /mnt/tmp

# mkdir /mnt/tmp/syslinux

# cp /boot/initrd.gz /mnt/tmp/syslinux
# cp /boot/vmlinuz /mnt/tmp/syslinux

# kedit /mnt/tmp/syslinux/syslinux.cfg

Put into syslinux.cfg: default vmlinuz initrd=initrd.gz

# umount /mnt/tmp

# sync

# syslinux /dev/sdc

# sync

Looks like a USB-ZIP in system with picky BIOS. Looks like a USB-HD in another system. Works in both.

I had done that as you suggested before but only get "Boot error" when either USB-ZIP or USB-FDD is selected in the BIOS. I am at lost.

Quote:

Originally Posted by oxblood (Post 3673336)

I had done that as you suggested before but only get "Boot error" when either USB-ZIP or USB-FDD is selected in the BIOS. I am at lost.

So you also tried to create a "superfloppy" and *without* writing a MBR?

There are no other boot options in the BIOS? Like "HD boot priority" or something?

Perhaps you could try another stick? Or try installing puppy which has several options for picky BIOS'es.

Don't give up, computers should behave! :)

Quote:

Originally Posted by uppman (Post 3674742)

So you also tried to create a "superfloppy" and *without* writing a MBR?

Can you elaborate as to how to create a superfloppy without writing a MBR?

Quote:

Originally Posted by uppman (Post 3674742)

There are no other boot options in the BIOS? Like "HD boot priority" or something?

There are only USB-ZIP and USB-FDD options relating to USB. Of course, other options such as floppy, ZIP, and unrelated selections are also available.

Quote:

Originally Posted by uppman (Post 3674742)

Perhaps you could try another stick? Or try installing puppy which has several options for picky BIOS'es.

If I had another stick, I would have. I might give Puppy Linux a try later on but not now.

Quote:

Originally Posted by uppman (Post 3674742)

Don't give up, computers should behave! :)

Some times you just have to concede to defeat. Not every battle must be won on the field of knowledge. My ego has been bruised before -- more than I like to admit when it comes to technology. This is perhaps one of those times. I'll try to install Slackware 13 on my "old" Toshiba laptop, which has been eating dust for the last several years, in the coming week and try to see if I can make a bootable USB on its system.

Quote:

Originally Posted by oxblood (Post 3674921)

Can you elaborate as to how to create a superfloppy without writing a MBR?

For a "superfloppy" the MBR gets created autmagically by the mkdosfs program:

mkdosfs -IF32 /dev/sdc

So to install another MBR afterwards would break the "superfloppy".