search for: int13

I tried to use memdisk 2.06 to boot a floppy image on my notebook which doesn't have a floppy drive. The boot failed, because the bootstrap code tried to reset the floppy drive (int13, ah=00). Memdisk passes reset calls on to the original int13 handler, which returns failure, because there is no floppy drive to reset (#1). Also i noted that some boot records (notably some created by win9x) use the extended int13 calls (ah=4x) without checking for presence (ah=41). memdisk do...

...g worked. Here is the output: Ramdisk at 0xdbef0000, length 0x002d0000 Disk is floppy 0, 2880K C/H/S = 80/2/36, EDD off Using raw access to high memory Total size needed = 2454 bytes, allocating 3K Old dos memory at 0x9d800 (map says 0x9d800), loading at 0x9cc00 1588: 0xffff 15E801: 0x3c00 0x7cbe INT13 08: Success, count = 0, BPT = 0000:0000 old: int13 = e320aaef int15 = e3200fab new: int13 = 9cc0000a int15 = 9cc0037e Loading boot sector... booting... Starting MS-DOS After that the computer completely freezes, and has to be powered down. Does anybody know of a way around this? Christian

...command line: initrd=freedos.img BOOT_IMAGE=memdisk.zi Disk is floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1494 bytes, allocating 2K Old dos memory at 0x9f000 (map says 0x9f000), loading at 0x9e800 1588: 0xffff 15E801: 0x3c00 0x1edf INT 13 08: Success, count = 1, BPT = f000:8ccd old: int13 = f00066ea int15 = f00066ef new: int13 = 9e800008 int15 = 9e800272 Loading boot sector... booting... FreeDOS kernel version 1.1.32a (Building 2032a) [Sep 24 2003 21:58:48] Kernel compatibility 7.10 - WATCOMC - FAT32 support (C) Copyright 1995-2003 Pasquale J. Villani and The FreeDOS Project...

...rd=../images/windows/winpe_x86.iso BOOT_IMAGE=../memdisk Disk is hard disk 0, 170496 K C/H/S = 340992/1/1 Total size needed = 2091 bytes, allocating 3K Old dos memory at 0x9bc00 (map says 09c00), loading at 09b00 1588: 0xffff 15E801: 03c00 0x71b9 INT 13 08: Success, count = 1, BPT = 0000:0000 old: int13 = f000827c int15 = f000cebe new: int13 = 9b000008 int15 = 9b000290 Loading boot sector... booting... I burned the WinPE ISO onto a CD and was able to boot the server fine. I'm using syslinux.x86_64 3.11-4 that came with RHEL 5.7 -- Greg

...e system does not have an HD. Has any seen this? Is there a solution? memdisk output: Disk is hard disk, 9216 K, C/H/S = 9/64/32 Total size needed = 2063 bytes, allocating 3K Old dos memory at 0x9dc00 (map says 0x9dc00), loading at 0x9d000 INT 13 08: Failure, assuming this is the only driveold: int13 = f000799a int15 = f000f859 new: int13 = 9d000008 int15 = 9d000286 Loading boot sector... booting... Non-System disk or disk error Replace and press any key when ready

...32-bit mode with a flat memory layout. > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > >> > > > Well, not exactly. Initialization is done in 32bit, but disk > > > reads/writes are done in 16bit mode since it should work from int13 > > > interrupt handler. The only way I know to access MMIO bars from 16 bit > > > is to use SMM which we do not have in KVM. > > > > Ah, if it's just the dataplane operations then there's another solution. > > > > We can introduce a virtqueue fla...

...32-bit mode with a flat memory layout. > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > >> > > > Well, not exactly. Initialization is done in 32bit, but disk > > > reads/writes are done in 16bit mode since it should work from int13 > > > interrupt handler. The only way I know to access MMIO bars from 16 bit > > > is to use SMM which we do not have in KVM. > > > > Ah, if it's just the dataplane operations then there's another solution. > > > > We can introduce a virtqueue fla...

...initrd=images/msdos/msd622bd.dosim BOOT_IMAGE=memdisk Disk is floppy 0, 1440 K, C/H/S = 80/2/18 Total size needed = 1899 bytes, allocating 2K Old dos memory at 0x9fc00 (map says 0xa0000), loading at 0x9f400 1588: 0xffff 15E801: 0x3c00 0x06d6 INT 13 08: Failure, assuming this is the only drive old: int13 = f000ac5e int15 = f000a60a new: int13 = 9f400008 int15 = 9f400290 Loading boot sector... booting... from then on nothing happens. Can this be a BIOS problem (PC engines uses its own TiniBios) or what else may I try? Thanks Uli

...itle NetBSD rescue disk (not yet functional) kernel /boot/memdisk initrd=/boot/rescue-tiny.fs ------------------------------------------- note: following outputs copied by hand, hope without errors ------------ sample output, netbsd: ------- [...] INT 13 08: Success, count = 2 BPT = 0000:0000 old: int13 = ec6a40bd int15 = f000f859 new: int13 = 9f000008 int15 = 9f00027c Loading boot sectore... booting... >> NetBSD/i386 BIOS Boot, Revision 2.13 >> (autobuild at tgm.netbsd.org, Tue Feb 10 21:25:10 UTC 2004) >> Memory: 636/127776 k Press return to boot now, any other key for boo...

..., EDD on, rw Using safe INT 15h access to high memory Code 1656, meminfo 276, cmdline 66, stack 512 Total size needed = 2510 bytes, allocating 3K Old dos memory at 0x9f800 (map says 0xa0000), loading at 0x9ec00 1588: 0xffff 15E801: 0x3c00 0x07dea INT 13 08: Success, count = 1, BPT = 0000:0000 old: int13 = f0005c6f int15 = f000f859 int1e = f000efc7 new: int13 = 9ec0000a int15 = 9ec0038c int1e = f000efc7 Loading boot sector... booting... Starting PC DOS... Though, when using any post-3.83 version of MEMDISK, the same disk image results in an unfavorable state. Notably, after booting the image,...

