similar to: [Arch] syslinux 6.02 patch test result

> I'm the developer of manjaroiso, the tool we use to build our install > medias for Manjaro Linux. > During our testings we found out, that syslinux6 won't work on older > hardware. I've a new Lenovo i7 notebook which booted up our images > just fine. Even with syslinux6. On my other PCs I got similar error > messages as Carl got. (snip) > > In

-- Re-sent as original may be stuck at awaiting "authorisation" (originally sent before I joined the mailing list) Hi All, It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or DVD on older - non-UEFI - systems. Any attempt to do so will result in the following error message: ISOLINUX 6.02 ETCDisolinux: Disk error 01, AX = 4279, drive FE It is still possible to

Hi, i am experiencing strange boot failures after repacking the ISO image archlinux-2013.11.01-dual.iso without isohybrid and EFI: # mount -o loop archlinux-2013.11.01-dual.iso /mnt $ xorriso -as mkisofs \ -o arch_repacked.iso \ -c isolinux/boot.cat \ -b isolinux/isolinux.bin \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -V "ARCH_201311" \

On 11/25/2013 04:39 PM, Thomas Schmitt wrote: > Hi, > > Gerardo Exequiel Pozzi wrote: >> Looks like there is something beyond LBA 65535 (As Mattias confirmed) > > I wanted to ask him now, whether this was already with > version 6. > But meanwhile he reported that it was 5. > > >> I can push isolinux.bin (4.07) to a really high LBA address and boot

On 11/25/2013 08:40 AM, Thomas Schmitt wrote: > Hi, > > Ady wrote: >> I guess that being isolinux.bin 4.07 smaller than 32KiB (24KiB), >> while isolinux.bin 6.02 being bigger (42KiB), and with the addition >> of multiple alternative boot images in the same ISO, the chances of >> isolinux.bin being located on a higher sector in the media seem to be >>

On 11/26/2013 01:14 AM, H. Peter Anvin wrote: > On 11/25/2013 06:32 PM, H. Peter Anvin wrote: >> On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote: >>> >>> I made some more and more experiments beyond LBA 65535 >>> >>> Works: * isolinux-4.07.bin (size 24574) * isolinux-5.00.bin (size >>> 34816) >>> >>> Does not work: *

On 11/25/2013 06:27 PM, Gerardo Exequiel Pozzi wrote: > On 11/25/2013 04:39 PM, Thomas Schmitt wrote: >> Hi, >> >> Gerardo Exequiel Pozzi wrote: >>> Looks like there is something beyond LBA 65535 (As Mattias confirmed) >> >> I wanted to ask him now, whether this was already with >> version 6. >> But meanwhile he reported that it was 5.

On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote: > > I made some more and more experiments beyond LBA 65535 > > Works: * isolinux-4.07.bin (size 24574) * isolinux-5.00.bin (size > 34816) > > Does not work: * isolinux-5.01.bin (size 34816) * isolinux-5.10.bin > (size 36864) * isolinux-6.00.bin (size 38912) * isolinux-6.02.bin > (size 43008) > > * I just

On 11/26/2013 02:22 AM, Gerardo Exequiel Pozzi wrote: > On 11/26/2013 01:14 AM, H. Peter Anvin wrote: >> On 11/25/2013 06:32 PM, H. Peter Anvin wrote: >>> On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote: >>>> >>>> I made some more and more experiments beyond LBA 65535 >>>> >>>> Works: * isolinux-4.07.bin (size 24574) *

> As stated earlier, the next version of xorriso will have > sort weight 2 for El Torito boot images by default. > But it will not harm to explicitely use --sort-weight > options with old and new versions of xorriso. FWIW, mkisofs is supposed to assign a +2 sort weight by default to the eltorito boot image and +1 to the boot catalog, at least when no sort file is provided. I

Hi, Gerardo Exequiel Pozzi wrote: > Looks like there is something beyond LBA 65535 (As Mattias confirmed) I wanted to ask him now, whether this was already with version 6. But meanwhile he reported that it was 5. > I can push isolinux.bin (4.07) to a really high LBA address and boot > without any issue. (Load LBA: 2048034 (0x001f4022)) ~4G This is riddling, given the statement of

Hi, the riddle about the failing repacks is solved, thanks to ISOLINUX wiki: "does support long (level 2) ISO 9660 plain filenames" The archlinux ISO makes use of such names. So i have to follow the wiki advise "use the "-l" or "-iso-level 2" option to mkisofs" Thus, a CD-bootable archlinux ISO without isohybrid and EFI can be repacked by # mount -o

Hi, Ady wrote: > I guess that being isolinux.bin 4.07 smaller than 32KiB (24KiB), > while isolinux.bin 6.02 being bigger (42KiB), and with the addition > of multiple alternative boot images in the same ISO, the chances of > isolinux.bin being located on a higher sector in the media seem to be > higher. > > So, perhaps the potential problem was always there, just that the

Im trying to get a program to work but it needs .NETFramework. I installed it using wine, but it seems to get a lot of errors when installing but then the installer says it has been installed successfully. After that when i try to the program from my windows section of the hard drive i get this error: $ wine '/media/disk/Program Files/ChatStat Technologies/ChatStat/ChatStat.exe'

Just FYI, MySQL stuff has been pulled from Asterisk since apparently now the client libraries are under GPL and not LGPL (and thus are incompatible with OpenH323). You may check out the MySQL code under "asterisk-addons", but you should not use both MySQL and OpenH323 (OpenSSL is also questionable) in the same Asterisk installation unless you downgrade your MySQL client libraries to a

On 11/24/2013 09:23 PM, Gerardo Exequiel Pozzi wrote: > On 11/23/2013 09:35 AM, Carl Duff wrote: >> -- Re-sent as original may be stuck at awaiting "authorisation" (originally >> sent before I joined the mailing list) >> >> Hi All, >> >> It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or >> DVD on older - non-UEFI -

Recently a patch by HPA was added to the elflink branch, "isolinux: Clear upper half of EDX before using..." http://git.zytor.com/?p=syslinux/syslinux.git;a=commit;h=870b84dd8714d dfccc9288025331423efa6d76b7 The patch was then applied to the firmware branch too. The patch solves an issue introduced by a prior commit "isolinux: Update LBA in getlinsec loop". Since the

On 06/13/2013 11:06 PM, Gerardo Exequiel Pozzi wrote: > On 06/13/2013 10:15 PM, Gene Cumm wrote: >> On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi >> <vmlinuz386 at yahoo.com.ar> wrote: >>> Hello >>> >>> While testing PXE booting, I decided to change IPAPPEND to the new >>> SYSAPPEND and does not work: nothing is appended to command

On 06/13/2013 10:15 PM, Gene Cumm wrote: > On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello >> >> While testing PXE booting, I decided to change IPAPPEND to the new >> SYSAPPEND and does not work: nothing is appended to command line. >> >> I tested using menu.c32 and vesamenu.c32, same issue.

On 06/06/2013 02:00 AM, Gene Cumm wrote: > On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello, >> >> First, this setup works fine without any error in syslinux 4.06 as show >> below. >> >> For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] >> directories (~2MB each) are uploaded