similar to: pxelinux+memdisk experience & problem..

Hello, I'm extremely new to Linux and am working on creating a PXE server/menu with PXELINUX and Microsoft DHCP/TFTP. I've gotten it to work great with the exception of one box: the IBM SurePOS 532. If I specify a boot image in my DEFAULT file, it works fine. However when I try to use MENU.C32, it gets stuck at "Trying to Load: pxelinux.cfg/default." Based on TFTP logs, it

Hello syslinuxers I'm stuck with a scientific problem which gives me headaches: I have a laptop (Gateway MX3410) which has a SD memory card reader. Recently an interesting thought crossed my mind: why don't I setup a 2GB SD card as a harddrive and put some rescue tools on it. So I dug on the net and I came across the idea of using memdisk to boot floppy images without the need of a

hi: our company want to use samba3+openldap with singal sign on. we have several branches.people would travel arround head quarter and branches with their notebooks. so we don't have roaming users, but we do have roaming computers. we want to use a single domain for every site, and we want every site keep working even when wan link is broken. my plan below: 1. place

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

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

Hi all, I try to boot an msdos system using pxelinux and memdisk on my PC engines Wrap-2.c card and I have problems with it This is what I see: PXELINUX 3.11 Debian-2006-03-16 Copyright (C) 1994-2005 H. Peter A boot: msdos Loading memdisk.... Loading images/msdos/msd622bd.dosim......................... Ready. dp83815: Setting full-duplex based on negotiated link capability. MEMDISK 3.11

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

Hi, I'm trying to boot Feature Tool 2.08 (free download from http://www.hitachigst.com/hdd/support/download.htm) from a pen drive via memdisk. QEMU can boot the pen drive all right, my ThinkPad can't: Loading ftool208.img.........................ready. MEMDISK 3.53 2007-11-17 Copyright 2001-2007 H. Peter Anvin e820: 0000000000000000 000000000009f000 1 e820: 000000000009f000

My system is hanging up when attempting to boot a bootable floppy disk image Does the following info tell any story as to what's happening? Thanks. LABEL dosdiskimage KERNEL memdisk APPEND keeppxe initrd=dos.img floppy Loading dos.img ............. Ready. MEMDISK 3.11 2005-09-02 e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 2 e820: 00000000000e0000

I am trying to PXE boot an ISO image using ISOLINUX. I am starting small just trying to get anything working but seem to be having problems. I followed the instructions on the isolinux page (http://syslinux.zytor.com/iso.php) but still cannot get it to work. I can get the ISO image to try to load but then it stops at the booting message. Any help would be greatly appreciated. Here is

Hi, I stumbled on a rather odd problem. A brand new HP Compaq dx2200 computer didn't want to boot up pxelinux+memdisk image. The computer just gave "Disk I/O error" and stopped there. Workaround was rather simple... Just attach regular floppy drive to the motherboard and everything started working fine. I tried with older 2.05 (pxelinux+memdisk) and newer 3.31. Both produced

Hi all, I have just pushed out SYSLINUX 3.55-pre5 and 3.60-pre7. I have decided to give them both release candidate status, with the intent of having a simultaneous 3.55 (bug fixes only) and 3.60 (new functionality) release. Please test them out and let me know how they do. -hpa

On Thu, Feb 2, 2017 at 1:26 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Hi all, > > > > I have observed a problem where, under legacy BIOS booting mode on the > > DL360g9, memdisk fails to execute. The same mechanism works fine on the > > DL360g8. The system displays the below on the console and ceases to > > respond and must be

Hi all, I have observed a problem where, under legacy BIOS booting mode on the DL360g9, memdisk fails to execute. The same mechanism works fine on the DL360g8. The system displays the below on the console and ceases to respond and must be power cycled. Updating the firmware didn't help. There didn't appear to be any similar issues on the mailing list unless I missed them. Wondering if

I often boot DOS using MEMDISK and 33MB HD images for remote flashing. After my flash I need to activate the NIC and send a signal. Currently I use different packet drivers for different NICs, but this link below looks like a universal solution: http://www.emboot.com/products_UniversalPacketDriver.htm Does any thing else like this exist that is open source or freely available and freely

Hi, I am aware that it is impossible to netboot ISO files through pxelinux/memdisk and that there are multiple reasons for not even attempting it (like the operating system which will try to access a physical optical drive through its own drivers anyway, BIOS issues etc.). When people ask questions regarding ISO support in pxelinux/memdisk, they're mostly told to convert the ISO into a

Hi I am using PXELinux to boot BartPE and some other application and it works fine. There are some other Boot application which I am using 3COM MBAUTIL PXE.mnu and floppy images. I have problem chaining from pxelinux.0 to 3com pxe.0 (pxe.mnu). Consider: BIOS->(DHCP-TFTP)->pxelinux.0 works fine. BIOS->(DHCP-TFTP)->3COM pxe.mnu works fine, the menu appears and I can choose a floppy

I apologize for the long delay in testing this. I can only reproduce the problem on fancy new laptops, and those do not stay in my hands for very long. As you may recall, certain floppyless laptops have a BIOS bug which prevented them from working with MEMDISK. Around a month ago, Robert Wruck contributed workaround patches, and hpa included a modified version of them in 2.07-pre1. He asked

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

Hi.. Well i too am having the same memdisk decompression error that states "ran out of input data" since the first when memdisk started supporting booting compressed images !!! I posted this several times but alwsys cudlnt understand whatthe admins want (like what inof they need to debug the problem)... I even offered to send screenshots of the screen but it was refused !!! The