[syslinux] pxelinux 512MB limitation ?

[Shao Miller]

Good day, guy.

How did you fare with using MEMDISK?

Also: There probably isn't any need for GRUB4DOS to be involved in this
scenario, as long as the disk image is bootable.

>From gpxelinux.0 (which is gPXE -> PXELINUX), you could run meminfo.c32 and
tell us about how memory is organized on the system.

- Shao Miller

-----Original Message-----
From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On
Behalf Of LinuxByExamples
Sent: Friday, October 19, 2012 11:33
To: For discussion of Syslinux and tftp-hpa
Subject: Re: [syslinux] pxelinux 512MB limitation ?

Hi,

I want to add more files to the image, but the old image is not space
enough. So I started to make a whole new one image with bigger size
(>512MB).

The bigger image is created by VirtualBox, using fixed size disk
(preallocated) in vhd format. Then I install winxp with NTFS
filesystem. After all I make it defragement, and I do not use
compression (gzip or ntfs compression).

I can succesfully boot the big image with grub4dos : directly map to
file or to mem (--mem). But I can not boot it using gpxelinux.0.

I use syslinux version 4.05-1.fc17 and grub4dos is most recent version.

-- Atrus.

On Fri, Oct 19, 2012 at 1:55 PM, Ady <ady-sf at hotmail.com> wrote:
>
>>
>> But when the vhd image getting bigger than 512MB (I added some more
>> files into the image), the booting proccess fail at the loading the
>> image step. Then I try boot the image on usb disk (without using
>> gpxelinux.0 and http) -> it works !
>>
>> Brs.
>
> Adding files to a disk image doesn't mean the disk image is bigger
> than before.
>
> How exactly you added files to the image?
>
> Is the vhd image fixed or dynamic?
>
> Have you defragged the vhd image?
>
> Which filesystem are you using in the vhd image?
>
> Have you compressed the vhd image (gz or anything else)?
>
> Have you defragged the compressed image?
>
> Which image is bigger than 512MB? Are you referring to the original
> vhd image or to the resulting image after compression?
>
> Which version of Syslinux you used?
>
> Are you using a recent version of grub4dos?
>
> Instead of adding files to the image (with whichever method you used
> until now), have you tried building a new vhd image bigger than
> before and starting the procedures all over again?
>
> I am probably not capable of helping you directly with gpxe (or
> ipxe), but probably those questions need answers anyway.
>
>   -- Ady.
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
_______________________________________________
Syslinux mailing list
Submissions to Syslinux at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.