similar to: LSS16 mime

Displaying 20 results from an estimated 600 matches similar to: "LSS16 mime"

2019 Nov 06
2
CTRL+X LSS16 Image embedded in "DISPLAY message" no longer works?
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
2014 Nov 02
2
lss broken when upgraded 4.05 to 6.03
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),
2003 Apr 11
2
Making logos...
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
2014 Nov 02
0
lss broken when upgraded 4.05 to 6.03
> 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
2014 Nov 04
1
lss broken when upgraded 4.05 to 6.03
>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
2015 Jul 20
1
[PATCH 0/1] lss16 parser
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.
2015 Aug 22
2
[PATCH 2/2] core/graphics: fix lss16 parsing
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
2015 Sep 01
2
[PATCH 2/2] core/graphics: fix lss16 parsing
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;
2014 Nov 02
1
lss broken when upgraded 4.05 to 6.03
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
2002 Feb 03
1
lss16 Images
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
2017 Jun 20
3
translate formula into R code
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)) /
2017 Jun 20
0
translate formula into R code
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
2005 Oct 21
1
Display images
Hi! First of all, sorry for my english. I have one problem. I'm creating a server to install PC's with PXE (dhcpd, tftp, nfs, etc...). And, at the syslinux moment, the image (splash.lss/logo.16/...) is not displayed, but the text into boot.msg works ok (colors and background ok). I copied files from Knoppix, Fedora and others... But it's the same: No image, but text and colors ok.
2004 Oct 18
1
Display file problem with PXELINUX
Hi All, I am having trouble with pxelinux display file not calling the correct name to retrieve the graphic image. I guess the filename length is determained the first time ^X is used, and doesnt re-size the field name on next call. For example when cycling through F1 - F2 - F3 the f1 image displays fine, and its the longer name f2 & f3 just display the text and no image, output from
2014 Oct 14
2
[LLVMdev] Problem of stack slot coloring
Hal's advice helps me a lot to understand the implementation much better. Thanks so much! So, now I am able to state my problem more clearly: 1) There are two kinds of locals, i.e., the local variables originated from the source code (like C/C++), and the compilation generated temporaries. After instruction selection phase, the former is seen as frame indexes, while the latter is seen as
2002 Oct 15
2
AMENDED: Ppmtolss16 trouble...
Upon finding a different image conversion program, I have eliminated the Premature EOF problem that I had(apologies if I post this before the moderator approves my first post...you can ignore it if/when it shows up). Now, I am seeing the script complete with no error. I tested my syslinux.dpy file with the syslogo.lss file from the samples, and it's fine. The lss file I created, however,
2019 Nov 06
0
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
2015 Aug 23
0
[PATCH 2/2] core/graphics: fix lss16 parsing
>>> > 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
2015 Aug 22
0
[PATCH 2/2] core/graphics: fix lss16 parsing
>>>> 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
2015 Aug 21
2
[PATCH 2/2] core/graphics: fix lss16 parsing
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