similar to: PXE boot screen

Hi, I'm new to R, and I'm not a statistician (stunned silence). I am trying to do the following: 1. read in a 2-column data file, e.g. status new db green title "Most Significant Excursions" 2. end up with an R list such that I can write e.g. lst$title and have R return "Most Significant Excursions". I know I could do this by coding lst = list(title="Most

Hello, I am trying to test a function argument to see if it is or is not a useful number. However I cannot seem to find a test that works. For example > f = function(x) { + print(exists("x")) + print(is.null(x)) + } >rm(x) > f(z) [1] TRUE Error in print(is.null(x)) : Object "z" not found exists gives TRUE, but then any other kind of test I try to run gives me an

Hi, I have an intermittent pxelinux boot problem. It happens rarely, for example it happened one day and then did not happen again until 6 days later. However when it does happen it is rather serious as it affects all clients on the network. Here is some basic info: - IBM netvista PCs, built-in pxe, banner says it is "PXE 2.x". - happens rarely, but when it does it affects all clients.

Hello, What options are available for me to debug my R scripts? For example I normally do something like >source("myfunctions.R") >function1("height", "weight") myfunctions.R is a large R source file that contains many functions. function1 is the "main" function in myfunctions.R. It calls many other user-written functions that are also in

When I use R, I am accustomed to developing programs in a text processor, and then copying from the text processor and pasting into R. This usually works fine, except that using the default text processor in Suse 9.0, long programs don't transfer completely. Using the 'source' program, also only works with small programs. Suggestions?

Hello! I just started using Linux and I like the possibilities it offers. I'm using Suse Linux (no MS Windows installed at all). I also discovered that syslinux is capable of making a USB pendrive bootable (with graphic menus). This is very nice. Since I'm a Windows user (up until now), I have some questions: 1 - I already downloaded syslinux 3.82 How do I install it on my pen drive

Hello, My desktop machine at work was replaced and they gave me a Dell Optiplex GX520 machine to use. When booting from CD-ROM I use isolinux 3.50 and the keyboard does not work. It does work once linux boots, and it works if I hit the F2 to go into bios before isolinux starts. I have searched google and the syslinux archives for 'Optiplex GX520' but have not found any reports of

Hi, I have been using syslinux on my portable disk with success on many types of machines (both bios boot and EFI boot) I however hit a small issue recently If I use menu.c32, on some UEFI systems (HP) the menu does not appear after the vendor splash screen. The system however goes ahead and after the timeout configured in the menu system syslinux boots the kernel. I can then (after kernel

Hi all, I would really appreciate feedback on the graphical menu system and its infrastructure. It's not really clear to me that it's what people want; it seems to me that it makes more sense than gfxboot, for example (C rather than pseudo-Forth), but I can understand people would disagree. Anyway, the more feedback I get the easier it will be to pick a direction and a priority for

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have done some additional testing, and gotten it a bit close to what I was looking for. I had to modify the cat.c to eliminate the printing of the arguments and file name, and added a Press Enter to return menu line. With the below isolinux.cfg the options do display the files, and pressing enter than returns to the vesamenu. DEFAULT

On 12/04/2013 02:58 PM, Gene Cumm wrote: > On Wed, Dec 4, 2013 at 12:02 PM, Adam Sawyer <acsawyer at gmail.com> wrote: >> All, >> >> I have scoured the mailing list and the web and I can't seem to find any >> help on this issue. I am attempting to have EFI machines boot over PXE and >> then load various Linux Live distributions. I have a similar setup

On Fri, Jul 8, 2016 at 11:46 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> Hi, >> >> I have been using syslinux on my portable disk with success on many >> types of machines (both bios boot and EFI boot) >> >> I however hit a small issue recently >> >> If I use menu.c32, on some UEFI systems (HP) the menu does not appear

We recently have upgraded syslinux and have noticed that the boot logo code via boot.txt no longer works. I have a couple patches that get it close to working but I appear to be having trouble with color maps. Is there someone would want to help me finish figuring this out? Any interest in the patches I have to fix the rle decoder?

>From: Scott Bower <s.bower@authentictkd.com.au> >I guess what I want to find out is: Is there a way of either starting it >with a cached password or alternatively, drop the "Always On Top" feature >of this splash screen logo? Here's a link to disabling the splash screen. Remember you still have a registry on your linux box (when using wine), even though its

System: Dell OptiPlex GX620 (Both BIOS A10 and A11 affected) Medium: Physical CD-RW Observed: ISOLINUX 5.11 0x51D1AE48 ETCD_ is the only line displayed on-screen. A flashing cursor trails at the end of the line. Escape key does not return boot: prompt. Line1 of syslinux.cfg: DEFAULT vesamenu.c32 Note: Reverting to syslinux-4.06 allows for successful booting on the same system. Patrick On Tue,

Is there a way to show only a splash screen during the boot up, like not even the BIOS text? I would like to make a kiosk with no indication of what is running. Thanks, Bryan

Hi group, currently I try do make my own PXE bootscreen. There is one thing i dont like. When I use vesamenu.c32 there is always a table on the screen (I mean the border lines are visible) Is there any command i have to add to the default file that this border lines are unvisible ? Thanks in advance

Updating myself again: On 07-08-15 16:03, Oscar Roozen wrote: > e466d24 still has an issue with png's in vesalinux causing crashes I can confirm this remaining crash is caused by the line "MENU BACKGROUND bootlogo.png". The original bootlogo.png is 640x480. Forcing the videomode with "MENU RESOLUTION 640 480" did not resolve the crashes, nor did resizing the png

Hello, Thanks very much for your suggestions. I have double checked that all .c32 files are from the same version of syslinux. What I don't know - I only put those .c32 files I have in there on the basis of trial and error - is what .c32 files are actually needed for menu.c32 and/or vesamenu.c32. I thought perhaps there might be a .c32 file missing that I needed to put in there (though

Just tested with the latest VirtualBox and that works OK, so it's definitely something specific to ESXi 6.0.0 (it worked previously under 5.x ESXi versions). Thanks, Dan Jackson (Lead ITServices Technician). -----Original Message----- From: Syslinux [mailto:syslinux-bounces at zytor.com] On Behalf Of Jackson, Dan via Syslinux Sent: 16 June 2016 09:27 To: 'syslinux at zytor.com'