On 14 Jul 2005 06:05:07 -0700, "Dima" wrote in comp.arch.embedded:
What could possibly make you think this question has anything at all to do with embedded systems? Try a Microsoft support group.
--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~ajo/docs/FAQ-acllc.html
Well, since you neglected to include any context, the SW in the US generally covers such states as California, Arizona, New Mexico. Similarly a Thunderbird may be an alcoholic drink or a breed of automobile, by Ford.
--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
You obviously have no idea what you are really dealing with. That's alright, none of us were born knowing everything.
Google groups is a very poor interface to the usenet system (which you can make useful by following the instructions in my sig below. The sig is the portion following the "-- " marker.) Googles forte is archiving things, including usenet. Most news servers expire news articles in a short time (a few days to a few weeks) after which they are gone forever.
Usenet extends world wide, and has been around a lot longer than google, or the WWW system. Most participants use a mailer which communicates with a news server (which google is not, it depends on a newsserver too). There is never any guarantee that any previous message is (or will ever be) available. Thus all articles have to stand on their own, and require proper context (quotations) and attributions (who said what). The '>' at the left of a line indicate a quotation, and the number of '>'s ties that line to an attribution.
Your ISP normally provides a newsserver. Some poorer ISPs do not.
Netscape (before version 8) and Mozilla can provide complete news, email, and WWW access, and are available for many systems. For news only (usenet) there are various readers, including xnews (but only for windows) and Thunderbird (which includes email). Some also include Outlook Express here, but that is also windows only and, until the appearance of the google interface, was far and away the worst possible mailer to use. There are also addons to EMACS such as gnus, with which I am not familiar. And others.
Here are a few references to read:
formatting link
formatting link
formatting link
formatting link
formatting link
formatting link
--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
Ah. Since you didn't quote my article, I didn't know you were asking me a question. You're not going to get very good results in Usenet unless you learn to follow the "rules".
SW == software
Thunderbird == a mail program that doesn't suck
formatting link
Why are you asking questions about Outlook in comp.arch.embedded????
--
Grant Edwards grante Yow! Hey, LOOK!! A pair of
at SIZE 9 CAPRI PANTS!! They
visi.com probably belong to SAMMY
DAVIS, JR.!!
A tree view is a concept of the used newsreader, not of Usenet itself. So anyone who jumps in into the middle of the discussion, might not see previous messages in his "tree view" because the messages might simply not be there.
You have made the mistake of assuming that Google Groups _IS_ Usenet.
It is not. Usenet is a global network of servers exchanging newsgroup messages using the NNTP protocol (and in times gone past, UUCP based protocols).
Google is merely one (large) site on this network. All that is different about Google is that it has decided to collect these messages and present them via a web based interface. Any messages entered by users of this web interface are then injected into this global network of Usenet servers by Google.
I, for one, use a text based client (running in a terminal session) and not a web browser when reading Usenet and posting to it.
Many of us (myself included) have been using Usenet before either Google or web browsers existed.
Based on your comments here, it seems that Google has not done a good job of explaining this.
HTH,
Simon.
--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Microsoft: The Standard Oil Company of the 21st century
Of course they do, many readers offer a tree view. But as I have told you before, this tree view is presented by the NEWSREADER and dependent on the messages the newsreader has stored. If I for instance, at this moment, decide to subscribe to comp.arch.embedded, there might be thousands of messages present. The first thing I do is apply the "Catch Up" function to start with a clean (=empty) list. If you then post a reply after that, to a message which was posted before I did the "Catch Up", I will only see your reply, no matter what Tree View I have. Clear now?
Example: I read this answer of yours, but I cannot see to whom you are replying, because after the catch up I did yesterday (which at least hides the read messages), I do not see previous messages from this thread in my tree view.
And that is why you have to qoute some of the originating text.
My newsreader also has a "tree view", but I still can't make sense of this thread. I don't keep messages I already marked as read, as do many others, so this "tree" now only consists of 3 contextless replies by you.
Not seeing read messages means I only see a dozen messages in this group every time I look. This is so much easier than to struggle through about
30000 messages each time I look.
--
Stef (remove caps, dashes and .invalid from e-mail address to reply by mail)
A man usually falls in love with a woman who asks the kinds of questions
he is able to answer.
-- Ronald Colman
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.