search for: fdos

I am planning to release SYSLINUX 2.08 in the next day or so; basically 2.08-pre9 without any further changes. So, I would appreciate any and all testers for this... -hpa

I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD fdoem_8mb.img APPEND floppy pause LABEL infinite_memdisk_loop LINU...

...essage come from UDMA2.SYS or...? > -hpa yes, it comes from UDMA2.SYS, it does a series of initialisation tests (read spead for example, and VDS). I don't know behaviour when booting to MSDOS on harddisk, only Isolinux --> A: and Isolinux --> Memdisk --> Disk image Bernd http://fdos.org/ripcord/beta9sr1/other/misc/Udma2_16.zip output on screen (sourcecode in UDMA2.ASM, line 855 and 736 ??? ) UDMA2 Disk Driver V1.6, 2-Dec-2004. Output overlap is disabled. UltraDMA controller found at I-O address 1050h. Vendor/Device I.D. 8086h/7111h. PCI bus 00h, device 07h, function 1 N...

...ware beta version to the next, so very probably it's a Vmware error (incomplete or buggy emulation). Booting through Smart Boot Manager did not help, unfortunately. 2.xx series works OK with Vmware beta versions, 3.xx series only in older Beta release. Bernd --------------- dumpfile: http://fdos.org/ripcord/beta9sr1/other/misc/vmware-vmx-9704.dmp http://fdos.org/ripcord/beta9sr1/other/misc/badcdrom.zip are 2 ISO files. In VMware 5 build 11888 (Win32) one ISO is working, 1 is failing. Both use the Isolinux bootloader, also used on many Linux distribution cdroms / DVDs. However the working...

...documentation, which tell you to add 'raw' parameter. The diskette image that WinXP creates uses a Windows Millennium kernel. Either the kernel or the bootsector used on it break booting through Memdisk on purpose somehow. I'll try to test if it's only the bootsector, as http://fdos.org/AutoIndex/index?dir=kernel/&file=SYS.dev.COM is able to write a diskette bootsector for WinME. create the WinXP/ME bootdisk, then: SYS.COM A: A: /BOOTONLY if the image works with Memdisk, then it's bootsector to blame. otherwise kernel, in which case you'd better use a Win98 image...

...l to make a bootable CD to flash my bios I get to mkisofs step, but what I get is not what I think I want. I dont understand if I unmount /tmp/floppy how the Mkisofs command of: mkisofs -o bootcd.iso -b FDOEM.144 FDOEM.144 how I get everything in /tmp/floppy Here is what I did: wget http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz gunzip FDOEM.144.gz mkdir /tmp/floppy mount -t vfat -o loop FDOEM.144 /tmp/floppy Copied the flash files to /tmp/floppy umount /tmp/floppy mkisofs -o bootcd.iso -b FDOEM.144 FDOEM.144 Can anyone help? -Jason

