Displaying 20 results from an estimated 9000 matches similar to: "Memdisk in Release 3.82 conflicts with a Intel BIOSupdate Image"
2009 Sep 21
0
Memdisk in Release 3.82 conflicts with a IntelBIOSupdate Image
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
2009 Dec 09
2
[PATCH] memdisk: Fix "might be used uninitialized" warnings
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>
2009 Oct 10
2
memdisk locks when loading imz dos image
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...
2009 Nov 20
0
[PATCH] memdisk: Use boot_lba logic for booting an offset within the di
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
2011 Jan 25
2
MEMDISK issue with OptiPlex GX280,620
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:
2011 Aug 06
4
[PATCH] ifmemdsk.c32: Allow boot options based on presence of MEMDISK
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]
2009 Mar 22
1
[PATCH] [memdisk] Additional comments in memdisk.inc and postprocess.pl
>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 +++++++++++++++++++++-------------
2009 Dec 07
3
[PATCH] memdisk: "safe hook" and mBFT
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
2009 Aug 18
2
MEMDISK-ISO: found another non-working ISO
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
2010 Dec 07
6
MEMDISK issue with OptiPlex GX280,620
A kind request for help please.
MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below:
MEMDISK 3.83:
Ramdisk at 0x07eeaa00, length 0x007bc000
command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk
MEMDISK: Image seems to have fractional end
2009 May 28
1
Message 11 Syslinux Digest, Vol 74, Issue 24(Re: PXEboot trouble with Soekris 4826 (Miller, Shao)
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
2009 Jun 02
0
[PATCH] [memdisk] Add some DriveShiftLimit logic
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:
2005 May 17
1
chain / memdisk / mboot of memtest86, SBM loader.bin, ISO image
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
2005 May 19
1
Memdisk ramdisk hangs using menu.c32, but ok from cmdline.
<..trying again after changing outgoing e-mail options to avoid bad
headers...>
I'm trying to use syslinux 3.08-pre11 on a Gateway E4000 with the
(sample) config file below, and the ramdisk images fail to boot if
selected as a menu option, but do boot if I press ESC and type the
command line manually.
The two options are for the same floppy image, but the first is
compressed, the
2009 Jul 31
1
[PATCH] [memdisk] Additional EDD Device Parameter Table fields
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
2009 Nov 20
2
MEMDISK El Torito Emulation
A very special thanks to H. Peter for finding the time to [at least
partially, if not wholly] scrutinize and merge the El Torito emulation
code for MEMDISK!
I'd like to ask that those who've previously used the stale MEMDISK-ISO
switch to this latest[1] MEMDISK proper and report any failures.
Gert, I believe this version addresses the PloP .ISO trouble you
reported. Could you
2009 Aug 04
5
New MEMDISK-ISO
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.
2010 Dec 01
1
MEMDISK ISO Drive 0xE0
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).
2009 Dec 08
1
[PATCH] doc: document mBFT and "safe hook"
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
2012 Oct 25
1
memdisk parameters in windows pe.
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