similar to: syslinux.com 5.01 pre3

In other words: I'm suggesting to use WinImage as it also allows easy injection of new files *and* updating of already existing files. May I ask which vendor is distributing a DOS FW update that is 20MB? I'd like to see the files. Sometimes you just need the .bin/.rom and the actual FW update EXE and it would fit a 5MB FDD image. On Mon, Jun 18, 2018 at 2:03 PM, R S <rene.shuster at

The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. If you are interested I could provide a 5MB FDD image template based on FreeDOS 2041 kernel (the latest available at that time in 2014) where you would just inject your ROM and EXE (and possibly adjust autoexec.bat to autostart/apply the FW update). It's a minimal FreeDOS FDD image that defaults to a clean boot with

Compile issue with tools/libfsimage/iso9660 char vs unsigned char signedness causes a warning when compiling iso9660 (xen-unstable). This patch changes the unsigned char * for char *. Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> diff -r 8eff89a69521 tools/libfsimage/iso9660/fsys_iso9660.c --- a/tools/libfsimage/iso9660/fsys_iso9660.c Fri Mar 02 18:42:00 2007 -0500 +++

Xen i386 xen-head.S fix sections mixup xen-head.S does not come back to the data section, leaving the text section as current section. It causes problems with a slightly enhanced DEBUG_RODATA that supports CONFIG_HOTPLUG and bringing a CPU up after the text has been marked read-only: reference to early_gdt_descr causes a page fault. It applies on 2.6.22-rc2-mm2. Signed-off-by: Mathieu Desnoyers

Hi folks, Syslinux 5.00 is out in time for the holidays. This release includes a lot of changes from 4.06. I've included the NEWS entries below, which highlight the major changes. Lots of assembly code has been rewritten in C, which makes further development much easier (and also really helped for the 'firmware' abstraction that appears in Syslinux-6.00-pre1). So be on the lookout

Xen i386 xen-head.S fix sections mixup xen-head.S does not come back to the data section, leaving the text section as current section. It causes problems with a slightly enhanced DEBUG_RODATA that supports CONFIG_HOTPLUG and bringing a CPU up after the text has been marked read-only: reference to early_gdt_descr causes a page fault. It applies on 2.6.22-rc2-mm2. Signed-off-by: Mathieu Desnoyers

Xen i386 xen-head.S fix sections mixup xen-head.S does not come back to the data section, leaving the text section as current section. It causes problems with a slightly enhanced DEBUG_RODATA that supports CONFIG_HOTPLUG and bringing a CPU up after the text has been marked read-only: reference to early_gdt_descr causes a page fault. It applies on 2.6.22-rc2-mm2. Signed-off-by: Mathieu Desnoyers

Hello! First, thank you Julian for the useful plugin ''unicode_hacks'' < http://julik.textdriven.com/svn/tools/rails_plugins/unicode_hacks/>. I have found some problems running my app in development on Webrick and looking at it with Safari (MacOS X 10.4.3, Safari 2.0.2). Some files are sent with different sizes (e.g. default css example, or controls.js ), and it

I noticed that, when decoding an ogg vorbis file that was encoded with the xiph library, that the comment header and setup header are encoded on one page. Okay, the vorbis documentation says you can do this, no problem. My question is, the lacing values seem to indicate where the packet boundaries for the two of these are, is this required, or is this just a hint? Further, I'm seeing

I noticed that LLD doesn’t preserve the symbol type for a defsym directive. For example: $ cat f.c void f() {} $ clang -c f.c $ ld.lld -shared --defsym=g=f f.o $ objdump -T a.out DYNAMIC SYMBOL TABLE: 00000000000012a0 g DF .text 0000000000000006 f 00000000000012a0 g D .text 0000000000000000 g f is marked as a function symbol, but g is not. I recognize this is hard to do in the general

Hi all, I have just started playing with speex, and come up with the following code, which just encode a frame of 160 shorts, and the decode it. For some reason the decoded sample is completely different than the original one. is my code wrong? If so what? Or is it a reasonable which depends of values that weren't correctly set? Thanks, Andre #include <stdio.h> #include

> > C_ While initially thought to be a problem with the INCLUDE > > directive, now it seems the problem is the second parameter of the > > CONFIG directive. The second parameter of the CONFIG directive (which > > sets a new CWD) doesn't seem to work correctly (tested with pwd.c32), > > specially when the new cfg file (the first parameter of the CONFIG >

I know it's really early in the project's life, but another question I had: How does the generated 68K code perform, at least compared to modern GCC? -- Chris

Hi,    I''ve been using xVM with no problems since 2009.06 release (centos4/5, rhel4/5, sol10 as guests). This was using the 111a version. Just installed a new server with the 111b version and .... virt-install --nographics -p -r 8192 -n CentOS_48_64_92 -f /dev/zvol/dsk/zm0/vm/CentOS_48_64_92 -l ftp://192.168.101.120/pub/CentOS-48 -w bridge=aggr0 --os-type=linux --os-variant=rhel4

Thank u Thomas...U just made my day ! Here the result www.claudehussenet.com Drag and drop of portlets ! See http://wiki.script.aculo.us/scriptaculous/show/SortableListsDemo -- uses SVN trunk code, and the new dropOnEmpty option. Thomas Claude Hussenet Independent J2EE Architect Consultant http://claudehussenet.com ____________________________________________________ Start your day

Just a heads-up even though it''s probably not remotely sploitable:: Unprivileged local users can gain elevated (root) privileges. http://www.securityfocus.com/archive/1/386436/2005-01-04/2005-01-10/0 http://isec.pl/vulnerabilities/isec-0021-uselib.txt

I'm putting Syslinux 3.82 on a short bug fix cycle. As a result, it will be based on the former for-3.81 branch (now renamed syslinux-3.8x) instead of the master branch. Fixed so far: Changes in 3.82: * isohybrid: fix the -partok logic for loading from a partition. * ISOLINUX: deal with systems which return from INT 13h with interrupts disabled. * Do not

I have released a SYSLINUX 2.06-pre3. This includes modifications to ppmtolss16 so that it should now be completely compliant with all modes of the PNM specification, raw/plain, PBM/PGM/PPM, with comment lines or without. ftp://ftp.zytor.com/pub/linux/utils/boot/syslinux/Testing/ Please test it out ASAP if at all possible. Since the fixes for -pre1 and -pre2 were pretty essential, I'd like

Arnaud, We've stumbled on a regression in nut-2.2.1 (also in nut-2.2.2-pre2) with regards to Tripplite USB devices. It turns out these devices will always indicate they have data available on the interrupt pipeline, no matter what. So we must limit the number of input reports we process to a single one in upsdrv_updateinfo() and leave any remaining ones to the next call in order to prevent

http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ Here is the list of changes in 1.75 so far: Changes in 1.75: * ALL: NASM 0.98.32 or later is now required to build SYSLINUX from sources. * SYSLINUX: put back in the workaround for the BIOS floppy table. This seems to be a requirement for "extended" floppy formats to work