Re: [Finale] File Overwrite Bug in FinMac2010b r.1

Yikes! -Randolph Peters Christopher Smith wrote: > I just experienced the file overwrite bug again, after several versions > without seeing it. Here is the tech support message I sent: > > I just had a Finale file overwritten by the contents of another Finale file. > Disaster was averted by t

[Finale] File Overwrite Bug in FinMac2010b r.1

I just experienced the file overwrite bug again, after several versions without seeing it. Here is the tech support message I sent: I just had a Finale file overwritten by the contents of another Finale file. Disaster was averted by the last backup being okay still, but I thought you guys

[Finale] File overwrite bug FinMac2005c

I just sent this to the tech support website. First time in a while for me - I thought I was finally immune because of my changed habits. Crap. I was bitten by the dreaded file overwrite bug again. It was as all the other times - I had a score open and I had extracted the parts. I was almost

Re: [Finale] file overwrite bug

Simon, At least send Alan the files in question (if you have them), and a note with everything you can remember -- how many files were open, what you were doing at the time, whether Finale because unresponsive, when you noticed the problem, etc. - Darcy - [EMAIL PROTECTED] Brooklyn, N

Re: [Finale] file overwrite bug

>Hi Allen, > >Just CC'd you on that. Simon Troup apparently got hit in 2k6. Damn. > >Told him to send you the details. I'm not sure there are any details to tell - I wasn't really concentrating on it as a beta test or anything so I was just left staring at the file thinking - well you can guess.

Re: [Finale] file overwrite bug

Hi Allen, Just CC'd you on that. Simon Troup apparently got hit in 2k6. Damn. Told him to send you the details. - Darcy - [EMAIL PROTECTED] Brooklyn, NY On 06 Sep 2005, at 11:52 AM, Fisher, Allen wrote: Out of curiosity, has anyone heard of this happening with 2k6? Thanks, Allen O

Re: [Finale] file overwrite bug

Out of curiosity, has anyone heard of this happening with 2k6? Thanks, Allen On 9/4/05 1:21 PM, "Christopher Smith" <[EMAIL PROTECTED]> said this: > > On Sep 4, 2005, at 7:33 AM, shirling & neueweise wrote: > >> >> finally got bit. macfin 2005r.1 >> >> > snip > >> >> i use auto-save whe

Re: [Finale] file overwrite bug

On Sep 4, 2005, at 7:33 AM, shirling & neueweise wrote: finally got bit. macfin 2005r.1 snip i use auto-save when working on the score, normally turn it off when doing parts, and had simply forgotten taht this was one of the things related to the bug and neglected to turn it off. Thi

Re: [Finale] file overwrite bug

On Sep 4, 2005, at 12:27 PM, Johannes Gebauer wrote: On 17:14 Uhr Randolph Peters wrote: It usually is Shift-Command-S on a Mac. and with 2k6 even Finale implements it. in 2005, too (on Panther, at any rate.) Christopher ___ Finale mailing li

Re: [Finale] file overwrite bug

Jef, Autosave is not related to the file overwrite bug. In fact, autosave can help you tremendously, because the most recently autosaved version of your conductor score is probably okay. - Darcy - [EMAIL PROTECTED] Brooklyn, NY On 04 Sep 2005, at 7:33 AM, shirling & neueweise wrote:

Re: [Finale] file overwrite bug

On 17:14 Uhr Randolph Peters wrote: It usually is Shift-Command-S on a Mac. and with 2k6 even Finale implements it. Johannes -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list Finale@shsu.edu http://lists.

Re: [Finale] file overwrite bug

At 9:46 AM -0400 9/4/05, Dennis Bathory-Kitsz wrote: I take advantage of that pause by a kind of muscle memory that takes over at the very beginning of that pause: A finger-practice of ALT-F-A ("Save as..." by keyboard, never a mouse; I assume the Mac has a global "Save as..." keystroke pattern)

Re: [Finale] file overwrite bug

