similar to: Cannnot Load image

Like a lot of people, I am using SYSLINUX + MEMDISK to make a technician universal boot disk on a USB key (I have done the same with ISOLINUX and MEMDISK for a CD using Bart's method for bootable CDs) I *LOVE* Syslinux and MEMDISK, and what I can do with floppy images! I have a few problems that have cropped up, most notably the DOCMEMORY program (www.simmstester.com) boots fing, but the

This is a minor tweak on 3.11-pre2. If nothing new comes up, I will release this as 3.11 probably early next week. -hpa

Hi all, I got a USB-HDD, but it doesn't looked like connect and cannot mount it just after PC boot. But insert and remove a usb cable from PC, it connect (with hotplug?) Is there any good how-to's for getting a usb-HDD to auto connect when It is booted the computer? lsmod is following: [lsmod of just after boot] Module Size Used by Not tainted parport_pc

Hi, I've been fighting with trying to get a Belkin Universal model F6C800-UNV to work with NUT. The error I am getting is as follows: ---------------------------------------------- * Starting UPS drivers ... Network UPS Tools - UPS driver controller 2.0.0 Network UPS Tools - Belkin 'Universal UPS' driver 0.06 (2.0.0) tcgetattr(/dev/ups): Inappropriate ioctl for device Driver failed

Anders Alexandersson wrote: > Hello! > > I get some odd behaviour using my structs: > > "myKernelMap" = type {int (sbyte*)*, int ()*} > "Kernel" = type {"myKernelMap"*} > > The second member ( int()* ) is a pointer to the %getchar() function. > > I want to call getchar using this function: > > int

Hello! I get some odd behaviour using my structs: "myKernelMap" = type {int (sbyte*)*, int ()*} "Kernel" = type {"myKernelMap"*} The second member ( int()* ) is a pointer to the %getchar() function. I want to call getchar using this function: int "callmyKernelgetchar_kernel"("Kernel"* "myKernel") { "PTRMAP" =

In Syslinux 5-6.02, the "global append" directive is being (unintentionally) ignored in some cases. Updating Syslinux from prior versions, when using a "global append" directive, will cause unexpected results. For example, take the following simple configuration file: *** DEFAULT mykernel APPEND root=/dev/sda2 *** Note that the 'append' line is a global

On Mon, 3 May 2004, Anders Alexandersson wrote: > Hello! > > I'm having trouble with pointer traversing. I have a design as follows: > class -> map -> classFunctions > > Starting with a pointer to the class, I want to get a pointer to a > classFunction via a pointer to the map. Okay... > I can't get that function pointer! > > How shall I think to get

On Sun, Mar 23, 2014 at 7:17 AM, Ady <ady-sf at hotmail.com> wrote: > 2_ In prior versions, a specific entry was executed as follows: > <mykernel> <global_append> <myappend_options> > corresponding to: > > *** > # The following is the global append, not part of a label entry. > APPEND <global_append> > > #The following is a sample

Hello! I'm having trouble with pointer traversing. I have a design as follows: class -> map -> classFunctions Starting with a pointer to the class, I want to get a pointer to a classFunction via a pointer to the map. I can't get that function pointer! How shall I think to get the traversing right (see code below)? Is it something with the fact that I am using only pointers in my

Hi, I have tried to enable IPSec support for my FreeBSD( 4.11-RELEASE) system. First, I copied the generic kernel configuration file to a file I called MYKERNEL: #cp /usr/src/sys/i386/conf/GENERIC /usr/src/sys/i386/conf/MYKERNEL Then, I added the following three lines to the options section of /usr/src/sys/i386/conf/MYKERNEL: options IPSEC options IPSEC_ESP options

Hi guys! I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 works fine both memtest 4.1 and 4.2. With version 6.00 no error message caught, only writes out dots. Any keypress does a reboot.With version 5.01 the error message is the follow:Loading images/memtest/memtest86... okBooting kernel failed: Bad file

Hello, FYI. This problem looks similar to the problem I reported in Februari http://www.syslinux.org/archives/2013-February/019517.html Kind regards, Wim. On 06/28/2013 10:02 AM, Matt Fleming wrote: > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: >> Hi guys! >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and >> i have issues to boot it with

Hi all, I am planning to improve virtualization in my company. So I have already a pool named p.e. Pool1. I have 5 servers Dell PowerEdge 1950 in it. Now I have 4 servers Dell PowerEdge 2850 too. Can I add 2850 to Pool1? I can''t find anything about compatibility for different hadrware in new release. -- Best regards, Den. _______________________________________________ Xen-users mailing

Hello !! <p> Can I get the vorbis -I encoder spects ..? I have Vorbis I specifications . That talks mostly about vorbis Decoder . <p>Leena --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the

Hello list, any try the new memtest86 v3.2 with isolinux 3.11 cd and pxeboot? How is the proper way to chainload memtest86 I was tried: label memtest kernel memtest.bin but, nothing happens just a weird hang (my older versions of memtest hangs too). Anyway chainloading in a floppy image with memdisk on CD or pxeboot was fine but if I use memory to emulate a floppy I was not using this memory

Hello, I'm trying to pass the serial port options to memtest86+ using Syslinux 5.01 but is not working. Debugging the memtest86+, the check at main.cpp function static void parse_command_line(void) if (*OLD_CL_MAGIC_ADDR != OLD_CL_MAGIC) return; Is being evaluated to true. What should I do? There is a way to instruct memtest to use the "old way" to pass

Hello, This is my first post to this list. After searching through the archives and google searches I could not find a solution for my memtest problem. In previous versions of pxelinux/gpxelinux (4.04 and 4.06) I could successfully start the memtest utility. But using pxelinux/gpxelinux versions 5.01 and 5.02 the memtest utility does not boot and I get an error message: boot: Loading

Hi! At first thanks for your great work! I started to make multiboot CDs 1,5 years ago, with Bart Lagerweij 's utils. I have a problem with the memtest86 floppy image, made by the authors in the .zip file, downloadable from it's homepage, when I use diskemu. Some days ago I found on Bart's page a new method to select boot images on CD with syslinux/isolinux/memdisk. I thought this is

Hi there, ----- Original Message ----- From: koxudaxi at gmail.com To: syslinux at zytor.com Date: 01.04.2013 10:00:27 Subject: Re: [syslinux] Problem with pxelinux 5.0 and memtest > On 04/01/2013 09:28 AM, H. Peter Anvin wrote: >> On 03/31/2013 05:26 PM, Koudai Aono wrote: >>> I ran the test on a x86 emulator is called Oracle VirtualBox. >>> I think it might not be