David Pilling wrote:
In message <45845C6D.3080200@xxxxxxxx>, Clive Bonsall <C.Bonsall@xxxxxxxx> writesNo, I didn't do that on the previous system. I've tried setting the /3GB switch in the Boot.ini file in the current system, but it makes no difference ... unless I've made the changes in the wrong place (?):Looks OK
>
I think I should do a build of OPW that supports 3GB, it should be simple for me.Maybe I've just exceeded the capabilities of this particular computer.Yes, but what capabilities?
Quite! Difficult to say ... In terms of hardware, the same memory modules were used for both machines, altho' the P4 has 2MB whereas the Athlon had only 1MB; the motherboards are different, in fact the Athlon m/b was several years older; the main difference is the lack of a separate graphics card in the P4. In terms of software/settings, they're pretty much the same.
Next step is to try reducing the size of the images before dropping them back into the file. Perhaps I can get the file down to a size that my current P4 system can handle.Presumably.
That has sorted the problem. When I put the originals into Photoshop, I discovered that altho' they were intended to be B&W images (by the author), several of them had been created/saved in 8-bit color. Reducing them to simple bitmaps has substantially reduced the file size ... down to 6MB!
Still, had they really been color images, I suppose I would have come up against the "not enough memory" problem anyway.
Incidentally, why doesn't referencing pictures or using proxies (seem to) have any effect on file size?I can only think that the undo buffer is not flushed. In other words you reference the image, but immediately after that step the image is still in memory in case you undo the step.
But I did flush the undo buffer ... and isn't the undo buffer automatically flushed when a document is saved?
-- CB
