similar to: Strange MEMDISK problem with XP Bootfloppy images

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

Hello all. Again I call upon the greats of this mailing list to help me with an issue related to MEMDISK - notably when paired with various Dell OptiPlex and Latitude systems. The issue presented itself sometime ago and I best dealt with it by remaining with version 3.83 of the SYSLINUX package. But valuing the improved changes fostered by newer versions, I would prefer to move forward with

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line:

git://git.zytor.com/users/genec/syslinux.git Branch memdiskdbg-for-sha0 This starts with adding another check in two of the disk probes (by Shao; Thank you), expands the debug output, adds an additional check in the third probe and expands/reorders the debug output. At this time, it appears to resolve the MEMDISK issues that Jason Vasquez first noticed. The additional check in the third probe

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.

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, My desktop machine at work was replaced and they gave me a Dell Optiplex GX520 machine to use. When booting from CD-ROM I use isolinux 3.50 and the keyboard does not work. It does work once linux boots, and it works if I hit the F2 to go into bios before isolinux starts. I have searched google and the syslinux archives for 'Optiplex GX520' but have not found any reports of

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,

On Tue, Dec 2, 2014 at 2:26 AM, Gregory Sloop <gregs at sloop.net> wrote: > I love the idea of a low-power high-performance appliance. A NAS will > work fine for storage, but it's not going to act as a DC etc. [At least > none that I'm aware of and would trust.] > > Even appliances sorta like this, that I've seen, are easily five times the > price. > >

Hello, I am new to this list. We are trying to move away from our WDS server with PXElinux mods and are testing using iPXE on a linux box only. We mainly use HP but also have Dells, Panasonic, and Lenovo. On almost a dozen models tested now, everything works great. These were mostly laptops but a Dell Optiplex 360 and 380 booted fine. So far we have just had a problem with the HP 6005 Pro SFF

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.

Hi, I'm trying to create a hd image to use with memdisk: dd if=/dev/zero of=doshd.img bs=1024 count=16384 and, via qemu, I installed freedos: qemu -cdrom fdfullcd.iso -hda doshd.img -boot d Everything gone ok and qemu boots freedos normally. But, when I try to use the same image on memdisk the following message appears: Invalid Operation System! I used the same process on USB key, with

System: Dell OptiPlex GX620 (Both BIOS A10 and A11 affected) Medium: Physical CD-RW Observed: ISOLINUX 5.11 0x51D1AE48 ETCD_ is the only line displayed on-screen. A flashing cursor trails at the end of the line. Escape key does not return boot: prompt. Line1 of syslinux.cfg: DEFAULT vesamenu.c32 Note: Reverting to syslinux-4.06 allows for successful booting on the same system. Patrick On Tue,

Just for the record, I want to let the list know that I succeeded in booting a modified Universal TCP/IP Network Bootdisk floppy from http://members.iinet.net.au/~bdriver/bootdisk/ I started with a Win98 Bootfloppy from http://www.tobs.uku.co.uk. Then I made a disk image from this, using dd.exe from cygwin. Then I converted this disk image from 1.44MB to 2.88MB with winimage. Then I copied

I just discovered the wonderful world of ISOLINUX/MEMDISK while investigating how to make a boot CD that doesnt have floppy disk size limitations on its boot images. One thing has struck me as very odd about MEMDISK though - its support for hard disk images is restricted to physical disk images (ie. containing MBR/partition table). It doesnt support individual partition images, despite the fact

Hi there, We had to setup a pxelinux on a new server (windows 2012) and used the latest release of pxelinux 6.0.2. Everything went ok on my first client test machine : dell optiplex 740. Pxe was really fast (vesamenu with large background image was appearing in less than 3 secondes) But on different client machine i got different results : On optiplex 790 (core i5 with intel 82579 nic) and

I have a 32MB HD image that I can pxelinux.0/memdisk boot without issue. I would like to both memdisk and my image on a CD and then boot from the CD with pxelinux.0. Is this possible? If so how? Thanks.

Im trying to boot memtest86 via pxelinux, memdisk, I found this advice on http://forum.x86-secret.com/viewtopic.php?t=2906 folks are making the image match a floppy size by one of the following: dd if=memtest86+-1.xx.bin of=memtest.img bs=360k count=1 conv=sync or dd bs=360k count=1 conv=sync if=memtest86+-1.xx.bin|gzip > memtest.gz I did the former, it did suppress the warning/errors I saw

Hi, I have a CentOS 7 desktop client installed on an old Dell Optiplex computer with an Intel video card integrated into the motherboard. The card has a single VGA connector, and the 19" monitor is connected to it. I wonder how I could connect a video projector to this computer while keeping the monitor, in a mirroring configuration, e. g. output is the same on the video projector and the

Hello syslinuxers I'm stuck with a scientific problem which gives me headaches: I have a laptop (Gateway MX3410) which has a SD memory card reader. Recently an interesting thought crossed my mind: why don't I setup a 2GB SD card as a harddrive and put some rescue tools on it. So I dug on the net and I came across the idea of using memdisk to boot floppy images without the need of a