similar to: [PATCH][git-pull] memdisk/setup.c: Limit available RAM hack

On Sun, Feb 6, 2011 at 07:49, Robert McLay <the80sphreak at yahoo.co.uk> wrote: > > ?Hi Gene, > > ?Not sure if you wanted this on/off list, feel free to forward to list > ?if you do. > >> Adding "int15maxres=#" will affect the memory calls that MEMDISK hooks >> into.? Specify the desired limit in bytes (ie "int15maxres=268435456" >> for

git://git.zytor.com/users/genec/syslinux.git Branch memdisk-maxmem-for-hpa The goal of the changes was to process a "mem=" parameter (ie "mem=128M" or "mem=134217728"; same value) and alter the memory map that MEMDISK returns in INT15h AXe820h by changing any type 1 (available) ranges above the "mem=" value to type 2 (reserved) and splitting a type 1 that

Hi, I am trying to use MEMDISK from the GRUB boot loader, and gets stuck on the memory detection. MEMDISK reports dos_mem = 0 low_mem = 0 high_mem = 0

When you add "quiet" to the append line, Syslinux doesn't display the file reading progress anymore. When you use this option to boot an image with MEMDISK, you still get a lot of text. ========================== LABEL mydisk LINUX memdisk INITRD mydisk.img APPEND raw quiet ========================== The following patch makes MEMDISK silent when the quiet keyword is passed to the

git://git.zytor.com/users/genec/syslinux.git Branch memdiskdbg-for-sha0 This starts with adding another check in two of the disk probes (by Shao; Thank you), expands the debug output, adds an additional check in the third probe and expands/reorders the debug output. At this time, it appears to resolve the MEMDISK issues that Jason Vasquez first noticed. The additional check in the third probe

Here's some reminders for various branches that are pending. All branches are at my public repo at git://git.zytor.com/users/genec/syslinux.git ( http://git.zytor.com/?p=users/genec/syslinux.git;a=summary ) HPA, I'd appreciate a response in the direction of a status like on hold, under review, denied or to be completed soon. Branch win64-mingw32-ubuntu-for-hpa adds more prefixes in

On Mon, Feb 7, 2011 at 07:03, Robert McLay <the80sphreak at yahoo.co.uk> wrote: > > Hi Gene, > >> label cesg >> ?menu label ^CESG Software (GeneC Memdisk Hack) >> ?kernel images/memdisk-res2 >> ?append initrd=images/cesg.img mem=268435456 > > ?That worked! ?The box had 1536MB RAM and I forced it down to 256MB and > ?all is well. ?I've spent most

(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, The method to boot an ISO using memdisk, memdiskfind and phram described in the wiki looks very promising to me. So, I looked into the sources trying to understand, how this works. Up to now, I could not find out how the memory containing the ISO image is preserved from being overwritten by the Linux kernel. Probably I'm missing something, could you please help me? Best regards, Bodo

I've changed my repo from git://github.com/geneC1/syslinux.git to git://github.com/geneC/syslinux.git and still have several git-pull requests pending. Change from native compiled C application to Perl to remove the platform association: git://github.com/geneC/syslinux.git diag-geodsp-perl-for-hpa Add AsciiDoc documentation and minor fixes to cptime.c32 and prdhcp.c32:

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: ...

>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 +++++++++++++++++++++-------------

git://git.zytor.com/users/genec/syslinux.git Branch diag-geodsp-for-hpa http://git.zytor.com/?p=users/genec/syslinux.git;a=shortlog;h=refs/heads/diag-geodsp-for-hpa Updates to diag/geodsp/Makefile and an additional variable (XZ) in mk/syslinux.mk. This removes unnecessary parts and makes the recipes more generic by using make variables. -- -Gene

The following changes since commit c647008831aed653e54c4c8470e3a9db5d0a140a: efi/: Fix displayed version; add DATE (2013-10-20 10:45:53 -0400) are available in the git repository at: git://github.com/geneC/syslinux.git firmware for you to fetch changes up to c647008831aed653e54c4c8470e3a9db5d0a140a: efi/: Fix displayed version; add DATE (2013-10-20 10:45:53 -0400)

Hi guys, This may be a stupid question... I was trying to get a machine to boot with PXE. Everything supportive is setup, the DNS/DHCP works fine, TFTP is also handing over pxelinux.0 and config files correctly. The problem happens at: label xxx kernel memdisk initrd blabla My machine would report "cannot find kernel: memdisk". When doing a tcpdump, I found the machine actually

I have just pushed out SYSLINUX 3.10-pre21; this fixes ISOLINUX, and adds a fix for MEMDISK -- it so happens that running ISOLINUX under Bochs triggers a bug with similar behaviour as I've seen reported on here, so I'm *hoping* this might fix the "doesn't work without harddisk" problem and perhaps the IBM/USB problem some people have been reporting. Again, I really want

I've been trying to use memdisk with grub2 to boot some iso images -( I've done this without any problem with pxe ) There is a memdisk.mod in /boot/grub/ and I've seen some material talking about this, but no example of a menu. After trying countless permutations - Right now I have : menuentry "Memtest-Plus 4.2" { echo `hello` insmod lvm

Hi, I saw the Nov. 2006 message on Memdisk having a problem with ThinkPads. I also saw the comment in the memdisk code enabling and disabling A20. I've got a ThinkPad x61t that memdisk is not loading disk images on. The symptom is that it gets as far as saying "Loading boot sector... booting..." Then image partially runs - FreeDOS prints out its kernel message and it's

Hi, I looked at the web http://clic.mandrakesoft.com/documentation/pxe/ch06.html, and create a floppy boot image by : dd if=/dev/fd0 of=boot.img. I copied the boot.img to /tftpboot, and my /tftpboot/pxelinux.cfg/default is : default freedos display boot.msg label freedos KERNEL memdisk APPEND initrd=/boot.img When I boot up my client, it shows : could not find kernel image: memdisk What

Memdisk 2.08 cannot boot an XP boot floppy image (XP appears to use WinME boot files for its bootable floppy). For example: http://members.iinet.net.au/~bdriver/bootdisk/download.htm This disk will not boot with Memdisk (Memdisk starts to load the image and then hangs). I'm using Bart's tools to build a boot CD: http://www.nu2.nu/corpmodboot/ Which uses Isolinux and Memdisk.