similar to: pxe + memdisk ..??

> > Thanks Ady, you were spot on, and I should have tested that scenario! > I narrowed the issue down to a line in my config: > > > ALLOWEDOPTIONS 0 > > > The comment next to it in my config indicates this was added to > disallow users dropping to the console with Escape or Tab, a > restriction I would like to keep. BUT, when this is set whichsys >

Apologies for how that formatted. Also on pastebin: http://pastebin.com/EXSq75yX --Ian > From: ian at internals.io > To: ady-sf at hotmail.com; syslinux at zytor.com > Date: Tue, 29 Apr 2014 19:09:09 -0500 > Subject: Re: [syslinux] Issues with syslinux_run_command(str) and parameters > > I don't think that's it, but fair enough, try this sample config: >

I'm running into an issue which I didn't expect to encounter. When specifying the "nopassany" parameter to hide physical drives, I'm getting different output from ELTORITO.SYS (v1.5, syslinux distro) such that it fails. My intent is a LiveCD functionality with a DOS RAMDISK program taking over as drive C:, meaning either no FAT partitions on harddisks and removable disks

hi i am a complete newbie to xen, and i have still a problem with hda(hdc): lost interrupt coming from the 2.6.10-xen0 kernel on an asrock k7s8x board with an additional promise 100 controller(doesn''t get recognized anyway) an amd athlon 2400+ and 512 mb ram. an ideas? regards toby ------------------------------------------------------- SF email is sponsored by - The IT Product

I have been trying to find the information by searching through the archives and google, so I am sorry if this question has been asked before I just have not been able to find an answer. I have a syslinux boot floppy which loads to the boot prompt, I wish to load a .gz image which is on my hd0 0 by using memdisk as the kernel. I have tried to kernel memdisk append root=/dev/hd0 0 (also just

a member of the FreeDOS project has transformed Smart Boot Manager into a COM32 module for Syslinux. Might be a bit more usefull than Syslinux -> memdisk -> imagefile -> Smart Boot Manager ( -> 'boot from cd -> cdrom ) I've inserted it into this diskette image: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/beta9sr1/fdos1440.img That's nice to

isolinux: Extremely broken BIOS detected Yoper 2.1 --------- ISOLINUX 2.11 2004-08-16 isolinux: Loading spec packet failed, trying to wing it... isolinux: Extremely broken BIOS detected, last ditch attempt with drive = 9F isolinux: Disk error 01, AX = 4209, drive 9F Boot failed: press a key to retry... Helix 1.5 --------- ISOLINUX 2.04 (Debian, 2003-06-06) isolinux: Loading spec packet failed,

HOPEFULLY fixes the 3.05 initrd bug. Please try it out and confirm; I will try to release it as 3.06 tomorrow. SIGH... -hpa

perhaps the boot-from-cdrom code in Smart Boot Manager? Bernd >>> No, since booting from CD-ROM requires that the El Torito part of the BIOS is activated, which it won't be if it didn't boot from CD-ROM in the first place. ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing:

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao Miller, Kenneth Davis, wrote: > [...] Thank you all for your responses. You helped me solve my problem. For anyone else that runs into similar trouble and finds this thread, here follow summaries of what I've learned. To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy images booted via MEMDISK.

Hi all, I have a server, with an Intel DG35EC motherboard, Q9300 CPU, 8GB Kingston DDRII RAM which can't take a lot of load. I have 4 XEN VPS's on there, which doesn't consume more than 4GBM RAM at this stage. Yet, the machine sky rockets at some times. I've moved the XEN VPS's to another server, with 4GM RAM, and it doesn't cause the same problems. So, apart from

I would like to implement a replacement MSCDEX driver (based on the replacement in FreeDOS SHSUCDX http://johnson.tmfc.net/freedos/shsucdx.html and SYSLINUX) however instead of talking to disk BIOS calls or PATA chipset I would like it to talk to the NDIS driver and act as a TFTP client simply forfulling application get block requests through TFTP. Its not clear where the ISO9660 CD

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes

I don't think that's it, but fair enough, try this sample config: ************************************************# Test File: isolinux.cfg default vesamenu.c32 ALLOWOPTIONS 0 LABEL Test kernel whichsys.c32 append -iso- memdisk initrd=fdboot.img -sys- initrd=fdboot.img MENU END************************************************ I am using binaries from 6.03-pre11 from kernel.org. I used

On Tue, 08 Jul 2014 15:54, H. Peter Anvin wrote: > >On 07/08/2014 11:26 AM, Ady wrote: >> >> It's interesting that you ask this, because every document related to >> newmkfloppyimg.sh specifically recommends adding: >> floppy c=$CYLINDERS s=$SECTORS h=$HEADS >> to the MEMDISK arguments. >> > >It would be important for floppies to know

Hello HPA, I think on harddisks, Syslinux is going to lose somehow from other bootloaders like LILO, Grub and others. However, SYSLINUX is still VERY usefull for removable media like diskettes, Zipdisks, USB Flash keys, etc.. I don't know if the fact that Syslinux is now installed using blockmapping is really breaking the usefullness for harddisks. You already mentioned system attribute

hm, nice algorythm thingie. I'm not a programmer, so here goes: currently: F1 helpfile.txt probably results in DISPLAY helpfile.txt perhaps extend this option: F1 arg1 arg2 arg3 argX if arg1 does not exist, abort (currently also done?) if arg1 ends in COM extension, execute it and pass the optional arg2/3/X parameters if arg1 ends in C32 extension, same thing. else DISPLAY arg1 // arg1

Try the following and let us know. If it doesn't work, we'll try other alternatives. *** DEFAULT vesamenu.c32 ALLOWOPTIONS 0 LABEL test COM32 whichsys.c32 APPEND -iso- iso -sys- sys LABEL iso LINUX memdisk APPEND initrd=fdboot.img LABEL sys LINUX memdisk APPEND initrd=fdboot.img *** Regards, Ady.

I have been using pxelinux with Intel 850 1.7 Ghz P4 motherboards using 10/100 ethernet switches for about a year in a multichannel visual generation system. We are shifting to SuperMicro P4SAA 2.8 Ghz P4 motherboards with onboard gigabit ethernet and gigabit ethernet switches. Put are hung up because the diskless slave nodes will not load the (Linux) kernel from the master 2.8 Ghz computer.