similar to: Fw: Re: Memdisk Question

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

git://git.zytor.com/users/genec/syslinux.git Branch memdisk-maxmem-for-hpa This is a preliminary hack to introduce a new option that will allow an end-user to limit the amount of available RAM as returned by any call that MEMDISK touches. This works by adding additional memory reservation(s) (through insertrange()) to reserve the memory between the specified address and the top of RAM. For

Hi Guys, I'm currently using pxelinux 4.03 and memdisk to boot a DOS based floppy we use this software for training purposes to run a basic hardware check. It does not seem to like systems which have more than 1GB of RAM, which is some of the machines our company are now starting to see. Is there a way I can ask memdisk or PXE linux to use only xxx MB of RAM, e.g. 256MB...?

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

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

I now have default_mail_env = mbox:~/mail:INBOX=:/var/spool/mail/%u I now getting: Apr 26 15:55:32 jedrik imap(mclay): open() failed with mbox file : No such file or directory I tracked down where the error message is getting generated and added some more printing: In mbox-index.c I added: int mbox_set_syscall_error(struct mail_index *index, const char *function) { i_assert(function !=

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

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

Some additional fields from the EDD-4 spec. draft for the Device Parameter Table have been added into the structure in setup.c and memdisk.inc. These were added in the hopes of resolving a FreeDOS MEMDISK bug on IBM ThinkPads. --- memdisk/memdisk.inc | 11 +++++++++++ memdisk/setup.c | 10 ++++++++++ 2 files changed, 21 insertions(+), 0 deletions(-) diff --git a/memdisk/memdisk.inc

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

BIOSs that don't support ISOLINUX, and it would be really helpful if you could tell us what the seriousness of the problem is, because we are supposed to be releasing Debian GNU/Linux 3.0 in about 3 weeks, so testing time is short. Do you know how the standard multiboot feature of mkisofs comapres to all of these? It's supposed to fail on some BIOSes, but in a way that means that you

hpa etal, Im trying to get PIRT running on an SBC which has no CD-ROM drive. (an 8 MB ISO which demo's RTAI - RealTime Application Interface, on linux patched with Adeos) (BTW, PIRT uses isolinux) anyway, Im trying to use pxelinux to chainload / memdisk / mboot it, Im having no success. Ive also tried booting memtest86, which I can boot on my laptop using grub, ie title memtest

> I'm having trouble getting memdisk 6.03pre18 to boot large floppies and > wondering whether I'm doing something incorrectly. > > 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz > 2) gunzip FDOEM.144.gz > 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img > 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img > 5) Use following pxelinux.cfg: > >

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>

Oops! My mistake in my 'freedos' branch. Silly mistake. - Shao diff --git a/memdisk/memdisk.inc b/memdisk/memdisk.inc index 237e020..9c19b58 100644 --- a/memdisk/memdisk.inc +++ b/memdisk/memdisk.inc @@ -980,8 +980,9 @@ EDD_DPT: .dpilen db 2ch ; DPI len .res1 db 0 ; Reserved .res2 dw 0 ; Reserved

Im trying to boot memtest86 via pxelinux, memdisk, I found this advice on http://forum.x86-secret.com/viewtopic.php?t=2906 folks are making the image match a floppy size by one of the following: dd if=memtest86+-1.xx.bin of=memtest.img bs=360k count=1 conv=sync or dd bs=360k count=1 conv=sync if=memtest86+-1.xx.bin|gzip > memtest.gz I did the former, it did suppress the warning/errors I saw

Has anyone managed to get OS/2 to fully boot via Syslinux's memdisk? I have played around with it a bit both as a floppy image and a hard disk image, but either it hangs when loading IBMINT13.I13 driver or doesn't load any .ADD driver and stops saying it cannot find COUNTRY.SYS (it needs at least one .ADD disk driver loaded before it can continue accessing the boot device). Going in

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

We are working on a prototype for an installation system, and it would be very useful if we could load two memdisk images, having one pretend to be normal A: drive, and another as B: drive. I have read through the docs as well as done some google searches, and haven't seen such a thing described. We have one person who has asm programming experience, and we were wondering if we could get

Greetings, I had a quick question about lower memory usage by memdisk. I've read through the mail archives and found a couple of posted questions but unfortunately no answers. I know the documentation states: "MEMDISK simulates a disk by claiming a chunk of high memory for the disk and a (very small - 2K typical) chunk of low (DOS) memory for the driver itself, then hooking the INT 13h