...51806-6 pages 61-62 'PC Interrupts' 2nd edition by Ralf Brown & Jim Kyle copyright 1994 1st printing 1993 ISBN: 0-201-62485-0 page 211 Note: this fixes an issue with older FreeDOS kernels that expect this structure to contain valid values. Signed-off-by: Kenneth J. Davis <jeremyd at fdos.org> diff --git a/memdisk/mstructs.h b/memdisk/mstructs.h index fecbff4..0b0dc07 100644 --- a/memdisk/mstructs.h +++ b/memdisk/mstructs.h @@ -121,9 +121,9 @@ typedef union { uint8_t specify1; /* "First specify byte" */ uint8_t specify2; /* "Second spe...

Hi I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy disk image 8440kB size. I've put FreeDOS kernel and bootsector into the floppy. Boot process goes fine with this command: isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy The problems begin when I try to run FreeDOS memory manager emm386 from the floppy image. my config.sys: ... 1?DEVICE=HIMEM.EXE /VERBOSE 1?DEVICE=EMM386.EXE X=C000-C800 NOEMS /VERBOSE ... System hangs (freezes) just after emm386 is loaded, leaving all information abou...

perhaps the boot-from-cdrom code in Smart Boot Manager? Bernd >>> No, since booting from CD-ROM requires that the El Torito part of the BIOS is activated, which it won't be if it didn't boot from CD-ROM in the first place. ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing:

Hello all, I ran across a couple bugs in memdisk concerning hd images the other day. With the attached patch I've been able to successfully boot a 32MB gzipped hd image. (I'll put the image up for a short while at ftp://ftp.io.com/pub/usr/duanev/fdoshd.img.gz) The pxelinux.cfg entry I'm using is: label fdos kernel memdisk append keeppxe initrd=fdoshd.img.gz syslinux/memdisk is great, thanks Peter et. al.! -- Duane Voth duanev at io.com -------------- next part -------------- --- memdisk.asm.orig 2007-08-20 13:02:26....

...o and have tried. 1) install mtools and syslinux-2.08-1 2) install and configure tftp and dhcp a) tftp works fine in tests b) dhcpd works fine and scope references 'filename "/tftpboot/pxelinux.0";' to hand out pxe file 2) download a quick pxe prepared 2.88MB floppy (http://www.fdos.org/ripcord/beta8h02/images/fd288mb.zip) 3) unzip the file (ramdskNT.img,newdos288.img) 4) mount my custom working ghostbootnet.img (mount -t vfat -oloop ghostbootnet.img /mnt/floppy) 5) mount the DOS/vfat version of the 2.88MB floppy to shim in all the files from my old floppy a)Is this last step...

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

I found that if I do not have a local floppy installed and enabled on my client, I will get the error 'Non-system disk' when I try to boot DOS floppy images. NT or Syslinux floppy images boot fine. If I enable the floppy in the BIOS, then it boots the DOS floppies just fine. Is this normal? Is there a workaround? There are MS-DOS images, so perhaps this is an MS-DOS limitation. --

rename the VMlinuz*.* to file 'vmlinuz' (no quotes ofcourse). a bootfloppy leaves me enough diskspace, not 860KB. format as FAT12 (ofcourse), install Syslinux (I do this on Win2K with syslinux.exe A:, win9x: syslinux.com A:) my example: http://www.fdos.org/ripcord/beta9rc4/fdboot.img unfortunately no Linux involved. If I could only show a Knoppix bootfloppy (but it's part of a 700MB download). anyways, the following files should be present (MEMDISK optional) ldlinux.sys 8.104 Systeembestand 09/12/2003 17:05:56 MEMDISK 23.548 Besta...

Hello! I'm trying to boot with a remastered Knoppix 3.4 CD. I burned it with debugging and I get the following output: isolinux: Starting up, DL = 9F isolinux: Loaded spec packet OK, drive = 9F isolinux: Loading main image from LBA = DEADBEF0 isolinux: Sectors to load = D5B7 isolinux: Disk error BE, AX = 42F0, drive 9F A don't understand everything in it and I can't find enough

...ing an image directly through MEMDISK, or booting to A:), and not when using a bootdisk directly or booting a bootdisk directly which has SYSLINUX on it. configuration: bootable cdrom with Isolinux 2.11/2.12pre9 as bootloader. 1.44MB bootdisk with MSDOS.SYS/IO.SYS and the UDMA2 dos driver, http://fdos.org/ripcord/beta9sr1/other/misc/Udma2_16.zip (sourcecode included) DEVICE=UDMA2.SYS SHELL=A:\COMMAND.COM A:\ /D /P Doesn't Isolinux clear everything before a localboot 0x00 ? I guess not, as sometimes the eltorito.sys driver from www.nu2.nu also still loads, which means parts of Eltorito boot...

Hi there, I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... what is the problem can anybody tell me.. Regards, Yogesh

Hi: Thank you very much for creating this very useful program. I downloaded the DOS version because there was a suggestion in th isolinux website. I was not able to detect the cd-rom on my pentium II computer with Award BIOS 4.51 v 1.10. I tried to set the IDE i/o address but I am not sure where to get the i/o address information. I used the i/o address in the Win98 device manager IDE

> I'm having trouble getting memdisk 6.03pre18 to boot large floppies and > wondering whether I'm doing something incorrectly. > > 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz > 2) gunzip FDOEM.144.gz > 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img > 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img > 5) Use following pxelinux.cfg: > > LABEL works > LINUX syslinux/memdisk > INITRD fdoem_8mb.img > APPEND f...

I'm considering the suggestion which was raised before about turning the debugging messages on by default in isolinux, or specifically, not building the non-debugging-messages version in the standard distribution. What do people think (especially distro maintainers?) -hpa