similar to: CTRL+X LSS16 Image embedded in "DISPLAY message" no longer works?

> 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

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 went by what the "file"

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

> 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

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.

>From: Ady <ady-sf at hotmail.com> >To: syslinux at zytor.com >Subject: Re: [syslinux] lss broken when upgraded 4.05 to 6.03 >Message-ID: <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

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

On 08/23/2015 12:33 AM, Patrick Masotta via Syslinux wrote: > >>>> > 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;

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

Hi! I'm trying to create a custom logo for syslinux but keep bumping my head on the conversion to LSS16. The sample syslogo.png works fine so I decided to start with a known quantity by loading it into the Gimp. I cleared the canvas, color filled a blue background (0x000033) placed some yellow letters on the blue (0xffff00) and saved the file back out with the default compression. The

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

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 VGAFilePtr is of type uint16_t*, but should be plain char*. This bug causes the

> 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 VGAFilePtr is of type uint16_t*, but > should

>>> > 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.? <<< Yes, but you published your patches after you knew about it. >>> 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

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

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

Dear gentlemen, I think I'd better start another thread for this... thanks to Ady Ady and Gregory Lee Bartholomew for their responses to my early question. Just for the record, my fresh experience with PXElinux 6.x follows: syslinux.efi version 6.03 does boot to the extent that it shows a prompt, but if I provide it with a CFG file containing several labels, no matter what label I type

Hello, I am trying to implement the following formula using for loops and vectors. I am sure you can use some fancy R code to solve this but I would like to keep it simple and stick to for and vector/array if that is possible. TP = 200; RL = 50; TPR1 = TP - RL; TPR2 = TP + RL; PPO = 0; LSS = 0.1; counter = 1; for(i in res) { # Even if(counter %% 2 == 1) { ls = abs((sum(LSS)* TP)) /

Cc'd back to the list... always use reply-all. You say res should have been LSS but LSS is a scalar so the for loop will only run once. What does a successful output look like for a sample input? How do you (we) know when success has been achieved? In fact, what is the formula you want to implement? If your code below is the definition of your "formula" then we are left with no

I asked before about config_cwd and after some more digging, it looks like it could be removed... Specifically, the documentation http://www.syslinux.org/wiki/index.php?title=Config#CONFIG says: ---------- * CONFIG config_file [new_WD] Load a new configuration file. The new configuration file is read, the Working Directory is optionally changed (if specified via an optional second parameter),