similar to: syslinux and dos memory limitation

Hi, I have been trying to boot a PC based terminal using your PXELINUX project and I am having a problem. The Terminal (a Netier NetXpress XL2000) has a m-systems Disk-On-Chip 2000 flash memory module which is normally used to boot a cut-down version of WinNT. I work in a repair department where we often have to open up these terminals and temporarily install a hard-drive to reflash the

Hello, I've a problem aligning tickmarks to an image. I've created a correlation matrix for 84 datasets. I'm visualizing the matrix as an image with colour coding according to the correlation coefficient. The 84 datasets are distributed over three factors, but the desgin is unbalanced, so that the tickmarks and the lables for the axis must not evenly distributed. A regular grid via

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, is there an easy way to circumvent the SYSLINUX novice protection thing? intended users don't know about CTRL key to circumvent it. I'm trying to make a generic bootdisk for systems of 8086 - Pentium4. however the bootdisk is slow, so I'd like to use Syslinux + Memdisk to load a diskette image. then the text displayed to user will be: 1) FreeDOS bootdisk (accelerated, 386

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.

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

On Tue, Jan 21, 2014 at 2:53 AM, David de Marneffe <daviddemarneffe at gmail.com> wrote: > Hello syslinux list, > > I have installed Arch over a btrfs-formatted dos/MBR primary > partition* (no btrfs subvolumes, just installing everything including > /boot in the root of the btrfs). > > I have been unsuccessful for several days trying to get it to boot > with syslinux

On Tue, Jan 21, 2014 at 7:42 AM, David de Marneffe <daviddemarneffe at gmail.com> wrote: > Hello Gene, thanks for your reply. > > Yes BIOS mode. The config wants a menu, which loads fine under ext4 > and not under btrfs. Under btrfs I have also tried to remove the > syslinux.cfg file altogether (which should trigger the boot: prompt if > I am not mistaken) and the result is

On Fri, May 23, 2014 at 8:29 AM, Ady <ady-sf at hotmail.com> wrote: > Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" > parameter, I found that it works as expected under MS-DOS and its DOS > variants, but it seems to fail under FreeDOS (please correct me if > I'm wrong). This sounds like either a bug in FreeDOS or another undesirable negative

On 05/24/2014 01:58 PM, Ady wrote: > > My guess is that if this was a bug in FreeDOS (as in "something" that > has nothing to do with the syslinux.com command) then it would be > somehow triggered by other DOS programs trying to write to the MBR. > Considering that there are several (open source) DOS programs that > are capable of successfully writing to the MBR

For the MBR: I usually don't touch the Microsoft MBR and chainload Linux from the Microsoft bootloader. However while trying to get my btrfs setup to work, I backed up the Microsoft MBR (dd if=/dev/sda bs=440 count=1 of=MBRbackup.bin) and I installed the syslinux MBR. I tried several ways: - with the script provided by Arch: syslinux-install_update -i -a -m - manual method with mbr.bin (first

I recently got a cheap PenDrive iVO which I'll be the first to admit is anything but perfect, but, a pretty decent player considering it's cost is that of the other players with half the memory. One of the things I was looking forward to was having a great bootable flashdrive with my favorite linux rescue image and a few other diagnostic/repair things. Unfortunately, since I tried to put

On Sat, May 24, 2014 at 11:22 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 05/24/2014 01:58 PM, Ady wrote: > > > > My guess is that if this was a bug in FreeDOS (as in "something" that > > has nothing to do with the syslinux.com command) then it would be > > somehow triggered by other DOS programs trying to write to the MBR. > > Considering

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

> On Fri, May 23, 2014 at 8:29 AM, Ady <ady-sf at hotmail.com> wrote: > > Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" > > parameter, I found that it works as expected under MS-DOS and its DOS > > variants, but it seems to fail under FreeDOS (please correct me if > > I'm wrong). > > This sounds like either a bug in

Hello, I'm trying to create and boot a Win98SE-DOS OS through Hard Disk emulation. My src files are from a Win98SE 1440K floppy image file, with a x86 boot sector (dl'd from the net - I have no floppy drive and a slow net link 3.2KB). I don't know what to put into the partition boot record of my image and how to load dos.bss properly (the docs explain for floppy images not for HD

Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" parameter, I found that it works as expected under MS-DOS and its DOS variants, but it seems to fail under FreeDOS (please correct me if I'm wrong). Using FreeDOS kernel v.2041 (386f32), Syslinux v.6.03-pre11 and either FAT16 or FAT32 partitions, executing: syslinux.com -m -i c: or: syslinux.com -f -m -i

Hello syslinux list, I have installed Arch over a btrfs-formatted dos/MBR primary partition* (no btrfs subvolumes, just installing everything including /boot in the root of the btrfs). I have been unsuccessful for several days trying to get it to boot with syslinux (6.02-8 package from Arch, also tried 4.07-1 Arch package). All I am getting is the copyright header line and a blinking cursor

Hi We have a couple of FSC Computers here which seem to have a very strange bios. I am trying to boot a MS-DOS disk to flash an Scsi Raid controller. Since the computer doesn't have a floppy anymore I tried syslinux from an usb stick. The menu loads fine but I cannot boot disc images with memdisk on this computer. It works fine on others, of course. But now comes the weird part, if I use the