UBCD V5.1 alpha 2 available for download

Icecube · **Joined:** Fri Jan 11, 2008 2:52 pm **Posts:** 1275

Quote:

pci.ids, modules.alias and modules.pcimap can optionally be gzipped (remove the gz extension afterwards), to save space and speedup loading.

This is if you don't specify the names on the APPEND line. HDT looks for those files in the Syslinux directory by default.

Victor Chew · **Joined:** Mon Feb 21, 2005 10:59 pm **Posts:** 1177

The "pciids" param has problems with long filenames, so I set the filename to "pciids.gz":

Code:

LABEL hdt
MENU LABEL Hardware Detection Tool V0.4.1
COM32 /boot/syslinux/hdt.c32
APPEND pciids=/boot/syslinux/pciids.gz

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 637

In /pmagic/boot/grub4dos/grub4dos.lst

Code:

title Default settings (Runs from RAM / Ejects CD)\n * Parted Magic version: 5.5

instead of the correct version 5.10

AND

Code:

kernel /pmagic/bzImage iso_filename=ubcd51a1.iso

instead of the correct

Code:

kernel /pmagic/bzImage iso_filename=ubcd51a2.iso

for every entry in this file.

In /pmagic/boot/isolinux/isolinux.cfg

Code:

instead of the correct version 5.10.

In /pmagic/boot/isolinux/isolinux.cfg
AND in /pmagic/boot/syslinux/syslinux.cfg

both have:

Code:

APPEND iso_filename=ubcd51a1.iso

instead of the correct

Code:

APPEND iso_filename=ubcd51a2.iso

for every entry in those files.

