Oops, I almost forgot. Don't you DARE respond to this on any of these Lists!!!!! This was meant in fun and intended to provoke thought among all you users. If you MUST respond, please do so to my personal email address, which you can certainly pick out from the FROM: header line in the message. SgtGeorge
Folks, here it is! At long last, the short, concise, "true" "Guide On How To Compose Email To Mailing Lists & Newsgroups". This message is from the Listowner of 11 Mailing Lists and 5 Newsgroups. I know whereof I speak and can attest to the fact that the following "Guide" from Richard Pence is the only one you, as a subscriber, will ever need. Please read all of it and learn something from it. (GRIN) (Gosh, I love it!!!!! Dick, you will surely win a Pulitzer Prize for this one.) *************************(Start of Quoted Message)************************* PREFACE: Over the past couple of years it has become increasingly apparent that many participants in the genealogy newsgroups are failing to fully utilize the potential of these media. Therefore, the following guidelines are presented for the benefit of both veterans and newcomers in the hope they will result in more effective participation by all. Effective Use of Genealogy Newsgroups 1. USE "HOT WORDS": Be sure to include one or more of the following words or phrases in either the subject or body of your messages: geneology, cemetary, calender, sirname, illigitimate, ancester, Morman, land warrent, proginy or desendant. Similar displays of originality are encouraged, as these help attract attention to your posts and demonstrate you are eager to learn. Note also that it isn't necessary to use normal punctuation or grammar in newsgroups because everyone knows what you intended. 2. POST EARLY AND OFTEN: No matter what you are writing about, you should post your messages in as many different newsgroups as possible. After all, the people who originally defined the content of each newsgroup couldn't possibly have anticipated that your messages would all transcend normal categorization. Bonus tip: Always vote "yes" when a new genealogy newsgroup is proposed, as this will give you another place to repeat your posts. It can always be assumed that if the newsgroup title includes the word genealogy, it's OK for you to post there. 3. QUOTE THE QUOTE: When replying to another article, by all means quote it in its entirety, including previously quoted material, the mail routing information and, especially, the total signature of the original poster. Otherwise, someone might not know what message you are replying to and where it came from. Alternatively: Don't quote any of the previous message; readers will enjoy the challenge of guessing what you might be referring to. One-line responses like: "I don't believe this is always true" are real attention-getters. 4. SIGN OFF WITH STYLE: Be sure to make the signature at the end of your messages as long as possible and include it with every one of your posts. The signature should always include your full name, address, phone numbers (including fax and modem), website address or addresses, and so on, for both your residence and office. Don't forget to include any titles, degrees or offices held (now or in the past), or the names of genealogical or other organizations to which you belong or belonged. Signatures should always have a large design made up of ASCII characters (simple + and - signs aligned across the page are hardly adequate because they don't lengthen your signature enough. If your imagination is faltering, a design showing a little man with a long nose, bulging eyes and his hair on end clutching at and peering over a fence is always a good choice. Your signature should _never_ be without one or more quotations, slogans (political slogans or those disparaging "the government" are always hits!) or "wise sayings," correctly or incorrectly attributed to famous people. If you don't have any good quotes from famous people, it is OK to swipe a cutesy one from someone else. Or you can use your state motto. Do NOT forget the disclaimer telling readers that what you write is your own opinion and does not represent the views of your company, your spouse, your children or neighbors. Your signature reflects YOU and YOUR personality, so you shouldn't spare the horses! [NOTE: The "non-signature signature" is an appropriate alternative. Under this method, you should never disclose your identity or where you are. Initials, "handles" or other esoteric identifiers are all acceptable. After all, it is never wise to tell people who you are in a public forum, especially one devoted to genealogy.] 5. CHOICE SUBJECTS: The best subject lines are quite general. If you include such phrases as "Help Needed," "Tracing My Geneology" (note the example of "hot word" usage), "What Do I Do Now?" or "Software Problem," readers must actually look at your article to find out what you are writing about. This gambit will solidify your reputation as a marketing whiz! 6. SURNAME QUERIES: When posting a surname query, it is not necessary to include such trivia as where the family lived or when. After all, anyone searching that name will know whether his or her line is related to yours. A query with the subject of "SMITH, JONES and JOHNSON" with the message asking "Anyone searching these families?"will garner many responses from others searching these lines. 7. BOOK-SHY: Questions that can be answered by looking in a dictionary or other common home reference, such as a roadmap or atlas, or by checking any one of a half-dozen websites are excellent choices for your postings. These always garner many responses and, at the same time, assure that no dust collects on the books owned by others. If you handle this with finesse, you can even get others to look up local phone numbers for you! Remember: The purpose of newsgroups and, indeed, the Internet itself, is to enable you to avoid visits to libraries, court houses or archives or having to look at musty old books. 8. BE AMONG THE FAITHFUL: True and faithful newsgroup participants respond to as many messages as possible, even if they are unfamiliar with the topic. Readers are always interested in the opinions of others, especially yours. Messages that begin with "I have heard that...," "Someone told me...," or "I always thought..." are among those which get high readership and help demonstrate the knowledge of and experience in genealogy of the posters. It is never necessary to cite an authority when making such responses; including such extraneous information draws attention from the answer. 9. KEEPING THE CROWD INFORMED: Always post your responses within the group itself rather than replying via private e-mail. Not only will this allow everyone to benefit from what you say, it gives them a sense of security to know they haven't missed anything. Requests that responses be made via e-mail are obviously not intended for you. And, if you get a message from someone warning about a virus that has invaded newsgroup messages or one warning about another dumb thing "the government" is doing, by all means post it in as many groups as possible. 10. MAKING SURE: If you do not see your article in the group within the hour, be sure to re- post it as soon as possible. Duplicate postings help assure that others will not miss your important messages. If, after several tries, no one responds, you should post several test messages asking everyone who sees the message to respond in the group so you can be sure your connection is working correctly. If is never sufficient to test your local connections. The only tests that get results are those which cover the entire Net. 11. CRAFTING CRAFTY REPLIES: Here are some tips that can help you with your newsgroup responses: (a) When someone asks for recommendations on "the best genealogy software," it is not necessary to know what equipment the person has or what his or her experience is in genealogy and computers or his or her genealogical goals. Simply respond saying, "I use ---- and LOVE it!" program YOU use. The same response is appropriate is some else says they like a different program. (c) The proper format for replies to surname queries is: "Were any of your SMITHs ever in [insert state here]?" Disregard any references to specific places. (d) The answer to the "cousin question is _always_ "second cousin, once removed." There are no exceptions. (e) If someone asks a question you may not know anything about, the proper response is a message giving the details of a family story your Great Aunt Betsey once told you. Special hint: When someone asks about an unusual given name or surname, be sure to respond with a message saying you are not familiar with that name, "but here are some of the unusual names I have encountered in my research...." (f) Even if a question has already been answered, you should also respond. Quote the entire question and the response and add: "I agree." (g) Above all, do not refer someone to a FAQ, website or other authority on the topic. This prevents thousands of others from benefiting from your knowledge and experience. Besides, most FAQs were written specifically for the purpose of heading off certain on-line discussions and, consequently, are obviously an effort to stifle free speech, and every knows you have the right to say whatever you please on the Internet. (h) If your response is especially important, WRITE IT IN ALL CAPITAL LETTERS. That way it will be sure to be read by everyone. 12. I KNOW IT'S TRUE: Finally, it is always safe to rely on the responses you see in the various newsgroups because no genealogist would post unless he or she was quite sure of the accuracy of what is being written. This is especially true if the question is: "What given name does the abbreviation 'Jno.' stand for?" (No fair looking in your dictionary!) ------------------------------------------------------------------------ [Before you start sending threatening mail, please look at the date this message was posted. If you still having problems understanding the meaning of the above, you should consult your children as quickly as possible. Do NOT wait until the weekend.] DISCLAIMER: The opinions expressed herein are those of the author and do not necessarily represent those of his employer, who could care less. While the situations depicted are factual, any resemblance to an actual message, living or dead, is entirely intended. This material is presented "as is" with no written or implied warranty. Have a good one. Richard A. Pence 1 April 1998 Richard A. Pence <richardpence@pipeline.com> Pence Family History <http://www.pipeline.com/~richardpence/index.htm
J. Sharp's message mentioned DORMAN. Seldom see it spelled that way. Wonder does she know of any Dormans that moved to KY and in 1796 could have been in the area that later became Gallatin Co. By 1843 STEVEN DORMAN was in Riipley Co., IN. Marna Stansberry
Marna My DORMAN line is from New Haven CT and NY. I don't know of any other spelling of Dorman. How do you spell yours? There was some Dormans in MA but I think they were German and mine were Eng. I wonder how it's spelled in England back then? Julie Sharp
Please unsubscribe me.
There seems to have been some problems on the Net Saturday night and Sunday. Several servers were bouncing all email and I have been deluged with "bounce" messages from RootsWeb. Many subscribers have been unsubscribed, especially those that use the WorldNet.ATT server. If you have had problems lately, this is probably the reason. If you were unsubscribed, you would have received a message from RootsWeb informing you, provided, of course, that your server was back online in time for you to receive the message from RootsWeb; otherwise, that notification would have bounced also. I know it's kind of stupid on my part, sending this out when the users who were unsubscribed won't see it. But, maybe if some of you have personal contact with users, you might inform them of the problem, and just tell them to re-subscribe. PLEASE DO NOT COMMENT ON THIS MESSAGE ON THE LISTS !!!!! If you wish to discuss it, send to my personal email address: mailto:sgtgeorg@concentric.net SgtGeorge Listowner
Looking for Edmund DORMAN b 1636 I believe he came from Derby-then to Connecticut 1657. I have all info from CT but need where and who parents or siblings are.
When a new user subscribes to a List at RootsWeb, he/she sends the subscription email to an address that contains "-request" in it. That new subscriber receives a Welcome Message that plainly states that email to the List goes to an address that does NOT contain the "-request". An address containing "-request" is ONLY for subscribing or unsubscribing. For some unfathomable reason, there are users who either don't read the Welcome Message, or who can't understand simple instructions. In the future (starting tomorrow, April 2), if a subscriber sends an email to the List address containing the "-request", I will immediately manually unsubscribe that user. If a user doesn't care enough to do things prop- erly, or to read the Welcome Message, then that user doesn't deserve to belong to the List. If you have argument with this stance and wish to discuss it, DO NOT send your reply back to the List !!!!! Send it to me personally at: sgtgeorg@concentric.net If you reply to this subject back to the List, I will unsubscribe you. I will not tolerate any off-topic arguments on the List. If you are confused as to what I am talking about, I will give you an example of the TWO address that are used with Lists. Where you see "LISTNAME", just substitute the name of the List to which you subscribe. To subscribe to, or unsubscribe from, a List at RootsWeb, you send your email to: LISTNAME-L-request@rootsweb.com or LISTNAME-D-request@rootsweb.com (Depending on whether you are subscribing to, or unsubscribing from, the Normal mode or the Digest mode.) To send email to the List, you send to: LISTNAME-L@rootsweb.com (You don't ever send email to "LISTNAME-D".) Some of you subscribe, using the address containing the"-request", then continue to forward email to that same address, even though the Welcome Message explicitly tells you not to. Sorry to be so cantankerous, but I've about had it with people who unpack their computers, plug them up and plug in a cord to the phone outlet, get "online", and then refuse to read anything they receive in the way of HELP files. You wanna participate, you gotta follow the rules. It's that simple. Regards, SgtGeorge List Administrator
If you are sending email that causes attachments to these Lists, please read the instructions below to find out how to re-configure your email browser to stop the attachments. PLEASE DO NOT ANSWER THIS EMAIL BACK TO THE LIST !!!!! If you feel you must make a comment to me, send it to my personal email address: sgtgeorg@concentric.net If you don't know whether or not you are sending attachments, follow the instructions below and make sure your configuration is in line with the requirements for sending email to mailing lists. If your browser is configured to send vCards, please turn them off. *************************************************************************** Reconfiguring Microsoft Internet Explorer Program: Open Microsoft Internet Browser; Click: "Mail" Icon; Select: "Read Mail"; Click: "Mail" along the top of the email screen; Click: "Options" Select the: "Send" tab; Go to: "Mail Sending Format"; Select: "Plain Text"; Click: "Settings" Select: "Uuencode"; Click: "OK"; Click: "Apply"; Click: "OK" ==================== Reconfiguring Microsoft Outlook Express Email Program: Open Microsoft Outlook Express; Click: "Tools" Click: "Options" Select the: "Send" tab; Go to: "Mail Sending Format"; Select: "Plain Text"; Click: "Settings" opposite "Plain Text" Select: "Uuencode"; Click: "OK"; Click: "Apply"; Click: "OK" ================ Reconfiguring Netscape Communicator Email Program: Using Netscape Communicator (Netscape 4.x), from the menu select "edit" then from that menu select "preferences." From that screen select "mail & groups" then "messages." Under '"messages properties" make sure the box "by default, send HTML message" is NOT selected. Thanks for your cooperation, SgtGeorge List Administrator NOTE: The above instructions were written by Lin Wright <ethelind@athens.net> and passed on to listowners.
Subscribers, please forgive me for sending this on to all of you, but I feel that you should know what is happening at RootsWeb and how it affects you. Many of you new subscribers may not know, but Brian and Karen at RootsWeb operate at a loss every year. We Listowners pay our fees for having these Lists (notice that we PAY for the privilege of being Listowners), and most of us pay much more than the minimum required contribution. You subscribers pay NOTHING for being able to use the Lists; there never is a fee for being a subscriber, and that will never change; however, RootsWeb DOES depend on generous subscribers sending in whatever they can to RootsWeb just to help out. If any of you feel generous and want to help, RootsWeb is always grateful for even small contributions. A dollar or two, $5, or whatever you can spare would go a long way to ensuring that this wonderful service continues to provide us with an almost unlimited opportunity to exchange ideas and data. Brian doesn't say so here, but last year RootsWeb spent $60,000+ more for necessary hardware and software than was received in the form of contributions, fees, etc. Fortunately Brian and Karen are able to do this without having to mortgage their home. (GRIN) But, you could all help out a little by some small contribution. PLEASE DO NOT CONSIDER THIS A COERCIVE PLOY TO GET YOU TO CONTRIBUTE. If you don't want to, you don't have to. You may go on receiving the many bene- fits of RootsWeb without ANY contribution. You can use "snail mail" and send contributions to: RootsWeb Genealogical Data Cooperative P.O. Box 6798 Frazier Park, CA 93222-6798 You may use RootsWeb Credit Card utility for contributing at this URL: http://www.rootsweb.com/rootsweb/how-to-subscribe.html In any case, do whatever your conscience allows. We will all be grateful. Below is Brian's latest update on the happenings at RootsWeb. (If you are not already a contributing member of the RootsWeb family, you might consider becoming one. There are many benefits of being a contributor, which you will find out if you go to the web site and read about subscribing, including hosting Lists, having Web Pages, etc. If you know of any genealogy researchers who might like to join us, let them know. After all, any server that handles close to 100 MILLION pieces of email a month has to be doing something right. SOMEONE must be gaining valuable information from the Lists!) ************************************************** This note is going to tell you that RootsWeb set a new record level of service to the genealogical community last month, but a more important message that I'd like to convey first is just how important your support has been. RootsWeb wouldn't be here without you. In February, without your support we couldn't have purchased a generator to keep the servers up during the El Nino storms, a new search engine server for the USGenWeb and mailing list archives, and a new server to host Cyndi Howells' Website and the USGenWeb query systems. Your continued support is essential to us: just to keep up with demand, in the next few weeks we're going to have to upgrade the main Web server, upgrade the mail hub server, and start preparing to add a third list server. All that costs money. And beyond those inescapable upgrades, we really want to be building a kitty for buying genealogical datasets and bringing more new services online for the whole community. If you can spread the word and help us find more Members, Sponsors, and Donors, you'll be helping us keep up with demand and bring new data and services online. *** AND NOW FOR THE REPORT *** February was an incredible month: El Nino storms repeatedly caused us to lose power, and I wound up having to 4-wheel- drive off the mountain in a snowstorm to find and buy a generator to keep RootsWeb online. Because of our batteries and our generator, we were down only minutes even though the power was off for days. Also, Cyndi Howells' Website moved to RootsWeb right in the middle of the storms and the USGenWeb query system needed more CPU cycles and bandwidth, so we added a server and load balanced our T1 connections to the Internet right in the midst of all the snowfalls and power outages. We had about 11% absolute growth during just the month of February, but that's deceptively low because February is a short month. Our actual *daily* load increased about 20%: o 29,372,613 Web files (27,751,946 in Jan) from 2,488 Websites (2,400 in Jan). - 8,602,112 were HTML pages (not images or cgi-bin) (8,308,561 in Jan). - 3,446,096 were cgi-bin database searches and such. (3,574,701 in Jan). - 17,248,967 were GIFs (15,850,655) or JPEGs (1,398,312) (15,784,790 in Jan were GIFs (14,529,204) or JPEGs (1,255,586). o 644,950 FTP file downloads from the USGenWeb Archives and the ROOTS-L Library (618,762 in Jan). o Thanks to a neat hack by Tim Pierce, we know we shipped about 82,150,000 pieces of mail (88,649,000 in Jan) pieces of mail to the 3,050+ (2,600 in Jan) mailing lists we host. (The 82 million is probably low; we had to archive a significant amount of mail before the count because of a disk space crunch on one of the mail servers ... ) o 60,000 alt.g and s.g.* Usenet News articles to hosts on three continents (same as Jan). o Approximately 505,361,000,000 bytes in total (451,786,000,000 in Jan). And that's what RootsWeb did in February. Let me thank you once again for supporting RootsWeb -- none of this would be available to the community without your help, and your continuing support can help us grow and provide even more service to the community. Thank you, B. -- Dr. Brian Leverich Co-moderator, soc.genealogy.methods/GENMTD-L RootsWeb Genealogical Data Cooperative http://www.rootsweb.com/ P.O. Box 6798, Frazier Park, CA 93222-6798 leverich@rootsweb.com
Subscribers, please be aware that I have contacted the ISP from whence this stupid, teenage SPAM originated. The site, for a beginning, shows much promise, but the owners have to realize they are antagonizing users of these Lists, and that they are severely hurting their potential by sending this SPAM. If you REALLY belive that SPAMMERS should be stopped and that they should be punished for their total disregard of Net protocol, DO NOT respond to their unsolicited ads and let them know at every opportunity that you are sick and tired of having to download their junk mail. SgtGeorge Listowner of all the Lists to which this is being sent, except for SURNAME-QUERY, which is managed by the fantastic Ron Lahti.
Having just received the article below from one of the services to which I subscribe, I thought I would share the knowledge with all you fellow subscribers. I apologize if it is off-topic, but I feel it is important enough to risk the wrath of some of you. I DO ask that if you wish to discuss this, that you send back to me via my private email address. DO NOT send your replies, comments, agree- ments, opposition, etc., back to the mailing lists. Sending something that is of value to users is one thing, making a thread of it is not. As both a Listowner and subscriber to many lists, I see this subject, COOKIES, show up from time to time and cringe at the uninformed opinions that I see on the subject. As you will see if you continue to read this post, COOKIES are absolutely nothing to fear. They can do you NO harm! In fact, they make your web browsing much easier. I don't know about you, but it pleases me that, when I log on to a URL that I have visited before, I don't have to retype UserName, ID, Password, etc., again and again. COOKIES are a wonderful invention and those software writers that keep producing programs/utilities to negate the COOKIES, are only preying on users gullibility and ignorance. Please read the article below to find out the truth. SgtGeorge ============================================================== - U.S. Government Advisory On Cookies The U.S. government is always warning its citizens about the dangers of tobacco, cholesterol, alcohol or sexually transmitted diseases. One branch of the Department of Energy also alerts all of us of the dangers of computer viruses and other computer security problems. But this week that same agency said that we should not worry about "cookies." Cookies are short pieces of data used by web servers to help identify web users. The "cookies" actually are stored in a text file on your own hard drive, but remote Web sites can write data to your cookies file and then retrieve that data on a later visit. Normally, cookies are used as "placeholders" so that you can return to the same page on a Web site. The cookies also could contain user IDs, passwords or personal information that you previously entered such as name, age, sex, mailing address or almost anything else that a Web site wishes to store on your hard drive for later use. Messages have floated around the online world for a couple of years now proclaiming the "dangers of cookies." Some of these messages were nearly panic-stricken texts describing all the "dangers." The online world seems to be a bit paranoid about cookies. In fact, you can even obtain programs that either disable cookies or hide them in such a manner that they are invisible to Web sites. Now the U.S. government says, "The popular concepts and rumors about what a cookie can do has reached almost mystical proportions, frightening users and worrying their managers." The highly-respected U.S. Department of Energy Computer Incident Advisory Capability office says that such concerns are hogwash. In a news alert quietly posted this week, the agency says: The vulnerability of systems to damage or snooping by using web browser cookies is essentially nonexistent. Cookies can only tell a web server if you have been there before and can pass short bits of information (such as a user number) from the web server back to itself the next time you visit. Most cookies last only until you quit your browser and then are destroyed. A second type of cookie known as a persistent cookie has an expiration date and is stored on your disk until that date. A persistent cookie can be used to track a user's browsing habits by identifying him whenever he returns to a site. Information about where you come from and what web pages you visit already exists in a web server's log files and could also be used to track users browsing habits, cookies just make it easier. The agency also says: The popular rumors about web cookies describe them as programs that can scan your hard drive and gather information about you including: passwords, credit card numbers, and a list of the software on your computer. None of this is close to the truth. My guess is that these wild rumors will continue to float around for a long time, regardless of what the U.S. Government or anyone else says. Human nature seems to force us to look for sinister motives in everything we do not understand. If you receive a message warning you about the "dangers" of cookies, ask yourself one question: "Really?" The full text of the government announcement is long and very detailed. It provides an in-depth explanation of the operation of cookies. To read the full story, look at: http://ciac.llnl.gov/ciac/bulletins/i-034.shtml ==============================================================
In reference to my previous post on the ProGentitor program, I feel I must forward this post from Florence Moore, concerning a program that will read the databases on the web and convert them to GEDCOM. If this program really works (I haven't logged on yet to try it), it is a fantastic program indeed. SgtGeorge At 08:17 AM 3/14/98 -0600, Florence Moore wrote: >Below is a Program I found on the net that is really great. Once you find one >of the sites with ancestors or descendants you save them to a file & have to >type them into your Genealogy program. THIS program takes that info & makes a >GEDCOM file. I don't get any kick back, so have nothing to do with the person >that wrote it. Doesn't cost to check it out. > >http://www.pratt.lib.md.us/~bharding/rippleeffect/index.html > >GenBrowser does the opposite of these two programs. Once you find a web page >with ancestry information, you can use the HTML2GED feature to trace the >ancestors or descendents of a specific person, and put the information in a >standard GEDCOM file > >George, you really did a nice job on your page!! >-- >Happy Hunting, Go dig up those Roots! >Florence Moore >URL: http://www.pcola.gulf.net/~rjmoore >
To start off, I must apologize for burdening some of you with what will be seen as superfluous trivia; however, in this day and age of posting genealogy data to web sites, I feel that it is important for you to know just what is available in the way of converting GEDCOM files to HTML and placing on Web Sites. I have just Registered, Downloaded, and Installed a program called "ProGenitor2". It takes GEDCOM files, converts them to HTML for uploading to a Web Site, and then makes those files available for users to view, search, copy, download, etc. I have been involved in doing this "genealogy thing" for over 12 years, starting back when the "Net" and "Web" weren't even figments of any- ones imagination. I've had my own web site for almost 2 years now. I have, over the past 2 years, used several programs to convert GEDCOM files to HTML, to upload to the site and allow users to easily find data on specific surnames/families. ProGenitor is absolutely the best one I have found. This email is not meant to be a "plug" for this program, it is meant to show you users what can be done with your own GEDCOM file, created from your computer genealogy program. On my web page, BROYLES/BRILES Family History, I already had several databases available, using a program called GED2HTML. It is a very nice program, but once you see what ProGenitor can do, I believe you will like it better. To test this new program, I chose a relatively small GEDCOM file that a correspondent had sent me. It contains only 945 names, and thus was one that would take up relatively little space on my ISP. The surname that is involved is FILLERS, and it is connected to the BROYLES surname. In Greene and Washington Counties in Tennessee, the name FILLERS/ FELLERS/G'FELLERS is one that is interwoven throughout Tennessee's history with the BROYLES/BRILES and WILHOIT/WILHITE families. Thus, I thought it a good one to experiment with. (I must warn you that there is one problem with this particular GEDCOM -- the BROYLES ancestors are not linked back to the immigrant Johannes BREYHEL (John BROYLES). It is a FILLERS history and the researcher didn't follow through with the BROYLES history.) I would like for any of you to visit this site: http://www.concentric.net/~sgtgeorg/fillers1/index.html Please navigate around and see how you like this format for putting databases on the web. When the home page pops up, I would sug- gest that you click on "Help" to see what you can do. Once you have read the help file, go back and click on "Search". You will get a page where every Surname in the database is listed. You can either scroll down the list until you find a Surname that you would like to investigate, or simply type in the surname in the avail- able search box and click "Search". Let's say you want to look for the BROYLES surname. Scroll down the page to BROYLES, click on the BROYLES name, go to the button bar at the top, Click on "Views", then "Display Records". This will give you a list of EVERY BROYLES name in the database. To give you a demonstration, after the "Display Records" screen has loaded, under "BROYLES, Addie", you will see "BROYLES, Lewis Melvin". Click on his name and you will get a complete family history for him and his wife. If you want ancestral charts or descendant charts, instead of clicking on "Display Records", click on "Ancestor" or "Descendants". To print out an ancestral chart or descendant chart, click on "Print" and FOLLOW THE INSTRUCTIONS !!!!! It may seem complicated at first, but I assure you that you will be surprised and delighted at the results. Now that I have led you through this morass, let me get to the REAL intent of this email. "IF" you have a database of a "Germanna" family, and IF you would like to have your database on the "Web", you can send me a GEDCOM of your database and I will use ProGenitor to convert it to HTML and post it to my web site. There is no charge and I'm making this offer in order to get as much data as possible of the Germanna families on the Web. Just remember, for every 200 names in your database, it costs me about 500 Kb (.5 Mb) of server space. So, if your database contains 2000 names, it will take 5 Mb of space. I would appreciate it if you would use the capabilities of your genealogy database program and make a GEDCOM of ONLY those names, trees, branches, lines, etc., that pertain to actual Germanna descendants. That is, don't include ances- tors of spouses if they are not Germanna descendants. When you send the GEDCOM, give me your name, email address, and (if you have one) the URL for your Web Site. I will not disseminate the data in the GEDCOM files to anyone else. They will reside on my server, only for the use of Germanna researchers, and may not be copied, compiled, nor re-trans- mitted for use by profit-making enterprises. I will copywrite the pages so that anyone wishing to use the data is warned "upfront" that it is not "public domain" material. Sorry for this overly-long email, but I just couldn't make it any smaller. For those of you who have sent me GEDCOM files in the past, I am now ready to convert them into HTML and post to the web site. Sorry it has taken so long. (Some GEDCOM files that I have received were not exported in the proper format and I can't use them. Also, some files were included as text in the body of the emails you used to send them -- these files will have to be re-submitted if I am going to be able to convert them and upload to the server.) Just remember, if you send me a GEDCOM file, DO NOT send it as part of the text body of an email. You MUST send it as a separate attachment!!!!! And, it must be exported from your genealogy program as a GEDCOM file, not as some other aberration of a file such as FTM produces. Oh, one thing I forgot to say was that one of the reasons I am so excited over this program is that I produces files that take up much, much less space on the server that do the other programs I have used. SgtGeorge Stretching the Boundaries of Genealogy Research
We have seen an increasing number of "junk" messages lately, dealing with "Return Receipts" for email posted to the mailing lists. Having written to several of the servers sending back these "Return Receipts", it has been brought to our attention that the servers are set to do this ONLY if there was such a request in an original email from a subscriber. What this means is, PLEASE do NOT set your email browser to ask for a "Return Receipt"!!!!! Unbeknownst to any of us, this not only gets the sender a receipt for his individual message, but, when that message's target is a mailing list, then gets sent out to several subscribers, the servers of some of those subscribers will automatically send a "Return Receipt" back to the MAILING LIST, not back to the ORIGINAL SENDER. It seems that anytime a subscriber is using server at a college or university, they are ALWAYS set to send a "Return Receipt", and of course it shows up either on the List itself or in the List- owners mailbox. In either case, they are nuisances and serve no useful purpose. I use Eudora and it has a button to click, "RR", at the top in the button bar. If this is checked, you are asking for a "Return Receipt" and will cause unnecessary email traffic to the Lists. I don't know the procedures for checking this in other email browsers, but PLEASE turn it off. Some of you DO have it turned on, because we are getting many replies. Thanks, SgtGeorge
This month's Newsletter, by Jeannette Holland Austin, covers Slave Census information. Jeannette also lists several dozen books on Census, giving info on the books, cost, etc. You can read the Newsletter at: http://www.genealogy-books.com/ SgtGeorge
>Thanks for the message. I am collecting data on Robert Dorman who married in >1666, Somerset Co., MD, "Elyzabeth" Knight. I have not connected him to >Matthew Dorman of the same county. I believe that Robert and Elizabeth's >daughter, Elizabeth, m. (1) Abraham Enloes and (2) John Ensor, both of >Baltimore Co. John died by c. Oct. 1720, and I wonder whether she m. for a >third time and/or migrated to the Carolinas with some of her sons. > >Ron Cofiell >cofiellra@aol.com > > > Dear Ron, Could your Elizabeth have had some brothers that may have migrated to the Carolinas with her? I have an Elizabeth Dorman who married Elisha Kirk in 1802 in Orange County, NC and am trying to research her family farther back with little or no success. Would appreciate any lead you may be able to give me, or if anyone else out there in the Dorman line might be able to help me a little. Susan
Thanks for the message. I am collecting data on Robert Dorman who married in 1666, Somerset Co., MD, "Elyzabeth" Knight. I have not connected him to Matthew Dorman of the same county. I believe that Robert and Elizabeth's daughter, Elizabeth, m. (1) Abraham Enloes and (2) John Ensor, both of Baltimore Co. John died by c. Oct. 1720, and I wonder whether she m. for a third time and/or migrated to the Carolinas with some of her sons. Ron Cofiell cofiellra@aol.com
---------------------------------------------- And now for today's tip... AVOID ATTACHING Avoid sending attachments to mailing lists. If you send an attachment as small as 20K to a mailing list that has 100 members, you generate over 2MB of increased Internet traffic. When you consider that most attachments are considerably larger than 20K and most mailing lists have many more members, you're looking at serious Internet slowdown. If you want to let mailing list members know about, say, a great article you just found online, include Mailing Lists Deliver Tech Info For the complete story, visit http://www.pcworld.com/tipnews ----------------------------------------------
Need ancestry info. for STEVEN DORMAN, b June 10, 1796, md CLARISSA (last name unknown) b April 12, 1795, d July 23, 1840. Gallatin Co., KY census of 1830 shows them with 2 (male) children. I have record of ELIZABETH MARY DORMAN, b Sept. 22, 1827 and SARAH E. DORMAN b June 22, 1839. They moved to Ripley Co., IN where STEVEN DORMAN md SARAH BRUNER on Jan 14, 1843. I have more info. on Elizabeth Mary and later generations but haven't located earlier family. Thank you. Marna Stansberry