On 31 Oct 2009 at 9:34, Johannes Gebauer wrote: > On 31.10.2009 David W. Fenton wrote: > > Sibelius needs to do this sooner than Finale because of their slower > > release cycle. > > Now that's an interpretation I cannot follow. Although Sibelius has had > a slower main release cycle, as far as I remember they were much quicker > in fixing and updating for new OS requirements than Finale ever was. > Finale is completely fixed on one main release a year, plus one > maintenance, occasionally two when it gets too embarassing. I cannot see > that Sibelius has a slower cycle in adopting new OSes.
I didn't say anything remotely like that. What I said was that since Win7 came out very shortly after the release of Sibelius 6, they couldn't wait for Sibelius 7 to make this change, because that's not due for a while. Finale, on the other hand, can (not *will*, but *can*) adapt to this for its next release. >From what I've read about the technical issues here (in MSDN articles on the /LARGEADDRESSAWARE compile switch), I don't think there's a huge amount of work involved in making a 32-bit Windows app able to use the extra RAM Win7 makes available to user processes (though I don't want to imply that it's as simple as just recompiling with the /LARGEADDRESSAWARE switch -- one of the articles I read discussed the dangers of common methods of calculating pointers, and said that these could go wrong if you didn't rewrite to account for the larger memory space -- if your codebase depends on those kinds of calcs, you'll likely have a harder time than if it doesn't). I could, of course, be wrong -- this is not my area of expertise -- but the programmers writing about it are not talking about completely re-engineering their codebases for this purpose. -- David W. Fenton http://dfenton.com David Fenton Associates http://dfenton.com/DFA/ _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
