On Mon, Apr 11, 2011 at 07:10:52PM +, Herve Poussineau wrote:
From: Herv? Poussineau hpous...@reactos.org
This option is described in RFC 1783. As this is only an optional field,
we may ignore it in some situations and handle it in some others.
Here, if client requests a block size
On 04/11/2011 10:10 PM, Herve Poussineau wrote:
From: Herv� Poussineauhpous...@reactos.org
Note: your charset is UTF-8 but this is Latin-1 (I think). Please use
consistent charsets.
--
error compiling committee.c: too many arguments to function
Hi,
Yes, I've tried booting with PXELINUX and gPXE, and I didn't see any
problem.
Hervé
Stefan Hajnoczi a écrit :
On Mon, Apr 11, 2011 at 07:10:52PM +, Herve Poussineau wrote:
From: Herv? Poussineau hpous...@reactos.org
This option is described in RFC 1783. As this is only an
On Sun, Apr 17, 2011 at 7:16 PM, Hervé Poussineau hpous...@reactos.org wrote:
Hi,
Yes, I've tried booting with PXELINUX and gPXE, and I didn't see any
problem.
Great. Thanks for confirming.
Stefan
On Mon, Apr 11, 2011 at 07:10:52PM +, Herve Poussineau wrote:
From: Herv? Poussineau hpous...@reactos.org
This option is described in RFC 1783. As this is only an optional field,
we may ignore it in some situations and handle it in some others.
Here, if client requests a block size
From: Herv� Poussineau hpous...@reactos.org
This option is described in RFC 1783. As this is only an optional field,
we may ignore it in some situations and handle it in some others.
Here, if client requests a block size bigger than the block size we emit
(512 bytes), accept the option with a
