Mailing List Archive

I checked the NEWS section and since I am not an expert at all on these kind of things, but could this maybe have something to do with the problem?

* ISOLINUX: Fix for certain broken CD-ROM BIOSes which
randomly corrupted register FS.


This is the code to create the image. It has never been changed in years.
It is from Barts old Boot CD and just uses MKISOFS to generate a isolinux CD image.


BCD, Build CD-Rom, v1.1.1
Copyright (c) 2002 Bart Lagerweij. All rights reserved.
This program is free software. Use and/or distribute it under the terms
of the NU2 License (see nu2lic.txt or http://www.nu2.nu/license/).

BCD: Checking for required files:
BCD: Processing (main) config file "bcd.cfg"
BCD: Application set to "BCD/MKISOFS"
BCD: System set to "Win32"
BCD: Processing (CD) config file "cds\corpmb\bcd.cfg"
BCD: Bootfile set to "isolinux\isolinux.bin"
BCD: Mkisofsargs set to "-J -N -joliet-long -no-iso-translate"
BCD: Processing bootdisk config file "cds\corpmb\bootdisk.cfg"
BCD: Bootimage "isolinux\cdrom.img" already exists, skip creation
BCD: Bootimage "isolinux\corpnet.img" already exists, skip creation
BCD: Bootfile is "isolinux/isolinux.bin"
BCD: Bootfile type is ".bin" adding "-no-emul-boot -boot-load-size 4"
BCD: Bootfile is ISOLINUX adding "-boot-info-table"
BCD: Hidding boot image in ISO9660 adding "-hide isolinux.bin"
BCD: Hidding boot catalog in ISO9660 adding "-hide boot.catalog"
BCD: Hidding boot image in Joliet adding "-hide-joliet isolinux.bin"
BCD: Hidding boot catalog in Joliet adding "-hide-joliet boot.catalog"
BCD: Creating ISO image file (running mkisofs.exe)
BCD: Arguments; -J -N -joliet-long -no-iso-translate -A BCD/MKISOFS -sysid "Win32" -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -hide isolinux.bin -hide boot.catalog -hide-joliet isolinux.bin -hide-joliet boot.catalog -v -o f:\bcd\image\bcd.iso cds\corpmb\files
mkisofs 2.01a17-Bart (i686-pc-cygwin)


--------------------------------------------------------------------------------
BÖWE SYSTEC Mailroom Communication GmbH
Sitz der Gesellschaft: D-86159 Augsburg
Amtsgericht Augsburg HRB 17386
Geschäftsführer: Michael Meyer
---------------------------------------------------------------------------------
Diese E-Mail und die darin enthaltenen Informationen ist/sind ausschließlich für den/die oben bezeichneten Adressaten bestimmt. Sie können vertraulichen Charakter haben und/oder gesetzlich geschützt sein. Unberechtigter Gebrauch, Vervielfältigung oder Offenlegung sind untersagt und widerrechtlich. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, benachrichtigen Sie den Absender bitte per E-Mail, Telefon oder Telefax.

This communication and the information it contains is only intended for the addressee(s) named above and may be confidential, legally privileged and protected by law. Unauthorised use, copying or disclosure of any of it is restrained and may be unlawful. If you have received this communication in error, please contact us immediately by email, telephone or facsimile.
-----Ursprüngliche Nachricht-----
Von: syslinux-bounces@zytor.com [mailto:syslinux-bounces@zytor.com] Im Auftrag von Geert Stappers
Gesendet: Freitag, 9. November 2007 10:10
An: syslinux@zytor.com
Betreff: Re: [syslinux] Booting of bcdw from isolinux does not workanymore with 3.52 but works with 3.51

Op 09-11-2007 om 08:48 schreef Zipf Christian:
> Von: syslinux-bounces@zytor.com [mailto:syslinux-bounces@zytor.com] Im Auftrag von H. Peter Anvin
> Gesendet: Donnerstag, 8. November 2007 18:07
>
> > Looks like syslinux booted it just fine and it's having a problem once
> > booted...
>
> I see your point since it is complaining about the second file it
> wants to load afterwards. Syslinux loaded the bcdwboot.bin fine but
> maybe in a different way than before?
>
> Did something change in the memory layout or somewhere else?

The file 'NEWS' has the changes documented.

> The script to create the image never changed in years and if I go back
> to any version before 3.52 it works again.

I have no clue which script creates the image.
Could the particular script rely on a "bug" in syslinux?

In other words: tell more about the mentioned script.


Cheers
Geert Stappers

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.


_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

It is a good thing to allow
archive and digest users to read in the discussion order.

In other words: Reply _below_ the text.

Op 09-11-2007 om 10:27 schreef Zipf Christian:
>
> I checked the NEWS section and since I am not an expert at all on
> these kind of things, but could this maybe have something to do with
> the problem?
>
> * ISOLINUX: Fix for certain broken CD-ROM BIOSes which
> randomly corrupted register FS.
>
> This is the code to create the image. It has never been changed in years.
> It is from Barts old Boot CD and just uses MKISOFS to generate a isolinux CD image.
>
> BCD, Build CD-Rom, v1.1.1
> Copyright (c) 2002 Bart Lagerweij. All rights reserved.
> This program is free software. Use and/or distribute it under the terms
> of the NU2 License (see nu2lic.txt or http://www.nu2.nu/license/).
>
> BCD: Checking for required files:
> BCD: Processing (main) config file "bcd.cfg"
> BCD: Application set to "BCD/MKISOFS"
> BCD: System set to "Win32"
> BCD: Processing (CD) config file "cds\corpmb\bcd.cfg"
> BCD: Bootfile set to "isolinux\isolinux.bin"
> BCD: Mkisofsargs set to "-J -N -joliet-long -no-iso-translate"
> BCD: Processing bootdisk config file "cds\corpmb\bootdisk.cfg"
> BCD: Bootimage "isolinux\cdrom.img" already exists, skip creation
> BCD: Bootimage "isolinux\corpnet.img" already exists, skip creation
> BCD: Bootfile is "isolinux/isolinux.bin"
> BCD: Bootfile type is ".bin" adding "-no-emul-boot -boot-load-size 4"
> BCD: Bootfile is ISOLINUX adding "-boot-info-table"
> BCD: Hidding boot image in ISO9660 adding "-hide isolinux.bin"
> BCD: Hidding boot catalog in ISO9660 adding "-hide boot.catalog"
> BCD: Hidding boot image in Joliet adding "-hide-joliet isolinux.bin"
> BCD: Hidding boot catalog in Joliet adding "-hide-joliet boot.catalog"
> BCD: Creating ISO image file (running mkisofs.exe)
> BCD: Arguments; -J -N -joliet-long -no-iso-translate -A BCD/MKISOFS
> -sysid "Win32" -b isolinux/isolinux.bin -no-emul-boot
> -boot-load-size 4 -boot-info-table -hide isolinux.bin
> -hide boot.catalog -hide-joliet isolinux.bin
> -hide-joliet boot.catalog
> -v -o f:\bcd\image\bcd.iso cds\corpmb\files
> mkisofs 2.01a17-Bart (i686-pc-cygwin)
>

The original error was/is:
| Error! Cannot load file (code: 0110h):
| \bcdw\bcdw.bin

But I can't see "\bcdw\bcdw.bin" in the above output.

And there is the report that 3.51 works, but 3.52 doesn't.


Say the upgrade to 3.52 did break things, now I dare :-) to say
that upgrade went wrong. I can't backup that, but I can imagion
that isolinux.bin and isolinux\isolinux.bin are different files
and that only one was upgraded where both should have been.
Other partly upgrades could also the cause of the problem.

Please don't get me wrong, I not saying the problem is at the other
side, I'm saying that I don't get the problem at my side.

Important is that the setup of the original poster should
be working also with Syslinux 3.52 and above.
And when it doesn't, it is important to known why it fails
or at least where it fails.


Cheers
Geert Stappers

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

--------------------------------------------------------------------------------
BÖWE SYSTEC Mailroom Communication GmbH
Sitz der Gesellschaft: D-86159 Augsburg
Amtsgericht Augsburg HRB 17386
Geschäftsführer: Michael Meyer
---------------------------------------------------------------------------------
Diese E-Mail und die darin enthaltenen Informationen ist/sind ausschließlich für den/die oben bezeichneten Adressaten bestimmt. Sie können vertraulichen Charakter haben und/oder gesetzlich geschützt sein. Unberechtigter Gebrauch, Vervielfältigung oder Offenlegung sind untersagt und widerrechtlich. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, benachrichtigen Sie den Absender bitte per E-Mail, Telefon oder Telefax.

This communication and the information it contains is only intended for the addressee(s) named above and may be confidential, legally privileged and protected by law. Unauthorised use, copying or disclosure of any of it is restrained and may be unlawful. If you have received this communication in error, please contact us immediately by email, telephone or facsimile.
-----Ursprüngliche Nachricht-----
Von: syslinux-bounces@zytor.com [mailto:syslinux-bounces@zytor.com] Im Auftrag von Geert Stappers
Gesendet: Freitag, 9. November 2007 12:32
An: syslinux@zytor.com
Betreff: Re: [syslinux] Booting of bcdw from isolinux does notworkanymore with 3.52 but works with 3.51


It is a good thing to allow
archive and digest users to read in the discussion order.

In other words: Reply _below_ the text.

Op 09-11-2007 om 10:27 schreef Zipf Christian:
>
> I checked the NEWS section and since I am not an expert at all on
> these kind of things, but could this maybe have something to do with
> the problem?
>
> * ISOLINUX: Fix for certain broken CD-ROM BIOSes which
> randomly corrupted register FS.
>
> This is the code to create the image. It has never been changed in years.
> It is from Barts old Boot CD and just uses MKISOFS to generate a isolinux CD image.
>
> BCD, Build CD-Rom, v1.1.1
> Copyright (c) 2002 Bart Lagerweij. All rights reserved.
> This program is free software. Use and/or distribute it under the terms
> of the NU2 License (see nu2lic.txt or http://www.nu2.nu/license/).
>
> BCD: Checking for required files:
> BCD: Processing (main) config file "bcd.cfg"
> BCD: Application set to "BCD/MKISOFS"
> BCD: System set to "Win32"
> BCD: Processing (CD) config file "cds\corpmb\bcd.cfg"
> BCD: Bootfile set to "isolinux\isolinux.bin"
> BCD: Mkisofsargs set to "-J -N -joliet-long -no-iso-translate"
> BCD: Processing bootdisk config file "cds\corpmb\bootdisk.cfg"
> BCD: Bootimage "isolinux\cdrom.img" already exists, skip creation
> BCD: Bootimage "isolinux\corpnet.img" already exists, skip creation
> BCD: Bootfile is "isolinux/isolinux.bin"
> BCD: Bootfile type is ".bin" adding "-no-emul-boot -boot-load-size 4"
> BCD: Bootfile is ISOLINUX adding "-boot-info-table"
> BCD: Hidding boot image in ISO9660 adding "-hide isolinux.bin"
> BCD: Hidding boot catalog in ISO9660 adding "-hide boot.catalog"
> BCD: Hidding boot image in Joliet adding "-hide-joliet isolinux.bin"
> BCD: Hidding boot catalog in Joliet adding "-hide-joliet boot.catalog"
> BCD: Creating ISO image file (running mkisofs.exe)
> BCD: Arguments; -J -N -joliet-long -no-iso-translate -A BCD/MKISOFS
> -sysid "Win32" -b isolinux/isolinux.bin -no-emul-boot
> -boot-load-size 4 -boot-info-table -hide isolinux.bin
> -hide boot.catalog -hide-joliet isolinux.bin
> -hide-joliet boot.catalog
> -v -o f:\bcd\image\bcd.iso cds\corpmb\files
> mkisofs 2.01a17-Bart (i686-pc-cygwin)
>

The original error was/is:
| Error! Cannot load file (code: 0110h):
| \bcdw\bcdw.bin

But I can't see "\bcdw\bcdw.bin" in the above output.

And there is the report that 3.51 works, but 3.52 doesn't.


Say the upgrade to 3.52 did break things, now I dare :-) to say
that upgrade went wrong. I can't backup that, but I can imagion
that isolinux.bin and isolinux\isolinux.bin are different files
and that only one was upgraded where both should have been.
Other partly upgrades could also the cause of the problem.

Please don't get me wrong, I not saying the problem is at the other
side, I'm saying that I don't get the problem at my side.

Important is that the setup of the original poster should
be working also with Syslinux 3.52 and above.
And when it doesn't, it is important to known why it fails
or at least where it fails.


Cheers
Geert Stappers

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.



I can assure you that isolinux.bin was updated accordingly. As I said before nothing was changed on that script at all. All I did was replace the isolinux.bin and memtest with the one from the 3.52 distribution and it stopped working. I am not saying that the problem lies within isolinux, it could be within bcdw as well, or I made a mistake somewhere. Bcdw has not been updated in years, and it never made any problems with all the other versions of isolinux I used before.

So what exactly do you need to look a little closer into this?
Would a simple script to creat a isolinux bootable cd that just loads bcdw, be enough?

Christian

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.