similar to: Intel Boot Agent: PXE-E32: TFTP open timeout for correctly configured tftp-hpa

Dear List. My requirement is to set up a samba share named "music" that: I. it's read-only accessible from both Windows 98 and Windows 2000/XP not requiring password; II. it's write-accessible from Windows XP protected by a password. I thought in order to cope with Windows 98 I need to I. use "security = share" (done), and set "guest ok =

Hi: First - pxelinux works great - got it up and running with few problems. However - I ran into a snag, I am assuming I have a configuration issue. Here are the details. Using: syslinux-1.75 dhcp-3.0pl1 tftp-hpa-0.29 A lot of what I have done is from: http://frank.harvard.edu/~coldwell/diskless dhcpd.conf: # DHCP configuration file for DHCP ISC 3.0 ddns-update-style

input: > values [1] 0.854400 1.648465 1.829830 1.874704 7.670915 7.673585 7.722619 > thresholds [1] 1 3 5 7 9 expected output: [1] 1 4 4 4 7 That is, need a vector of indexes of the maximum value below the threshold. e.g. First element is "1", because value[1] is the largest below threshold "1". Second element is "4", because value[4] is the

Hiya, Just joined the list and started using pxelinux. Very cool product!!! I searched the, 8+ MB, archives looking for multicast entries. I know that the pxelinux page says that the support of mtftp in pxelinux isn't in the works but I'm not sure how old/relavant that comment is. I have noticied some comments from H.P.A. describing the difficulties in doing MTFTP. Are there any plans to

Dear list Sorry to ask a user's question on developer list. I didn't find the user list. I am experimenting with --cuesheet and encoded a flac file with a cuesheet. Result is: * Totem on opensuse 10.2 opens the flac file with no meta data, no play list. "Next" button doesn't work; * Mplayer on opensuse 10.2 opens the flac file with no meta data,

Hello, i've found a strange bug, here is my situation: - all of our computers makes a pxeboot request by default dhcp server is configured: option option-128 code 128 = string; option option-129 code 129 = text; option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned

Sorry for top-posting but my webmail forces me to. I added -W to the APPEND line as suggested but I'm still getting the same result: Booting... Altiris, inc. X86PC PreBoot, PXE-2.x Enhanced Build ID=402 PXEPreZero: Invalid PXE Server list format. and the client PC freezes right there. Here's the full content of my dhcp.conf: max-lease-time 86400; ddns-update-style interim;

I've got two data frames, as shown below: (NR means Number of Record) > record.lenths NR length 1 100 2 130 3 150 4 148 5 100 6 83 7 60 > valida.records NR factor 1 3 2 4 4 8 7 9 And I intend to obtain the following skip-table: >

Hi- On the pxelinux web page here: http://syslinux.zytor.com/pxe.php Mr. Anvin says the following: " PXELINUX does not support MTFTP, and I have no immediate plans of doing so. It is of course possible to use MTFTP for the initial boot, if you have such a setup. MTFTP server setup is beyond the scope of this document. " I am curious as to the possibility of 'mtftp for the

I have a patch that I think may help your situation of syslinux.efi being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if any of you are using an EFI ia32 platform). The basics are that we try to enable UseDefaultAddress as it helps certain clients with routing and works on numerous other clients. If we timeout on receiving a packet and have never received any packets, disable

On Wed, 2014-03-05 at 13:18 -0500, Gene Cumm wrote: > Second, I notice the Altiris server specifies _3_ options of code 43, > including one of length 253. The pack/unpack _should_ handle this but > may split it differently. That's legal, and treated as if the values had been concatenated. See RFC2131, section 4.1, and particularly the second paragraph on page 24. Unfortunately, a

On Thu, Nov 27, 2014 at 8:59 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > Gene, > > As it happened I started working on this again just as you mailed me. I saw it in IRC. > It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no

Ady: You seem to be taking (copy$paste) parts and pieces from different resources. Luke: Nope. The configuration works fine with PXE 2.01 clients, it's the UEFI PXE 3.2 that is having issues with the dhcp requests. The gospel is the Intel PXE 3 spec I'm RTFMing now. No copy and paste, I just started with someone elses configuration file that claims to support UEFI - or at least hopes to

On Wed, Oct 7, 2015 at 2:33 AM, Geert Stappers <stappers at stappers.nl> wrote: > On Tue, Oct 06, 2015 at 10:27:15PM -0400, Gene Cumm via Syslinux wrote: >> > On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> >> >> I have a patch that I think may help your situation of syslinux.efi >> >> being unable to load

Gene, As it happened I started working on this again just as you mailed me. It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no joy. The bootfile size shows up as zero because that relates to "option boot-size" in dhcp and doesn't seem to

On Fri, Oct 02, 2015 at 01:46:19PM -0700, Derrick M via Syslinux wrote: > On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > > I have a patch that I think may help your situation of syslinux.efi > > being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if > > any of you are using an EFI ia32 platform). > > > >

> On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> I have a patch that I think may help your situation of syslinux.efi >> being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if >> any of you are using an EFI ia32 platform). >> >> The basics are that we try to enable UseDefaultAddress as it helps >>

Hi, I have refered to ur documents for creating a Diskless node in linux ,but could not get through the installation . The exact problem that i am facing is mention below , also, there r few queries, which i would be greatfull if u can answer First let me explain u what i have done . I am trying the configuration with one server machine and one client. server configuration 256mb ram AMD Athlon

On Sat, Oct 03, 2015 at 09:20:10AM +0300, Ady via Syslinux wrote: > > > I have a patch that I think may help your situation of syslinux.efi > > being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if > > any of you are using an EFI ia32 platform). > > > > The basics are that we try to enable UseDefaultAddress as it helps > > certain clients

On Dec 25, 2014 2:11 AM, "Luke Ledgerd" <luke.ledgerd at niteco.se> wrote: > > Hey guys, > > We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off