similar to: Can USBstikA boot USBstkB ?!

Gene Cumm wrote:- >TC64 still has ISOLINUX. The basics are to use chain.c32 to boot >USB-B:p3 but syntax depends. Ideally, it's a modern enough Syslinux >version that you can use the "guid" or "label" options to auto-detect >its location rather than "chain.c32 hdN M". Hopefully your FS >label/GUID is unique sdb3 Boot Primary

Amazing how zillions of us victims tolerate web-based gmail ? On 12/10/17, eas lab <lab.eas at gmail.com> wrote: > Gene Cumm wrote:- >>TC64 still has ISOLINUX. The basics are to use chain.c32 to boot >>USB-B:p3 but syntax depends. Ideally, it's a modern enough Syslinux >>version that you can use the "guid" or "label" options to auto-detect

On Sat, Dec 2, 2017 at 10:35 AM, eas lab via Syslinux <syslinux at zytor.com> wrote: > AIM: from <isolinux> on USBstikA, > boot Debian7 installation on USBstikB. I thought we answered this but perhaps it's not the "Can I boot ISOLINUX/SYSLINUX from USB-A and boot to USB-B" whose short answer is "No" but long answer is "It depends on the BIOS/CSM

PS. Since I've now only got a laptop, I mostly use TinyCore linux; which is also sysylinx booted; and makes provision for *THE SLOW REACTION TIME OF SOME USB DEVICES*; which may be the subtle cause of my problem in trying to boot a second USBdevice [other than the <boot device>]. WDYS? On 6/14/17, eas lab <lab.eas at gmail.com> wrote: >> I don't think that syslinux be

]You seem to be assuming that changing from a direct SATA and IDE ] connections to some USB adapter would have no impact on how the ] respective HDDs are recognized/detected by the BIOS. ] You seem to be ] assuming that the BIOS from 2 different PCs/Laptops would recognize all ] your devices in the same exact way and that there would be no changes ] in behavior or in supported features by the

> ]You seem to be assuming that changing from a direct SATA and IDE > ] connections to some USB adapter would have no impact on how the > ] respective HDDs are recognized/detected by the BIOS. > > ] You seem to be > ] assuming that the BIOS from 2 different PCs/Laptops would recognize all > ] your devices in the same exact way and that there would be no changes > ] in

> I don't think that syslinux be in concern here. If I understand well > Slackware is installed on a hard disk partition that you want to access > through the USB-adaptor to IDE/SATA. No. I'm not married to Slak. It's important to distinguish between verbatim/pasteable and what the old-writer merely thinks/remembers. I want to be able to boot ANY installation/partition as I

> I don't think that syslinux be in concern here. That's why I pasted the `ls -l` of the directory: to show that the previous working USBstik was *SYSLINUX* based.

> Yes this is the SAME question, that I can't get an answer from a month ago! > > I have the files, from a USBstik [now stolen] which I previously could > edit at boot time, to boot any of my IDE or SATA partitions. How exactly were you editing (something)? Do you mean that you somehow changed some boot command from the Syslinux boot prompt during boot? In that case, which

[quoted lines from Ady Ady]: > At this time, Syslinux by itself cannot boot files located on a > different filesystem volume. > Using chain.c32, you can load a boot sector (MBR or VBR) located on > another device. Since the list of files located in your boot stick did > not include chain.c32, my assumption (and not only mine, if you > carefully read some of the prior

Yes this is the SAME question, that I can't get an answer from a month ago! I have the files, from a USBstik [now stolen] which I previously could edit at boot time, to boot any of my IDE or SATA partitions. Now, with a laptop, I want to boot the same IDE or SATA via a USB-adaptor to IDE/SATA. And also I want to boot a Toshiba 500GB USB disk. The obvious question is: why [if] the old system

Hi there!! I has been modified the syslinux.cfg file according to the rules to add some boot parameters but since this modification, every time I that I highlight the modified entry in the boot menu and hit the TAB button on my keyboard, the entry's boot parameters is displayed twice and when I try to "backspace" them out, the line again get displayed twice and so on. So my

So ever since syzbot discovered fbcon, we have solid proof that it's full of bugs. And often the solution is to just delete code and remove features, e.g. 50145474f6ef ("fbcon: remove soft scrollback code"). Now the problem is that most modern-ish drivers really only treat fbcon as an dumb kernel console until userspace takes over, and Oops printer for some emergencies. Looking at

Hello all, I have a few questions about the menuing system that I haven't been able to find in the archives (it would be nice if they were available in a searchable form other than having to click on a month-by month basis and read through them - if they are searchable I would love to find a way to do this but it hasn't jumped out at me). My first question is : What is menu.c32? I

So ever since syzbot discovered fbcon, we have solid proof that it's full of bugs. And often the solution is to just delete code and remove features, e.g. 50145474f6ef ("fbcon: remove soft scrollback code"). Now the problem is that most modern-ish drivers really only treat fbcon as an dumb kernel console until userspace takes over, and Oops printer for some emergencies. Looking at

There is a maximum of 255 characters of parameters you can pass to the kernel. At least that's what I recall, but I may be wrong. -----Original Message----- From: Roberto De Leo [mailto:deleo at unica.it] Sent: Thursday, October 03, 2002 5:19 PM To: syslinux at zytor.com Subject: [syslinux] maximum number of characters in APPEND Hi, I wonder whether there is a maximum number of

Hi Daniel, CC linux-fbdev Thanks for your patch! On Thu, 29 Oct 2020, Daniel Vetter wrote: > So ever since syzbot discovered fbcon, we have solid proof that it's > full of bugs. And often the solution is to just delete code and remove > features, e.g. 50145474f6ef ("fbcon: remove soft scrollback code"). > > Now the problem is that most modern-ish drivers really

On Wed, Oct 28, 2020 at 8:02 PM Thomas Zimmermann <tzimmermann at suse.de> wrote: > > Hi > > Am 28.10.20 um 17:06 schrieb Daniel Vetter: > > So ever since syzbot discovered fbcon, we have solid proof that it's > > full of bugs. And often the solution is to just delete code and remove > > features, e.g. 50145474f6ef ("fbcon: remove soft scrollback

I am using the following simple menu and have noticed that items at the bottom are dropping off. I seem to be limited to 12 items. Is there a limit to how many items can be on the simple menu? default pxelinux.cfg/menu.c32 prompt 0 MENU TITLE UWSP PXE Boot Menu # TIMEOUT 200 LABEL bartpe MENU LABEL Build 12 KERNEL /STARTROM.0 APPEND keeppxe LABEL 11dnet MENU LABEL Build 11DNET beta

Hi there Gene! Thanks you about your quick response!! As for your request, here is my whole Syslinux.cfg file: default /syslinux/vesamenu.c32 prompt 0 timeout 00 menu hshift 15 menu width 49 menu title Boot menu menu background /syslinux/splash.png menu color title * #FFFFFFFF * menu color border * #00000000 #00000000 none menu color sel * #ffffffff #76a1d0ff * menu color hotsel 1;7;37;40