Displaying 5 results from an estimated 5 matches for "proboot".
Did you mean:
probook
2004 Dec 18
2
UNDI NDIS DOS Driver
I found the 3Com one, but I'm looking for the intel one. The PXE PDK
doesn't have it anymore, and the intel site points me to the proboot.exe
archive, which has no *.dos files in it. Does anyone know of other generic
drivers for dos that work with memdisk's keeppxe option?
2004 Nov 11
1
PXELinux and Mess-DOS
Hi,
Quoting the memdisk.doc:
Similarly, if you're booting DOS over the network using PXELINUX, you
can use the "keeppxe" option and use the generic PXE (UNDI) NDIS
network driver, which is part of the PROBOOT.EXE distribution from
Intel:
Does anyone know what this means? It sounds like a generic network driver
for DOS exists. I have a copy of the PROBOOT.EXE, but I can't work it out.
If this is what I think it is, has anyone made it go or even better, made
a version that works with Bart's ModBo...
2005 Apr 26
3
A HowTo guide?
I've very new to this... what I want to achieve, is to have my clients
network boot - and then be presented with a menu, allowing them *well,
me* to choose what to do.
Maybe, boot from the main hard disk, or boot a disk image from a samba
share, or maybe even boot a CD image, instead of having the actual CD in
the drive.
Also, I would want to be able to change this menu, without actually
2005 Dec 02
3
PxeLinux menu.c32 chaining
...KERNEL startrom.0
LABEL Local
MENU LABEL boot local drives
LOCALBOOT 0
---------------
XPE1 and local boot work perfect. XPE1 also chains to a new BS loader.
If multinet.bs is loaded (same behaviour if loaded as multinet.0) the 3COM loader reports the error message "ERROR: Proboot API not found!"
Because loading multinet.bs directly without menu.c32 works fine, but loading it from within menu.c32 in the same way does not work I think menu.c32 modifies some IRQ vector for example and does not restore the values on exiting and moving the control to the new BS loader.
Of c...
2005 Dec 03
5
Re: SYSLINUX Digest, Vol 33, menu.c32 chaining
...make the according changes to the
configuration file and try again.
Cheers
Alex
------------------------------>
Of course I also tried that. See my original text at:
"If multinet.bs is loaded (same behaviour if loaded as multinet.0) the 3COM loader reports the error message "ERROR: Proboot API not found!"
Thanks and best regards
Klaus
------------------------------
Message: 4
Date: Fri, 02 Dec 2005 07:02:17 -0800
From: "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [syslinux] PxeLinux menu.c32 chaining
Do you have any details on pxelinux having problems with...