similar to: Booting a 135MB Iso file with syslinux fails - version3.85

Hi, i'm trying to boot an 135mb acronis iso image with syslinux but have no luck, client gets stuck[1] a few seconds after selecting the image - i used linux memdisk initrd acronis/acronis_home_2010_multi.iso append iso tftpd-log shows: Mar 25 14:45:15 smbsrv in.tftpd[18837]: RRQ from 192.168.0.102 filename pxelinux.cfg/default Mar 25 14:45:15 smbsrv in.tftpd[18838]: RRQ from 192.168.0.102

Hi All, I am still having troubling with PXE. Thanks for replying Shao.I did follow ur suggestions and my results have improved a bit.From Ethereal and TCPdump, I can see that the client sucessfully dowloads the file pxelinux.0 from the server but stops at this point. here is the output of tcpdump tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:05:41.966864 IP

From 43e0635d7d90f65055d1f49d998974041315f4fc Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Fri, 11 Dec 2009 01:26:59 +0000 Subject: [PATCH] memdisk: Fix "might be used uninitialized" warnings The checksum_buf function was providing an incorrect checksum on at least one build. Signed-off-by: Shao Miller <shao.miller at yrdsb.edu.on.ca>

The previous MEMDISK El Torito code merge did not actually work without this. Signed-off-by: Shao Miller <shao.miller at yrdsb.edu.on.ca> --- memdisk/setup.c | 17 +++++++++-------- 1 files changed, 9 insertions(+), 8 deletions(-) diff --git a/memdisk/setup.c b/memdisk/setup.c index 40f3f8c..5a45f39 100644 --- a/memdisk/setup.c +++ b/memdisk/setup.c @@ -338,6 +338,7 @@ struct geometry

After 64 prereleases, 626 commits, 52,742 lines of changes, and tons of work by many, many people, Syslinux 4.00 is now officially released. Syslinux 4.00 is the first of a set of major code restructuring releases. The single biggest new features are btrfs and ext4 support, and support for disks larger than 2 TiB. Huge thanks to: - Intel, for sponsoring mine, Alek Du's and Feng Tang's

Syslinux 3.84 has been released. This is a mixed minor new features/minor bug fixes release. Changes in 3.84: * SYSLINUX: make the DOS installer work for MS-DOS 7.x/8.x (Win9x/ME) again. * HDT: updated to version 0.3.6 (numerous changes.) * mboot.c32: now supports video mode setting if requested by the image. * MEMDISK: Fix floppy images of

Let's try that patch again... Here's a better one, instead. I tested with: qemu -kernel memdisk -initrd memdsk.hdd -append pause -hda one.hdd -hdb two.hdd -hdc three.hdd -hdd four.hdd On each HDD image, I had a file (and volume label) to identify the HDD with the DOS 'dir' command. The expected behaviour was met; I wound up with DOS drive letters: C: memdsk.hdd D: one.hdd E:

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

Changes in 4.05: * HDT updated, and now supports uploading data to a TFTP server. * ISOLINUX: remove the .img file support; it has been broken on virtually all systems since the beginning, and has been totally broken since 4.00 at least. Use MEMDISK instead. * chain.c32: Support chaining ReactOS' FreeLdr (Shao Miller) * isohybrid:

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

Two additions to MEMDISK to support OS drivers. The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines") is a means for an OS driver to follow a chain of INT 13h hooks, examining the hooks'' vendors and assuming responsibility for hook functionality along the way. For MEMDISK, we guarantee an additional field which holds the physical address for the

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line:

After way too long, a new production release of Syslinux is finally available. Syslinux 4.04 is primarily a bug fix release, but with some new features. Changes in 4.04: * PXELINUX: Fix handling of unqualified DNS names. * PXELINUX: Fix timer bug when PXELINUX might be unloaded (Gene Cumm). * core/writedec.inc: Fix duplicate declaration and overflow

From 8be8951015673d6279d7d49b0138645194317dc2 Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Wed, 9 Dec 2009 19:11:38 +0000 Subject: [PATCH] doc: document mBFT and "safe hook" --- doc/memdisk.txt | 40 ++++++++++++++++++++++++++++++++++++++++ 1 files changed, 40 insertions(+), 0 deletions(-) diff --git a/doc/memdisk.txt b/doc/memdisk.txt

For anyone wanting to boot an .ISO with MEMDISK: http://git.etherboot.org/?p=people/andytim/syslinux.git;a=shortlog;h=ref s/heads/memdisk-iso NOTE: Your protected-mode OS (Windows, Linux, *BSD) booted from such a MEMDISK will not magically find the MEMDISK image in RAM and use it as a CD without a MEMDISK driver. There are currently 0 MEMDISK drivers in the field, but that might change someday.

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

Good day Gert Hulselmans, You had reported to me at one point that MEMDISK -> .ISO -> ISOLINUX had failed under certain circumstances. I just noticed with a MEMDISK 3.86 that specifying the "iso" option on the command-line actually resulted in the .ISO getting BIOS drive number 0xFF. I had to specify "iso harddisk=224 pause" to confirm that it resulted in 0xE0 (hd96).

>From 8fb8c285e69c0f4cde28061019a8e399641d5ef1 Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sun, 22 Mar 2009 00:27:56 -0400 Subject: [PATCH] [memdisk] Additional comments in memdisk.inc and postprocess.pl Just a sprinkling of comments adding further description to the code. --- memdisk/memdisk.inc | 34 +++++++++++++++++++++-------------

hi everyone. i have a small tftp/pxe server i use to install different OS's without having to burn countless cd's (not all the machines i work on support usb boot). until recently, these were mostly linux/bsd-based systems (plus freedos). recently i've been trying to deploy a network-based windows installation, by booting windows pe (3.1, the one based on win7) with memdisk and from

On Jun 26, 2014 4:20 AM, "Ross, Matt" <m.g.ross at herts.ac.uk> wrote: > > Hello, > > I am running Debian testing x64 and have manually installed the 6.03pre17 deb packages for extlinux, pxelinux, syslinux, syslinux-common, syslinux-stuff and syslinux-utils. > Loading memdisk... ok > Loading http://ourserver.ourdomain.com/Software/Util1.iso...failed: No such file