wrote:
> <snip>
>>This isn't a Windows issue, so it's off topic... but you know that
>>already.
>
> I disagree. Many questions are asked and answered here where the problem may or may not be an OS
> question. The poster is having an issue running application in Win 7. Until the solution is known,
> one can't say there is not some setting in Windows that can resolve the issue. Even it not a Win 7
> issue, the group consist of Win 7 users and as such someone may be able to help... and after all
> isn't that what the group is for? If you don't want to answer all you have to do is keep quiet.
Except you replied to the wrong post. You replied to Rick, the OP, who
asked for help, not to SC Tom. Could be a problem with your choice of
newsreader: NewsLeecher. It's probably geared to yanking attachments
from posts in binary groups than for participating in discussions.
GrabIt is like that: okay for yanking binaries but sucks for discussion.
Notice NewsLeecher doesn't even bother to insert the References header
needed to properly thread the posts in a discussion to show their
hierarchy. Without the References header, all a newsreader has for
threading is the Subject header, and that means a flat setup instead of
a hierarchy of posts into threads (so your reply looks like it was to
the Rick and not to SC Tom).
If you intend on participating in discussions then use a newsreader that
adds the References header. The References header was defined in RFC
822 way back in 1982. There's no excuse your newsreader doesn't include
it in your replies. Newsleecher is a crappy news*writer*. It was
designed to be a news*reader*. And yet they have the gall to charge $20
for this grot. I didn't think there was a worse newsreader than Outlook
Express but I was wrong. Newsleecher is worse.
However, the whole thread is moot as Rick decided after waiting only 48
minutes (probably much less) that there would be no response to his post
in the Mozilla forum. Yeah, not long, but apparently Rick wasn't going
to wait for replies and wasn't really that interested in fixing the
problem with Firefox since he then decided to do none of the
troubleshooting mentioned here and uninstalled Firefox and returned to
IE as his web browser. He wanted instant gratification with no effort
on his part to diagnose the problem so anything we suggested was a waste
of our time. The OP is gone and now using IE. That's his immediate
solution.