David wrote:
Message: 4
Date: Mon, 05 Apr 2004 13:35:35 -0400
From: "David W. Fenton" <[EMAIL PROTECTED]>
Subject: Re: [Finale] Re: David's issue
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII
Uh, no, it can't possibly be that: etc.
and a lot of other stuff that shouldn't have been written at all.
This is what I get for trying to help someone unappreciative. Pray, David, did your mama teach you to talk that way to complete strangers?
Since you feel it is in your right to talk to me that way, I am so entitled as well. The first thing I will say is that if you know it all then why the Hell did you have to ask us? And even more why the Hell did you ask us if someone might say something you didn't want to know about and would put your bowels in an uproar?
Oh yeh, before I start -- you assumed I was a Mac person. I'm *not*. I'm WinFin all the way -- with no major issues *ever*. I'm also my "IT prof" (the exact phrase I used was "IT prof opinion" falling back on 15 years of support and experience). This is what you get for assuming and I'm sure you've heard the old adage about what AssUming does.
Now, the thing I would have done was to call up support and email them the file ... asking them instead of us. They have the "known issue" database at hand. That's what you paid them for. You *did* pay them didn't you? Don't you want your money's worth? If that's why you're asking here and not there then it's no wonder your machine's failing since you'd've been trusting the crackheads and warezheads, and I daresay you get what you bleeding well deserve if that's the case.
Since Mac people can open your file, having a Mac person translate it (since they can open it) and saving it under a new name for retranslation should fix the problem for you (and support can do this for you on clean machines -- not your buddy's machine that has all sorts of gobbledygook that *he's* using on it, if he exists -- while you're on the phone if you need proof). That doesn't explain how the issue came to be or guarantee that it won't happen again. All you get from that is work in Finale saved which you should have been backing up which you would know if you "did this for a living." So you still have some sort of issue among many -- but I'm only dealing with your file issue, can't help you on the others -- on the OS/Hardware level else it wouldn't have gotten that way in the first place. These things don't happen by themselves. I might be full of shit but if You weren't fuller, you wouldn't be asking us. Quid pro quo, dearie.
Or to put it simply, there's no place for the issue to be other than these possibilities:
1. Peculiar WinFin glitch -- this would have to be related to paging/saving, so you still have the hardware/OS bugaboo. Not WinFin's fault, else we'd all experience it somewhere -- so the screwup was while something was being written to the drive. See #3.
2. Software conflict -- if the file opens in safe mode you have one.
3. File structure issue -- cure is restructure. Temporary cure is file structure utilities.
4. Hard drive failure -- cure is replacement and restructure.
That makes 3 out of 4 being a restructure and one is easily testable.
If you do this for a living I shouldn't have to tell you this, but then again you are the All-Being, Master Of Time, Space & Dimension and I'm not. I'm just the guy who doesn't have these sorts of issues with WinFin.
You can spend time trying to isolate the esoteric problem and fixing it or you can spend a lesser amount of time starting with a clean slate and curing all potential ills in one fell swoop -- the ounce of prevention is a pound of cure. Do what you will as it's your machine, but don't ever say that no-one tried to help you, you unappreciative excuse for a git. When you've spent more than a day on this issue you think about how you could have had it over and done with in a few hours, and *enjoy* the opportunity you've had to drive yourself crazy.
Keef.
_______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
