Re: [Etherboot-developers] stumbling block for 5.2

[<ke...@et...>]

>Just a small comment on what I was thinking when I coded this.
>1) Unless we reserve all of the memory dos is using it is non-trivial
>   to return to, especially after etherboot has had a failed image load.
>   So the quit function was just a best effort kind of thing.

It may be necessary to use .exe format to ensure that all the memory
that Etherboot uses is known to DOS and also to support images > 64kB.
But this would mean obtaining information from the load map or branching
off earlier than .img. I'm not in a hurry to do anything about this.
.com is just a carrier. Maybe there's no public demand for fixing the Q
problem.  Maybe somebody will want it badly enough to fix it himself.
I'll leave it as is.

The 5.2 tarball has been uploaded and is ready to release. The CVS area
is in place. I'm just wondering when will be the first 5.2.1 patch. :-)