[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-xorriso] About run xorriso under Win32
From: |
Thomas Schmitt |
Subject: |
Re: [Bug-xorriso] About run xorriso under Win32 |
Date: |
Thu, 20 Nov 2014 10:10:01 +0100 |
Hi,
> libisofs_DEBUG: size=24576, ret=24541, 0x5FDD
As expected, a short result of read(2).
But the reason is still a riddle. If it was some Cygwin limit
on the size of a read(2) then i would have expected a number
which is aligned to some block size.
But the number of requested bytes is a neat number (2 exp 13 * 3)
and the reply 24541 (11 * 23 * 97) is not a multiple of any
plausible block size.
The disk file in question is
isolinux/isolinux.bin
What do you get from
ls -l isolinux/isolinux.bin
and
wc isolinux/isolinux.bin
> If possible, could you please point me about how to use the libisoburn?
Normally you just unpack libisoburn-1.3.8.tar.gz and do
configure && make. But first you'd need to build and install
libburn-1.3.8 and libisofs-1.3.8.
So let's stay with GNU xorriso, which brings all non-standard
equipment in its tarball and needs no system-wide installation.
The source code is the same. Only the way of linking differs.
GNU xorriso does not need nor tries to use the installed
libisofs and libburn.
> Actually, I had tried mkisofs (schily-cdrtools-3.01a25) [...]
> -eltorito-platform 0xEF -no-emul-boot -b "boot/grub/efi.img" [...]
> However the generated iso can't boot EFI machine due to some reason even it
> can boot BIOS machine.
Let's hope it is a flaw of mkisofs and not of your EFI.
What do you get from an inspection of the resulting ISO ?
(The command -report_el_torito is known only to xorriso-1.3.8
or later)
..\xorriso -indev ..\a.iso -report_el_torito plain
Here is example output from an Archlinux ISO for BIOS and (U)EFI:
El Torito catalog : 42 1
El Torito cat path : /isolinux/boot.cat
El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA
El Torito boot img : 1 BIOS y none 0x0000 0x00 4 20078
El Torito boot img : 2 UEFI y none 0x0000 0x00 63488 21108
El Torito img path : 1 /isolinux/isolinux.bin
El Torito img opts : 1 boot-info-table isohybrid-suitable
El Torito img path : 2 /EFI/archiso/efiboot.img
What happens about EFI booting if you leave out the BIOS
boot options in your xorriso run ? I.e.:
..\xorriso -as mkisofs -U -A centos65 -V centos65 -volset centos65 -J
-joliet-long -r -v -T -o ../centos65.iso -c isolinux/boot.cat -e
boot/grub/efi.img -no-emul-boot .
(No -boot-info-table causes no read attempt for patching. So
the code part which throws the error will not be executed.
The lfs_read() calls for copying file content into the
emerging ISO image request smaller chunk sizes than the
call for patching the BIOS boot image.)
> Do you have some suggestions about it?
Hopefully i augmented lfs_read() so that it tries to read
the missing bytes if read(2) delivers not the expected amount.
This still needs some testing here, because it is a very central
function of libisofs.
In the course of this day i will prepare and upload a new
development snapshot xorriso-1.3.9.tar.gz and give you a note.
(Do not download an existing xorriso-1.3.9.tar.gz now, because
it is not yet on the newest state.)
Have a nice day :)
Thomas
- [Bug-xorriso] About run xorriso under Win32, jiang gary, 2014/11/19
- Re: [Bug-xorriso] About run xorriso under Win32, Thomas Schmitt, 2014/11/19
- Re: [Bug-xorriso] About run xorriso under Win32,
Thomas Schmitt <=
- Re: [Bug-xorriso] About run xorriso under Win32, gary jiang, 2014/11/20
- Re: [Bug-xorriso] About run xorriso under Win32, gary jiang, 2014/11/21
- Re: [Bug-xorriso] About run xorriso under Win32, Thomas Schmitt, 2014/11/21
- Re: [Bug-xorriso] About run xorriso under Win32, Thomas Schmitt, 2014/11/21
- Re: [Bug-xorriso] About run xorriso under Win32, Thomas Schmitt, 2014/11/21
- Re: [Bug-xorriso] About run xorriso under Win32, gary jiang, 2014/11/21
- Re: [Bug-xorriso] About run xorriso under Win32, gary jiang, 2014/11/22