similar to: 10 year old question

Is there a non pae version of this repack available? I like the .dat file approach... got to the end of loading the RAM disk image and it said pae not available on cpu and quit Sent from my iPhone > On May 13, 2020, at 4:31 PM, Daryl Kuchay <daryl.kuchay at icloud.com> wrote: > > ?Thank you for your information. I did look at this last week on the murga forum and saw archive.org

Hi All, I used to run webdt.org and this was built to support a tablet computer that hit the market around the late 90?s. DT Research makes them and they get sold to mostly enterprise applications. That being said there are still a few hundred thousand of these in circulation. The hardware is a bit of a hack. Its usb1.1 with a 44 pin flash module on 44 pin pata half height headers. MFGR

/sudo/pseudo code/ On Wednesday, April 23, 2014 9:32 AM, Don Cupp <doncuppjr at yahoo.com> wrote: I actually propose another strategy that may kills many birds with one stone. I think it should be able to be handled internally. Right now, we take a kernel argument as a literal file name hdt.c32 really mean load file hdt.c32. That great, it works, that is how most config files are written.

> > It looks like Clonezilla and Ultimate Boot CD both prescribe > special installation procedures for USB stick. > isohybrids can be put onto stick just by e.g.: dd of=/dev/sdb > Make a backup of the stick if you later want to restore its > partitioning. > The (recent yet not latest) versions of Clonezilla that used Syslinux 5.xx will fail in some systems when writing

Renato, I don't think it would take that long to make a little script that even an XP user could use to generate GPT formatted thumb-drives. I believe someone made the Rufus utility for just such an occasion Rufus - Create bootable USB drives the easy way Rufus - Create bootable USB drives the easy way Rufus Create bootable USB drives the easy way Rufus is a utility that

Then again, I suppose you could have a script in your init that detects when it has been booted from a *special* UUID. In such cases it goes to the first instance of a volume with that *special* UUID and re-writes it to a genuine UUID, as well as updates the syslinux configs on the volume. You could then create your seed image with that *special* UUID and then even an XP user could write it to a

Hi, On 11/11/2014 02:55, Ady wrote: > Again, dd'ing your isohybrid image onto your (virtual or real) drive > will fail to boot in EFI mode. Your "syslinux.efi-based" > "/isolinux/efiboot.img" will not be capable of booting. This is one > of the steps that corresponds to grub2, not to whichever other EFI > bootloader you use (e.g. syslinux.efi). So,

> Syslinux is used to boot many distributions of linux however on this hardware > the most recent version of syslinux that I have seen work is version 3.82 or > version 3.83. If I try a distribution on v4 or newer of syslinux I see the boot > hang on the first line indicating what version of syslinux is being used. Are you saying that official Syslinux 3.86 (the last in the 3.xx)

Hi All, We seem to have a strange problem with our NEC ML4 pcs. When using pxelinux to network boot, we are getting our menu (using menu.c32) when we choose a option the machine just locks up. If the option requires a password it shows the password box , I put in the password and then it locks up. But strangely the machine will boot from local disk which is an option on the boot menu. Our

On 02/24/16 20:45, Shao Miller via Syslinux wrote: > On 2/24/2016 22:55, Shao Miller wrote: >> Suppose...: >> - For non-releases: "git" + We take the first 6 chars of git commit >> - For releases: "ver" + major + "." + minor >> - For tar-balls: Something clever, maybe involving the date >> >> ...that we embed such a version in

On 10/11/2014 04:02, Ady wrote: > >> Hi there, >> >> I failed to boot an installer in a VMware player (Version6.0.3 >> build-1895310) >> using syslinux 6.03, be it off an hybrid ISO image and an USB stick. >> >> Booting succeeds if the VM is set to use a BIOS firmware with both media, >> but fails using an efi firmware. >>

Hi, On Fri, Jul 03, 2015 at 07:13:18AM +0300, Ady via Syslinux wrote: > It is not so clear to me which version of Syslinux (or which version of its > Fedora's packages) you are actually using to boot these systems (not just the one > currently failing). Sorry I wasn't clear. Fedora 19 was installed on a / and /boot partition. I then installed Fedora 21 on a separate /

Because everything I searched on for a PXELinux mailing list pointed me to here. And because PXELinux is a derivative of SYSLinux. If there is a better mailing list for my questions, please let me know. Since you say its possible, care to enlighten me on how to do so? Marc From: Don Cupp [mailto:doncuppjr at yahoo.com] Sent: Tuesday, August 25, 2015 10:58 AM To: Marc Tousignant

I have successfully created bootable USB flash drives containing the following bootable products: 1) Clonezilla (recent version) 2) Ultimate Boot CD (recent version) 3) OpenELEC (recent version) All of these apparently use SYSLINUX as part of the boot process. All three boot up just fine and with no problems at all on virtually all of the various systems that I have here at my

There are no pre-compiled binaries (official or otherwise) on kernel.org. I assume what is meant is https://www.kernel.org/pub/linux/utils/boot/syslinux/ At least, that is where the "downloads" page of syslinux.org directs you. Under there are the various source tarballs (tar.gz format, tar.bz2 format). Also a directory called RPMS/. But that kernel.org RPMS/ directory is devoid of

Hi! I'm preparing what should be a general "network boot" solution for the ones that needs to do network boot on PC without BIOS support / ROM chips. It supports both PXE (like pxelinux.0) and NBI images. I've prepared a precompiled multi-driver image that can autodetect and handle nearly 30 PCI and ISA NICs. My "remote boot kit" contains the same image in 4

> If I may... If I were to say something like "Syslinux doesn't boot", I > would mean that I cannot even get to a simple Syslinux's "boot:" > prompt. In other words, I would mean that _Syslinux_ (in one of its > variants / family members) is failing to boot. Whether the problem is > in Syslinux itself or in some other area (HW, FW, user error, >

> > You are probably imitating / following some procedure used by > > Slackware to create EFI-compatible ISO images. The problem, as > > mentioned in a recent email this last week, is the particularities of > > the documents regarding, in this case, grub2 as EFI bootloader (as > > oppose to documents covering EFI bootloaders in general and clearly > >

In message <BLU0-SMTP557B92590B4CC34F8318088BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Since in all cases you get to see at least the Syslinux copyright >message, the problem doesn't seem to be related to whether your BIOS >can identify the USB disk and boot from it. I can only agree. >Some GA motherboards might identify some USB drives as

> > Hi, > > On 11/11/2014 02:55, Ady wrote: > > Again, dd'ing your isohybrid image onto your (virtual or real) drive > > will fail to boot in EFI mode. Your "syslinux.efi-based" > > "/isolinux/efiboot.img" will not be capable of booting. This is one > > of the steps that corresponds to grub2, not to whichever other EFI > >