Mack, as noted, was simply being impatient. As for your post, there are
approx. 1000 posts per day in this NG. Most of the worker bees here focus
upon issues for which they have an immediate answer or are interested in
researching (which is something most of us MVPs, anyway, are most interested
in. That's where all the fun comes from.) If we have no answer, and the
issue simply isn't within our personally determined perview, the responsible
among us don't respond. That way when someone comes along who might have an
answer, they aren't put off by some lengthy but wildly irrelevant thread
that is engendered by the less responsible among us (lots of wrong answers
or just plain stupidity and troll-like arguing,) or they see that a known
responsible person has posted to the thread a few times and figure it's
handled.
My routine is to refresh all the NGs I participate in, look for new posts in
threads where I'm already participating (in the Windows 98 groups that is my
primary interest), reply as necessary, then check all the (few) new posts in
those groups, then come to this and the XP.General groups and respond to
threads where I've already joined in discussion. Once that's all taken care
of, I start over. When I'm totally caught up, I start reading new posts in
the Vista and XP groups. But it only takes a little time for unread messages
in these two groups to number in the hundreds, so I simply mark them all as
Read, and then finally review the latest ones for anything I'm interested
in. Which is how I happened upon Mack's un-called-for comments, decided to
get him started on a solution, anyway, after reading your initial post and
thinking bout it in the back of my mind while I worked on his issue, and
then, finally, responded directly to your initial post.
Anyway, to answer your question more succinctly, no, you didn't do anything
wrong. As I said in the other reply, I think it's just a bug in Vista that
may or may not be able to be fixed in the future (if it's not Explorer
itself, it's likely some part of IE), and that you should simply re-post it
every month or two until someone sees it who knows what's what. Your issue
is so unique that I don't think anyone else has probably ever come across
it, but you never know. Regardless, you should definitely follow through
with a bug report via the second link I provided in my other reply.
--
Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com
"Threshold" <> wrote in message
news:...
>
> Ok and still what about my problem?
> Are we doing something wrong so that nobody replies? 
>
>
> --
> Threshold