|
From: Tim R. <ti...@su...> - 2004-05-21 22:43:38
|
In message <9DE...@sm...>
John M McIntosh <jo...@sm...> wrote:
> Hi, when I saw this, what happen was that os-x decided to load the 1GB
> image at the 2GB boundary, versus the 1GB or earlier location.
> This was a choice made by the OS, which then caused immediate failure.
Likewise - startofmemory was &7xxxxxxxx and endofmemory was well into
&8xxxxxxxxx territory. The good news is that the image segment loading
is the only thing I've noticed failing because of that, though it's not
impossible that occasional mysterious crashes are due to the problem.
As with OSX, it's an OS memory allocation choice that isn't
controllable by the application.
tim
--
Tim Rowledge, ti...@su..., http://sumeru.stanford.edu/tim
It said, "Insert disk #3," but only two will fit!
|