similar to: Adding image file support for Windows

Cross-posting to the Syslinux mailing-list. Joakim Schicht wrote: > But part of the question is also about "memdisk raw" vs "memdisk iso". "raw" and "iso" are not mutually exclusive. I think that perhaps you meant "HDD versus El Torito emulation." One can do: LABEL ramwin KERNEL memdisk APPEND raw iso INITRD ramwin.iso > Lets say

> -----Original Message----- > From: Shao Miller [mailto:sha0.miller at gmail.com] > Sent: Saturday, March 12, 2016 10:39 AM > To: Phil Garcia <phil at thinkedge.com> > Subject: Re: [syslinux] Adding image file support for Windows > > On 3/12/2016 13:16, Phil Garcia wrote: > > On 3/12/2016 12:21, Shao Miller wrote: > > > >> On 3/11/2016 22:32, Phil

On Wed 5/5/2010 3:28 AM Miller, Shao wrote, ---------------------------------------------- Good day again Matthew, As per (c=80) * (h=2) * (s=48) * (sect_size=512) = 3,932,160 bytes = 7,680 sectors: For Windows, you might enjoy: - "DD for Windows" by John Newbigin and chrysocome[1] - "ImDisk Virtual Disk Driver" and "Zero and Random Device Driver" by Olof

On 3/11/2016 22:32, Phil Garcia via Syslinux wrote: > I would like to request that SYSLINUX be extended to install on a filesystem > image file on the Windows platform. This feature is available on Linux > (option -t); however, on Windows SYSLINUX only installs with a raw device > path. > > This feature would be use by another open source project. As an small > incentive,

Hi. I'm working on replacing a PXELINUX/MEMDISK loaded DOS based installation image with a PXELINUX/MEMDISK loaded WinPE ISO image. So far everything seems to work well (appending "bigraw" to memdisk solved booting problems on several machines), but I kind of miss the option of using getargs.com to get/set environment variables from the memdisk command line. Is there any way to

Does someone know where I could get my hands on an ima that's larger than 2.88meg... I use winimage for all my ima's and stuff but i'm having trouble configuring a custom size. If anyone has a large ima I could utilize that would be great, preferably one fitting this memdisk supported size: 3,932,160 bytes (3840K) c=80 h=2 s=48 3.5" DSED (extended) If not instructions on making

I tested the memdisk-acpi branch with following results: - Bochs The BIOS provides a RSDT. Available tables are RSDT, FACP, DSDT, FACS, APIC, SSDT. memdisk-acpi is able to hook the SSDT. - VMware The BIOS provides a RSDT and XSDT. Available tables are RSDT, FACP, DSDT(*), FACS(*), BOOT(*), APIC(*) and XSDT, FACP, DSDT(*), FACS(*), BOOT(*), APIC(*). Tables marked with an asterisk (*) are

After so much time and improvements, I'm glad to see and publicize a pre-release, 6.04-pre1 in https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ Personally, I've already been working testing the pre-release as-is and my tests have been positive so far. I appreciate feedback like that from Gabriele Balducci and testing "make bios installer". Yes, there are a

I am currently unable to get Syslinux v6.03 to load kernel + ramdisk when booting from a PXE server in EFI mode. Is this a feature that is currently supported? If not, is there a known time frame for which support will be added? Thanks. -Bryan

Hi there, i just build a new ipxelinux.0 with an EMBED=../../syslinux-5/core/pxelinux.0. i'm trying to load up my vesamenu.c32 menu from http:. and offcorse i want this as optimal as possible, with the least needed GET requests. OLD situation with v4: PXE ROM -> ipxelinux.0 (tftp) -> menu.php (http) -> vesamenu.c32 (http) NEW situation with v5: PXE ROM -> ipxelinux.0 (tftp)

I have set up a RHEL 5.7 PXE server and trying to get a WinPE ISO to work. Currently PXE seems to handle the image properly but the process stops after Loading boot sector... booting... Full list of what is going on. Ramdisk at 0x72b9c00, length 0x0a680000 command line: iso initrd=../images/windows/winpe_x86.iso BOOT_IMAGE=../memdisk Disk is hard disk 0, 170496 K C/H/S = 340992/1/1 Total size

I am trying to build an RPM starting from the TAR archive. The relevant error is: make[1]: Entering directory `/tmp1/Software/rpmbuild/BUILD/syslinux-5.00/libinstaller' perl bin2c.pl syslinux_bootsect < ../core/ldlinux.bss > bootsect_bin.c perl bin2c.pl syslinux_ldlinux 512 < ../core/ldlinux.sys > ldlinux_bin.c perl bin2c.pl syslinux_mbr < ../mbr/mbr.bin > mbr_bin.c perl

As you know, the Linux version of syslinux supports mount points. But for the Win32 version, it only supports drive letters as in: syslinux ?ma e: However, drive letters are not always available, such as drives mounted to NTFS folders. In order to install syslinux to these drives, future release of syslinux should support using mount points as the drive spec; or alternatively, support disk

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

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 Syslinux core and in all OS programs and modules. Maybe even with some nearby magic so that a "whichver" command can examine and answer.

On 3/8/2016 07:23, Pete Batard via Syslinux wrote: > [...] the merging of ldlinux.sys and isolinux.bin, which I would very > much like to rally people on this list into seeing as beneficial. [...] My understanding is that isolinux.bin and ldlinux.bin are pretty much twins[1]. If I understand correctly, you'd like the latter to be tacked onto the former because people are too stupid

With companies like Facebook and Google offering cash prizes for people who can find security holes in their products, has there ever been any consideration given to offering cash rewards to people finding security exploits in CentOS or in commonly bundled services like Apache? (Provided of course they follow "responsible disclosure" and report the exploit to the software authors

Hello everyone, I am trying to PXE boot my Acer Aspire G3-773G laptop. It uses UEFI, so I load 64bit syslinux.efi (v6.03) and it automatically loads ldlinux.e64. All is fine. But when I want to use cmenu.c32 (with UI cmenu.c32 in the config file), the loader downloads: * cmenu.c32 * libmenu.c32 * libcom32.c32 * libutil.c32 Then syslinux reports: "unable to load cmenu.c32:

I'm trying to boot bartpe from gpxelinux I'm using gpxelinux and memdisk. my pxelinux.cfg/default looks as follows LABEL bartpe kernel memdisk initrd http://<path to iso> append iso raw Both of these I think I have working correctly. So my question I guess is for people that may have done this? Anyways I see the bartpe load screen then the xp load screen and then it blue

On 02/27/2010 10:31 PM, swdamle at bsnl.in wrote: > Hello, > This has reference to ""Dos installer" from Win98se in Syslinux-3.84. > > Sorry to say the problem CONTINUES with Syslinux-3.85. Following is > for your reference please. > You may want to try: http://www.zytor.com/~hpa/syslinux/syslinux.com ... which is compiled with debugging information turned