similar to: Problem booting Fujitsu Amilo Xa 2528

Hello Sam, I've got a Fujitsu Siemens Amilo Pro V3515 laptop, with a builtin autheros-wifi card, but I can't get it working. I am running FreeBSD 7.0-STABLE, I don't know whether it works in -CURRENT. Over here I have the dmesg: http://junk.quis.cx/VNViVksv/blackbox.dmesg.txt I haven't compiled it in, it didn't boot that way (kernel panic iirc). When I kldload if_ath I get

On 01/11/2013 05:36, Ady wrote: > >> That is with syslinux 4.05 on Slackware-14.0: >> >> bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso >> catalogue offset: 561 >> ve[0]: 1, cs: 1 >> ve[1]: 0, cs: 1 >> ve[2]: 0, cs: 1 >> ve[3]: 0, cs: 1 >> ve[4]: 0, cs: 1 >> ve[5]: 0, cs: 1 >> ve[6]: 0, cs: 1 >> ve[7]: 0, cs: 1

Hi, Ady wrote: > so, why the original isohybrid image from Debian and many other > isohybrid images have mostly (but not all) "00s" in place of the "90s"? That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. * Fedora has it with EFI FAT filesystem in one partition

That is with syslinux 4.05 on Slackware-14.0: bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso catalogue offset: 561 ve[0]: 1, cs: 1 ve[1]: 0, cs: 1 ve[2]: 0, cs: 1 ve[3]: 0, cs: 1 ve[4]: 0, cs: 1 ve[5]: 0, cs: 1 ve[6]: 0, cs: 1 ve[7]: 0, cs: 1 ve[8]: 0, cs: 1 ve[9]: 0, cs: 1 ve[10]: 0, cs: 1 ve[11]: 0, cs: 1 ve[12]: 0, cs: 1 ve[13]: 0, cs: 1 ve[14]: 21930, cs: 21931 ve[15]: 43605, cs:

> I built a Slackware package for 4.07, upgrading fro 4.05, ran isohybrid on a copy of the ISO image and got again > "seek error - 3: Invalid argument" > > Just wondering: is it possible that the bug correction made in 4.06 wasn't ported to 4.07? > > Or should I upgrade another component? I would suggest using the official binary files already included in

High all, In WinXP, I have created file "image.iso" using mkisofs, but unable to postprocess with the "isohybrid". I worked as follows: cd F:\syslinux-4.05\utils F:\syslinux-4.05\utils> isohybrid F:\image.iso and received >'isohybrid' is not recognized as an internal or external command, operable program or batch file. What next? Thanks in advance.

> > I ponder whether it would be possible to create a diagnostic MBR > which does not necessarily have to boot but rather tells what the > isohybrid MBR would perceive: Presence of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... > > One could preserve the isohybrid MBR of an ISO and replace it by >

I've got an embedded x86 system built with Yocto, which boots from a USB flash drive. It uses a loop mount to give access to an ext3 root file system contained within a FAT16 file, which means it has persistent storage. What I want is something that boots from the flash drive, but copies everything into a large RAM disk, and runs from there, so that it doesn't touch the flash drive once

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

On 01/08/2013, at 24:37, Gene Cumm <gene.cumm at gmail.com> wrote: > On Wed, Jul 31, 2013 at 7:36 AM, Daniel O'Connor <doconnor at gsoft.com.au> wrote: >> Hi, >> I am trying to create a hybrid ISO image for FreeBSD 9.2 using syslinux 6.01 and isohybrid.pl I found at http://www.overclockix.com/sources/isohybrid.pl (I know there is a C version in syslinux but I

> Hi, > > Ady wrote: > > http://repo.or.cz/syslinux.git/tree/HEAD:/diag > > "handoff.bin > > This does not look like it would tell much of the properties in question. > Nevertheless its print functions might be of interest for an isohybrid > diagnostic MBR. > > > > and at least 2 geodsp*.{bin,img(gz)} > > I am now reading >

> Hi, > > > Not being compatible with EFI/GPT is already a problem for the Perl > > variant. > > The relation of both is: > > isohybrid.in/.pl is being left behind. > http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/Makefile > has: > SCRIPT_TARGETS += isohybrid.pl # about to be obsoleted > > isohybrid.c replaces it feature-wise

Thomas Schmitt wrote: > I ponder whether it would be possible to create a diagnostic MBR > which does not necessarily have to boot but rather tells what the > isohybrid MBR would perceive: Presence of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... ... > The diagnostic MBR should only use 432 bytes because at

Hi, My wife and I live in a two-storey flat, and we have a small home LAN (100% CentOS 5) with a "classical" configuration: On the ground floor, there is the telephone jack with the DSL modem router (192.168.1.254). This modem has a mini-switch with two Ethernet jacks to it, and the two are used by: - the server (192.168.1.1), a "black box" running in a cupboard 24/7 -

When call isohybrid with option '-u', it overflows on a 32 bits host. It seeks to 512 bytes before the end of the image to install gpt header. If the size of image is larger than LONG_MAX, it overflows fseek() and cause error: isohybrid: image-x86-64-20140505110100.iso: seek error - 8: Invalid argument Replace fseek with fseeko to fix this issue. Signed-off-by: Kai Kang <kai.kang at

> Hi, > > Ady: > > Since both included variants are currently different, and both > > variants have problems > > I am not aware of problems of the perl version. It is just lacking > the newer features which support EFI/GPT and Mac/APM. > The known bugs of isohybrid.c are with those newer features. > http://www.syslinux.org/archives/2012-May/017843.html >

> Hi, > > > All the "isohybrid.exe" I know of are based on the Perl variant. > > I just got one from > http://www.filewatcher.com/m/isohybrid.exe.39568-0.html > > Its strings seem not to stem from isohybrid.pl. > > Digging in slitaz source brought a shell script (that would be > variant #5 then): >

> Hi, > > at [Tails] we're in the process of shipping hybrid ISO images by > default again. We're using `isohybrid -h 255 -s 63' to do that (thanks > to the advice we got on this mailing-list a few months ago!). > > And then, we've discovered that sometimes, isohybrid produces ISO > images whose size is not a multiple of 2048 bytes. > > Who cares?

Dear list, I have been trying to debug a build failure for a while in the utils directory on isohybrid which seems to be distro specific. On Fedora 17 64bit the build completes without problems, but under both Ubuntu 32/64bit 11.10 and 12.04 I get the following: tim at oxygen:/usr/src/git/syslinux/utils$ make gcc -O2 -luuid -o isohybrid isohybrid.o isohdpfx.o isohybrid.o: In function

Hi, i wrote: > > Well, it is about really usable capabilities of isohybrid, Ady wrote: > but their practical combination, usage, effects, > goals... are not expressed clearly enough for the common user to put in > practice. How to express the embarrassing fact that ISOLINUX is not ready for UEFI but isohybrid is ? http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI would