similar to: Booting DOS (FLOPPY) via PXE / MEMDISK

Hi group, currently I try do make my own PXE bootscreen. There is one thing i dont like. When I use vesamenu.c32 there is always a table on the screen (I mean the border lines are visible) Is there any command i have to add to the default file that this border lines are unvisible ? Thanks in advance

Hello, I'm trying to boot a dos floppy stored on a disk image which is initially loaded over pxe using memdisk. I've created the disk image as follows: dd if=/dev/zero of=$IMGLOCATION/$IMGNAME bs=$(( 1024 * 1024 )) count=20 LOOPDEV=$(losetup --show -f $IMGLOCATION/$IMGNAME) MAJOR_MINOR=$(ls -l $LOOPDEV|awk '{print $5$6}'|sed 's/,/:/') DMSIZE=$(( $(ls -l

Hello, I'm investigating ways to boot a DOS floppy image stored on the FAT32 EFI System Partition using Syslinux and Memdisk. The system will be running Win8 using UEFI mode (GPT disks) and secure boot off. Change the Windows efi boot loader is the easy part... With the current syslinux's alpha version (6.0), is it possible to boot the syslinux's efi module from the FAT32 EFI

Hello, I'm investigating ways to boot a DOS floppy image stored on the FAT32 EFI System Partition using Syslinux and Memdisk. The system will be running Win8 using UEFI mode (GPT disks) and secure boot off. Change the Windows efi boot loader is the easy part... With the current syslinux's alpha version (6.0), is it possible to boot the syslinux's efi module from the FAT32 EFI System

Good day Ercolino, Are you using the ELTORITO.SYS DOS CD-ROM drive driver? You should be, if you're using MEMDISK. You might also enjoy some of the discussion here[1]. Also, as an aside, you can create an 8 MB superfloppy image which could contain your BIOS/firmware upgrade. Maybe search the mailing-list archive for "superfloppy". Have a nice day. - Shao Miller [1]

Hi all, We are hoping to update our BIOSes remotely with pxelinux and memdisk (it is for a 600 node Beowulf cluster with no floppy access). The DOS floppy loads and starts, however somehow the flash utility 'phlash.exe' or 'phlash16.exe' are both unable to load the provided rom image and just stop doing nothing. It looks like it can't access the rom image somehow, which is

---snip--- PXE entry point found (we hope) at 9CAA:00FA My IP Address seems to be C0A801F5 192.168.1.245 ip=192.168.1.245:192.168.1.254:192.168.1.1:255.255.255.0 TFTP prefix: pxelinux.cfg/ ^^^^^^^^^^^^^^^^^^^^^^^^^what?s up with this? check your "filename" option in dhcpd.conf... ---snip--- Greets, Thorsten

Hi there, I do not know if it has to do with my english knowledge, but I tried several times to understand the difference beetween Etherboot and PXE-Linux. I know that Etherboot can be put on a Nic's ROM, but for what on h*ll then is the Etherboot floppy for? Please, could someone explain me stupid person these things? Thanks a lot. Greets, Thorsten

I found that if I do not have a local floppy installed and enabled on my client, I will get the error 'Non-system disk' when I try to boot DOS floppy images. NT or Syslinux floppy images boot fine. If I enable the floppy in the BIOS, then it boots the DOS floppies just fine. Is this normal? Is there a workaround? There are MS-DOS images, so perhaps this is an MS-DOS limitation. --

Hello, I'm Rene living in Germany. I have a problem when I use syslinux versions greater than 3.xx for booting DOS (over dos.bss) and DSL-linux from a hard disk. (I've tried version 3.11 and the newest 3.36). The problem occurred after booting DOS - I can not access to the ordinary 3.5'-floppy drive (e.g. the command "dir a:" fails after a while). DOS not even notices

Hi, bit of a newbie if I'm honest but was wondering if issue mentioned here: http://syslinux.zytor.com/archives/2006-October/007586.html was ever fixed? basically I have the same issue with the same machine. I have 4 different types of PC's here that i'm trying to boot by USB stick. It works fine on 3 of them, but on the 4th, A HP/Compaq dx2200 MT, memdisk will not boot the .ima

Hello Mr Anvin, I'm trying to get my system to show a bootscreen during the entire boot. Since using Linux's fbdev doesn't quite work out (kernel segfault) I'd like to just stick with what Syslinux has put on the screen in the first place and leave it there. No unfortunately, even though I've left out the VGA console from the kernel, the picture still vanishes after shortly

Hi, I'm trying to convert my PXE enviroment from the 3com to PXELinux but I've got a problem when loading a image created by 3com's utility. At first when I tried to launch the bootimages with memdisk but I had no luck Then I added a MBR to the images and now Norton Ghost can launch but it first gives me a Windows 98 bootscreen and my customized Universal Network Bootdisk can't

Anyone know the correct syntax for specifying a floppy image in the /tftpboot/pxelinux.cfg/default file? I am trying to use: label Dos Bootdisk MENU LABEL Dos bootdisk FDIMAGE discimage.img But when I select it the menu, I get a message saying "Automatic boot in 30 seconds" and nothing happens. I would use: label Dos Bootdisk 2 MENU LABEL Dos bootdisk 2

Hallo, i've got a little question: is it possible to query the domain controller which user is loggid in from which workstation. I'm writing an webapp for teachers; it would be nice to know which pupil logged on from which workstation to shutdown the correkt workstation in order to kick the pupil (force logoff) or is there an other way to

Hi, I'm sorry to bring this up again but I can't quit get this too work. I'm trying to build a 2.88 floppy image so that I can use PXE to load Ghost. I'm useing the following to get a copy of the bootsector: dd if=/dev/fd0 of=bootblock bs=512 count=1 Then I build the image file with: mformat -C -t 160 -s 18 -h 2 -B bootblock x: Then use mcopy to put the required

Thanks for Remko for his help to solve the fractional cylinder problem. But there is the second problem, the boot disk failure (see below << [B]) # but when booting via PXE (pxelinux.cfg/default) ... LABEL t KERNEL memdisk c=2 h=256 s=63 APPEND initrd=disk.img # the following things occur boot: t Loading memdisk Loading disk.img ...................................(16MB)......... Ready.

Memdisk 2.08 does not appear to be able to boot an XP DOS image (it starts to boot and then hangs). XP DOS appears to be borrowed from WinME (v4.90.3000). I was trying to make a multiple boot CD with Bart's method: http://www.nu2.nu/bootcd/#multimemdisk but substituting Brads TCP boot disk instead of Barts: http://members.iinet.net.au/~bdriver/bootdisk/index.htm Brad uses XPs DOS as it

Hello, I seemed to have encountered a problem with memdisk that I have seen before when I was playing around with USB device booting at one time. Here's the scenario: Take fx a image of a PC DOS bootable diskette. Boot the image via memdisk. This should boot fine if you use the built-in motherboard ide controllers (ide0,ide1). Now install a PCI IDE controller and put one IDE disk on the

I've got $SUBJ almost working except for the DOS bit where the CD needs to be read. My pxe config: label Firmware menu label Update IPMI firmware kernel memdisk append keeppxe raw iso initrd=<isofile> The ISO is about 400Mb, and works fine when I boot it from an actual CDROM drive. It also boots fine over PXE, I can see FreeDOS being booted up etc. The problem is - once