similar to: MEMDISK un-loading from memory..

Hi Peter, I'm using isolinux and memdisk to create a multiboot rescue cd for personal use as described on Bart's page (www.nu2.nu). One boot item is to boot DOS 7.1 from Win98SE with a lot of other staff for emergencies. This DOS bootimage puts all necessary stuff into it's own ramdisk (XMSDSK). Some progs on the ramdisk needs access to floppy drive A: and unfortunately I've no

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)

I have been using memdisk (version 3.82) with no problem. I use it to boot my x86 computer with a compressed image I created/modified from an original DOS floppy bootable diskette. The original size of the image is 2.44 MB. I tried memdisk (version 3.83) and the bootable image gets uncompressed, bu the computer locks up and the las two lines in my screen are: Loading Boot Sector... Booting...

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

Hello, Can anyone help me? Does any of you manage to load (boot) Bootitng through CDShell? How can I ensure that diskemu emulates a 1.44MB floppy? Any ideas? Thank you Andreas Gortsilas -----Original Message----- From: David F. [mailto:support at terabyteunlimited.com] Sent: Tuesday, May 17, 2005 9:48 AM To: 'Andreas Gortsilas' Subject: RE: Bootitng and

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

Hello, I saw your post on booting a Norton Ghost image via pxe, syslinux, memdisk. I would like to how if you were able to do it? And also how you did it? I tried converting to .img to no use Thank?s Marcus Nascimento Ger?nte de TI Mikropar Ind. e Com. Ltda (11) 4662-9100

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

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

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

Hi! Although it may seem so, this is the wrong place to put your question. Please contact the CDShell developer. Luis Correia > -----Original Message----- > From: Andreas Gortsilas mailing list account > [mailto:agorts_mlst at sabo.gr] > Sent: Tuesday, May 17, 2005 7:59 AM > To: 'syslinux at zytor.com' > Subject: [syslinux] RE: Bootitng and CDShell... > >

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

'nopassany' is missing in the MEMDISK documentation: http://www.zytor.com/pipermail/syslinux-commits/2010-February/000096.html - Gert Hulselmans commit aeb2406ea701d974c85aa7fdd9af7c53106d7e48 Author: Gert Hulselmans <gerth at zytor.com> Date: Sat Mar 6 22:33:09 2010 +0100 Document 'nopassany' in MEMDISK documentation. diff --git a/doc/memdisk.txt b/doc/memdisk.txt