similar to: USB boot: No DEFAULT or UI configuration directive found!

On Fri, Mar 24, 2017 at 05:38:31PM +0100, Thomas Schmitt via Syslinux wrote: > isohdpfc pushes the CX value to the stack which it gets from INT 13 AH 41. > Quite surely bit 0 of that CX is not set. But bit 2 "Enhanced Disk Drive" > could be set. > https://en.wikipedia.org/wiki/INT_13H > > I understand on David's BIOS after > > andw $1,%cx

Hi, Geert Stappers wrote: > Contact David off-list, he did unsubscribe. Can you tell when he unsubscribed (i.e. which of the messages he got as last one) ? > Martin posted elsewhere in this thread "Thomas, you found the bug" > and provided a patch. Open question is whether the fix helps with David's BIOS. The newest answer from Martin indicates that a failure to read

I have tested isolinux without a config file and discovered the following: ISOLINUX 3.86 30-g9cc609c ETCD Copyright (C) 1994-2010 H. Peter Anvin et al No DEFAULT or UI configuration directive found! boot: and ISOLINUX 4.02 4.02* ETCD Copyright (C) 1994-2010 H. Peter Anvin et al ERROR: No configuration file found seems to hang here. no_default_msg gets printed too, but is overwritten since the

"syslinux No DEFAULT or UI configuration directive found! boot:" "In order to fix this problem, you will have to plugin the USB drive into another computer and then rename the "isolinux" folder to "syslinux". In addition to that also rename the "isolinux.bin" and "isolinux.cfg" files in the same folder to "syslinux.bin" and

Hi, i am looking now at the code which i assume loads the rest of isolinux.bin. The entry point for program execution from the MBR is obviously at http://git.zytor.com/syslinux/syslinux.git/tree/core/isolinux.asm#n186 (Do i get it right that this is the Intel syntax ? (Gronfff)) If POP yields the victim of the most recent not yet popped PUSH, then this does not look correctly coordinated

SYSLINUX 4.00 2010-06-28 EDD Load error - Boot error Booting from USB on old IBM T43 or newer Esprimo E5731E. No problems with version 3.86 and same usb-stick.

Hi, C/H/S addressing and reading of first block seems to be ok in isohdpfd.bin. The main suspect for the failure of the attempt with isohdpfd.bin is the number or content of the blocks read after the first one. But i have no clue why isohdpfc.bin should do better than isohdpfd.bin. They differ just by one instruction (JC = 0x72 versus JMP = 0xEB) which both are performed before the reading and

Thomas Schmitt wrote: > I still don't get the "backwards" aspect. (Probably not enough background > knowledge.) Sigh. inst x, y gas use x and possibly y, operates according to inst and puts the result in y. Intel lives with the misconception this should mean use y and possibly x, operate according to inst and put the result in x. If you come from gas background the first

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: > Some of the things you should / could (re)test / (re)try: > > _ Verify the md5sum of the ISO image. SHA256 verified for downloaded image and for contents of USB flash drive (see below). > _ Is this particular USB device _still_ capable of booting newer > computers? Yes. > What happens if you would try _again_ to boot a

On Tue, Mar 21, 2017 at 09:03:35AM +0100, Thomas Schmitt via Syslinux wrote: > I think we should offer David a binary which he can combine with > the MBR of the ISO and the image with the recognizable blocks. > I will later today upload a binary version of my block producer > and post the URL. > > The combination will be: > 432 bytes from Martin's MBR > 80 bytes

We use "isolinux.bin" 3.72 and meet an issue : we put all the files(including config file, kernel and initrd file) under the root directory and some additional normal files in it. If adding enough files in the root directory, the created ISO will fail to boot, hanging at "ISOLINUX 3.72 3.72 ETCD Copyright (C) 1994-2008 H. Peter Anvin". Is this a known issue? Is it fixed in the

On 13.07.2015 18:48, Gene Cumm wrote: > On Mon, Jul 13, 2015 at 10:20 AM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.07.2015 15:19, Gene Cumm wrote: >>> On Mon, Jul 13, 2015 at 9:03 AM, poma <pomidorabelisima at gmail.com> wrote: >>>> On 13.07.2015 14:53, Gene Cumm wrote: >>>>> On Mon, Jul 13, 2015 at 6:42 AM, poma

On 13.07.2015 15:19, Gene Cumm wrote: > On Mon, Jul 13, 2015 at 9:03 AM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.07.2015 14:53, Gene Cumm wrote: >>> On Mon, Jul 13, 2015 at 6:42 AM, poma <pomidorabelisima at gmail.com> wrote: >>> >>>> A patch like this? >>>> >>>> >>> >>> Correct. Have you

At first I thought, I was dealing with the known EBIOS/CBIOS-problem. The symptom was exactly the same (hangs at ...EBIOS). As 3.10-pre8 and 3.10-pre9, in contrary what was mentioned in the ML, did not bring any improvement, I looked deeper into what could be my specific problem. I found out that the program just halted at 'cmp [esi],edx' (line 658; ldlinux.asm 3.10-pre9)! By replacing

I have just pushed out SYSLINUX 3.10-pre9. Please test it out, especially everyone who has been working with me on various systems trying to get them to work, or have had recent breakage. -hpa

> 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

On 29.06.2015 17:06, Matthew Miller via Syslinux wrote: > > It actuallly looks from Adam's investigation that this isn't different > for this package. So, less than certainly. It looks like maybe more a > gcc 5 difference. > > > Regardless of whatever is actually causing this, here is the isolinux-debug.bin output: Booting from DVD/CD... ISOLINUX 6.03

On 08.02.2016 19:04, H. Peter Anvin wrote: > On 02/03/16 10:30, H. Peter Anvin via Syslinux wrote: >> On February 3, 2016 7:17:37 AM PST, Celelibi <celelibi at gmail.com> wrote: >>> 2016-02-02 18:50 UTC+01:00, poma via Syslinux <syslinux at zytor.com>: >>>> On 30.01.2016 16:59, poma wrote: >>>>> ... >>>>> >>>>>

On 14.07.2015 01:31, Gene Cumm wrote: > On Mon, Jul 13, 2015 at 3:24 PM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.07.2015 18:48, Gene Cumm wrote: > >>> It stops after printing the access type "ETCD" and before printing the >>> remainder of the banner. I presume this is not a hybridized image? >>> >> >> >> I