search for: f000f859

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

...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 boot menu booting hd0a:netbsd...

...T 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, the system's SATA drive i...

.....", cursor at beginning of next line. There is no difference on the values displayed before success or lockup ... Old dos memory at 0x9fc00 (map says 0xa0000), loading at 0x9f400 1588: 0xffff 15e801 0x3c000 0xee7 Int 1308 Success, count=0, BPT = 0000:0000 old: int 13 = f000b6ac int15=f000f859 new: int 13 = 9f400008 int15 =9f400272 loading boot sector ... booting ... _<=cursor blinking here, lockup or success Any ideas? cu, Knut Petersen

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

...ne 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)

...mages/c201.img BOOT_IMAGE=memdisk Disk is floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1491 bytes, allocating 2K Old dos memory at 0x9f000 (map says 0x9f400), loading at 0x9e800 1588: 0xffff 15E801: 0x3c00 0x3e66 INT 13 08: Success, count = 1, BPT = f000:98a9 old: init13 = f0008590 init15 = f000f859 new: init13 = 9e800008 init15 = 9e80027c Loading boot sector... booting... Starting Windows 98... Windows is bypassing your startup files. Microsoft(R) Windows 98 (C)Copyright Microsoft Corp 1981-1999 A:\> Any idea's why this is not booting my proper image? Here is my configuration...

....img BOOT_IMAGE=memdisk Disk is hard disk, 20160 K, C/H/S = 40/16/63 Total size needed = 1425 bytes, allocating 2k Old dos memory at 0x9fc00 (map says 0xa0000), loading at 0x9f400 1588: 0xffff 15E801: 0x3c00 0x0dc3 INT 13 08: Failure, assuming this is the only drive old int 13: f000ec59 int 15: f000f859 new int 13: 9f400008 int 15: 9f40027c Loading boot sector... booting... --- After the last message, the system hangs. Any clues? Is this because I'm using a hard disk image? Should I be using a large floppy image? Could this be an IDE controller issue? I do have a floppy drive on my syste...

....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 cursor on it. Interesting, the...

...Disk is > floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1491 bytes, > allocating 2K Old dos memory at 0x9f000 (map says 0x9f400), loading at > 0x9e800 > 1588: 0xffff 15E801: 0x3c00 0x3e66 > INT 13 08: Success, count = 1, BPT = f000:98a9 > old: init13 = f0008590 init15 = f000f859 > new: init13 = 9e800008 init15 = 9e80027c Loading boot sector... > booting... > Starting Windows 98... > My guess: Someone, or something is pressing F5 right here. This is why MS-DOS/Win98 is bypassing the startup files. > > Windows is bypassing your startup files. > >...

...sk initrd=testcd.iso Disk is hard disk 0, 1822 K, C/H/S = 3644/1/1, EDD on Total size needed = 2353 allocating 3K Old dos memory at 0x9d000 (map says 0x9d000), loading at 0x9c400 1588: 0xffff 15E801: 0x3c00 0x3edc INT 13 08: Success, count = 1, BPT = 0000:0000 int13 = e000d390 int15 = f000f859 new: int13 = 9c400008 int15 = 9c400376 Loading boot sector... booting... It just hangs here... Note that I am able to boot regular diskette and hard drive images on this same system but I really need to figure out how to boot ISO images. Thanks in advance for the help. Mike...

It appears that the 3.74 completely broke the "keeppxe" directive -- not due to the command-line parser, but due to mishandling of the flag later. I consider this to be severe enough to do a short-cycle 3.75. As a result, I would like help with: a) are there any other bugs that snuck through? b) once I have a 3.75-pre1, I would really appreciate help testing it. The goal is to have

...info 276, cmdline 66, stack 512 Total size needed = 2598 bytes, allocating 3K Old dos memory at 0x9fc00 (map says 0xa0000), loading at 0x9f000 1588: 0xffff 15E801: 0x3c00 0x7dc3 INT 13 08: Success, count = 1, BPT = 0000:0000 Drive probing gives drive shift limit: 0x82 old: int13 = f0005c6f int15 = f000f859 int1e = f000efc7 new: int13 = 9f00000a int15 = 9f0003ba int1e = f000efc7 Loading boot sector... press any key to boot... No 'lost drive' message was reported and the internal hard drive is now visible to the booted environment. I also tried (only on the OptiPlex GX280, at this time) this d...

...xegiga_av.img BOOT_IMAGE=memdisk Disk is floppy 0, 1440 K, C/H/S = 80/2/18 Total size needed = 1946 bytes, allocating 2K Old dos memory at 0x9ec00 (map says 0x9f800), loading at 0x9e400 1588: 0xffff 15E801: 0x3c00 0x1ad6 INT 13 08: Success, count = 1, BPT = f000:99a9 old: int13 = f0007f80 int15 = f000f859 new: int13 = 9e400008 int15 = 9e400290 Loading boot sector... booting... Disk I/O error Replace the disk, and then press any key Now later at home I realized that I could have taken logs with floppy attached to see if there were any differences but I didn't remember to do that. -- Anssi...

...OT_IMAGE=unattended/memdisk Disk is floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1977 bytes, allocating 2K Old dos memory at 0x9f800 (map says 0x9fc00), loading at 0x9f000 1588: 0xffff 15E801: 0x3c00 0x1ee7 INT 13 08: Success, count = 1, BPT = f000:79f9 Old: int13 = f00030e4 int15= f000f859 New: int 13=9f000008 int15=9f000286 Loading boot sector.booting.. Starting.. And here my client hangs although the floppy disc was working, but the image is always ending with this message. Is there anybody who could help me in this matter ? If I need a hard disk image how do I do...

...168000 command line: initrd=dos6 BOOT_IMAGE=memdisk Disk is floppy, 1440K, C/H/S = 80/2/18 Total size nedeed = 1300 bytes Old dos memory at 0x9fc00 (map says 0xa0000), loading at 0x9f400 1588: 0xf5c0 15E801 0x3c00 0x02e7 INT 13 08: Success, count = 1, BPT = 0000:0000 old: int 13 = f0009a64 int 15 = f000f859 new: int 13 = 9f400008 int 15 = 9f40022c Loading boot sector ... booting ... Non-System disk or disk error Replace and press any key when ready Florin

>+ booting floppy34.fs image from the CD works correctly (no ISOLinux, in >built BIOS emulates the floppy) Hi, have you tried the following (Isolinux direct emulation): KERNEL 34FS.IMG should function the same as if direct 1.44MB eltorito emulation was used. but using MEMDISK it fails? KERNEL MEMDISK APPEND INITRD=34FS.IMG that's all I can come up with .

...initrd=ghost.imz 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)

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,

I have been using pxelinux for quite a while to automagically build linux boxes with great success. Thanks to everyone involved! Now, I am trying to download a floppy image and get that to boot. My conf file looks like: default sir4 label sir4 kernel ia32/memdisk append initrd=ia32/sir4/floppy.img Everything starts off fine. pxelinux loads I see it get the conf file. gets memdisk