search for: lss16

Hi, this patch is not a finished job; It fixes some regression issues but it displays some other ones. It initially deals with the correct migration (asm to C ) of the lss16 parser code at core/graphics.c referenced here: http://bugzilla.syslinux.org/show_bug.cgi?id=10 There were some emails with reports, and a couple of emails with some (incomplete, and erroneous) attempt to solve the issue. http://www.syslinux.org/archives/2014-October/022732.html http://www.syslin...

...<BLU436-SMTP134329F24C9A85B97FF55BF8B990 at phx.gbl> >Content-Type: text/plain; charset="US-ASCII" > > >> On 11/2/14, Ady <ady-sf at hotmail.com> wrote: >> > >> > FWIW, Utopic uses 6.03-pre18, not the final release (although, the >> > lss16 problem is present in both). >> > >> > About the lss16 issue, we all would welcome patches, really. Any >> > volunteers? >> > >> > @Barry, see http://www.syslinux.org/archives/2014-October/022734.html >> > >> >> Ady, >> Thanks...

G'day, I created a file to add mime-type detection for lss16 images... All you need to do is put it (unzipped) in /usr/share/mime/packages (or your equivalent) and run: update-mime-database -V /usr/share/mime Then you can just associate lss images with Mtpaint, to make life easier... Note: - I didn't know about the name (lss vs. lss16), so I just wen...

On 11/2/14, Ady <ady-sf at hotmail.com> wrote: > > FWIW, Utopic uses 6.03-pre18, not the final release (although, the > lss16 problem is present in both). > > About the lss16 issue, we all would welcome patches, really. Any > volunteers? > > @Barry, see http://www.syslinux.org/archives/2014-October/022734.html > Ady, Thanks very much for the information. My memory got jogged, and I recalled the Puppy d...

