On 22 Jan 2005 at 21:31, [EMAIL PROTECTED] wrote: > My theory is that at this point, there is a problem with the way > Finale has been programmed. . . .
I think *that's* indisputable! > . . . A problem, which results in the Overwrite > Bug, that when there is more memory in a machine, doesn't occur. > But when there isn't enough memory and the system gets to the point > of thrashing, then the mistakes made in the way that Finale was > written result in this problem. I don't know that anyone has identified low memory as a requirement to produce the bug. > Can you think of anything in the way a program is coded that would > fit into this scenario and possibly cause the overwrite bug? > Problems with the way the program uses threads? I/O issues? > Caching? etc....? I can't think of a reason why low memory could suddenly cause corruption of such a minor type. When a program can't handle low memory conditions, usually the results are fairly catastrophic. Of course, it depends on the type of low memory condition. I still don't think the memory issue really has anything to do with it. When the OS is thrashing, Finale should just slow down to a crawl, and, perhaps, stop. But all that I'm writing here is mere speculation as I don't know the conditions necessary to produce the bug. All I know is that I think this is the least likely cause of the problem because the symptoms do not match up with this kind of root cause. -- David W. Fenton http://www.bway.net/~dfenton David Fenton Associates http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
