search for: ufd

Hi, I would like to ask if there are any known issues with booting an ISOLINUX hybrid iso image from a USB Flash Drive on older Dell PC's (i.e. P4 2.2GHz). I've tried several that one should just be able to write to UFD and boot, but they all fail on my hardware. I get "isolinux.bin missing or corrupt" message on screen. This function would be very convenient for me, so I'd like to find out if there's anything I can do to get it working. Thanks!

I have a USB flash drive that I'd like to image, and then load that image via pxelinux and memdisk. The flash drive was formatted under Windows 98 SE as FAT, and boots just fine on its own. The PXE boot process gets as far as loading the image via memdisk, but then when the boot process switches over to the RAM disk, it fails: [...PXE diagnostic information...] Loading boot

Just tried the latest release and found a minor bug. Have a UFD w/ SYSLINUX, which boots a simple .BSS image no problem. Launching exactly the same image on a ISOLINUX disc fails w/ the following error msg: Invalid image type for this media That's it for this msg. Later....Jet -- Powered by Outblaze

I'm working on a debugging/diagnostic image in order to debug/diagnose an issue with very recent machines using a UFD (USB Flash Drive) which really _should_ be partitioned but someone decides to be a little too quick and uses it raw. (FAT* file system on /dev/sdb rather than /dev/sdb1). Anyways, I've got a successful first iteration that'll say what the BIOS thinks about geometry and fetches key sectors...

