Displaying 20 results from an estimated 1000 matches similar to: "nopassany parameter causing trouble"
2010 Mar 06
1
[Patch]: Document 'nopassany' in MEMDISK documentation.
'nopassany' is missing in the MEMDISK documentation:
http://www.zytor.com/pipermail/syslinux-commits/2010-February/000096.html
- Gert Hulselmans
commit aeb2406ea701d974c85aa7fdd9af7c53106d7e48
Author: Gert Hulselmans <gerth at zytor.com>
Date: Sat Mar 6 22:33:09 2010 +0100
Document 'nopassany' in MEMDISK documentation.
diff --git a/doc/memdisk.txt b/doc/memdisk.txt
2004 Jun 04
2
chainload cdrom
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:
2014 Mar 04
2
6.03-pre6 minor building suggestions
In Syslinux 6.03-pre6:
_ The txt/html/*.html files are currently created 3 times, one for
each firmware. I think they should be created only once (under the
main txt/html/ directory), just as the rest of the documentation is.
In that case, the <respective_firmware>/txt/html/ subdirectories
should not even be created.
_ The bios/dosutil/ directory contains copybs.com and eltorito.sys,
2014 Mar 15
2
6.03-pre6 minor building suggestions
On Mar 4, 2014 7:42 PM, "Ady" <ady-sf at hotmail.com> wrote:
>
>
> > In Syslinux 6.03-pre6:
> >
> > _ The txt/html/*.html files are currently created 3 times, one for
> > each firmware. I think they should be created only once (under the
> > main txt/html/ directory), just as the rest of the documentation is.
> > In that case, the
2005 Sep 03
3
MSCDEX over NDIS ethernet
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
2011 Nov 13
1
missing syslinux details/docs
I'm running into some issues with regard to isolinux and memdisk, and am
not sure where to ask/look in the best way possible. These are
DOS-related issues.
So here goes:
* Can MEMDISK map a imagefile (compressed? harddisk?) to more than
(and/or beyond) 4GB of memory? Say you'd have 8/16GBGB and want 4GB
available to the user so might as well use the other 4/12GB for MEMDISK.
Or max
2014 Apr 29
2
Issues with syslinux_run_command(str) and parameters
>
> 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
>
2014 Apr 30
2
Issues with syslinux_run_command(str) and parameters
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:
>
2004 Aug 24
3
pxe + memdisk ..??
Hello ALL,
I've got a diskless server working (under Gentoo), booting on it works. (a linux session start with no problem.)
My Big problem, is to get Memdisk to boot with PXE. In fact memdisk is loaded, but it cannot find the img file. I've tried a lot of thing, but nothing works...
tftp use : /diskless
the config file for PXE in then in : /diskless/pxelinux.cfg/
the root for the
2014 Jul 29
2
isohybrid: slint64-14.1.iso: unable to find mac efi image
HI,
In http://slint.fr/misc/MacBoot/ you'll find all context information. All
files referenced here are stored there.
Long story short: once dd-ed on an USB stick the ISO image can boot on
a BIOS or EFI machine, but I want it to be able to boot on most x86_64
Macs with an EFI firmware.
Unfortunately I get the error message:
isohybrid: slint64-14.1.iso: unable to find mac efi image
The
2014 Jul 29
2
isohybrid: slint64-14.1.iso: unable to find mac efi image
> Hi,
>
> > I don't understand why you say "*But* the El Torito...". I don't see
> > a difference with what the mkisofs manual says.
>
> The manual announces "Mac" for Apple Mac.
> The program obviously writes Platform Id 1 in this case.
> The El Torito specs say "Platform ID 0 = 80x86 1=Power PC 2=Mac".
> In the sum this
2014 Jul 29
0
isohybrid: slint64-14.1.iso: unable to find mac efi image
Hi,
> Unfortunately I get the error message:
> isohybrid: slint64-14.1.iso: unable to find mac efi image
This is probably due to El Torito Platform id "Mac" in
-eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \
-eltorito-boot isolinux/macboot.img \
This caused in the image
http://slint.fr/misc/MacBoot/slint64-14.1.iso
platform id 1 with the third image. (I would
2014 Jul 29
0
isohybrid: slint64-14.1.iso: unable to find mac efi image
HI,
On 29/07/2014 22:23, Ady wrote:
> Even without such "Mac" hardware at hand, it might still be helpful
> to test mkisofs 3.01a24 and then check the resulting ISO image.
> Perhaps Didier can update his current version of mkisofs and retry
> with his current scripts/receipts.
I will upgrade the cdrtools package from 3.01a17 to 3.01a24 in the
coming days and see what I
2013 Nov 15
2
Image checksum error while booting Isolinux
Hi,
I am trying to build a custom installer for a popular linux distro on MacOS.
Here is how:
makehybrid \
-o isos/muaaa.iso temp/ \
-eltorito-boot temp/isolinux/isolinux.bin \
-no-emul-boot \
-iso -joliet -boot-load-size 4 \
-default-volume-name "Custom Installer" \
-eltorito-platform temp/isolinux/boot.cat
This happens when I boot up the new image:
2013 Nov 24
2
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
On 11/24/2013 09:56 AM, Ady wrote:
>> The very early code that emits this message is *identical* between
>> Syslinux 4 and Syslinux 6. The biggest difference is the size of
>> isolinux.bin, so it is possible that that might be the source of the
>> problem.
>>
>> -hpa
>
> I wonder if isolinux.bin should be limited to max. 16 sectors (of
> 2KiB
2014 Nov 13
2
Boot fails in a VMware player VM - syslinux 6.03
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,
2015 Oct 22
2
Isohybrid wiki page and UEFI
On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux
<syslinux at zytor.com> wrote:
> 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2
> confs) stored on a iso9660 media by genisoimage and its
> -eltorito-alt-boot -efi-boot $imagefile -no-emul-boot option doesn't
> work. I get a red screen with debug info (attached). However, I'm not
>
2012 Jun 25
1
how to create bootable FreeDOS HDD or USB flash drive?
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
2006 Oct 04
3
Boot image from hard drive from syslinux initiated by a floppy disk boot
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
2014 Nov 13
0
Boot fails in a VMware player VM - syslinux 6.03
>
> 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
> >