similar to: Debugging version of MEMDISK available

Hi,, I wud just like to inform that the previous issue of memdisk not booting compressed images still persists !! The release 2.05 that was supposed to fix this issue dint yet solve the problem !! Please, let me know if more info on the problem is required !! Bye, Jassi >From: syslinux-request at zytor.com >Reply-To: syslinux at zytor.com >To: syslinux at zytor.com >Subject:

hi, i've tested with 2 version of awdflash and uniflash: here the results: it only worked with freedos, not with win98 dos; with win98 the images were not bootable; but that does not matter; freedos is ok. awdflash 8.27.45: flash ok awdflash 8.27.41 (uses protected mode): flash ok uniflash 1.40: when starting flashing the program freeze. awdflash 8.27.45 never worked before so i think this

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

Hello everyone, I have pushed out SYSLINUX 3.08. It's identical in all but version number to 3.08-pre11. Sorry for everything that probably should have been done that didn't make it, but I simply haven't had time :( :( :( However, given several bugs fixed in 3.08, this seemed important... Changes in 3.08: * SYSLINUX: Fix performance regression (-s mode always

git://git.zytor.com/users/genec/syslinux.git Branch memdisk-maxmem-for-hpa This is a preliminary hack to introduce a new option that will allow an end-user to limit the amount of available RAM as returned by any call that MEMDISK touches. This works by adding additional memory reservation(s) (through insertrange()) to reserve the memory between the specified address and the top of RAM. For

Hello list, I had to boot a Dell Diagnostic Disk today, and tried doing this via memdisk - which was when I noticed memdisk isn't working for me at all, neither from pxelinux nor syslinux. After trying around with 'raw', 'bigraw' and the like I noticed it doesn't even do anything when just using: LABEL diag KERNEL memdisk .. when I try that: boot: diag nothing

H. Peter Anvin, The following problem came to my attention with memdisk. I cannot claim the credit, but wanted to be sure the information made it back into the program for the benefit of all users... In file memdisk.asm, in respect of the operation of the raw and bigraw options, the order of pop instructions does not correspond to the order registers are pushed;

Hi, bit of a newbie if I'm honest but was wondering if issue mentioned here: http://syslinux.zytor.com/archives/2006-October/007586.html was ever fixed? basically I have the same issue with the same machine. I have 4 different types of PC's here that i'm trying to boot by USB stick. It works fine on 3 of them, but on the 4th, A HP/Compaq dx2200 MT, memdisk will not boot the .ima

Hi Peter, I'm using isolinux and memdisk to create a multiboot rescue cd for personal use as described on Bart's page (www.nu2.nu). One boot item is to boot DOS 7.1 from Win98SE with a lot of other staff for emergencies. This DOS bootimage puts all necessary stuff into it's own ramdisk (XMSDSK). Some progs on the ramdisk needs access to floppy drive A: and unfortunately I've no

Has anyone had a problem with afud408 (Award flash program) freezing the system when ran from memdisk? The freeze occurs when just running afud408 (not attempting to update bios, although it freezes then as well.) I was using pxelinux/memdisk 3.36, I upgrade to 3.51, and also fell back to 2.11 all have the same issue. I have tried all the switches for memdisk that I saw posted on the memdisk

Hi, I'm trying to boot Feature Tool 2.08 (free download from http://www.hitachigst.com/hdd/support/download.htm) from a pen drive via memdisk. QEMU can boot the pen drive all right, my ThinkPad can't: Loading ftool208.img.........................ready. MEMDISK 3.53 2007-11-17 Copyright 2001-2007 H. Peter Anvin e820: 0000000000000000 000000000009f000 1 e820: 000000000009f000

With windows, if your "virtual" floppy is drive B:, then windows will treat it specially. It will basically copy the contents into memory from real mode using int13h, knowing that it will not be able to access the device after it switches to protected mode. I asked a few days ago about support for making a memdisk image behave as drive B:, but got no answer. :-( We have our

Hi... I'm Jaspreet. I've been having the memdisk memory overlapping problems since 2.04 Its always seen in the compressed images whereas the uncompressed images works just fine !!! It just stops at the error "Ran out of input data".. Even the memdisk 2.05 dint solve my problem !!! maybe there r still some bugs remaining. !! My motherboard is Intel 845GEBV2 and i've got

hpa, Seeing your post about 3.71, I wanted to get a message out even though I don't have the stats right now. I am having a problem with memdisk with a lot of shuttle computers, but also affects a variety of other hardware (low though, 5%? less?). The image that I can most reliably test against is the Hitachi Drive fitness Test.

I'm new to memdisk and I wanted to have multiple floppy boot images on my USB key, I installed GRUB2 as the boot loader and have memdisk in /syslinux and my images in /image, I first tried booting normal images, memtest86+ works, my linux kernel work and they boot perfectly. Now using memdisk, I tried booting Spinrite which uses FreeDOS, it booted fine with no argument them frozen at querying

Hi All, I am still having troubling with PXE. Thanks for replying Shao.I did follow ur suggestions and my results have improved a bit.From Ethereal and TCPdump, I can see that the client sucessfully dowloads the file pxelinux.0 from the server but stops at this point. here is the output of tcpdump tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:05:41.966864 IP

2018-06-26 2:10 GMT+08:00 H. Peter Anvin via Syslinux <syslinux at zytor.com>: > On 06/18/18 13:06, R S via Syslinux wrote: >> The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. >> >> If you are interested I could provide a 5MB FDD image template based on >> FreeDOS 2041 kernel (the latest available at that time in 2014) where you >>

On Wed, Jun 5, 2013 at 4:38 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 06/05/2013 02:34 PM, Gene Cumm wrote: > > On Wed, Jun 5, 2013 at 4:18 PM, upen <upendra.gandhi at gmail.com> wrote: > >> Sorry to bring this old thread up. I saw the note on the release of > >> syslinux-5.10 which I have just finished installing. I would like some > help >

Here is the script I put together now. I hope I haven't overlooked anything. You might need to modify the first section of variables to suit your setup. Ofcourse you need to run this as root. May be some version of this should be included with syslinux? Basically given an existing floppy image, it creates a larger image and copies its contents over and sets up the bootsector of the

> It would be possible -- in fact, fairly easy -- to hack the > "raw" mode of MEMDISK to drop the system into big real mode > after finishing instead of real mode; such a "bigraw" mode > might solve the problem with this particular program. > > The PC hardware... gotta love it. ok, i don't understand a lot of this; but sounds nice ;) could you please