similar to: Disabling MEMDISK

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

Dear all, I am using R version 2.9.2 in Windows. I would like to output the results of a function I have written to a .txt file. I know that I can do this by using the code write.table(boothd(10),"boothd10.txt",sep="\t",append=TRUE) etc. However, I would like to bootstrap my function 'boothd' several times and get each vector of results as a new line in my text

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

Sensei H. Peter Anvin, I have successfully modified/enhanced memdisk so that one can chainload a local operating system after running diskless FreeDOS. I would like your advice regarding the appropriate interface for invoking this functionality. In addition, I would like to know what steps to take so that you feel comfortable considering including this in the standard syslinux distribution.

Hi, Anyone has tried to use pxechain with Etherboot? Here is my problem: The Etherboot client had no problem to get the list of install servers manual from the pxechain. But didn't matter which server was chosen, Etherboot client always tried to use the first server to do the installation. Etherboot 5.4 was used. What the problem may be? PXEchain or Etherboot? Thanks, Joyce --

Hello! I have been successful using SYSLINUX and Etherboot to create a generic "PXE-on-a-disk" package, a floppy image and CD image that support as many Ethernet cards as possible. These have support for all of Etherboot's modules that support real PCI cards: about 25-or-so drivers and 250-or-so cards. I've built Etherboot ZLILO images, one for each driver, set up to boot

I'm not sure if this belongs here or on an etherboot list. I've given up on trying to get a single floppy syslinux with enough stuff to remote mount a file system. I'm trying an etherboot floppy. When I boot the system finds the dhcp server and gets the right file name but then it gives me the message "not a valid image." A quick search of the net didn't help much.

Hi, Peter Lister <P.Lister at sychron.com> schrieb am 06.02.02: > In way way better and easier? When I have criticised pxelinux I think > I've always stated *why* etherboot seems better for our environment. > > I'm not trying to be religious, or get anyone to change a working system > - I'm genuinely interested what differences others perceive. I've looked

Hello, I just grabbed http://bits.xensource.com/oss-xen/release/4.2.0-rc2/xen-4.2.0-rc2.tar.gz and tried to build it on Fedora 17 x86_64 host (gcc 4.7.0): make tools: .. make[5]: Entering directory `/root/xen/xen-4.2.0-rc2/tools/firmware'' make -C etherboot all make[6]: Entering directory `/root/xen/xen-4.2.0-rc2/tools/firmware/etherboot'' make -C ipxe/src bin/rtl8139.rom

Hi, I need help about the stuff in nilo that gets burnt on a rom to make it a pxe bootrom. In etherboot, it's the file .rom and .lzrom etc. please help me indentify, what component in nilo is used with an eeprom writer to create a pxe bootrom from a 27c512 eprom. thanx and regards, milan -- Powered by Outblaze

This patch set mainly allows the user to build a seabios or rombios only version of hvmloader. In addition, when building a seabios only hvmloader, Option ROMs like vgabios and etherboot are no longer required, and therefore can be disabled from the build. Dependency on the bcc compiler can also be avoided the same way. v2: Separate patches for separate issues Introduced config option to

Hello, I got in a situation where pxelinux 3.7 (or 3.6) reboots constantly after loading the configuration file and displaying the 'display' option file, but never showing 'boot:' prompt. config file is following: # PXE SYSLINUX config file - look at # http://syslinux.zytor.com/faq.php for syntax # # ---------- This is gate configure file ------- timeout 20 prompt 1 display

Hi, hm at seneca.muc.de schrieb am 29.05.03 21:40:34: > I would like to load pxelinux as a second stage bootloader from a machine > which does not have a PXE BIOS (namely, from a VMware guest machine) in > order to perform an automated Linux installation. A boot floppy would > be nice. It seems that there are some commercial solutions around but > is there someting in the OSS

Tim Legge has passed the following message on to me: hpa wrote: > Quinn wrote: > > Now it seems I have found a bug in PXELINUX with regards to etherboot. > > Up until 2.07 pxelinux was responsive to the keyboard. From 2.08 and > > up the keyboard is locked at the boot prompt when pxelinux is loaded > > via etherboot 5.3.14. > > That would not be a PXELINUX bug,

Hi All, I'm playing with KVM in order to adopt the technology for dev / testing purposes. Installing RHEL5 from ISO images works ok, no problems with installation. The problem occurs with PXE boot - it is simply doesn't try to do PXE boot, according to what I can see: Booting from Hard Disk... Boot from Hard Disk failed: not a bootable disk FATAL: No bootable device. _ I have: CentOS

Hi, "David Ehrmann" <exobyte at bigvalley.net> schrieb am 10.07.03 11:02:54: > I've been doing that for a while, but I seem to be finding conflicting > information. Some sources focus on the boot ROM aspect of etherboot > while others think etherboot is an alternative to PXE. Correct me if I'm > wrong, but it seems like there is etherboot the program and

Hi, I've been using pxe-enabled nic's with an lzpxe-etherboot image generated by rom-o-matic.net to boot a ltsp.org kernel, with dhcp 3 to use if statements to determine which filename option he gives to the pxe/etherboot dhcp client.Explained at http://www.ltsp.org/documentation/pxe.howto.html This works perfectly, except for the fact that you can't use 1 etherboot pxe image for

This patch set mainly allows the user to build a seabios or rombios only version of hvmloader. In addition, when building a seabios only hvmloader, Option ROMs like vgabios and etherboot are no longer required, and therefore can be disabled from the build. Dependency on the bcc compiler can also be avoided the same way. v2: Separate patches for separate issues Introduced config option to

Folks: I've used etherboot to create a zrom that successfully brings a image of a bootable floppy into high memory. What I'd like to do is glue memdisk in so that it can hook int13 and serve the transferred image for booting when etherboot hands control back to the BIOS. The trick, and this is where I'd appreciate "gotchas", pointers or "this is an approach I

Hi all, I've searched the depths of the resources on the internet; however I'm having trouble deploying a pxeboot solution via pxelinux. So far what I have successfully implemented in my infrastructure is a successful pxeboot setup for FreeBSD ( without the use of pxelinux ). I'd ultimately like to have a solution that will allow me to choose a network install of various Unix-like