...link branch? I figured since I had a concern for how the CLI is implemented and how it would impact serial performance (I have machine where the sole physical console is a serial port and can't recall if it will let me adjust rates from Syslinux). When I tried quickly with a 2GB unpartitioned UFD (flash drive) with a 16 MB test FAT file system, it really didn't get too far other than display some memory-related info and drop me to a prompt that didn't know about the configs at all. I also tried the same UFD fully partitioned with FAT file system and got the same results. Am I doin...

Hello, Is it possible for syslinux to boot from a different partition ? I have a UFD with 2 partitions. The first one is fat32 and the second one is a squashfs. I have the OS files in the squashfs partition. As the syslinux won't boot from a squashfs partition, I thought of creating a fat32 (first partition) and install syslinux in it. If I do that, is it possible to configure...

...ot at stream:~# uname -a Linux stream 2.6.32-13-pve #1 SMP Mon Jul 9 08:39:20 CEST 2012 i686 GNU/Linux root at stream:~# icecast2 -v Icecast 2.3.3-kh2 googling only resulted in the source code of the error: http://svn.xiph.org/icecast/branches/kh/icecast/src/connection.c <snip> if (ufds[i].revents & (POLLNVAL|POLLERR)) { ERROR0 ("signalfd descriptor became invalid, doing thread restart"); slave_restart(); // something odd happened } </snip> any ideas what my be the cause of my problems? thanks rob

...to non LBA ([2] - also see the comment at line 822). I seem to recall that, unless you did that, you would indeed run into trouble during boot. Oh, since it might be useful for OP's testing, I should probably point out that Rufus can also be used to install a blank Syslinux v4 or v5 on an UFD (so you if you add something with a config file and some .c32, you should be able to test whether the Syslinux versions that are embedded in Rufus can boot). This is an advanced feature, so it is not available in default mode, but if you want to enable it, just click on the white arrow near &qu...

...> One such example that was fairly common back then was a simple transformer > that had two primary windings and two secondary windings. One could buy > them as 1:1.5 (600 ohm to 900 ohm), 1:1 (600 ohm to 600 ohm), and other > commonly used impedances. The transformer along with two 2.0 ufd > capacitors allowed DC to pass through, but changed the impedence from > one value to another. I've thought of using a transformer by itself, but obviously that wouldn't let the DC signals required for looping through. Could you give me an ascii schematic? > > As far as subs...

Hi, I'm trying to install debian-6.0.5-amd64-CD-1.iso from USB memory-stick. The problem is, that Debian-Installer is not able to "Detect and mount CD-ROM" during the installation process. The USB memory-stick is a 2GB model containing MBR and FAT32 file system: # fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160

....32-13-pve #1 SMP Mon Jul 9 08:39:20 CEST 2012 i686 > GNU/Linux > root at stream:~# icecast2 -v > Icecast 2.3.3-kh2 > > googling only resulted in the source code of the error: > http://svn.xiph.org/icecast/branches/kh/icecast/src/connection.c > > <snip> > if (ufds[i].revents & (POLLNVAL|POLLERR)) > { > ERROR0 ("signalfd descriptor became invalid, doing thread > restart"); > slave_restart(); // something odd happened > } > </snip> > > any ideas what my be the cause of...

Greetings, I wonder whether there are any plans to build udflinux or the likes. I've searched through the mailing list, finding out that should I create a mixed ISO9660/UDF filesystem. Unfortunately, that is not an option if I want to use a significant feature of UDF filesystem, which is writing. Making a mixed ISO9660/UDF, using mkisofs -udf, will (to my best knowledge) not allow me to

I'm posting as an FYI. I was testing BIOS A04 with a UFD (USB Flash Drive) but it probably applies to everything that looks like a USB hard drive. My previous statement was partially incorrect as I did find a scenario to the contrary. I tried with FDD then CD at the top of the list and tried with both just disabled (without reordering first). I tried...

I have a isohybrid-ized image (isohybrid.pl from syslinux-4.03, no options passed) which works on several other systems, but can't boot a Kontron CG2100 from stick (same image boots fine from a portable CD-ROM drive though). The BIOS shows its initial splash, accesses the stick, then the system reboots - no errors logged in the BIOS event log. I tried disabling the "USB boot

Is there a cable length limit to use with a fxsmod (TDM400B) ? I noticed that if I use a very long cable 148 feet, I can hear some parasite : I hear the radio ! If I use a short cable, there is no problem... Thanks for help, St?phane HENRY

...oll.c +++ klibc-1.3.7/klibc/ppoll.c @@ -3,6 +3,9 @@ */ #include <sys/poll.h> +#include <sys/syscall.h> + +#if defined(__NR_ppoll) __extern int __ppoll(struct pollfd *, nfds_t, struct timespec *, const sigset_t *, size_t); @@ -12,3 +15,5 @@ { return __ppoll(ufds, nfds, timeout, sigmask, sizeof *sigmask); } + +#endif --- klibc-1.3.7.orig/klibc/SYSCALLS.def +++ klibc-1.3.7/klibc/SYSCALLS.def @@ -21,7 +21,7 @@ <?!ia64> pid_t clone::__clone(unsigned long, void *) <?ia64> pid_t clone::__clone2(unsigned long, void *, void *) # if ! _KLIBC_NO_MMU...

Another app I would like to run is Ghost32.exe. This is their "old school" version that looks awfully like Windows 3.1 and is a "self contained app" meaning that on Windows machines I just take the Ghost32.exe to another device and it will launch. No "install" is really ever done. When trying to launch in wine I get the following errors: $ wine ghost32.exe

I used syslinux 4.03 for my brand new usb-stick (16GB FAT32, no Partition Table). It works, but on some computers i get "boot error". My investigation reveals three bugs in the boot code. Int 13 function 8 destroys the contents of register ES. Ah, now it is corrected in version 4.04 pre 5. Well done. I am happy now. But there are still other bugs. Look on version 4.04 pre 5,

Hi, ? I tried to use the syslinux.exe (version 4.04)?to make my usb drive bootable. When i run the syslinux.exe with the respective options I get this error ? "Accessing physical drive: The request is not supported. Did not successfully update the MBR; continuing..." ? I have administrator privilege and I started cmd prompt with "Run as Administrator" option too. I tried the

...012 i686 >> GNU/Linux >> root at stream:~# icecast2 -v >> Icecast 2.3.3-kh2 >> >> googling only resulted in the source code of the error: >> http://svn.xiph.org/icecast/branches/kh/icecast/src/connection.c >> >> <snip> >> if (ufds[i].revents& (POLLNVAL|POLLERR)) >> { >> ERROR0 ("signalfd descriptor became invalid, doing thread >> restart"); >> slave_restart(); // something odd happened >> } >> </snip> >> >&g...