similar to: Boot USB:SATA:Partition4 from USBstik?

When a USBstiked-syslinux starts, it's the PC's firmare that's reading the USB ? But once the USBsyslinux takes over, has IT also got a USB driver? Since my MotherBoard & 2009 Slackware built USBstik syslinux booter were stolen I bought a <WinTel> laptop and USBextender to access my old IDE & SATA disks. With WinTel's new arrangement of not allowing the tail of the

>Do you mean boot SYSLINUX from stik-A but then load files like a >kernel/initrd from stikB:partition5? It's possible but only from a >development version of Syslinux that has the multifs patch merged. Yes: before my x86MotherBoard & <syslinux>USBstik were stolen, I could edit the <syslinux prompt> to boot to different partitions of the attatched IDE & SATA. Now

On Mon, May 1, 2017 at 7:45 AM, eas lab via Syslinux <syslinux at zytor.com> wrote: >>Do you mean boot SYSLINUX from stik-A but then load files like a >>kernel/initrd from stikB:partition5? It's possible but only from a >>development version of Syslinux that has the multifs patch merged. > > Yes: before my x86MotherBoard & <syslinux>USBstik were stolen,

When a USBstiked-syslinux starts, it's the PC's firmare that's reading the USB ?. But once the USBsyslinux takes over, has IT also got a USB driver? So that USBsyslinux can install a different USBstik/partition? Ie. boot with stikA to install & run stikB:partition5 ? ------------ Is the following sound logic? > Do zero out the partition table first so you don't

Previously I've been using a laptop with an "Aptio Setup Utility...2015" to "Disable UEFI Boot" and allow a USBstik with partition1 having: /boot/isolinux/isolinux.bin , isolinux.cfg , menu.c32...etc. to boot 64bit TinyCore. Now this newer laptop has: "Aptio Setup Utility...2018" which is completely different from the 2015 version. I fail to boot linux from

Internet reports that I'm 1-of-many victims, failing to run linux on new/cheap laptops. Eg. quad-Atom; connex L1470. What is syslinux's recomended method to overcome <WinTel's UEFI lockout> using a USBbootStik ? Are wifi drivers: RTL8723BS for linux available yet ? ==TIA.

I've been using linux:TC from a USBstik in order to not break the M$ capability, as previously always happened. Since TC runs in RAM, it has many extra problems; like reinstalling all the apps and your private settings at each boot. The sample isolinux.cfg which I've been emailed by the oficianado is very unfamiliar and worrying. Where is the official syntax ? -- Without knowing if/how

Dear, I always used dovecot in version 2.0 and in the last month i update my servers to dovecot 2.2 but now i have problems with comand dovecot import, not works for me, bellow i put 2 examples used in my tests in boths cases not works for me. Someone already saw some case similar or can help me with this ? doveadm import -u teste at aaaaa.com mdbox:~/mdbox-backup "" mailbox INBOX from

> 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

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

AIM: from <isolinux> on USBstikA, boot Debian7 installation on USBstikB. EXISTING STATE: USBstikA is TinyCore64bit booter, with:- /boot/isolinux/* 61312 Oct 26 2016 menu.c32 24576 Oct 26 2016 isolinux.bin 2069 Nov 22 01:24 isolinux.cfg ... USBstikB-partition3: Currently boots a 32bit installation, via GRUB using the entry:----- menuentry 'Debian GNU/Linux, with Linux

My previous question: "can syslinux on a USBstik also boot installations on other USB devices ?" got no proper reply, so I'm now including more background detail. The new problem is that my 32bit partition of ETHOberon, only gives a proper font-size under Debian7:DVDinstaller:rescueMode, since I'm forced to use a laptop, after my previous systems were stolen. Neither gnome nor

On Sunday, December 8, 2019, 07:42:43, eas lab via Syslinux wrote: > Internet reports that I'm 1-of-many victims, failing to run linux > on new/cheap laptops. Eg. quad-Atom; connex L1470. > What is syslinux's recomended method to overcome <WinTel's UEFI > lockout> using a USBbootStik ? Syslinux should work fine with UEFI (it does for me), and if for some reason you

> On Sunday, December 8, 2019, 07:42:43, eas lab via Syslinux wrote: > > > Internet reports that I'm 1-of-many victims, failing to run linux on > > new/cheap laptops. Eg. quad-Atom; connex L1470. What is syslinux's > > recomended method to overcome <WinTel's UEFI lockout> using a > > USBbootStik ? > > Syslinux should work fine with UEFI (it

> 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.

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

> 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

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