...ther code is a massive single patch and would be hard to review > since it would be difficult to bisect should a bug be introduced. I > will try to split the other patch into logical parts and submit as time > permits. > <<< > > Yes I know; unfortunately solving the lss16 issue cannot be done with a couple of 4 line patches. > The code to fix was originally ported to C from the assembler of a previous SL version, and it > never really worked before; it was needed re-writing certain parts. > Now the new code ( http://www.syslinux.org/archives/2015-July/023...

On Sat, 2015-08-22 at 00:56 -0700, Patrick Masotta wrote: > Please take a moment and see what the quoted code does; it'll save you lot of time. I wrote my versions before I knew about the other code. Unfortunately, that other code is a massive single patch and would be hard to review since it would be difficult to bisect should a bug be introduced. I will try to split the other patch

Dear gentlemen, this is just a marginal quirk... I've been using a graphical logo at the pxelinux prompt in our LAN for many years. It's always been the same LSS16 picture, and it's always been working fine. I've been using pxelinux 3.53 until recently. Right now I'm in the process of introducing "UEFI netboot" into our LAN, and also the diskless boot into Debian would make use of some goodies (variables) from modern pxelinux... henc...

> I've been using a graphical logo at the pxelinux prompt in our LAN for > many years. It's always been the same LSS16 picture, and it's always > been working fine. I've been using pxelinux 3.53 until recently. Right > now I'm in the process of introducing "UEFI netboot" into our LAN, and > also the diskless boot into Debian would make use of some goodies > (variables) from modern...

...t;> Unfortunately, that other code is a massive single patch and would be hard to review since it would be difficult to bisect should a bug be introduced.? I will try to split the other patch into logical parts and submit as time permits. <<< Yes I know; unfortunately solving the lss16 issue cannot be done with a couple of 4 line patches. The code to fix was originally ported to C from the assembler of a previous SL version, and it never really worked before; it was needed re-writing certain parts. Now the new code ( http://www.syslinux.org/archives/2015-July/023835.html ) has...

Good Evening: We've been using SysLinux in our admin class in college as part of a KickStart package designed to overcome multiple-use constraints in our computer lab (just pop the floppy in and suck the OS out of the server...). I have attempted to find out about the LSS16 file format you mentioned as part of your discussion of the DISPLAY format. We'd just love to use a cute "stand by" graphic of some sort (like your TUX graphic) but I can't seem to find any info on this format. Do you have sources for this? That's all. Thanks for the co...

...; Barry Kauler > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > FWIW, Utopic uses 6.03-pre18, not the final release (although, the lss16 problem is present in both). About the lss16 issue, we all would welcome patches, really. Any volunteers? @Barry, see http://www.syslinux.org/archives/2014-October/022734.html TIA, Ady.

Hi, I have just joined the list. I am the original creator of Puppy Linux, now letting other guys take the reins, and I am working on a fork of Puppy called Quirky Linux, where I try various experimental ideas. Up until now, in Puppy and all offshoots, we have used syslinux 4.05 or older. Over the last few days I have been testing 6.03 (using the binary DEBs from Ubuntu 14.10 Utopic Unicorn),

>>>> getnybble() needs to return four bits at a time from every byte. During rle decode, rows are rounded to an integer number of bytes. The rle length needs to be able to hold values > 255. Signed-off-by: Chas Williams <3chas3 at gmail.com> <<<< I think this change is also already included in the patch quoted previously by Ady

Hi, the display of LSS16 files from a DISPLAY file (as documented in http://www.syslinux.org/wiki/index.php/SYSLINUX#Display_graphic_from_filename:) seems heavily broken since syslinux has been converted from assembler to C. I already discovered one bug in core/include/graphics.h (and core/graphics.c): the pointer VGAFileP...

getnybble() needs to return four bits at a time from every byte. During rle decode, rows are rounded to an integer number of bytes. The rle length needs to be able to hold values > 255. Signed-off-by: Chas Williams <3chas3 at gmail.com> --- core/graphics.c | 35 +++++++++++++++++++++-------------- 1 file changed, 21 insertions(+), 14 deletions(-) diff --git a/core/graphics.c

> Hi, > > the display of LSS16 files from a DISPLAY file (as documented in > http://www.syslinux.org/wiki/index.php/SYSLINUX#Display_graphic_from_filename:) > seems heavily broken since syslinux has been converted from assembler to > C. I already discovered one bug in core/include/graphics.h (and > core/graphics.c):...

...ou should look at the Linux Progress Patch. You may also set the TIMEOUT to a bigger value, but i'm not sure that's what you want. regards, sylvain Le Sun, 6 Apr 2003 13:13:57 +0200 Ole Hansen <ole at danelec.dk> a ?crit: > Hello > > I am trying to get a graphical-image(lss16) to be displayed during the > booting of kernel and filesystem. > I have my console redirected to COM1 (SERIAL 0 9600): > > syslinux.cfg: > > default linux > prompt 1 > timeout 20 > > SERIAL 0 9600 > > display boot.msg > > label linux > kernel lin...

Hello, CONFIGURATION Syslinux "old": 3.36 Syslinux "new": 5.01 (B)LFS i686-pc-linux-gnu 3.8.0 Machine #1: ASUS P5E-VM HDMI. Latest BIOS. circa 3 years ago. Machine #2: ASUS P8H77-I. Latest BIOS. This year. USB Flash stick: Kingston "Data Traveler" 4GB. Clean (blank) STRANGE (UNEXPLAINED) syslinux BEHAVIOR DIFFERENCE Steps: 1. Set up KNOPPIX 7.05

Hello I am trying to get a graphical-image(lss16) to be displayed during the booting of kernel and filesystem. I have my console redirected to COM1 (SERIAL 0 9600): syslinux.cfg: default linux prompt 1 timeout 20 SERIAL 0 9600 display boot.msg label linux kernel linux append root=/dev/nfs rw mem=192M initrd=vr5000.tgz The image is displ...

...86 and v.4.07. > > > > Or, perhaps this documentation is incomplete / wrong? > > > > Well, it obviously requires vesamenu.c32 since it is graphical. > > -hpa Is the matter related to the png format of the background? In other words, if, instead of png, I choose LSS16, should it work with menu.c32 (in v3.86 or v.4.07) with this same syntax? Or, is the second parameter syntax itself not available for menu.c32 (and/or in CLI) whichever the format of the background? TIA, Ady.