Displaying 20 results from an estimated 10000 matches similar to: "memdisk possible bug"
2008 Jun 06
3
memdisk question
Hello,
I am using syslinux 3.63 and I am trying to get an image file going for
ghost. I was able to get the unicast image working by using winimage
and creating the format for the image as 2.88mb and saving the boot
sector as win 95/98.
I tried the same thing with a ghost multicast image and it doesn't work,
says invalid system disk..
Lots are variables so I am not sure where
2003 Dec 01
1
Memdisk/XMS bug, big floppy image
>that image under B: or X: or whatever. This will allow us to cross the
>size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect
>memdisk to mount it, just that set things up so that DOS mounts it there.
I'm using a 5MB image which emulates floppydisk.
label test
kernel data/memdisk
append initrd=data2/test.img c=80 h=8 s=18 floppy
problems are
2004 Jan 12
5
DOCMEMORY 2.0 (simmtester) and MEMDISK
Like a lot of people, I am using SYSLINUX + MEMDISK to make a technician
universal boot disk on a USB key (I have done the same with ISOLINUX and
MEMDISK for a CD using Bart's method for bootable CDs)
I *LOVE* Syslinux and MEMDISK, and what I can do with floppy images!
I have a few problems that have cropped up, most notably the DOCMEMORY
program (www.simmstester.com) boots fing, but the
2004 Apr 12
1
Newbie RIS Replacement
Doing a lot of RTFM lately about PXE. I have done xCAT builds but want
to take the voodo out of the process so I can control and understand the
whole system. I am new to PXE technology and so consider me ignorant.
The current server is a MS RIS server and I am attempting to migrate our
facility to use Linux / PXE instead.
First stage: take existing DOS bootnet floppy and convert to boot from
2005 Jan 11
2
[memdisk] remote booting diskless Mini-ITX system
Hi,
As the subject suggests, I am trying to remote boot a Mini-ITX system.
I am using PXELinux as the bootloader,
and Memdisk (2.11) as the 'kernel'. My ramdisk image is a hard drive
image based on PC-DOS.
Two things go wrong during the boot process.
1. "INT 13 08: Failure, assuming this is the only drive" message
2. "Loading boot sector... booting..." message,
2009 Oct 04
1
Build a bootable floppy image which contains HDT
It is now possible to build a bootable floppy image which contains HDT,
with my patch applied to Erwans HDT branch:
http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=16b37fe2266c920087f88cdec94243b71218d871
Unpack the Syslinux archive and build whole Syslinux first,
then cd to ./com32/hdt/ and make hdt.img
$ make
$ cd ./com32/hdt/
$ make hdt.img
Now you have a 2.88 MB floppy image which
2003 Dec 30
5
Pxelinux/memdisk with XP "MS-DOS" boot disk
I'm trying to use this universal DOS TCP/IP boot disk available here:
http://members.iinet.net.au/~bdriver/bootdisk/
It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image
2007 Jul 13
1
[memdisk] collision between memdisk and emm386 (FreeDOS)
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:
...
2005 Sep 02
3
MEMDISK - floppy=1 Outputs: Disk is hard disk, 1440 K, C/H/S = 80/20/18
Hi,
I am trying to load an disk image as Floppy=1, og B: using ISOLINUX.
My Config file reads:
------- Begining Of File -------
KERNEL MEMDISK
APPEND raw floppy=1 initrd=CERC6.IMG
------- End Of File ------------
--- MEMDISK Output Snip ------
Ramdisk at 0x03b58000, length 0x00168000
command line: initrd=CERC6.IMG raw floppy=1 BOOT_IMAGE=MEMDISK
Disk is hard disk, 1440 K, C/H/S =
2014 Jul 08
3
Possible memdisk issue
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:
LABEL works
LINUX syslinux/memdisk
INITRD
2006 Oct 31
3
Laptop+SDMMC+Extlinux+Memdisk+Floppy images=headaches
Hello syslinuxers
I'm stuck with a scientific problem which gives me headaches:
I have a laptop (Gateway MX3410) which has a SD memory card reader.
Recently an interesting thought crossed my mind: why don't I setup
a 2GB SD card as a harddrive and put some rescue tools on it.
So I dug on the net and I came across the idea of using memdisk
to boot floppy images without the need of a
2007 Jul 19
4
Help Memdisk + Pxelinux hangs
Hello,
I am a *nix newbie
I am trying to boot a DOS boot disk using PXE (to Ghost on windows
images).
We have an existing PXE server which successfully serves out PXElinux and
Fedora builds based on that but my floppy disk image with memdisk isn't
working
I have tried a few different floppy images which people have posted as
ones that work for them but I doubt the disk is the problem
2005 Aug 16
1
memdisk as A: and B:?
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
2002 Nov 01
2
pxelinux / memdisk booting problem
I have been using pxelinux for quite a while to automagically build
linux boxes with great success. Thanks to everyone involved!
Now, I am trying to download a floppy image and get that to boot.
My conf file looks like:
default sir4
label sir4
kernel ia32/memdisk
append initrd=ia32/sir4/floppy.img
Everything starts off fine.
pxelinux loads
I see it get the conf file.
gets memdisk
2017 Feb 06
1
memdisk load failure on HP DL360g9
On Thu, Feb 2, 2017 at 1:26 PM, Ady Ady via Syslinux <syslinux at zytor.com>
wrote:
>
> > Hi all,
> >
> > I have observed a problem where, under legacy BIOS booting mode on the
> > DL360g9, memdisk fails to execute. The same mechanism works fine on the
> > DL360g8. The system displays the below on the console and ceases to
> > respond and must be
2004 Jan 16
3
unloading memdisk
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
2006 Oct 27
3
Memdisk doesn't work without floppy drive
Hi,
I stumbled on a rather odd problem. A brand new HP Compaq dx2200 computer
didn't want to boot up pxelinux+memdisk image. The computer just gave "Disk I/O
error" and stopped there. Workaround was rather simple... Just attach regular
floppy drive to the motherboard and everything started working fine.
I tried with older 2.05 (pxelinux+memdisk) and newer 3.31. Both produced
2004 Apr 10
1
Floppy image larger than 2,88MB
I hope I've understand that all, somebody wants to create a floppy-image
larger than 2.88MB an use it with memdisk? I have modified a tool from Bart
Lagerweij (Big thanks!) and can create Floppy-Images with 5760kB and 8100kB,
and boot them with ISOLINUX and MEMDISK (or also with a modified
DISKEM1X.BIN), is this what you mean? These tools must run under windows, but
booting no problem.
2003 Aug 27
2
MEMDISK without floppy drive
I tried to use memdisk 2.06 to boot a floppy image on my notebook which
doesn't have a floppy drive.
The boot failed, because the bootstrap code tried to reset the floppy
drive (int13, ah=00). Memdisk passes reset calls on to the original
int13 handler, which returns failure, because there is no floppy drive
to reset (#1).
Also i noted that some boot records (notably some created by
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