Syslinux - Sep 2004 - Problem with syslinux booting via network in floppy image

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 using the free client from 3com, that looks exactly the
same as Argon Technology's client. All the PC clients are
PXE clients.

Firstly I want to say, using bpbatch to boot and load the
syslinux image works 100%, but I was forced to use the 3com
setup to load other ms dos images (to use the universal
ndis pxe dos driver). Now the problem using the
Argon/3com boot menu, is that it stops at the screen:

Could not find ramdisk image: initrd.gz

I would guess that it could be 

1) when vmlinuz loads it reinitialize the memory and wipe
out the ram floppy image...

2) when booting, the initrd.gz is not on /dev/fd0 because
the 3com/Argon pxe boot loader do not emulate like bpbatch
does. So it would be something else ?

Can I add something else to floppy image that will make it
boot via the network ?

I too use the 3Com boot menu.  I have the exact same problem of cannot find
the ramdisk: initrd.gz with all versions of syslinux since 1.72.  Download
1.72 and install this version of syslinux on the floppy, then use the 3Com
Boot Image Editor to create an image of the floppy, then edit the pxe file
(usually deploy.pxe) to include the new image.  

I have met with resistance to fixing this problem.  I once offered to look
at and find the differences between 1.70 and 1.71.  1.70 does not work, but
1.71 and 1.72 do work.  Unfortunately I was unable to setup the environment
needed to compile syslinux.  I am told that I would need to get and install
the mingw compiler.  I found the mingw compiler homepage, but I am not sure
what I would need to download.  I use Fedora Core 2, so do I still need the
gcc from mingw?  I had several other type questions, so I gave up.  

It was also suggested that a packet capture might show the problem, but I
have not had time to look at getting the packet sniffer in the room, setup,
capture a 1.72 packet transfer, capture a 2.11 packet transfer, etc.  This
is on my things to do list.  

Jason