[EMAIL PROTECTED] / 05.1.21 / 00:52 PM wrote:
With Photoshop, it can be helpful to have the temp files stored on a separate hard drive...not a separate partition but an actual separate hard drive...things run a little more efficiently that way. Maybe this could help Finale too.
The vm stack is created when instruction sets needs a lot of cashing, while temp file is created the file based caching such as opening huge file and acquire the undo caching. But they are separate tasks.
I know...I'm talking about putting the temp files on another disk for physical hardware reasons much in the same way that some people put their swap files on another drive in earlier versions of the OS (much riskier to do in Jag and Panther.) The less the drive heads on the disk have to "run around" to different parts of a disk the faster data can be read.
Someone pointed out the bug seems to be caused by the array pointer, and I have the same feeling. It shouldn't be related to the amount of the available memory but rather an address bug.
But I think that if the problem was solely due to an address bug, it would happen more often. And problems with addressing is exactly what can happen during a page fault...(when the working set of pages of a process, which contains addressing information doesn't have enough physical memory...a page fault occurs....it the OS has enough memory to keep the working sets of all processes in physical memory there will be fewer page faults.) Page faults don't occur very often. Only when the system is stressed do they happen more frequently...the same goes for the Overwrite Bug.
.......related to hacked and twisted code to make Finale work under OSX.
I whole heartedly agree that something has not been coded properly under OSX and that that is adding to the problem. :-)
-Karen
-- _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
