similar to: memdisk 3.62 problem / Loading boot sector... booting :(

I am using the following simple menu and have noticed that items at the bottom are dropping off. I seem to be limited to 12 items. Is there a limit to how many items can be on the simple menu? default pxelinux.cfg/menu.c32 prompt 0 MENU TITLE UWSP PXE Boot Menu # TIMEOUT 200 LABEL bartpe MENU LABEL Build 12 KERNEL /STARTROM.0 APPEND keeppxe LABEL 11dnet MENU LABEL Build 11DNET beta

I search for long time to make works ghost floppy image "out of the box" with syslinux without success. The only solution i found is to modify the the file generated by ghost boot wizard. the ghost boot wizard generate a "file.sys" i made (with the help of irc helper) a script to modify this file : you have to put the file.sys without extension as parameter #!/bin/bash

Hello everybody, I want to boot my HP x86 PCs with a Norton Ghost 12 boot disk image via PXE. I followed all the steps but I have still the same message and the booted computer hangs always. 0- I created the boot image. 1- A folder named tftpboot and tpftpboot\pxelinux.cfg created. 2- The pxelinux.0 copied in tftpboot folder. 3- memdisk copied in tftpboot folder. 4- the image file (norton.iso)

Does someone know where I could get my hands on an ima that's larger than 2.88meg... I use winimage for all my ima's and stuff but i'm having trouble configuring a custom size. If anyone has a large ima I could utilize that would be great, preferably one fitting this memdisk supported size: 3,932,160 bytes (3840K) c=80 h=2 s=48 3.5" DSED (extended) If not instructions on making

Hi, I'm trying to get the above working, without success so far: UNDIS.DOS refuses to load with an invalid NDIS stack message (from memory). keeppxe has some effect: it reduces the available conventional memory by 140 kbytes or so... still, the packet driver doesn't seem to find the interface. Does anybody have a working setup I could look at? -- Thanks, Feri.

Hello. We've been using a very old version of SYS-/PXELINUX, 3.36, going by the proven "if it works, don't break it" philosophy. We us it mostly to load floppy disk images to kick off OS installations. Unfortunately we've recently had some PXE menu problems (USB keyboard stopped working) for a certain Fujitsu PC model, and decided to upgrade to the latest version, i e 3.84.

I have many hp laptops that boot msdos with memdisk + pxelinux perfectly. However, I recently have the need to usb boot msdos with syslinux. And memdisk. When the dos Image loads I get "loading bootsector..." and then it halts. Sometimes I can get "starting ms-dos" but freezes as well. I'm trying to boot clean msdos floppy image created with winimage. I'm using

Hi, It is becoming a bad habit for big OEM vendors to sell computers & servers without floppy drives. Unfortunatly both Windows and Linux (RedHat) need a floppy drive to load storage drivers etc. during installation. This is what I was thinking: Use ISOLINUX and MEMDISK to load a floppy image of a driver disk into memory as a viritual floppy drive "A:"/"/dev/fda" And then

I am using memdisk to remotely flash the BIOS and other firmware. It works well for most flash programs. After the flash I need to initialize the NIC to send a signal to my management server that the flash is complete. I am curious as to how others have solved this problem. Thanks.

I've got $SUBJ almost working except for the DOS bit where the CD needs to be read. My pxe config: label Firmware menu label Update IPMI firmware kernel memdisk append keeppxe raw iso initrd=<isofile> The ISO is about 400Mb, and works fine when I boot it from an actual CDROM drive. It also boots fine over PXE, I can see FreeDOS being booted up etc. The problem is - once

Using PXELINUX and MEMDISK I started a MS-DOS-Diskimage. How can I get the DHCP-Options or BOOTP-Tags from within MS-DOS?? (Like bppatch from 3com.) Thanks! _______________________________________________________________________ Jetzt neu! Sch?tzen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220

HI: i just trying memdisk that comes with syslinux 3.35. i try to load a dos image, which contains ghost verison 8.3 and ghost version 11. both version of ghost hangs when start-up. memdisk that comes with 3.40 pre is ok. and many earlier versions is ok too. i try some parameter like "safeint","raw". but none work. i use memdisk with pxelinux, below is part of my

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

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

On Wed 5/5/2010 3:28 AM Miller, Shao wrote, ---------------------------------------------- Good day again Matthew, As per (c=80) * (h=2) * (s=48) * (sect_size=512) = 3,932,160 bytes = 7,680 sectors: For Windows, you might enjoy: - "DD for Windows" by John Newbigin and chrysocome[1] - "ImDisk Virtual Disk Driver" and "Zero and Random Device Driver" by Olof

PXELINUX has stopped recognizing the keeppxe option on the kernel command line. Here is a patch to make it work again. With COM32, it is no longer possible to use preprocessor directives to determine the SYSLINUX variant. The code inside the #if will never be compiled. So, I changed it to use syslinux_filesystem() to determine the variant. Also, I moved the relevant code from

I am trying to acheve pxe booting of a image of barts boot disk (www.nu2.nu). I have managed to get LTSP booting via pxelinux, so I know my dhcp/tftp servers are ok. However when I try to boot memdisk with either a stock suselinux boot image file (taken from SuSE 9.1) or my dos disk (created by dd if=/dev/fd0 of=/imagefile) I get output like MEMDISK 2.08 command line : BOOT_IMAGE=memdisk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am having trouble with memdisk not freeing all all memory - mem /c shows only about 570K memory (and I happen to need that extra memory in DOS ... :-( ). I found some (rather old) information about this issue. It seems as if this is just what is happening to me: http://syslinux.zytor.com/archives/2003-June/002213.html

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

We're having an issue with connecting a Cisco ITS installation to * such that DTMF tones are passed to *. DTMF tones aren't passed to voicemail or to any of the interfaces behind *. On the Cisco Side: dial-peer voice 8 voip destination-pattern 9999$ session protocol sipv2 session target ipv4:172.16.1.249 session transport udp dtmf-relay rtp-nte codec g711ulaw no vad We have also