Displaying 20 results from an estimated 10000 matches similar to: "Booting to a DOS boot disk using pxelinux?"
2003 Oct 06
4
Bootable 2.88MB floppy image
I would like to be able to create a 2.88MB bootable floppy image to hold the kernel and initrd -- will be used for automated install. In various newsgroups there have been many posting attempting to describe how to achieve this, but none of them is complete.
Can syslinux be used to achieve this?
What about memdisk?
Thank you in advance.
Fet
2003 Oct 07
3
Boot Failed: please change disks...
I had to create a single floppy image holding the kernel and initrd of SuSe8.0 distibution. When I boot the computer, it first loads the kernel, and starts loading the initrd. After a short while it halts saying ?Boot Failed: please change disks and press a key to continue.?
The floppy image is served by a PXE server, so I am not sure if the problem I am facing has anything to do with ?bad
2003 Sep 24
2
MTFTP support in PXElinux??
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
2003 Nov 21
1
pxelinux web page question...
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
2014 Nov 28
1
pxelinux efi64 boot woes on hyper-v gen 2
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
2014 Nov 28
0
pxelinux efi64 boot woes on hyper-v gen 2
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
2005 Oct 04
3
Boot DOS through Pxelinux
Hello list,
My set up is almost complete in booting DOS through PXELinux, but I need to
create a DOS boot image from (2 )DOS floppies. I've search the archives and
google
but didn't find any relavant info...
My current set up now works with the standard setup (with one DOS floppy):
kernel: memdisk
append: initrd=floppy.img ramdisk=10000
My goal to is create a floppy.img from 2 DOS
2004 Feb 13
1
PXELinux; Question regarding UNDI
I have already a running automated Deployment system using
pxelinux and tftd and a 1,44 floppy image (memdisk) with ms-dos and
3-com undi drivers.
The whole thing is working good, and i am not unhappy about it.
But, the dos image solution has a few disadvanatages, because
i cannot find a mtftp client for ms-dos to deploy a lot of system
at the same time.
Under linux such client exists, but i
2014 Nov 27
2
pxelinux efi64 boot woes on hyper-v gen 2
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
2013 Apr 02
1
Problem with pxelinux 5.0 and memtest
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
2002 Dec 03
2
pxelinux/memdisk booting MSDOS floppy image requires local floppy disk
I found that if I do not have a local floppy installed and enabled on my client,
I will get the error 'Non-system disk' when I try to boot DOS floppy images.
NT or Syslinux floppy images boot fine.
If I enable the floppy in the BIOS, then it boots the DOS floppies just fine.
Is this normal? Is there a workaround?
There are MS-DOS images, so perhaps this is an MS-DOS limitation.
--
2002 Sep 04
2
PXE-E55 ProxyDHCP - No reply to request on port 4011
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
2006 Sep 06
3
Intel Boot Agent: PXE-E32: TFTP open timeout for correctly configured tftp-hpa
Hello. In my case I can successfully boot up my Thinkpad X32, but the
same configuration doesn't work for my desktop computer with Intel
network card, with Intel Boot Agent 2.2
DHCP server is 10.0.0.1, tftpd (used tftp-hpa) runs on 10.0.0.32.
netstat told me the daemon listen to 69 UDP port just fine. running tftp
in commandline also shows it works (retrieve pxelinux.0 less then 1
second).
2014 Dec 26
0
Chain-loading from WDS to PXELinux on a different tftp server
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
2010 Nov 12
2
Strange bug since 3.83 version
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
2014 Mar 05
2
Cannot chain to another PXE server on the same subnet
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;
2003 Jul 17
2
PXE: Booting Diskless Node
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
2014 Dec 25
2
Chain-loading from WDS to PXELinux on a different tftp server
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 anything you want to including PXELinux.
The stuff I was talking about before with PXELinux not working in
2014 Mar 06
2
Cannot chain to another PXE server on the same subnet
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
2003 Dec 30
5
Pxelinux/memdisk with XP "MS-DOS" boot disk
I'm trying to use this universal DOS TCP/IP boot disk available here:
http://members.iinet.net.au/~bdriver/bootdisk/
It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image