similar to: memdisk.asm patch

Hi, "Mircea Popescu" <nufarul.alb at go.ro> schrieb am 29.01.02: > I have this problem: > I've partitioned my hard drive with PQMagic 7 in the following way: > hda1 - fat32 > hda2 - ext2 > hda3 - fat16 > hda4 - extended > hda5 - Linux Swap > hda6 - fat32 > hda7 - ext2 > hda8 - fat32 > > I've put syslinux on

H. Peter Anvin, The following problem came to my attention with memdisk. I cannot claim the credit, but wanted to be sure the information made it back into the program for the benefit of all users... In file memdisk.asm, in respect of the operation of the raw and bigraw options, the order of pop instructions does not correspond to the order registers are pushed;

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

Hi, This also has been discussed in SSHSCI's SSH context. All SSH versions (both SSHSCI and OpenSSH) derive value for DISPLAY variable from `uname -n`. The problem is that the returned value is not necessarily resolvable to a valid IP number which in turn might cause a failure. To make it fool-proof I suggest to set DISPLAY to the interface's address the user has reached the system in

I just finished up a port of Andy Polyakov's excellent dvd+rw-tools to FreeBSD, and he has incorporated the patches into his release: http://fy.chalmers.se/~appro/ http://fy.chalmers.se/~appro/linux/DVD+RW/ http://fy.chalmers.se/~appro/linux/DVD+RW/tools/ (version 5.8.4.4.4) These tools support DVD-R, DVD-RW, DVD+R, and DVD+RW format dvd burners, including the popular Sony

I have added instructions to memdisk.doc for how to disable MEMDISK. However, it's unlikely that this will work if you're running under DOS, since DOS will be very unhappy about drives changing underneath it. Anyway, until the next (pre)release comes out, here are the instructions: --- memdisk.doc 27 Apr 2004 06:49:36 -0000 1.10 +++ memdisk.doc 6 Jul 2004 01:29:03 -0000 @@ -122,5

It appears that the WinME/XP DOS boot disk links code into the INT 15h AH=87h "mover" function which crashes the system DELIBERATELY (it puts the system in a cli/hlt/jmp loop.) I first thought it was specific to MEMDISK, but it's not; calling this function under just about any circumstances from within this version of DOS seems to crash the system hard. It's possible

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

Has anyone been able to boot a bartpe image successfully using pxelinux or does anyone know if this is impossible? For those who don't know, bartpe is a legitimate way to make a trimmed down installation of Windows XP or Server 2003 using your installation media. For more information on bartpe see: http://www.nu2.nu/pebuilder Basically the pebuilder gathers the minimum files needed to

Hi, I've already discussed this issue in SSHSCI's SSH 2.2 context on ssh at clinet.fi list. My standpoint is that it's wrong and meaningless to perform chown in sftp-server as the file is most likely copied between systems with distinct accounting system where user is not necessarily (and even unlikely) has same numeric user id. The original bug report was that user couldn't

Hi, We're planning to deploy PXELINUX as a primary kernel loader in cluster environment. Problem is that we plan to have IP numbers assigned dynamically while there is no guarantee that all machines has same CPU architecture. This makes IP-based config search algorithm inappropriate for our purposes because we [naturally] expect loaded kernel to match hardware. For this reason I've

Good day to all, Gert Hulselmans requested a feature for MDISKCHK.COM that would function roughly like GETARGS.COM[1] by Murali Krishnan Ganapathy: DOS SET command output for MEMDISK kernel arguments passed by previous boot-loaders. He also needed to support the case for MEMDISK-in-a-MEMDISK type situations, where all MEMDISK kernel arguments could be gathered together and output as a list

Hello, How do I set up the registers to find out that MEMLINUX is installed? I know it is an int 13h / ah=08h call - but I cannot figure out how to specify the other registers... Also, I need to find a way to be able to: unhook int 13h and int 15h and put them back to the BIOS vectors, and yes, I know some DOSses rehook int 13 - but it can be done.. I need to be able to boot a CD, load the

First off, Thank you for pxelinux. It works as expected and for my needs it is a most useful project. I apologize in advance for posting this question as it is in part off topic, but I have searched extensively with little results. Are there any alternatives to memdisk for use with pxelinux for booting troublesome floppy images with such applications that fail to use INT 15h, AX=E820h. Having

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:

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

Hi all, I am new to Syslinux and Memdisk. I setup a PXE boot server that services an image file via memdisk. This works very well. However, I am trying to figure out as to where memdisk the image puts in memory? On the wiki page it says: "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,

Would it be a better ripping technique to read the CD as an image, rather than ripping audio? >>> Andy Polyakov <appro@fy.chalmers.se> 08/30/02 07:15a.m. >>> > > Is it possible to use flac on a CD audio image (e.g. on the .bin file > > of a > > cdrdao .bin + cue-file setup)? > > probably not. I don't know the file format, but unless it

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

Helle, I'm facing a strange issue with memdisk The context : syslinux 3.75 gpxelinux.0 the gpxe stript called from a menu executed through menu.c32 : #!gpxe kernel /modules/memdisk initrd=/freedos initrd /freedos The output before the freeze : /boot.gpxe. ok /modules/memdisk. ok /freedos...... ok MEMDISK 3.75 3.75 Copyright 2001-2009 H. Peter Anvin et al e820: 0000000000000000