In a message dated 3/3/04 9:37:35 PM GMT Standard Time, bobv@... writes: > Now it is up to us to precisely tell them how we got this result. It > may not hurt to not only tell them how we got the result but also > email them the song you are working on that produced this. Do not > email it here. I do not know for sure where it should go but > support@... may be a good bet. Hello Bob Vandiver, I understand what your saying, but between you and me, they never replied a single email I sent out to them. Do you get me? Gino

> Hello Bob Vandiver, > > I understand what your saying, but between you and me, they never replied a > single email I sent out to them. Do you get me? > > Gino I get you. Their job is to write great software and collect the data needed to do so. Replying to every bug report is a different priority, one best suited to their advertising staff. Bob Vandiver

>I get you. Their job is to write great software and collect the data >needed to do so. >Replying to every bug report is a different priority, one best >suited to their advertising >staff. Actually, how about assigning a technical "receptionist' to let one know the info has been received? Even a reply-bot might suffice. Getting no response at all is insufficient. What shall I expect an advertising staff really to know about _bugs_? "They'll die in the next upgrade; that's the ticket". -- hank alrich * secret__mountain audio recording * music production * sound reinforcement "If laughter is the best medicine let's take a double dose"