...d the system (German message: 'Kein System oder Laufwerksfehler', don't know the english one from the boot sector). On a different system (this one has a floppy controller!) it works. With a different bootdisk (Win98) both work, too. Both systems tell me: [..] INT 13 08 failure old: int13 = nnnn int15 = mmmm new: int13 = oooo int15 = pppp [further messages from boot sector and dos] Maybe it's also a bios issue, since the controllerless machine is only used for Netbsd (Network Station Manager), Linux and OS/2 (Workspace on Demand), it's an IBM Networkstation 2800 with toke...

I need some help with the following: My system hangs while booting from a CD using?SysLinux?(2.08).? I think that the?driver?hooks into the INT13 and INT15 handlers, writing their new handler hook into the Extended BIOS Data Area (EBDA) used by Phoenix BIOS for BIOS data information.? This area is?used and modified during legacy USB SMI's. I think that the hang happens because the new handler hook for INT13 or INT15 gets corrupted after...

...SK 2.08 command line : BOOT_IMAGE=memdisk initrd=sussboot.img Disk is floppy, 1440 K, C/H/S = 80/2/18 Total size needed 1359 bytes, allocating 2K Old dos memory at 0xa0c00 (map says 0xa0c00), loading at 0xa0400 1588: 0x0000 15e801: 0x0000 0x0000 INT 13 08 : Success, count = 1, BPT =f000:8487 old: int13 = f000ec59 int15 = f000f859 new: int13 = a0400008 int15 = a0400272 Loading boot sector... And hangs at this point. Any ideas what I may be doing wrong? Thanks Rob Keeling -- I love deadlines. I love the whooshing noise they make as they go by. - Douglas Adams

...hat we are trying to do, the windows installer can load driver updates from a memdisk image. The problem is that it then switches to protected mode and tries to copy the driver from the disk. This, of course, fails because at that point windows is using its own protected mode floppy handler and not int13. But, there is a workaround. If the floppy is B:, windows will treat the floppy specially, as a "virtual" floppy, loading the entire image into memory before switching to protected mode. This means that driver updates would be possible using memdisk. The approach is to lay down syslinux...

...0x00168000: ok command line initrd=dos.img BOOT_IMAGE=memdisk Disk is floppy 0,1440 K, C/H/S = 80/2/18 Total size needed = 1905 bytes, allocating 2K Old dos memory at 0x9fc00 (map says 0x9fc00), loading at 0x9f400 1588: 0xffff 15E801: 0x3c00 0x08e8 INT 13 08: Sucess, count = 1, BPT = e086:43af old: int13 = f000eed2 int15 = f000f859 new: int13 = 9f400008 int15 = 9f400290 Loading boot sector ... booting... Starting.. (at this point the system hangs here)

...mand line: initrd=ftool208.img BOOT_IMAGE=memdisk Disk is floppy 0, 1440 K, C/H/S = 80/2/18, EDD off Total size needed = 2356 bytes, allocating 3K Old dos memory at 0x9f000 (map says 0x9f000), loading at 0x9e400 1588: 0xffff 15E801: 0x3c00 0x1e57 INT 13 08: Success, count = 0, BPT = 0000:0000 old: int13 = f00067c1 int15 = f00067c6 new: int13 = 9e40000a int15 = 9e40037c Loading boot sector... booting... Starting PC DOS... And the cursor sits here blinking until I press Ctrl-Alt-Del. I tried version 3.08 and 3.54-pre1 with the same result. raw, bigraw, safeint or edd didn't help either. Wh...

...? After all, any hard drive now a days cannot be represented under CHS as having less than 1024 cylinders (as they are all beyond 8G in size) and those drive boot fine. So is this warning intended to people which may have to boot the hybrid ISO under old BIOS which doesn't support the extended INT13, forcing isohdpfx.S to use CHS instead of LBA when reading isolinux.bin? And possibly (I didn't had time yet to read this code section) the same for isolinux.asm when it attempt to read the configuration files and the kernel. And would this exhibit an issue only if any of these files (isolinux...

...gt; > > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > > > >> > > > > > Well, not exactly. Initialization is done in 32bit, but disk > > > > > reads/writes are done in 16bit mode since it should work from int13 > > > > > interrupt handler. The only way I know to access MMIO bars from 16 bit > > > > > is to use SMM which we do not have in KVM. > > > > > > > > Ah, if it's just the dataplane operations then there's another solution. > > &gt...

...gt; > > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > > > >> > > > > > Well, not exactly. Initialization is done in 32bit, but disk > > > > > reads/writes are done in 16bit mode since it should work from int13 > > > > > interrupt handler. The only way I know to access MMIO bars from 16 bit > > > > > is to use SMM which we do not have in KVM. > > > > > > > > Ah, if it's just the dataplane operations then there's another solution. > > &gt...

...ne: initrd=images/boot_flp.img floppy=0 BOOT_IMAGE=memdisk Disk is floppy 0, 1440 K, C/H/S = 80/2/18 Total size needed = 2008 bytes, allocating 2K Old dos memory at 0x9dc00 (map says 0x9dc00), loading at 0x9d400 1588: 0xffff 15E801: 0x3c00 0x1ada INT 13 08: Success, count = 0, BPT = 0000:0000 old: int13 = e8a87ab8 int15 = f000f859 new: int13 = 9d400008 int15 = 92400290 Loading boot sector... booting... Starting MS-DOS... and that's all folks, it never goes any further than this... Another example, the bootit floppy image also starts booting but it stops on a black screen with the mouse cu...