Hmmmm..... was this intended for me? That would be odd, if not more than a wee bit snarky, so I'm hoping that I'm reading this wrong. It's not like I can just sit around and watch this thread for responses all the time.... in fact, reading your last post, it seems that you thought the discussion of my issue should end, at any rate, because you deemed it irrelevant to this thread, and no one else was commenting at all. The fact that we're on the road most of this month and the next, notwithstanding, making it less likely that I would be glued to Taperssection 24/7.....
For the record, I'm ALWAYS thankful for anyone who might take an interest in trying to help me solve a problem, if you're concerned about that - although interestingly, I've never actually received answers to the specific questions I've asked here, such as HOW to use the header repair utility; as I explained a few times, I could not get my head around that, and no one has replied with info that would help me understand it. I appreciate the fact that you took a look at my problem file, but can you at least wait until I have time to sort through these things, before I give you a response?
Ironically, by sheer dumb luck, my wife actually resurrected this file just recently, using a trick she learned from some of the developers she works with: using a binary reader, she went past the presumed header, into the data area, and randomly plucked out two pairs of zeros. That reversed the flaw in the file, turning the first two minutes of the .wav file into an overloaded signal which could almost be mistaken for white noise, and all of the audio from the set appeared, and after careful eximination, is stable. God bless taper's wives; good thing I married a fellow geek!
Of course, I STILL have no idea how to work with the wave header repair utility, although now I DO have a better understanding of what a .wav file actually looks like in a binary reader.
You're welcome.