similar to: Disk preparation

I've been trying to make up for a mismatch in functionality between bpbatch and pxelinux by trying to use both depending what I'm trying to do by chain booting the two. I'm able to chain boot in either direction, either pxelinux then bpbatch or bpbatch then pxelinux, but once I've done this, and boot either Linux or DOS, I find the adapter I used to network boot is not detected by

What is the difference between PXELINUX and bpbatch ? AFAICT, bpbatch doe not require a TFTP server which supports the 'tsize' option. So in the absence of such a server, I may need to explore bpbatch... It seems that bpbatch can be used to remotely boot DOS. Can PXELINUX also do this? -- John

I just wanted to chime in and mention that I'm running into the problem with getting a "Non-system disk..." error on a system using a USB floppy when the floppy is not attached when I try to boot the system over the network using memdisk to boot a floppy image. Its actually fairly important to be able to do this, as the architecture of the hardware that I'm working with utilizes

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

Hi, I want to use PXELINUX to load a DOS disk image which I currently use for Win2K/XP unattended installs. I want to move away from reliance on specific NDIS2 drivers and use the 3Com UNDIS3C driver instead. I have used this successfully to start the MSClient, but the problem is that the UNDI and PXE layer take about 90K of base memory, which means that WINNT.EXE has insufficent memory to run

Hi as described on the syslinux pxe webpage: A multi-hardware boot floppy is included with Windows Server 2000 and 2003. A company called Argon Technology used to offer a free-as-in-beer updated version, but is seems to have gone fully commercial. This floppy (which can also be burned to a CD using El Torito in floppy-emulation mode), is known to work with PXELINUX 2.03 or later only I'm

Hello, THE PLAN: a cross-plattform unattended setup system for linux and windows on a RH72 box with PXE, ISC-DHCP2 and TFTP. Lanboot should be offered with linuxinstall and a dos6.22 LANMAN 3.0 bootdisk + djgpp bash for scripting (see http://unattended.sourceforge.net) THE PROBLEM: DOS Utilities force reboot after partitioning. By then the decision if the bootimage or the HD should be booted

Hi, I'm not sure what you call it, but I do not use EFI, so I guess it is BIOS/legacy system. My idea was to have the option to install windows 7 on my computer and it should install drivers that's not recognized in the install progress. My default file is this: DEFAULT menu.c32 PROMPT 0 MENU TITLE PXE Special Boot Menu MENU INCLUDE pxelinux.cfg/graphics.conf MENU AUTOBOOT

On Sun, Nov 26, 2017 at 8:38 AM, Kenneth Vandb?k <valnurat at gmail.com> wrote: > I looked at the link and it seems to this is what I need to do. > I have copied wimboot file to my \tftpboot directory, but it seems it can't > find the file in the progress. > > I have a QNAP nas for this. > > This is my setup.menu file: > > MENU TITLE Setup Menu > >

Hi community, since more than one week I try now to boot my client via PXE. More informations about my equipment: Client: Board ASUS K8V-X SE Amibios with BIOS Revision 1501 (newest) Intel UNDI, PXE-2.0 (build 082) Server: Tyan Tomcat K7M Board with Eisfair 1.6.1 (www.eisfair.org) With exactly the same hardware unattended boots where working for more than one year perfectly without any

On Tue, Dec 5, 2017 at 1:11 PM, Kenneth Vandb?k <valnurat at gmail.com> wrote: > I found out that "wimboot" has to be lowercase. Merely match what the tftpd will work with. > Now wimboot, but I get this problem as the attachmen shows. > > My configfile is like this: > > # setup.menu begin > MENU TITLE Setup Menu > LABEL MainMenu > MENU LABEL ^Return

On Fri, Nov 24, 2017 at 8:24 AM, Kenneth Vandb?k via Syslinux <syslinux at zytor.com> wrote: > Hi. > > I have looked at PXElinux<http://www.syslinux.org/wiki/index.php?title=PXELINUX> to understand all this, but I'm very sorry I don't. > > I have managed to setup to boot from PXELinux, but I'm not an expert on how to setup a menu file for making a windows

Hi, I'd just want to express my gratitude for the recent versions of pxelinux and memdisk. They allowed me not only to install Linux, but also to boot those darn rescue Floppys on my IBM ThinkPad X22, which comes without Floppy or CDDROM drive, but a built-in Ethernet card which supports PXE. I also had a look at other projects, like bpbatch, but none were so easy to use and functional as

On Fri, Nov 24, 2017 at 09:07:22AM -0500, Gene Cumm wrote: > On Fri, Nov 24, 2017 at 8:24 AM, Kenneth Vandb?k wrote: > > Hi. > > > > I have looked at > > PXElinux<http://www.syslinux.org/wiki/index.php?title=PXELINUX> > > to understand all this, but I'm very sorry I don't. > > > > I have managed to setup to boot from PXELinux, but I'm

> > On 09/20/2013 02:34 AM, Ady wrote: > >> There might be an alternative (and possibly others too): let the user > >> select the appropriate firmware from within pxelinux.cfg/default. > >> > >> So, keep using the same method you used in previous versions, instead > >> of selecting the Syslinux cfg / firmware from the DHCP snippet that >

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

I have some hardware vendor diagnostic utilities that I'd like to use via PXE. One example is a three diskette test suite. How can I merge all these diskettes into a single PXE bootable image? I have been using pxelinux, memdisk, and isolinux successfully for other things, so I'm a little embarrased even asking. Is there a way to PXE boot ISO images? Can syslinux support larger than 2.8MB

I downloaded the 'seatools for DOS' diskette creator on seagate website. it's a windows program that creates the diskette; so a floppy disk must be present in the drive. running the program is ok, but creating the diskette fails, it says "the current diskette format not valid". while the diskette is blank, vfat, mounted and linked to a: in wine; so everything seems to be ok.

hi! I?m working on a projekt ( unattended.sourceforge.net ) This is using a linuxboot.iso My problem is the following: I opened up the iso with winiso, extrcat the isolinux.cfg, edited it with vi for windows as follows: # isolinux/pxelinux configuration file default unattended label unattended kernel bzImage # Add options (z_user=..., z_path=..., etc.) to this line. append