similar to: memdisk locks when loading imz dos image

Sorry for makeing a new post, but I already erased my old mails. In the following I describe my Server-Situation (Sorry for my bad english) * I have a eisfair server http://www.eisfair.org with version 1.6.1 (newest) * I have a ISC-DHCPD 3 Server running * I have a TFTP Server running http://www.kernel.org/pub/software/network/tftp/ * I have Samba installed and a DNS Server is running My

Thank you Shao I have no Linux env to compile the newest snapshot to C32 format. Instead, I downloaded the 3.83pre11 from http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/syslinux-3.83-pr e11.zip and replaced the files on my PXE server. Unluckily, it didn't work. I suspect it is not due to memdisk. I tried to use a combination of pxelinux.0(in 3.73) and memdisk(in 3.82), it did

Hi community, since more than one week I try now to boot my client via PXE. More informations about my equipment: Client: Board ASUS K8V-X SE Amibios with BIOS Revision 1501 (newest) Intel UNDI, PXE-2.0 (build 082) Server: Tyan Tomcat K7M Board with Eisfair 1.6.1 (www.eisfair.org) With exactly the same hardware unattended boots where working for more than one year perfectly without any

Hello, I seemed to have encountered a problem with memdisk that I have seen before when I was playing around with USB device booting at one time. Here's the scenario: Take fx a image of a PC DOS bootable diskette. Boot the image via memdisk. This should boot fine if you use the built-in motherboard ide controllers (ide0,ide1). Now install a PCI IDE controller and put one IDE disk on the

Good day Sean, Could you be interested in trying a MEMDISK from Syslinux 3.83-pre11? You could 'git clone' it or download a snapshot of the source from: http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=snapshot;h=08d95ca 91f87a0c8ec452bb17e837e845738d530 There was a bit of work done with MEMDISK between 3.82 and 3.83-pre11. Let us know. - Shao Miller

Hello all. Again I call upon the greats of this mailing list to help me with an issue related to MEMDISK - notably when paired with various Dell OptiPlex and Latitude systems. The issue presented itself sometime ago and I best dealt with it by remaining with version 3.83 of the SYSLINUX package. But valuing the improved changes fostered by newer versions, I would prefer to move forward with

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

Dear All. I have some problem with combined two data frame. .... I have first data frame .. GPAX THAI MATH SCINCE SOCIAL HEALT ART CAREER LANGUAGE 1227 2.99 3.32 2.50 2.64 3.05 3.60 3.72 3.57 2.62 1704 2.81 2.56 2.48 2.86 3.22 3.19 3.55 3.20 2.51 617 2.18 1.90 1.97 2.06 2.38 3.50 3.54 2.33 1.70 876 2.82 3.14 2.73 2.46 2.71 3.11 3.04 3.24 2.90

So I have a few questions. I have already made the base part of making a windows TFTPD running with memedisk. So that part works, but what I was wondering, if there is a way to some how add an option to the config file. What I have is something like this: label winstall kernel unattended/memdisk append initrd=unattended/winstall.imz That all works great, However, for each image, I have

MEMDISK included in the freshly released Syslinux v3.10 is unfortunately broken. v3.09 works properly. Scenario: Isolinux --> MEMDISK --> FDBOOT.IMG (FreeDOS 360KB diskette image). Then try to access drive B: , which normally is your first diskette drive with driveletter A:. However, in this case MEMDISK occupies A:, and real diskdrive becomes B: Bug: when accessing B:, you're asked

Hi Shao Miller, I found another ISO that doesn't work with MEMDISK-ISO. It is the ISO of the PloP bootmanager. It is a ISO which uses floppy emulation. When I boot it with MEMDISK-ISO (run from Syslinux), my PC instantly reboots. When I extract the floppy image from the ISO and boot this file with MEMDISK, it works fine. Grub4dos iso emulation works fine for this iso. When using Grub4dos

I'm new to memdisk and I wanted to have multiple floppy boot images on my USB key, I installed GRUB2 as the boot loader and have memdisk in /syslinux and my images in /image, I first tried booting normal images, memtest86+ works, my linux kernel work and they boot perfectly. Now using memdisk, I tried booting Spinrite which uses FreeDOS, it booted fine with no argument them frozen at querying

I have an image of a dos floppy that loads the undi driver from 3com and mounts an smb share. This works great with pxelinux(from syslinux) and memdisk I need to make it work with pxegrub so we can use menus. (or figure out a menu system for pxelinux) With pxegrub I use memdisk as the kernel and load the dos image as a ramdisk. The undi driver loads and doesn't complain but, the network is

Thanks for Remko for his help to solve the fractional cylinder problem. But there is the second problem, the boot disk failure (see below << [B]) # but when booting via PXE (pxelinux.cfg/default) ... LABEL t KERNEL memdisk c=2 h=256 s=63 APPEND initrd=disk.img # the following things occur boot: t Loading memdisk Loading disk.img ...................................(16MB)......... Ready.

In our testing, pxelinux and Dos UNDI is much more stable than pxegrub with ten different nic drivers compiled in. The only thing holding us back on using pxelinux for all of our tftp images is the lack of a menu system. We are very close to buying a proprietary software but, I would much rather use an open source type solution. It should be possible to write some comboot code

Hello, I am a *nix newbie I am trying to boot a DOS boot disk using PXE (to Ghost on windows images). We have an existing PXE server which successfully serves out PXElinux and Fedora builds based on that but my floppy disk image with memdisk isn't working I have tried a few different floppy images which people have posted as ones that work for them but I doubt the disk is the problem

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > 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.. > please read Syslinux and Memdisk

For the boot floppy at http://superkeen.com/peacecorpsfiles/FUZOMA14.IMG using memdisk from syslinux version 3.72 boots correctly, but for memdisk versions newer than 3.72 (I tested 3.73, 3.75, 3.85, and 3.86) all hang at boot with the following message: Loading boot sector... booting FreeDOS kernel - SVN (build 2039 OEM:0xfd [compiled Oct 2 2009]) Kernel compatibility 6.22 - BORLANDC ... XMGR,

Hi, I tested this version and it works all right ! Thanks a lot for the quick fix. Do you still want to see the output in order to check everything is OK, or you don't need it ? --------------------- Sylvain Faivre EdifiXio - AIH Team +33 1 56 90 51 24 www.edifixio.com > -----Message d'origine----- > De : H. Peter Anvin [mailto:hpa at zytor.com] > Envoy? : mardi 18 novembre

Hi, I'm trying to build a boot CD following "Bart's way to create bootable CD-Roms (www.nu2.nu)" using isolinux and memdisk. The image I'm trying to boot is built containing IBM's PC-Dos. This works perfectly on 2 of my machines, but the 3rd fails. I get all the 'normal' memdisk messages, finishing with: Loading bootsector... booting... Non-System disk or