At 07:33 AM 9/4/05 -0400, shirling & neueweise wrote: >i use auto-save when working on the score, normally turn it off when >doing parts, and had simply forgotten taht this was one of the things >related to the bug and neglected to turn it off. crap. I have not been bitten by these bugs in any

[Finale] file overwrite bug

finally got bit. macfin 2005r.1 opened an orchestral score, a related extract score and two parts which had already been extracted and did 3 measures of notehead changes (using mass edit, partial measures) in all 4 documents. did a save all. it's very late and i'm trying to remember the o

Re: [Finale] File overwrite bug

David W. Fenton / 2005/05/03 / 12:38 PM wrote: >None of the modern OS's should require rebooting, ever. All NT-based >versions of Windows and OS X have memory management and resource >limits that should allow them to run for months, if not years, >without reboots. But you wouldn't know that s

Re: [Finale] File overwrite bug

On May 3, 2005, at 12:38 PM, David W. Fenton wrote: On 3 May 2005 at 8:21, Christopher Smith wrote: As I had mentioned, though, the bug seems to occur when Finale has been open and running for a long time, which might be the result of some sort of build-up that can be avoided by rebooting (or quitt

Re: [Finale] File overwrite bug

On 3 May 2005 at 8:21, Christopher Smith wrote: > On May 3, 2005, at 5:48 AM, Johannes Gebauer wrote: > > > > As far as I understand the file overwrite bug has nothing to do with > > rebooting, it is a bug in Finale. > > As I had mentioned, though, the bug seems to occur when Finale has > been op

Re: [Finale] File overwrite bug

On May 3, 2005, at 5:48 AM, Johannes Gebauer wrote: As far as I understand the file overwrite bug has nothing to do with rebooting, it is a bug in Finale. Johannes As I had mentioned, though, the bug seems to occur when Finale has been open and running for a long time, which might be the result

Re: [Finale] File overwrite bug

Karen Guthery schrieb: I actually reboot nearly as often as I shower. I shower more often only because traffic on the 405 here in LA is such that you get to know your lane neighbor pretty well and the stinky police are out in force heading into the summer. This small rule (both in showering a

Re: [Finale] File overwrite bug

On May 2, 2005, at 9:09 AM, Johannes Gebauer wrote: What are the "don't"s with the File overwrite bug (2k5b, Mac). I don't often work with several files open at once, and have avoided it when the bug was made known, but now I want to edit some parts and could save some time if they were open at

Re: [Finale] File overwrite bug

On 2 May 2005 at 12:04, Christopher Smith wrote: > For sure, if the window title doesn't match the contents of the > window, the bug has occurred. I've been doing a lot of Finale work the last week with multiple files open, combining different files from a multi-movement work into a single file

Re: [Finale] File overwrite bug

On May 2, 2005, at 9:09 AM, Johannes Gebauer wrote: What are the "don't"s with the File overwrite bug (2k5b, Mac). I don't often work with several files open at once, and have avoided it when the bug was made known, but now I want to edit some parts and could save some time if they were open at

[Finale] File overwrite bug

What are the "don't"s with the File overwrite bug (2k5b, Mac). I don't often work with several files open at once, and have avoided it when the bug was made known, but now I want to edit some parts and could save some time if they were open at the same time, is this risky? Johannes -- http://ww

Re: [Finale] File Overwrite Bug in Action

On 26 Jan 2005 at 16:04, Jari Williamsson wrote: > Darcy James Argue wrote: > > > I haven't tried cmd-shift-D, but last time I had the problem, I > > noticed it *before* closing windows because, although the displayed > > file was correct, printing it resulted in printing a completely > > differe

Re: [Finale] File Overwrite Bug in Action

Well, this is good to know! Maybe because more than one person was working on a server when this happened in my situation, the files were being saved before anyone noticed what was going on. But this is good to know. I will definitely try this next time if it happens again and pass the info

Re: [Finale] File Overwrite Bug in Action

This sounds right to me, as far as I can tell. When I have saved the file, it saves with the wrong contents. If I change to Scroll View, or redraw, or update, the proper contents seem to come back. Weird. Christopher On Wednesday, January 26, 2005, at 09:04 AM, Darcy James Argue wrote: On 26 Ja

Re: [Finale] File Overwrite Bug in Action

Darcy James Argue wrote: I haven't tried cmd-shift-D, but last time I had the problem, I noticed it *before* closing windows because, although the displayed file was correct, printing it resulted in printing a completely different file. Re-opening the same document from Finale's File menu (with

Re: [Finale] File Overwrite Bug in Action

I don't think this is the same thing, because I seem to remember him saying that a redraw corrects, or maybe it's my jet lag talking. On 1/23/05 8:49 AM, "Christopher Smith" <[EMAIL PROTECTED]> wrote: > > On Jan 21, 2005, at 6:20 PM, David W. Fenton wrote: > >> On 21 Jan 2005 at 23:15, Jari W

Re: [Finale] File Overwrite Bug in Action

On 26 Jan 2005, at 12:07 AM, [EMAIL PROTECTED] wrote: The thing is...and maybe someone can either affirm or deny this for sure...on the Mac platform, the file is actually overwritten permanently rather than what happens in Windows if I am understanding correctly i.e. the information in the windo

Re: [Finale] File Overwrite Bug in Action

(from Jari's reply to Christopher) The questions was because it's the connection between the doc window and the enigma document database that malfunctions before the overwrite bug strikes. And I would assume that the first place to look would be at places that in some way access the table (or ar

Re: [Finale] File Overwrite Bug in Action

On Jan 23, 2005, at 12:27 PM, [EMAIL PROTECTED] wrote: That should help...also, Do you mind telling me how much RAM you have in your computer? You can do this off list if you prefer. Thanks. I'm trying to get a idea of what sorts of machines this is happening on...especially memory specs. I'm

Re: [Finale] File Overwrite Bug in Action

On 24 Jan 2005 at 22:45, Darcy James Argue wrote: On 24 Jan 2005, at 7:39 PM, David W. Fenton wrote: > Has Darcy reported low memory as a part of his problems? That's hard to say. I had 768 MB of RAM in my old Mac, but I also routinely run Mail and Safari and iKey and DragThing and RealPlayer

Re: [Finale] File Overwrite Bug in Action

On 24 Jan 2005 at 22:45, Darcy James Argue wrote: > On 24 Jan 2005, at 7:39 PM, David W. Fenton wrote: > > > Has Darcy reported low memory as a part of his problems? > > That's hard to say. I had 768 MB of RAM in my old Mac, but I also > routinely run Mail and Safari and iKey and DragThing and

Re: [Finale] File Overwrite Bug in Action

On Jan 24, 2005, at 10:50 PM, Darcy James Argue wrote: I would suggest adding (at least) another 256 MB of RAM to your PowerBook. You will notice a considerable difference. Enh, you know me. I have simple needs, and I'm not the sort of person who craves speed. I don't perceive any problem with

Re: [Finale] File Overwrite Bug in Action

Christopher Smith wrote: On Jan 23, 2005, at 4:54 AM, Jari Williamsson wrote: Here are some more thoughts: * Have you closed any documents prior to when the bug occurs? Always. * Have you had multiple windows for the same document opened? Not me, in this case. * Has any plug-ins been run that suppo

Re: [Finale] File Overwrite Bug in Action

Hi Mark, With only 256 MB of RAM on your machine, memory is likely to be tight even with only a single application open at any one time. OS X's memory demands are considerable, and most people do not believe that 256 MB of physical RAM is sufficient even for casual, everyday use. I would sugge

Re: [Finale] File Overwrite Bug in Action

On Jan 23, 2005, at 12:27 PM, [EMAIL PROTECTED] wrote: That should help...also, Do you mind telling me how much RAM you have in your computer? You can do this off list if you prefer. Thanks. I'm trying to get a idea of what sorts of machines this is happening on...especially memory specs. I'm

Re: [Finale] File Overwrite Bug in Action

On Jan 23, 2005, at 8:22 PM, [EMAIL PROTECTED] wrote: I just looked back at a couple of posts one from Chuck and one from Mark. Chuck mentioned that his system seemed to start to slow down after a long Finale session and that is when the icon for the selected tool in the tool palette turns into

Re: [Finale] File Overwrite Bug in Action

On 24 Jan 2005, at 7:39 PM, David W. Fenton wrote: Has Darcy reported low memory as a part of his problems? That's hard to say. I had 768 MB of RAM in my old Mac, but I also routinely run Mail and Safari and iKey and DragThing and RealPlayer and iTunes along with Finale, and I often have 20+ win

Re: [Finale] File Overwrite Bug in Action

On 23 Jan 2005 at 20:22, [EMAIL PROTECTED] wrote: [quoting me:] > >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, w

Re: [Finale] File Overwrite Bug in Action

Hi Jari, FWIW, I have had the bug strike without doing any of these things. I have also had the bug strike having done one or more of these things. - Darcy - [EMAIL PROTECTED] Brooklyn, NY On 23 Jan 2005, at 4:54 AM, Jari Williamsson wrote: Christopher Smith wrote: Oh, we've tried! Here are

Re: [Finale] File Overwrite Bug in Action

[EMAIL PROTECTED] / 05.1.23 / 05:32 PM wrote: FreeBSDPanther is using FreeBSD 5. Ha-ha. Didn't know that :-) It's kinda confusing since pre Jag had all the BSD man docs. I actually never installed FreeBSD I bought so I even don't know if BSD and FreeBSD shares man docs. Hiro, I'd love to hear

Re: [Finale] File Overwrite Bug in Action

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. B

Re: [Finale] File Overwrite Bug in Action

On 23 Jan 2005 at 19:18, A-NO-NE Music wrote: > David W. Fenton / 05.1.23 / 06:56 PM wrote: > > >Applications don't call the VM. The OS does, based on the memory > >requirements of the applications the OS is running. > > Perhaps you would elaborate why a huge chunk of vm is set when certain > ap

Re: [Finale] File Overwrite Bug in Action

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 oc

Re: [Finale] File Overwrite Bug in Action

On 23 Jan 2005 at 11:49, Christopher Smith wrote: > On Jan 21, 2005, at 6:20 PM, David W. Fenton wrote: > > > On 21 Jan 2005 at 23:15, Jari Williamsson wrote: > > > >> A-NO-NE Music wrote: > >> > >>> Someone pointed out the bug seems to be caused by the array > >>> pointer, and I have the same fe

Re: [Finale] File Overwrite Bug in Action

On 23 Jan 2005 at 1:59, A-NO-NE Music wrote: > David W. Fenton / 05.1.22 / 07:37 PM wrote: > > >Mac users are probably confused about virtual memory because of the > >way it was bolted onto Mac OS as an extension that often conflicted > >with applications. > > > >You're now living in a completely

Re: [Finale] File Overwrite Bug in Action

[EMAIL PROTECTED] / 05.1.23 / 05:32 PM wrote: >FreeBSDPanther is using FreeBSD 5. Ha-ha. Didn't know that :-) It's kinda confusing since pre Jag had all the BSD man docs. I actually never installed FreeBSD I bought so I even don't know if BSD and FreeBSD shares man docs. >Hiro, I'd love to

Re: [Finale] File Overwrite Bug in Action

[EMAIL PROTECTED] / 05.1.23 / 05:14 PM wrote: Apple's Darwin kernel is based on FreeBSD I thought it was BSD, not FreeBSD, no? FreeBSDPanther is using FreeBSD 5. Hiro, I'd love to hear more from you too about how Finale is using memory...and this whole topic. You seem to know much about this

Re: [Finale] File Overwrite Bug in Action

[EMAIL PROTECTED] / 05.1.23 / 05:14 PM wrote: >Apple's Darwin kernel is based on FreeBSD I thought it was BSD, not FreeBSD, no? -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Boston, MA ___ Finale mailing

Re: [Finale] File Overwrite Bug in Action

David W. Fenton / 05.1.22 / 07:37 PM wrote: Mac users are probably confused about virtual memory because of the way it was bolted onto Mac OS as an extension that often conflicted with applications. You're now living in a completely different world, one where the apps don't know anything about mana

Re: [Finale] File Overwrite Bug in Action

At 12:28 PM 01/23/2005, A-NO-NE Music wrote: >Not on Word Mac version. If you try to open the same doc, it will >replace the open one. In the effect, it does Revert to Saved. Not *open* the same doc, just a new window. In WinWord, I can do Window | New Window, which is exactly the same menu comm

Re: [Finale] File Overwrite Bug in Action

On Jan 23, 2005, at 1:08 AM, [EMAIL PROTECTED] wrote: [answering Christopher Smith] Safari leaks memory? I don't think it does anymorebut it was a problem as far as I know up until 10.3.5 and possibly 10.3.6. But I'm hearing that this was fixed in 10.3.7. I'm not exactly a computer geek, s

Re: [Finale] File Overwrite Bug in Action

On Jan 23, 2005, at 1:08 AM, [EMAIL PROTECTED] wrote: [answering Christopher Smith] Safari leaks memory? I don't think it does anymorebut it was a problem as far as I know up until 10.3.5 and possibly 10.3.6. But I'm hearing that this was fixed in 10.3.7. I'm not exactly a computer geek, so

Re: [Finale] File Overwrite Bug in Action

> >So you can easily copy music from one part of a document to another, for > >example, by having two windows open and visible. This is not unusual; Word > >lets you do the same thing. > > > Not on Word Mac version. If you try to open the same doc, it will > replace the open one. In the effect, i

Re: [Finale] File Overwrite Bug in Action

Jari Williamsson / 05.1.23 / 00:41 PM wrote: >> Not on Word Mac version. If you try to open the same doc, it will >> replace the open one. In the effect, it does Revert to Saved. > >In both Word and Finale (in Windows at least), you use "Window/New Window" I see. But Finale let you open the sam

Re: [Finale] File Overwrite Bug in Action

A-NO-NE Music wrote: Aaron Sherber / 05.1.23 / 11:33 AM wrote: So you can easily copy music from one part of a document to another, for example, by having two windows open and visible. This is not unusual; Word lets you do the same thing. Not on Word Mac version. If you try to open the same do

Re: [Finale] File Overwrite Bug in Action

Aaron Sherber / 05.1.23 / 11:33 AM wrote: >So you can easily copy music from one part of a document to another, for >example, by having two windows open and visible. This is not unusual; Word >lets you do the same thing. Not on Word Mac version. If you try to open the same doc, it will replac

Re: [Finale] File Overwrite Bug in Action

A-NO-NE Music wrote: Jari Williamsson / 05.1.23 / 04:54 AM wrote: * Have you had multiple windows for the same document opened? I even didn't know this is possible. I just tried, and sure enough, Finale let you do this. But why? It's an easy way to copy sections of a piece to another

Re: [Finale] File Overwrite Bug in Action

On Jan 21, 2005, at 6:20 PM, David W. Fenton wrote: On 21 Jan 2005 at 23:15, Jari Williamsson wrote: A-NO-NE Music wrote: Someone pointed out the bug seems to be caused by the array pointer, and I have the same feeling. As I've said earlier when this have been discussed, the window handle/ID starts

Re: [Finale] File Overwrite Bug in Action

On Jan 23, 2005, at 4:54 AM, Jari Williamsson wrote: Christopher Smith wrote: Oh, we've tried! Here are some things that have cropped up, confirmed and unconfirmed by others: [...] Here are some more thoughts: * Have you closed any documents prior to when the bug occurs? Always. * Have you had mu

Re: [Finale] File Overwrite Bug in Action

At 11:27 AM 01/23/2005, A-NO-NE Music wrote: >Jari Williamsson / 05.1.23 / 04:54 AM wrote: > >>* Have you had multiple windows for the same document opened? > > >I even didn't know this is possible. I just tried, and sure enough, >Finale let you do this. But why? So you can easily copy music fro

Re: [Finale] File Overwrite Bug in Action

Jari Williamsson / 05.1.23 / 04:54 AM wrote: >* Have you had multiple windows for the same document opened? I even didn't know this is possible. I just tried, and sure enough, Finale let you do this. But why? -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Boston, MA

Re: [Finale] File Overwrite Bug in Action

Christopher Smith wrote: Oh, we've tried! Here are some things that have cropped up, confirmed and unconfirmed by others: [...] Here are some more thoughts: * Have you closed any documents prior to when the bug occurs? * Have you had multiple windows for the same document opened? * Has any plug-i

Re: [Finale] File Overwrite Bug in Action

Safari leaks memory? I don't think it does anymorebut it was a problem as far as I know up until 10.3.5 and possibly 10.3.6. But I'm hearing that this was fixed in 10.3.7. I'm not exactly a computer geek, so I don't know what this means. It is when an application, because of a bug, fails t

Re: [Finale] File Overwrite Bug in Action

On Jan 22, 2005, at 7:07 AM, Jari Williamsson wrote: Perhaps it would be more productive if the Mac users who repeatedly experience this problem analyzed (in detail) what they did _prior_ to when the problem occured that is _different_ to what they do when it does _not_ happen. It can be any sil

Re: [Finale] File Overwrite Bug in Action

Christopher Smith / 05.1.23 / 02:33 AM wrote: >I did not know that. You were right on to point that out to me. I ran >Terminal for the first time when Karen mentioned it a few posts ago. There are a few useful tools: MemoryStick: This wil

Re: [Finale] File Overwrite Bug in Action

On Jan 21, 2005, at 1:39 AM, A-NO-NE Music wrote: You might want to consider rebooting OSX time to time because the number of swapfile will not go away less than 4 or 5 until you reboot. OSX needs about 1GB free space for vm stack, which can be eaten up quickly when swapfile() accumulates 6-7 of

Re: [Finale] File Overwrite Bug in Action

On Jan 20, 2005, at 7:47 PM, [EMAIL PROTECTED] wrote: On my machine, I got to the paging stage with no other files open (pictures, PDF's etc.) in the other applicationsjust files open in Finale. Add PDF's pics etc in and I'll bet you are getting low on free memory. Additionally, if there i

Re: [Finale] File Overwrite Bug in Action

David W. Fenton / 05.1.22 / 07:37 PM wrote: >Mac users are probably confused about virtual memory because of the >way it was bolted onto Mac OS as an extension that often conflicted >with applications. > >You're now living in a completely different world, one where the apps >don't know anything

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 18:14, [EMAIL PROTECTED] wrote: >On 21 Jan 2005 at 15:43, [EMAIL PROTECTED] wrote: > >> >[EMAIL PROTECTED] / 05.1.21 / 00:52 PM wrote: > >[] > >> But I think that if the problem was solely due to an address bug, >> it would happen more often. And problems with addressi

Re: [Finale] File Overwrite Bug in Action

On 22 Jan 2005 at 16:18, Jari Williamsson wrote: > David W. Fenton wrote: > > > But it *has* happened to *me* on Windows -- I've never lost data, > > but as I've said many times, I've seen the wrong data displayed for > > the window titles (i.e., document names). > > And I also saw this occasion

Re: [Finale] File Overwrite Bug in Action

On 22 Jan 2005 at 9:13, Darcy James Argue wrote: > > Darcy James Argue wrote: > > > >> I have no idea if that's a workable solution, but I would like Coda > >> to at least *try* it. Since the problem with the corrupted > >> pointers is proving elusive, maybe it's time to address the root of > >>

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 23:00, A-NO-NE Music wrote: > David W. Fenton / 05.1.21 / 06:10 PM wrote: > >The programmers of OS X, you mean -- Finale knows nothing about > >virtual memory, which is entirely handled by the operating system's > >virtual memory subsystem. > > Well, Finale might or might not, w

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 18:14, [EMAIL PROTECTED] wrote: > >On 21 Jan 2005 at 15:43, [EMAIL PROTECTED] wrote: > > > >> >[EMAIL PROTECTED] / 05.1.21 / 00:52 PM wrote: > > > >[] > > > >> But I think that if the problem was solely due to an address bug, > >> it would happen more often. And problems with

Re: [Finale] File Overwrite Bug in Action

David W. Fenton wrote: But it *has* happened to *me* on Windows -- I've never lost data, but as I've said many times, I've seen the wrong data displayed for the window titles (i.e., document names). And I also saw this occasionally in FinWin2003, but I believe it was fixed in FinWin2004. Or are

Re: [Finale] File Overwrite Bug in Action

- Darcy - [EMAIL PROTECTED] Brooklyn, NY On 22 Jan 2005, at 9:13 AM, Darcy James Argue wrote: Darcy James Argue wrote: I have no idea if that's a workable solution, but I would like Coda to at least *try* it. Since the problem with the corrupted pointers is proving elusive, maybe it's time t

Re: [Finale] File Overwrite Bug in Action

On 22 Jan 2005, at 7:07 AM, Jari Williamsson wrote: Darcy James Argue wrote: (Of course, they could also just fix the problem where the window handle/ID starts to map to the wrong Enigma Doc ID, but apparently that's easier said than done.) But that's _exactly_ what they have to do!!! Moving the

Re: [Finale] File Overwrite Bug in Action

Darcy James Argue wrote: I have no idea if that's a workable solution, but I would like Coda to at least *try* it. Since the problem with the corrupted pointers is proving elusive, maybe it's time to address the root of the problem -- shared temp files. If the same temp files weren't shared b

Re: [Finale] File Overwrite Bug in Action

Darcy James Argue wrote: (Of course, they could also just fix the problem where the window handle/ID starts to map to the wrong Enigma Doc ID, but apparently that's easier said than done.) But that's _exactly_ what they have to do!!! Moving the Enigma mapping currently made to disc into RAM will

Re: [Finale] File Overwrite Bug in Action

Darcy James Argue wrote: I have no idea if that's a workable solution, but I would like Coda to at least *try* it. Since the problem with the corrupted pointers is proving elusive, maybe it's time to address the root of the problem -- shared temp files. If the same temp files weren't shared by

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 15:43, [EMAIL PROTECTED] wrote: >[EMAIL PROTECTED] / 05.1.21 / 00:52 PM wrote: [] 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

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 18:39, Darcy James Argue wrote: > I think the people who are blaming memory paging for the corruption > have a fundamental misunderstanding of the structure of a modern > operating system. Just to be clear -- I'm not "blaming memory paging for the corruption" and I don't thin

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 20:02, Darcy James Argue wrote: > Okay, I see what you are saying now -- I assumed that OS X was > accurately reporting the size of Fin temp files, whereas Windows was > just giving you zero KB for the whole temp files folder. . . . I'm just reporting how other database applica

Re: [Finale] File Overwrite Bug in Action

Hi David, Okay, I see what you are saying now -- I assumed that OS X was accurately reporting the size of Fin temp files, whereas Windows was just giving you zero KB for the whole temp files folder. But what you say makes sense. I would like some confirmation from Coda about this, though. Se

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 19:32, Darcy James Argue wrote: > Brooklyn, NYOn 21 Jan 2005, at 7:10 PM, David W. Fenton wrote: > > > I don't know what the actual filespace usage of Finale temp files on > > disk > > Mine are typically 11-15 MB total, which is practically nothing. It > seems silly to write f

Re: [Finale] File Overwrite Bug in Action

Brooklyn, NYOn 21 Jan 2005, at 7:10 PM, David W. Fenton wrote: I don't know what the actual filespace usage of Finale temp files on disk Mine are typically 11-15 MB total, which is practically nothing. It seems silly to write files that small to disk, instead of to RAM. So, my assumption is that

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 19:13, Raymond Horton wrote: > In FINWIN 2005a, I have often extracted a part from a score, then > edited the part. Then when I come back to the score, I temporarily > see the part where the score should be until I do a screen redraw. > > This is as close as I have ever gotten

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 15:43, [EMAIL PROTECTED] wrote: > >[EMAIL PROTECTED] / 05.1.21 / 00:52 PM wrote: [] > 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 worki

Re: [Finale] File Overwrite Bug in Action

In FINWIN 2005a, I have often extracted a part from a score, then edited the part. Then when I come back to the score, I temporarily see the part where the score should be until I do a screen redraw. This is as close as I have ever gotten to this bug. Is this, by any chance, what you mean by

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 18:39, Darcy James Argue wrote: > > I think the people who are blaming memory paging for the corruption > > have a fundamental misunderstanding of the structure of a modern > > operating system. > > Just to be clear -- I'm not "blaming memory paging for the corruption" > and I d

Re: [Finale] File Overwrite Bug in Action

[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 cre

Re: [Finale] File Overwrite Bug in Action

Hi David, I think the people who are blaming memory paging for the corruption have a fundamental misunderstanding of the structure of a modern operating system. Just to be clear -- I'm not "blaming memory paging for the corruption" and I don't think anyone else here is either. What I'm suggesting

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 23:15, Jari Williamsson wrote: > A-NO-NE Music wrote: > > > Someone pointed out the bug seems to be caused by the array pointer, > > and I have the same feeling. > > As I've said earlier when this have been discussed, the window > handle/ID starts to map to the wrong Enigma Doc

Re: [Finale] File Overwrite Bug in Action

On 21 Jan 2005 at 1:23, A-NO-NE Music wrote: > Just to be clear, > Only the programmer knows how Finale is paging. For example, on my: > > Dual-450/1.5GB 37.54MB RAM, 267.98MB vm > TiBook800/1GB 30.75MB RAM, but only 159MB vm > > FinMac2005a (initial launch, one doc open) on OSX10.3.7 (cold

Re: [Finale] File Overwrite Bug in Action

A-NO-NE Music wrote: Someone pointed out the bug seems to be caused by the array pointer, and I have the same feeling. As I've said earlier when this have been discussed, the window handle/ID starts to map to the wrong Enigma Doc ID. I think that's pretty obvious, but of course that doesn't expla

Re: [Finale] File Overwrite Bug in Action

[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 sta

Re: [Finale] File Overwrite Bug in Action

On 20 Jan 2005, at 07:47 PM, [EMAIL PROTECTED] wrote: Finale uses a lot of memory I have noticed. It uses a lot of shared memory too which leads me to believe that the new graphics are using up a lot of memory. I personally would trade the nice graphics for having the program use less memory.

Re: [Finale] File Overwrite Bug in Action

Christopher Smith / 05.1.20 / 08:32 AM wrote: There's a kicker. I usually have a bunch of stuff open at the same time, like AppleWorks, Mail, Safari, TextEdit, Preview, and maybe Word or Excel. I typically only quit one of the first five apps or Finale when it acts up (rare these days in OS X) or i

Re: [Finale] File Overwrite Bug in Action

Christopher Smith / 05.1.20 / 08:32 AM wrote: >There's a kicker. I usually have a bunch of stuff open at the same >time, like AppleWorks, Mail, Safari, TextEdit, Preview, and maybe Word >or Excel. I typically only quit one of the first five apps or Finale >when it acts up (rare these days in OS

  1   2   >