On 5 Apr 2004 at 13:24, Keef wrote: > Sounds like a paging issue to me, and would point to a hard drive > getting ready to croak in some manner (physically or informationally).
Uh, no, it can't possibly be that: 1. saving as ETF then opening the ETF exhibits precisely the same crash at precisely the same point. 2. a truncated version of the file (only the 3rd movement) exhibits the exact same problem at exactly the same measure, only this file is much smaller (and the measure number is 94 instead of 452), and is a different file on the hard drive (stored in a different sector). 3. another person with WinXP and WinFin2K3 experiences the same crash. > If you can open the file on other machines and scroll past the > measure, it's *not* the file or Finale. My IT prof guess is that you > have some sort of "hole" in your drive (file structure issue -- either > physical as in a ding on the drive, or structural as in your file > system). . . . I would say your IT prof is an idiot. I do this for a living -- his explanation makes absolutely no sense whatsoever. > . . . When you page so many graphics to wherever on the drive this > is handled, and the mail slots taken by the paged information do not > match what the map says their location is (resource forks, etc), . . . Resource forks do not exist on the PC. > . . . you > get all sorts of bizarre crashes because the information the system > expects isn't there or is the wrong information. Maybe on a Mac, but not on Windows. > If you are pressed for time as you probably are, the answer is to wipe > the slate clean, so to speak. There is no sense in chasing your tail > to fix a problem when it is possible that there can be a domino effect > costing you valuable time. It sounds like a big job but it isn't if > you are prepared for it. As it stands now my system could fail > immediately and I would be back up in about four hours. Er, no, thanks. I'll just leave it alone. Backups are good, yes, but I don't have a problem that warrants rebuilding the drive in question. > You may be (very likely) looking at a restructuring of your hard > drive, and I would prepare accordingly. *NOW*. Just in case it is > your hard drive failing or in the process of failing -- better safe > than sorry. In the meantime make sure that all utilities to correct > this (Disk Dr, etc) are run, but be aware that they can lie -- so > whatever it fixes is a temporary measure only. Do not trust it > implicitly. Clearly, you don't have much experience in this field. Maybe the Mac is so unreliable (though I strongly doubt it), but on PCs, it just doesn't happen that way -- the symptoms of disk failure or disk structure problems just don't look like this (and the NT file system is self-repairing for a lot of low-level problems, anyway, so you never even know there was a problem). > When this happens to me, I take the necessary steps to put a new drive > in the machine regardless (to save myself the headache), and relegate > the possible bad drive to a secondary drive situation (usually > externally). Sometimes a repartitioning fixes the issue and I can > recycle the drive, sometimes the drive is dead. The idea here is to > get your stuff protected absolutely *before* you start determining > whether the drive is still good. This may seem drastic but from 15 > years experience I have learned that this is the most sensible > approach when problems like this happen, and I build my systems on the > assumption that this will happen eventually. I think you're completely full of beans. -- 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
