similar to: My last try to fix memdisk boot problem

Howdy to all, We've been using isolinux quite successfully for quite some time now, and I have come across a couple of laptops where isolinux balks at my config file.. Upon booting on this systems, the image background appears corrupted, and at the boot prompt, the following happens automatically. Unknown keyword in config file. Could not find kernel image: 1 boot: Any label input here

Sorry for makeing a new post, but I already erased my old mails. In the following I describe my Server-Situation (Sorry for my bad english) * I have a eisfair server http://www.eisfair.org with version 1.6.1 (newest) * I have a ISC-DHCPD 3 Server running * I have a TFTP Server running http://www.kernel.org/pub/software/network/tftp/ * I have Samba installed and a DNS Server is running My

Greetings again, I am experiencing a lockup when ghost casting about 1 out of 5 client machines locks up. I don't recall if I was having this issue when I was using 3com pxe menus or not. I was wondering if the issue I am seeing could be caused by pxelinux since it basically is loading a Linux kernel then booting a MSDos.imz file. I cannot find any errors from the ghostcast side or the

So I have a few questions. I have already made the base part of making a windows TFTPD running with memedisk. So that part works, but what I was wondering, if there is a way to some how add an option to the config file. What I have is something like this: label winstall kernel unattended/memdisk append initrd=unattended/winstall.imz That all works great, However, for each image, I have

I am using PXELINUX, ISOLINUX, and memdisk in my project (http://unattended.sourceforge.net/). When memdisk gained support for compressed images, I started using it because it is cool. I used gzip to compress floppy.img to create floppy.imz, and all was good. But now my users are complaining that they cannot use WinImage (a Windows floppy image editing tool) to edit my floppy.imz files. I have

My system is hanging up when attempting to boot a floppy disk image. Does the following info tell any story as to what's happening? Loading ghost.imz ............. Ready. MEMDISK 3.11 2005-09-02 e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 2 e820: 00000000000e0000 0000000000020000 2 e820: 0000000000100000 0000000009ef0000 1 e820: 0000000009ff0000

Hi, there now i am booting pxelinux menu32 with 2 boot images 1. DOS boot image 2. Thinstaion pxelinux and my directory structure is like this (Pxelinux with menu32) /tftpdroot/pxelinux.0 /tftpdroot/pxelinux.cfg/default /tftpdroot/dos.imz (DOS bootimage) /tftpdroot/memdisk (memdisk package) (Thinstation Pxelinux) /tftpdrooot/pxe/pxelinux.0 /tftpdroot/pxe/initrd

Here's the problem in a nutshell: One samba-server (stand alone) A couple of Windows XP (sp2) clients All connected through a gigabit network Transfers between two of the windows computers works just fine and the speed is about 20-30MB/s. Transfers from the server to any windows computer also works fine and has the same speed. Transfers TO the server from any windows computer is horribly

lower your debug level. High debug level lowers performance... Mit freundlichem Gru?, Dirk Laurenz Systems Engineer Fujitsu Siemens Computers Sales Central Europe Deutschland Professional Service Organisation Nord / Ost Hildesheimer Strasse 25 30880 Laatzen Germany Telephone: +49 (511) 84 89 - 18 08 Telefax: +49 (511) 84 89 - 25 18 08 Mobile: +49 (170) 22 10 781 Email:

Good day again Daniel, So the first thing I did was to remove the >NUL for your XMSDSK line and put a PAUSE after it in AUTOEXEC.BAT. That way, I could see the error message: *** XMS RAMdisk v1.9I (FU - 08/98): XMS get free mem error. Then I noticed that if you run AUTOEXEC.BAT manually from the DOS CLI, XMSDSK actually succeeds! So that led to a new test: Duplicate the XMSDSK line. ...

Hello. We've been using a very old version of SYS-/PXELINUX, 3.36, going by the proven "if it works, don't break it" philosophy. We us it mostly to load floppy disk images to kick off OS installations. Unfortunately we've recently had some PXE menu problems (USB keyboard stopped working) for a certain Fujitsu PC model, and decided to upgrade to the latest version, i e 3.84.

Hi friends, I am new to this list and have some questions about PXE Booting, because its not working well. My Situation: I was preparing my Server like described on http://unattended.sourceforge.net And everything was working well, this means I was able to install Windows XP via PXE onto my clients. But now, I thought, It would be really a great Idea to make my clients able to

The following patch allows memdisk to support compressed floppy images created by WinImage. WinImage creates a PKZIP-style archive with a single member, the .img (or .ima) file containing the floppy image. WinImage names such archives with a .imz extension. This patch lifts the header/trailer checking code from gunzip() to a new function, check_zip(), which both checks for a valid ZIP image and

Hi, I tested this version and it works all right ! Thanks a lot for the quick fix. Do you still want to see the output in order to check everything is OK, or you don't need it ? --------------------- Sylvain Faivre EdifiXio - AIH Team +33 1 56 90 51 24 www.edifixio.com > -----Message d'origine----- > De : H. Peter Anvin [mailto:hpa at zytor.com] > Envoy? : mardi 18 novembre

> ONTIMEOUT is meant to be a label I think that wrong . :) Actually, I just looked at my config and I have TIMEOUT .localboot -1 -----Original Message----- From: Ardill, Robert (DTEI) Sent: Thursday, 31 August 2006 10:05 AM To: 'Greg_Chu at Wendys.com' Cc: 'SYSLINUX at zytor.com' Subject: RE: [syslinux] Time out would not boot from local drive ONTIMEOUT is meant to be a

I will really hate myself if this has already been solved, i searched the archives but didn't really find anything pertaining to it. I have a 2.88mb dos boot floppy image, with ghost.exe, dos nic drivers, and dos system files. It works fine when burnt to a cd. As for the thumbdrive when trying to configure this hpghost.ima file to run from my syslinux.cfg menu, it works and boots up fine but

I am having the darnedest of times trying to get my WinPE to work off the syslinux loader. I used to use isolinux, and my isolinux config would just invoke the etfsboot.com file which i had renamed to loader.bin, and everything would work just fine off a cd. But now I'm trying to transfer all of my cd functionality to thumbdrives. With Syslinux, i have my syslinux.cfg file calling loader.bin

Hello, many of our platforms do not have a integrated floppy, some even don''t have a floppy controller. As pxelinux still has a problem with machines without a floppy in combination with some bios versions I need to chainload a different bootstrap loader which works on the floppyless platforms. But I also need to load a BartPE and the other BS loader does not support that. So I tried to

I have been using memdisk (version 3.82) with no problem. I use it to boot my x86 computer with a compressed image I created/modified from an original DOS floppy bootable diskette. The original size of the image is 2.44 MB. I tried memdisk (version 3.83) and the bootable image gets uncompressed, bu the computer locks up and the las two lines in my screen are: Loading Boot Sector... Booting...

Hi, I'm trying to get the above working, without success so far: UNDIS.DOS refuses to load with an invalid NDIS stack message (from memory). keeppxe has some effect: it reduces the available conventional memory by 140 kbytes or so... still, the packet driver doesn't seem to find the interface. Does anybody have a working setup I could look at? -- Thanks, Feri.