search for: 0x55aa

...kio_bios.c --- syslinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400 +++ syslinux-6.02/core/fs/diskio_bios.c 2014-02-20 12:15:08.000000000 +0400 @@ -337,7 +337,7 @@ struct disk *bios_disk_init(void *privat /* Get EBIOS support */ ireg.eax.b[1] = 0x41; ireg.ebx.w[0] = 0x55aa; - ireg.eflags.b[0] = 0x3; /* CF set */ + ireg.edx.b[0] = devno; __intcall(0x13,&ireg,&oreg); @@ -353,6 +353,7 @@ struct disk *bios_disk_init(void *privat edd_params.len = sizeof edd_params; ireg.eax.b[1] = 0x48; + ireg.edx.b[0] = devno; ireg....

...W SATA Dual Layer (Fimware IL00) [GH20NS15] ------------------------------------------------------------------- $ dumpet -i archlinux-2013.11.24-dual.iso Validation Entry: Header Indicator: 0x01 (Validation Entry) PlatformId: 0x00 (80x86) ID: "" Checksum: 0x55aa Key bytes: 0x55aa Boot Catalog Default Entry: Entry is bootable Boot Media emulation type: no emulation Media load segment: 0x0 (0000:7c00) System type: 0 (0x00) Load Sectors: 4 (0x0004) Load LBA: 22792 (0x00005908) Section Header Entry:...

-- 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

...d boot disks that need to have hardware independent CD-Rom support... At the moment it has some small bugs, but when it is stable maybe you can mention it in your memdisk documentation... One small question, can isolinux also chainload NT CD-Rom bootstrap loaders? They are 2KB in size and have a 0x55AA signature at the end... I've tried: label bcnt4 kernel bcnt4.bs But isolinux says: Loading Invalid or corrupt kernel image. boot: Best regards, Bart. -- Bart Lagerweij Mailto:bart at cts-bv.nl -- CTS, Computer Technology Systems B.V. Oosteinde 85, 3925 LB P.O. Box 113, 3925 ZJ Scherpenz...

...ow see you have included it in isolinux 1.73 and higher. Great!!! I tried it using isolinux 1.74 and 1.75pre2, but I cannot get it to work. It says: -- Loading Invalid or corrupt kernel image. -- I use the file extension ".bin" as I see in the isolinux.asm source, the file is 2KB and has 0x55aa stamp in the last 2 bytes. What can be wrong? Regards, Bart. --- Bart Lagerweij - http://www.nu2.nu To contact me go here: http://www.nu2.nu/contact/bart ---

...gt; > ------------------------------------------------------------------- > > $ dumpet -i archlinux-2013.11.24-dual.iso > Validation Entry: > Header Indicator: 0x01 (Validation Entry) > PlatformId: 0x00 (80x86) > ID: "" > Checksum: 0x55aa > Key bytes: 0x55aa > Boot Catalog Default Entry: > Entry is bootable > Boot Media emulation type: no emulation > Media load segment: 0x0 (0000:7c00) > System type: 0 (0x00) > Load Sectors: 4 (0x0004) > Load LBA: 22792...

...slinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 13:59:03.000000000 -0400 +++ syslinux-6.02/core/fs/diskio_bios.c 2014-02-23 14:04:17.876084866 -0500 @@ -337,6 +337,7 @@ struct disk *bios_disk_init(void *privat /* Get EBIOS support */ ireg.eax.b[1] = 0x41; ireg.ebx.w[0] = 0x55aa; + ireg.edx.b[0] = devno; ireg.eflags.b[0] = 0x3; /* CF set */ __intcall(0x13, &ireg, &oreg); @@ -353,6 +354,7 @@ struct disk *bios_disk_init(void *privat edd_params.len = sizeof edd_params; ireg.eax.b[1] = 0x48; + ireg.edx.b[0] = devno;...

...then CX will indicate if wanted EBIOS calls are supported or not as the and will mask away all but the interesting bit. The code: /* Check to see if we have EBIOS */ pushw %dx /* drive number */ movb $0x41, %ah /* %al == 0 already */ movw $0x55aa, %bx xorw %cx, %cx xorb %dh, %dh stc int $0x13 jc 1f cmpw $0xaa55, %bx jne 1f andw $1,%cx /* Bit 0 = fixed disk subset */ jz 1f /* We have EBIOS; patch in the following code at...

...mainly to manipulate image files), I missed that. How do you tell if it is the "usual" single sector of 512 bytes or more? Wouldn't there need to be some flag at some location? Or is the assumption that fat32 can skip any number of sectors until it reaches one with the magic signature 0x55AA and it takes all sectors from 0 until that one as the VBR? > moving ldlinux.sys within a FAT32 boot volume could > potentially affect the boot process when using SYSLINUX. In such case, > executing the command line installer would be the simplest/quickest > solution. But even so, it i...

...s > are supported or not as the and will mask away all but the interesting > bit. > > > The code: > /* Check to see if we have EBIOS */ > pushw %dx /* drive number */ > movb $0x41, %ah /* %al == 0 already */ > movw $0x55aa, %bx > xorw %cx, %cx > xorb %dh, %dh > stc > int $0x13 > jc 1f > cmpw $0xaa55, %bx > jne 1f > andw $1,%cx > /* Bit 0 = fixed disk subset */ > jz 1f > >...

...d run the following: nvagetbios -S PRAMIN > vbios_pramin.rom nvagetbios -s PROM > vbios_prom.rom If fetching the VBIOS from PROM fails with (for example): [root at nisroch tables]# nvagetbios -s PROM >vbios.rom Attempt to extract the vbios from card 0 (nva8) using PROM Invalid signature(0x55aa). You may want to try another retrieval method. [root at nisroch tables]# Then it's possible that we need to fetch it from ACPI instead. The easiest way is probably to reboot with "nouveau.vbios=ACPI" in your kernel options, and then: mount -t debugfs debugfs /sys/kernel/debug cp...

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

...m attaching my dmesg and my vbios in case it helps. Note though that nvagetbios reported a warning when dumping the BIOS: > No extraction method specified (using -s extraction_method). Defaulting to PRAMIN. > Attempt to extract the vbios from card 0 (nve6) using PRAMIN > Invalid signature(0x55aa). You may want to try another retrieval method. Let me know if there?s additional information I could supply. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org...

...n table is a "disk image" as in a "full disk image", as opposed to a device which is unpartitioned and could be used via the "per partition block device" thing in the block driver. It seems that your block device does include the DOS MBR/partition table indicator (the 0x55aa signature at the end of the first sector) and therefore is considered to be a disk image. But perhaps it doesn't actually contain a valid partition table? What does "fdisk -l" report for this device? Does this still happen with pygrub from a newer Xen? I can see that much has changed...

I've been playing with OrcJIT a bit, and from the looks of it I can (like in the previous JIT I suppose?) ask for a function to be re generated. If I've given the address of the function that LLVM gave me to an external party, do "I" need to ensure thread-safety? Or is it safe to ask OrcJIT to re generate code at that address and everything will work magically? I'm

...hdpfx.S b/mbr/isohdpfx.S index 17e1efe..14eca14 100644 --- a/mbr/isohdpfx.S +++ b/mbr/isohdpfx.S @@ -151,7 +151,7 @@ next: /* Check to see if we have EBIOS */ pushw %dx /* drive number */ - movb $0x41, %ah /* %al == 0 already */ + movb $0x41, %ah movw $0x55aa, %bx xorw %cx, %cx xorb %dh, %dh @@ -167,20 +167,22 @@ next: read_sector_cbios: movb $0x42, %ah ; jmp read_common */ movl $0xeb42b4+((read_common-read_sector_cbios-4) << 24), (read_sector_cbios) - jmp 1f + jmp 2f 1: + xor %cx, %cx /* Clear EBIOS flag. */ +2: popw...

On Fri, 2005-09-30 at 23:14, Josh Coalson wrote: > but all samples in buffer[] are 32-bit signed integers in host > order, regardless of the bits-per-sample of the frame. so to get > them down to shorts (assuming they'll fit), do like: > > FLAC__int32 * LChannel = buffer[0]; > short TempSource = (short)LChannel[LPos]; > > instead of > > LChannel =

...ddr 2: self powered, config 1, USB2.0 Hub Controller(0x0224), NEC Corporation(0x050d), rev 1.00 port 1 powered port 2 addr 3: self powered, config 1, DeskJet 970C(0x1004), Hewlett-Packard(0x03f0), rev 1.00 port 3 powered port 4 addr 5: power 100 mA, config 1, USB CompactFlash(0xb000), (0x55aa), rev 5.00 port 2 addr 4: low speed, power 98 mA, config 1, USB-PS/2 Optical Mouse(0xc00e), Logitech(0x046d), rev 11.00 Many thanks, -- Mark A. R. Knight finger: markk@knigma.org Tel: +44 7973 410732 http://www.knigma.org/

...x-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400 > +++ syslinux-6.02/core/fs/diskio_bios.c 2014-02-20 12:15:08.000000000 +0400 > @@ -337,7 +337,7 @@ struct disk *bios_disk_init(void *privat > /* Get EBIOS support */ > ireg.eax.b[1] = 0x41; > ireg.ebx.w[0] = 0x55aa; > - ireg.eflags.b[0] = 0x3; /* CF set */ I don't understand where the removal of that line matches with 'DL register is not set' from the description of this patch. > + ireg.edx.b[0] = devno; > > __intcall(0x13,&ireg,&oreg); > > @@ -353,6 +353,...

...ADJUST_DRIVE pushw %dx /* -14: dl -> drive number */ /* Copy down to 0:0x600 */ movw $0x7c00, %si movw $_start, %di movw $(512/2), %cx rep; movsw ljmpw $0, $next next: /* Check to see if we have EBIOS */ pushw %dx /* drive number */ movb $0x41, %ah /* %al == 0 already */ movw $0x55aa, %bx xorw %cx, %cx xorb %dh, %dh stc int $0x13 jc 1f cmpw $0xaa55, %bx jne 1f andw $1,%cx /* Bit 0 = fixed disk subset */ jz 1f /* We have EBIOS; patch in the following code at read_sector_cbios: movb $0x42, %ah ; jmp read_common */ movl $0xeb42b4+((read_common-read_sector_cbios-4...