similar to: ISOLinux and OpenBSD?

hi there. I'm trying to boot several OSes floppy images from a cdrom via memdisk. Actually, Linux and FreeBSD boots fine, but, while i'm using the same method, I couldn't get into booting netbsd nor openbsd. The boot process seems to hang up, in those two cases, when the second stage native bootloader try to load the kernel (i'm not absolutely sure about this). The native first

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

dear all: I try to configure a bridge in my embedded linux. I had fininshed these operations below: 1) configure kernel, select the option "802.1d bridge" 2) compile bridge-utils 3) issue these commands: ifconfig eth0 0.0.0.0 ifconfig eth1 0.0.0.0 brctl addbr vb brctl addif vb eth0 brctl addif vb eth1 ifconfig vb 192.168.110.24 up

http://bugzilla.mindrot.org/show_bug.cgi?id=105 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From markus at openbsd.org 2002-02-07 06:54 ------- could you please try this without scp? e.g.

Hi all, I try to boot an msdos system using pxelinux and memdisk on my PC engines Wrap-2.c card and I have problems with it This is what I see: PXELINUX 3.11 Debian-2006-03-16 Copyright (C) 1994-2005 H. Peter A boot: msdos Loading memdisk.... Loading images/msdos/msd622bd.dosim......................... Ready. dp83815: Setting full-duplex based on negotiated link capability. MEMDISK 3.11

My system is hanging up when attempting to boot a bootable floppy disk image Does the following info tell any story as to what's happening? Thanks. LABEL dosdiskimage KERNEL memdisk APPEND keeppxe initrd=dos.img floppy Loading dos.img ............. Ready. MEMDISK 3.11 2005-09-02 e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 2 e820: 00000000000e0000

dear all: I try to configure a bridge in my embedded linux. I had fininshed these operations below: 1) configure kernel, select the option "802.1d bridge" 2) compile bridge-utils 3) issue these commands: ifconfig eth0 0.0.0.0 ifconfig eth1 0.0.0.0 brctl addbr vb brctl addif vb eth0 brctl addif vb eth1 ifconfig vb 192.168.110.24 up

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,

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

Hi everybody. Hardware: Several computers with Asus P/I-P55t2P4S motherboard, CPU Pentium MMX and K6-2/3, 128 to 384 MB RAM, Award 4.51PG Bios, Hard disks from 8 GB to 123.5 GB Realtek 8139D based NICs with PXE Boot-Proms PXELINUX 2.06 / MEMDISK 2.06: - fails to boot Compaq PC-DOS 3.31 PXELINUX 2.08 - succeeds to boot Compaq PC-DOS 3.31 with 0, 1, 2 and 3 hdds installed in

Hey, Firstly i like to say good work on your project, I love the ability to use PXE to ghost all my machines without the use of floppy disks. Now i managed to setup PXE correctly using a copy of Barts Boot Disk's with ModBOOT and modified it to meet our company needs. This works perfect and i can ghost not a problem using the standard loader prompt boot: and inserting text depending on

I'm seeing this on a HP Blade and i'm not sure why this is happning since the nature of the issue is so wierd. I compiled mboot.c with a DEBUG defined in the mboot.c file. In the funciton init_mmap(), it prints the e820 map and on the HP blade this map values come out to be totally random. Some weird numbers which dont make any sense at all. However, if i add a while(1); or a exit(1); at

dimesio wrote: > > durammx wrote: > > Hi all! > > I trying to run this program (http://appdb.winehq.org/objectManager.php?sClass=version&iId=17469) but I'm a really noob on wine. :? > > Can a big master of wine test? > > > > Also posted a bug (http://bugs.winehq.org/show_bug.cgi?id=19678) on bugzilla. > > > > Hope I did it well. >

Franga . wrote: > > Now i moved to my next step of trying to get Simple Menu's working. My > problem occurs after selecting a menu option. The image loads and > gives me this output: > > command line: initrd=images/c201.img BOOT_IMAGE=memdisk Disk is > floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1491 bytes, > allocating 2K Old dos memory at 0x9f000 (map

Hi, I am aware that it is impossible to netboot ISO files through pxelinux/memdisk and that there are multiple reasons for not even attempting it (like the operating system which will try to access a physical optical drive through its own drivers anyway, BIOS issues etc.). When people ask questions regarding ISO support in pxelinux/memdisk, they're mostly told to convert the ISO into a

Hello, I have an odd problem on a dual processor, dual core Opteron system. Obviosously it is x86_64 so should have no problem large amounts of RAM. The system has 4 GB installed (2GB on each processor). If I boot the system with a fresh install of Debian Etch it sees all the memory fine. dmesg reports: Memory: 4107008k/5242880k available (1929k kernel code, 86836k reserved, 864k data, 176k

Hello, I have an odd problem on a dual processor, dual core Opteron system. Obviosously it is x86_64 so should have no problem with large amounts of RAM. The system has 4 GB installed (2GB on each processor). If I boot the system with a fresh install of Debian Etch it sees all the memory fine. dmesg reports: Memory: 4107008k/5242880k available (1929k kernel code, 86836k reserved, 864k data, 176k

I have an old 400mHz Dell with a 20G hard drive and 125M ram. Can I install and run CentOS on it? Thanks, Mike.

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

I am not sure how to interpret the output of the DF -h command. Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 112G 12G 95G 11% / /dev/hda1 99M 12M 82M 13% /boot none 125M 0 125M 0% /dev/shm The filesystem Centos is using is new to me since I have RH 9 on my other server. I assume the