The "VMALLOC=256MiB" is present in the syslinux.cfg only. (I'm not sure if this should be valid for the other files too).

So, it seems the syslinux and grub4dos files under pmagic were not updated for ubcd51a2 and PMagic 5.10.

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 637

The scripts under \ubcd\tools\ include:

Code:

SET VOLUME_ID=UBCD51a1

instead of the correct:

Code:

SET VOLUME_ID=UBCD51a2

.

From mkfdubcd.cmd:

Code:

VOLUME_ID=FDUBCD140

instead of the correct:

Code:

VOLUME_ID=FDUBCD141

.

Victor Chew · **Joined:** Mon Feb 21, 2005 10:59 pm **Posts:** 1177

For the pmagic discrepancies, I will try to work them out in the next alpha.

For the tools discrepancies, I will fix them in the next alpha. Problem is I wrote a script that tries to change the version string in the various related files automatically, but there were some bugs that I didn't catch.

Thanks!

Icecube · **Joined:** Fri Jan 11, 2008 2:52 pm **Posts:** 1275

Set the Volume Label for the FDUBCD floppy image:

The mlabel (mtools suite) command adds a volume label to a disk. Its syntax is:

Code:

mlabel [-vcsn] [-N serial] drive:[new_label]

       Mlabel supports the following options:

       c      Clears an existing label, without prompting the user

       s      Shows the existing label, without prompting the user.

       n      Assigns a new (random) serial number to the disk

       N serial
              Sets  the  supplied  serial  number. The serial number should be
              supplied as an 8 digit hexadecimal number, without spaces

http://www.gnu.org/software/mtools/manu ... html#SEC57

Generate a random serial number (only needs to be done once). Probably there is already one set in the current image, but it doesn't hurt.

Code:

mlabel -i fdubcd.img -n ::

Everytime the FDUBCD floppy version is increased, update the Volume Label.
Make the Volume Label just 11 characters long (pad with spaces): "FDUBCD141 "
For some reason mlabel doesn't pad the Volume Label with spaces, like it should do (Ubuntu includes mtools v4.0.12):

Code:

mlabel -i fdubcd.img ::"FDUBCD141 "

This issue seems to be fixed in mtools v4.0.14 and higher, so for those versions, you can use:

Code:

mlabel -i fdubcd.img ::FDUBCD14

For the current image, the Volume Label isn't set correctly.

Quote:

This 11 byte long string should match the volume label entry in the root directory. If no such entry is available this field should contain the string 'NO NAME ' (11 bytes long string). When updating the volume label, both, this field and the entry in the root directory should be updated.

http://www.maverick-os.dk/FileSystemFor ... ystem.html

In the FDUBCD floppy image the Volume Label field in the boot sector is empty (11 spaces), while the Volume Label in the root directoy is NwDsk340.

Code:

mlabel -i fdubcd.img -s ::
 Volume label is NwDsk340

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 637

Icecube wrote:

For the current image, the Volume Label isn't set correctly.

Quote:

This 11 byte long string should match the volume label entry in the root directory. If no such entry is available this field should contain the string 'NO NAME ' (11 bytes long string). When updating the volume label, both, this field and the entry in the root directory should be updated.

http://www.maverick-os.dk/FileSystemFormats/FAT12_FileSystem.html

In the FDUBCD floppy image the Volume Label field in the boot sector is empty (11 spaces), while the Volume Label in the root directoy is NwDsk340.

Code:

mlabel -i fdubcd.img -s ::
 Volume label is NwDsk340

It seems the problem is Windows (I did NOT check several different versions, so this may vary). Apparently, when you select the "properties" of a floppy (or floppy image) in Windows Explorer, and there you set the "VolumeLabel" (at least for the first time), the "VolumeLabel" is set in the "RootDirectoryEntry" only, but not in the boot sector.

Icecube · **Joined:** Fri Jan 11, 2008 2:52 pm **Posts:** 1275

Another usefull command is:

Code:

minfo -i fdubcd.img ::

or with hexdump of the boot sector:

Code:

minfo -v -i fdubcd.img ::

minfo will show the Volume Label set in the boot sector only.
while mlabel displays the Volume Label set in the FAT root dir.

For the original FDUBCD image of UBCD v5.1 alpha 2:

Code:

$ minfo -v -i fdubcd.img ::
device information:
===================
filename="fdubcd.img"
sectors per track: 36
heads: 2
cylinders: 80

mformat command line: mformat -t 80 -h 2 -s 36 ::

bootsector information
======================
banner:"        "
sector size: 512 bytes
cluster size: 2 sectors
reserved (boot) sectors: 1
fats: 2
max available root directory slots: 240
small size: 5760 sectors
media descriptor byte: 0xf0
sectors per fat: 9
sectors per track: 36
heads: 2
hidden sectors: 0
big size: 0 sectors
physical drive id: 0x0
reserved=0x0
dos4=0x29
serial number: 00000000
disk label="           "
disk type="FAT12   "

Boot sector hexdump:
000  eb 3c 90 00 00 00 00 00 00 00 00 00 02 02 01 00 .<..............
010  02 f0 00 80 16 f0 09 00 24 00 02 00 00 00 00 00 ........$.......
020  00 00 00 00 00 00 29 00 00 00 00 20 20 20 20 20 ......)....     
030  20 20 20 20 20 20 46 41 54 31 32 20 20 20 fa fc       FAT12   ..
040  31 c0 8e d8 bd 00 7c b8 e0 1f 8e c0 89 ee 89 ef 1.....|.........
050  b9 00 01 f3 a5 ea 5e 7c e0 1f 00 00 60 00 8e d8 ......^|....`...
060  8e d0 8d 66 a0 fb 80 7e 24 ff 75 03 88 56 24 c7 ...f...~$.u..V$.
070  46 c0 10 00 c7 46 c2 01 00 e8 e9 00 46 72 65 65 F....F......Free
080  44 4f 53 00 8b 76 1c 8b 7e 1e 03 76 0e 83 d7 00 DOS..v..~..v....
090  89 76 d2 89 7e d4 8a 46 10 98 f7 66 16 01 c6 11 .v..~..F...f....
0a0  d7 89 76 d6 89 7e d8 8b 5e 0b b1 05 d3 eb 8b 46 ..v..~..^......F
0b0  11 31 d2 f7 f3 89 46 d0 01 c6 83 d7 00 89 76 da .1....F.......v.
0c0  89 7e dc 8b 46 d6 8b 56 d8 8b 7e d0 c4 5e 5a e8 .~..F..V..~..^Z.
0d0  9b 00 72 2f c4 7e 5a b9 0b 00 be f1 7d 57 f3 a6 ..r/.~Z.....}W..
0e0  5f 26 8b 45 1a 74 0b 83 c7 20 26 80 3d 00 75 e7 _&.E.t... &.=.u.
0f0  72 59 50 c4 5e 5a 8b 7e 16 8b 46 d2 8b 56 d4 e8 rYP.^Z.~..F..V..
100  6b 00 58 72 46 1e 07 8e 5e 5c bf 00 20 ab 89 c6 k.XrF...^\.. ...
110  01 f6 01 c6 d1 ee ad 73 04 b1 04 d3 e8 80 e4 0f .......s........
120  3d f8 0f 72 e8 31 c0 ab 0e 1f c4 5e 5a be 00 20 =..r.1.....^Z.. 
130  ad 09 c0 74 24 48 48 8b 7e 0d 81 e7 ff 00 f7 e7 ...t$HH.~.......
140  03 46 da 13 56 dc e8 24 00 73 e5 e8 17 00 20 65 .F..V..$.s.... e
150  72 72 00 30 e4 cd 16 cd 19 8a 5e 24 ff 6e 5a 31 rr.0......^$.nZ1
160  db b4 0e cd 10 5e ac 56 3c 00 75 f3 c3 56 89 46 .....^.V<.u..V.F
170  c8 89 56 ca 8c 46 c6 89 5e c4 b4 41 bb aa 55 8a ..V..F..^..A..U.
180  56 24 84 d2 74 19 cd 13 72 15 d1 e9 81 db 54 aa V$..t...r.....T.
190  75 0d 8d 76 c0 89 5e cc 89 5e ce b4 42 eb 2c 8b u..v..^..^..B.,.
1a0  4e c8 8b 56 ca 8a 46 18 f6 66 1a 91 f7 f1 92 f6 N..V..F..f......
1b0  76 18 89 d1 88 c6 86 e9 d0 c9 d0 c9 8a 46 18 28 v............F.(
1c0  e0 fe c4 08 e1 c4 5e c4 b8 01 02 8a 56 24 cd 13 ......^.....V$..
1d0  73 06 30 e4 cd 13 eb a2 8b 46 0b f6 76 c0 01 46 s.0......F..v..F
1e0  c6 83 46 c8 01 83 56 ca 00 4f 75 ea 8e 46 c6 5e ..F...V..Ou..F.^
1f0  c3 4b 45 52 4e 45 4c 20 20 53 59 53 00 00 55 aa .KERNEL  SYS..U.

Icecube · **Joined:** Fri Jan 11, 2008 2:52 pm **Posts:** 1275

Quote:

Thu 21/Apr/2011

Plop Boot Manager 5.0.12 released

The licence has been changed for 5.0.12. The boot manager is still free for personal and non-commercial use, but not free for commercial use! Maybe I give 5.0.12 free for commercial use in the future, but not now.

New:

* Hotkey ALT-u: Select/skip usb device before its fully identified.
* Ignore USB devices: Use USB Mass Storage device has been replaced with this new feature to ignore any usb device. This should avoid hangs on builtin webcams.
* Booting from 2nd, 3rd or 4th hard disk activates now an int13 driver that swaps the hard disk drive number.

Updates:

* Boot manager init routine updated.
* Some USB driver updates.
* Better MAC support.
* Bugfix: The hang when using CTRL-u to boot another usb drive than the first one is fixed.
* plpcfgbt updated for "ignore usb devices".
* plpcfgbtGUI updated.

http://www.plop.at/en/bootmngrusblog.html

UBCD V5.1 alpha 2 available for download

Who is online