similar to: ISOLINUX: 'Image checksum error' layout bug

From: Kim Mik <kimmik999999 at yahoo.co.uk> To: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> Sent: Tuesday, 29 September, 2009 22:21:39 Subject: Re: [syslinux] Chainc.32 missing some \n one error messages > From: Kim Mik <kimmik999999 at yahoo.co.uk> > To: syslinux at zytor.com > Sent: Monday, 17 August, 2009 1:30:04 > Subject: [syslinux] Chainc.32

Used rosh.c32 from syslinux-3.74-pre11. When I typed 'pzd' in the shell: > pzd /boot/syslinux > pwd /boot/syslinux I use an azerty keyboard. Due to that I typed 'pzd'. Is it a feature or a bug? Gert Hulsemans

I got the following message with chain.c32 ===================== Loader file too largeBoot: ===================== Like you can see, there should be a new line after 'large'. I guess that some other error messages, will result in the same behavior. Gert Hulselmans $ diff -u com32/modules/chain.c.old com32/modules/chain.c.new --- com32/modules/chain.c.old 2009-08-17

Comments fix and usage output corrected for chain.c32 - Gert Hulselmans Signed-off-by: Gert Hulselmans <kimmik999999 at yahoo.co.uk> $ diff -u syslinux-3.84/com32/modules/chain.c.old syslinux-3.84/com32/modules/chain.c --- syslinux-3.84/com32/modules/chain.c.old 2009-12-29 01:46:34.058793767 +0100 +++ syslinux-3.84/com32/modules/chain.c 2009-12-29 01:53:41.150794351 +0100 @@ -49,7

chain.c32 of SYSLINUX 3.82 does set the boot drive passed to the DL register to 0x80 and not to the boot drive (CD-drive). This can be a problem if you want to chainload grldr (grub4dos bootloader) from a CD and if you want to let grldr search for its menu.lst file on the CD. For more info: http://www.boot-land.net/forums/index.php?showtopic=8457 This 1 line patch fixes the issue (Thanks to

$ git log -p commit d8c5e94803fa01f0d52475a50b69681ad3135700 Author: Gert Hulselmans <kimmik999999 at yahoo.co.uk> Date: Sat Jan 9 15:30:49 2010 +0100 chain.c32: Add grldr= command for Grub4dos grldr of Grub4dos wants the partition number in DH: 0xff: whole drive 0-3: primary partitions 4-*: logical partitions diff --git a/com32/modules/chain.c

The following patch for chain.c32 adds support to boot the Recovery Console of Windows NT/2K/XP. Normally when you want to boot the recovery console, you need to patch "cmdcons\0" into the bootsectorof the partition (8 bytes starting at 0x3 (4th byte)). We can do this patching in memory: strcpy((char *) 0x7c03, "cmdcons"); To boot the recovery console with chain.c32:

Improving chain.c32 help message Impact: Error message is more detailed In case of syntax error, the message is far more detailed and provides the same content as the documentation integrated in the source code. You can get this patch from Erwan's git repo: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=3fc3126d0c7df5701680e043c34f200166f24564 Add 'isolinux=' option to

Hi, > makehybrid \ > -o isos/muaaa.iso temp/ \ > -eltorito-boot temp/isolinux/isolinux.bin \ > -no-emul-boot \ > -iso -joliet -boot-load-size 4 \ > -default-volume-name "Custom Installer" \ > -eltorito-platform temp/isolinux/boot.cat > ... > [at boot time:] > Image checksum error, sorry I guess it is the Boot Information Table feature

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot

Hi, I am trying to build a custom installer for a popular linux distro on MacOS. Here is how: makehybrid \ -o isos/muaaa.iso temp/ \ -eltorito-boot temp/isolinux/isolinux.bin \ -no-emul-boot \ -iso -joliet -boot-load-size 4 \ -default-volume-name "Custom Installer" \ -eltorito-platform temp/isolinux/boot.cat This happens when I boot up the new image:

This patch builds a floppy image with contains HDT, so users of GRUB or GRUB4DOS can use HDT too, without installing Syslinux. When you compile Syslinux, this floppy image isn't build automatically. To build it, runthe following from the extracted Syslinux source: $ cd ./com32/hdt $ make hdt.img As suggested by Pierre-Alexandre Meyer, all extra files required for building the floppy

Hi, I tried to install redhat 8.0 on a laptop and ran into the following problem. ISOLINUX 1.75 2002-06-14 isolinux failed to get sector size, assuming 0800 isolinux: Image checksum error, sorry... At that point, I followed the advice on the isolinux webpage, and reburned a CD using isolinux 2.00 with debug. The error message was: ISOLINUX 2.00 2002-10-25 Copyright (C) 1994-2002 H. Peter

A floppy image with Drive Fitness Test hangs in VirtualBox 3, while the same iso works fine in Qemu. Tested with MEMDISK from Syslinux 3.83-pre6. Adding raw or bigraw doesn't help. The image hangs with the text: ========================== loading bootsector..... loaded... starting PCDos... ========================== You can find the gzipped floppy image with Drive Fitness Test at the

Hi, Ady wrote: > During May 2009, a commit by Peter deleted the checksumiso.pl file. The > commit is: > core: LZO compress the PM part of the core > repo.or.cz/syslinux.git/commit/0d82b71304d596d80f3c4520f9dcf90048ca50b7 > And so, since version 4.00, the 'code/checksumiso.pl' file is no longer > included. > How is the checksum of isolinux.bin calculated since

Hi, Ady wrote: > Apparently, one of the consequences seems to be that the default > checksum included in isolinux.bin doesn't seem to help those > users/programs that, for whichever reason (e.g. user lacking > knowledge), do not patch the boot info table. I agree and still riddle about the reason. > So, my question is whether there is some intentional reason for these

> Ady wrote: > > This is a quote from Wonko/Jaclaz, who has also been investigation this > > issue and deserves credit for it: > > Ok, not that I understand the code, but what *somehow* happens is that > > the "embedded" checksum in Isolinux.bin (starting from 4.00) is the > > checksum of the WHOLE file (i.e. starting from offset 0 instead of 64) >

> Hi, > > i think i found a suspect in lzo/prepcore.c and it would indeed be a > wrong range of checksumming (speculative congratulations to Ady). Thank you Thomas for your replies and for looking into this issue. My part on the initial investigation that triggered this email thread is relatively small. Others deserve much more credit. I was/am providing not just my own report,

Hi Mr Anvin, after downloading the Freedos bootable cd, which now uses your projects (ISOLINUX & MEMDISK) instead of Bart Lagerweij's DISKEMU (www.nu2.nu), I contacted the creator of the freedos cdrom. I was interested in how he did make that cd bootable. Now I understand it a bit. As I'm a MS Windows user, I had to figure some things out. However, upon booting I get a beautiful

H, Ady wrote: > A_ The default checksum included in the tested isolinux.bin (offset 20, > 4-bytes-long) is the "correct" one (as oppose to the current situation, > since version 4.00). That's good news. > F_ In the tested isolinux.bin file, there are two additional bytes that > I found to be changed/affected by some ISO-building tools (e.g. > mkisofs), at