similar to: loading/starting memtest with pxelinux-2.06 fails

Hi! I hope this is the right list for sending tftpd-patches - if not, please point me in the right direction... I experienced quite strange problems when trying to use tftp-hpa in newer Cygwin versions. It simply isn't able to parse its command line correctly because it seems to use another optind variable than getopt(). When you try to start it with something like tftpd.exe -s /mypath

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

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

Additional information: I was tried it with 2 virtualbox (version 4.2.14r86644).1rst: debian weezy with isc-dhcp-server, pxelinux5.01, pxelinux 6.00, tftp-hpa2nd: empty virtualbox booting from virtual network card. So memtest 4.1 and 4.2 worked with pxelinux 4.06 Peter > Date: Fri, 28 Jun 2013 09:02:30 +0100 > From: matt at console-pimps.org > To: coolpet80 at hotmail.com > CC:

> 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

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

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

On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote: > But, in Syslinux 4.06, there is linux.c32, which is a sort of > introduction to Syslinux 5.xx (please allow me to be not strictly > accurate in this sentence in this context). > > Booting with any variant of Syslinux 4.06, but using linux.c32, > memtest would fail, which indicated some kind of problem

Hi there, I am using the latest version of both syslinux ( acutally isolinux ) and memtest86. I get the error "Cannot load a ramdisk with an old kernel image." the memtest is just called memtest ( renamed from .bin as I read that in the archives that was bad ) My isolinux.cfg is just label memtest kernel memtest I searched google with not much avail. Is this a known issue to you?

On 06/28/2013 04:07 PM, Gene Cumm wrote: > On Fri, Jun 28, 2013 at 12:53 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote: >> >>> But, in Syslinux 4.06, there is linux.c32, which is a sort of >>> introduction to Syslinux 5.xx (please allow me to be not strictly >>> accurate in

It depends on the exact memory map of the system. Gene Cumm <gene.cumm at gmail.com> wrote: >On Fri, Jun 28, 2013 at 7:31 PM, H. Peter Anvin <hpa at zytor.com> wrote: >> On 06/28/2013 04:07 PM, Gene Cumm wrote: >>> On Fri, Jun 28, 2013 at 12:53 PM, Gene Cumm <gene.cumm at gmail.com> >wrote: >>>> On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf

On Fri, Jun 28, 2013 at 7:31 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 06/28/2013 04:07 PM, Gene Cumm wrote: >> On Fri, Jun 28, 2013 at 12:53 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote: >>> >>>> But, in Syslinux 4.06, there is linux.c32, which is a sort of

On Fri, Jun 28, 2013 at 12:53 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote: > >> But, in Syslinux 4.06, there is linux.c32, which is a sort of >> introduction to Syslinux 5.xx (please allow me to be not strictly >> accurate in this sentence in this context). >> >> Booting with any

Hi, does somebody else experience booting problems after normal installation on SD32G2 based Shuttle systems. A CentOS 5.0 installation can be performed without any problems but after the first reboot the systems are just stopping the boot process after the grub is searching for the kernel. The last line is some- thing like: [ Linux-initrd @ 0x37db8000, 0x237858 bytes]. We tried already the

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

Hello all, I wonder if there is a way to set up the so-called JDF library required by several Adobe software? I haven't been able to find out what it is, nor whether wine has any way to set this up, or even if I can copy windows DLL's over. I can get Adobe Acrobat 7.0 to run, for example, but many actions fail with the error "cannot initialize JDF library". Any enlightenment

On Dec 7, 2015, at 4:21 PM, Gernot Zander <debian at scorpio.in-berlin.de> wrote: > > Hi, > > am 7 Dez schrieb Marks, Connor: >> Well I just need to monitor the UPS battery for testing and I do about >> 10 UPS's a day. So having to restart my computer every time gets old >> real quick. > > In that case - what about not starting nut-client (upsmon)

Hi, My problem is following now: I would like to set the filters for port 8099. I have tried it, but nothing happened. When I try the same filter for the port 8080 it is working very well. .) working filter (here I can see the dropped packages): tc filter add dev eth0 parent ffff: protocol ip u32 match ip dport 8080 0xffff police rate 1kbit burst 1 drop flowid :1 .) not working filter (here I

Hi, The problem is this is my goal to use the policier and not the iptables. Because with the policier i think you can give more rules and restrictions to the incoming tcpip traffic. So I would prefer to use the policier and not the iptables. Thanks Gernot > GRAMES Gernot > __________________________________ > SIEMENS AG Austria > PSE SMC AI 21 > * Tel.: +43 (0) 5 1707

Good Morning, Thanks for your hint, now I can see the dropped packages! But it is only working for port 8080 why not for port 8099?? (If you need some indices please let me know) Thanks Gernot > GRAMES Gernot > __________________________________ > SIEMENS AG Austria > PSE SMC AI 21 > * Tel.: +43 (0) 5 1707 24356 > * FAX: +43 (0) 5 1707 54600 > * E-Mail: