Oh just the simple fact that they might have told you the same thing and since you didn't want to accept that as a possibility or likelihood, you come to us looking for someone who'll tell you what you want to be told, rather than how to fix the problem (and the problem is in case you'd forgotten that during a write operation to the drive involving Finale there was blockage). And the action to take was first to see if you can salvage the file and then more importantly to prep your system so that it doesn't happen again. It is possible that you yourself were responsible for the interruption during the write process (like having Windows force the program closed in its various ways or a manual reboot), and you're rather conveniently not chinning up to that possibility. I was discounting this on what little good faith I had. If support couldn't get the file back in the way I described, you *lose.* You can put a bag over your head and scream if you like. Good. I look forward to rendering you speechless in the future. Seems like it might be a good thing.As to the rest of your message, I have nothing to say. Okay. I'm wrong. Good. Doesn't matter whether I'm wrong or right. Telling me so won't fix the problem, or suddenly keep you from being an unappreciative excuse for a git. You lose and you'll have to do some real work I'm afraid. Spend your time how you wish because after all, you're always right and everyone else is always wrong, and I'm not the first person to notice that. I'm willing to bet my eyeteeth that when your system does go down (and it will) everything will run smoothly once you get it back up and running until you screw with it again. .You are simply wrong that the symptoms described along with all the different things I described could possibly have been caused by a problem in the file system of my computer.Wrong. Keef. Keef. |
_______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
