) ( ( ) Good Morning Family! ( \ .-.,--^--. ( Come on in. . . \* ) \\|`----'| - The coffee pot's on. . . .=|=. \| |// ...and we even have decaf, |~'~| | |/ tea, and hot chocolate! | | \ / _|___|_ ------ (_______) Today's topics include: 1. Welcome to new cousins 2. Holiday CHAT: forum is open 3. The Antebellum Christmas *** REMINDER: GIFTS FOR OUR FAMILY CHRISTMAS ARE DUE TO ME BY SATURDAY, DECEMBER 8th *** If you're new or have lost your original message regarding this family event, let me know <ladyaudris@earthlink.net> and I'll send you a copy. TO OUR NEWEST COUSINS ~~ On behalf of the entire family, I'd like to extend a most hearty welcome to those cousins who came into the family fold this past week. We are very glad to have you with us and hope you'll stay and remain a part of our online family. As soon as you're comfortable with us and the list, please send in your Bower[s]/Bauer, Baur or Bowra lines so we can all see how we're related to you. We do not have a fancy format for sending in records or queries to the list. Post as many as you wish! If the data has anything to do with Bower[s]/Bauer, Baur or Bowra ancestors or any of the 81+ variant spellings we research that might help someone, please feel free to post it. Every scrap of information is appreciated. If you haven't visited the homesite of this list yet, you are encouraged to do so. Our home is Bower Community, located at <http://bowercommunity.com>. There, we currently have two sites: The Bower Family Homestead [a.k.a., the Homestead] is our primary homesite and the gathering place for much of our information. It waits to join us all in welcoming you into the family at <http://bowercommunity.com/homestead>. Smaller is our sister site, the Bower Cottage, which houses most of our projects including an online GEDCOM fed by cousins from our research groups. Find the Cottage is at <http://bowercommunity.com/cottage>. HOLIDAY CHAT: FORUM IS OPEN The holiday season is what most people call the "family time" of year. Just as we do every year, I'm opening the list up for any family discussion outside of our normal genealogy. Every year, between Thanksgiving and New Year's, the CHAT: forum opens for everyone to discuss holiday traditions and memories, pass greetings and recipes along, etc. The CHAT: forum is the safe harbor for off-topic discussion. Does anyone have any holiday family traditions or memories they'd like to share? As long as CHAT: starts out your subject line, you are in CHAT: forum and you can safely discuss non-genealogy subjects. HOWEVER, so everyone understands how this works, there are a few guidelines for the CHAT: forum: 1. You MUST start your subject line with CHAT: 2. Absolutely NO genealogy is to be put in CHAT: forum messages because not everyone in the family wants to read CHAT: messages. Those people know to simply delete messages with CHAT: in the subject line knowing they won't miss any genealogical data. CHAT: format messages are not an everyday occurrence. They normally happen here and there. The only, and longest, time the CHAT: forum is actively open is the holiday season ... now. After January 2nd, the CHAT: forum closes and resumes its normal inactivity with occasional messages only. Please remember everyone, to use the CHAT: forum for all your holiday greetings and traditions messages. And for your own protection, step into the CHAT: forum and start your subject line with CHAT: THE ANTEBELLUM CHRISTMAS Antebellum, Latin for 'before the war,' is a word that came into use about 1847. It specifically means 'existing before the Civil War.' When I hear this word I picture white plantation mansions with weeping willow trees. I picture the ladies' long, flowing gowns ... Let's back up in time a little more ... The early 17th century saw a wave of religious reform changing the way Europe celebrated Christmas. Oliver Cromwell and his Puritan forces took over England in 1645 and they had vowed to rid England of decadence. As part of their effort, they cancelled Christmas. However, Charles II was restored to the throne and with him, came the return of the now popular holiday. The Pilgrims were English separatists who came to America in 1620 possessing Puritan beliefs more orthodox than Cromwell. These beliefs resulted in Christmas not being celebrated in early America. From 1659 to 1681, the celebration of Christmas was outlawed in Boston. Anyone exhibiting the Christmas spirit was fined five shillings. By contrast, in the Jamestown settlement, Captain John Smith reported that Christmas was enjoyed by all and passed without incident. As years passed, attitudes relaxed and Christmas began to see a beginning in America. However, following the American Revolution, English customs fell out of favor, including Christmas. In fact, Congress was in session on December 25, 1789, the first Christmas under America's new constitution. Thank goodness for the American South and her people! It was the South that put both the holy day and the holiday of Christmas on the map in America. The first Christmas worship services took place in St. Augustine, Florida, and in the colony of Jamestown, Virginia. The first Christmas tree in America was decorated in the home of a judge in colonial Williamsburg, again in Virginia. Later, in 1831, Louisiana and Arkansas became the first states to recognize Christmas as a legal holiday at a time when celebrating it in Puritan New England could get one fined or thrown into the stockade. Alabama follwed in 1836 and, as fifteen more states (including Illinois, Ohio, Wisconsin and Minnesota) quickly joined after 1850 to make it a legal holiday, the date of December 25th became standardized. Previously, celebrations took place on December 6th (St. Nicholas's day), or on January 6th (Epiphany). Christmas wasn't declared a federal holiday until June 26, 1870. Provisions for the closing of schools, banks, and government offices generally did not appear until then. Even before Christmas trees became popular in the South in the 1850s, it was customary for families to "add color" to their homes at Christmas by hanging holly wreaths on doors and walls and trimming everything from columns and staircases to chandeliers and punch bowls with garlands of ivy or cedar. Old South favorites still widely used today include orange pyracantha berries, red and white camellias, the South's naturally decorated Christmas trees ~ yellow jasmine, pinecones, pine branches, magnolia leaves and, of course, the poinsettia, first used as a holiday adornment in Charleston, South Carolina. Just as now, mistletoe also figured prominently in Southern Christmas celebrations. References to "kissing balls" of mistletoe can be found in the diaries of Southern belles and antebellum hostesses alike. In advance of a Christmas gathering where the loveliest belles and the dandiest beaus in the county might be expected, a party of hunters would venture into the woods, to "shoot down the mistletoe." As you might guess, the lucky marksman who succeeded was rewarded with the first Christmas kiss. By some accounts, Southern Christmases of old could be noisy, raucous affairs filled with fiddle music, dancing, pistol reports and fireworks at midnight. To be sure, they usually began with a solemn, early-morning ride in a wagon to a nearby church for a service. No self-respecting Southern host or hostess would allow Christmas to pass without offering guests a toast and a cup of eggnog. Creating this holiday beverage involved the mixing of at least three different spirits with egg whites, cream and spices. Significantly, the task of making this "virile" drink fell to the master of the house and was never given over to the hostess or to a servant. Still today, eggnog and syllabub reflect our English heritage. Originally fueled by a strong dark ale or beer, Southerners adapted them, adding our indigenous alcoholic beverage, bourbon. Food also sets the Southern Christmas tradition apart. From Maryland to Mississippi, the scent of oranges, a rare commodity in those times, was a giveaway that Christmas had arrived. Given their wide range of enjoyment, not even the old Southern black-eyed peas and hog jowls on New Year's Day can accomplish this today. As well, most Georgia natives expect cornbread stuffing gracing his or her plate at Christmas dinner. The Southern Christmas tradition reflects the wide ethnic and cultural differences of all the original Southern settlers. In Maryland, turkey with sauerkraut, not stuffing, is still served on on Christmas Day. In Georgia, old-timers continue their ancestor's traditional "Open House" on New Year's Day. When the holidays approach in Natchez, Mississippi, little girls make "tussie mussies," antebellum Christmas ornaments used to decorate the tree, just as their counterparts did more than a century ago. Today as then, when "the animals speak with the gift of tongues," you know that Christmas has arrived in Dixie. It was during the Antebellum period that Dickens' "A Christmas Carol" and its "carol" philosophy added another element with its assertion that brotherhood, kindness, and charity should be a part of life ~ especially at Christmas ~ was quickly accepted and added to American tradition. And, it was within such an atmosphere that Christmas as we know it began to manifest itself. Christmas trees had become relatively established in the United States by 1860. Trees of the period were decorated with various edibles and home-crafted ornaments ~ fruits, strands, and candles. By 1860 glass trinkets made in Germany were becoming available to adorn the branches. Music exclusively associated with Christmas was added to songbooks during this period. Caroling became increasingly practiced. Most of it was of a sacred nature and alluded to Christ's birth. "It Came Upon a Midnight Clear" 1851), "See Amid the Winter's Snow" (also 1851), "There Came A Little Child to Earth" (1856), and "We Three Kings of Orient Are" (1859) all were composed before the Civil War. Christmas cards were relatively well-known in England by 1860, but the custom of sending holiday greetings was unknown in America during this period. As early as the 1830s newspapers were filled with enticements to lure "Christmas shoppers." Raisins for baked goods to pianofortes for the parlor to uplifting books for the mind and soul were pushed via the papers. Merchants were quick to realize the potential of the gift-giving season and capitalize on the growing importance of Christmas. Santa Clauses had begun to appear on street corners and in stores by 1850. Santa Claus was evolving during this period. Although it would be several years before our modern Santa would be given his enduring jolly, round form, "Santa Claus" of 1860 would still be recognizable to today's child. The revival of holiday traditions provides continuity with our past while enriching our present. And in America, we have our ancestral South to thank. Family ... it's what we're all about. To you December babies - the cousins and I wish you a very happy and exciting year ahead. Happy Birthday! You are loved! Thank you for allowing me to spend this time with you today. I wish each of you a week filled with health, productivity, fun, and above all, filled with love and inner peace. ) ( ) _.-~~-. (@\'--'/. Colleen ('``.__.'`) `..____.'

Thought I would pass this along as a reminder -- The National Archives will be releasing the 1930 census April 1, 2002. Late next year, if you are not in D.C. or near a National Archives branch and are near or will be visiting in Houston, you might check to see if the Clayton Genealogy Library has the reel you need. Clayton is a public library and the 'Friends' have already raised $17,200 towards the 1930 census which the library will acquire in full as fast as possible. Clayton is a fantastic library and presently has all the census records from 1790 through 1920 among many other genealogical resources. Don't forget, you can always use the LDS FHC.

Hi cousins, My computer crashed yesterday (last nite, actually) my harddrive decided to "give it up" and go to harddrive heaven, taking with it all my messages from the past year. Virus recovery instructions were on that harddrive, so were the Chrismas pages and all the presents. I've spent most of today trying to recover any of the gifts with no luck. So, following this message I'll begin rebuilding the recovery instructions, then tomorrow start rebuilding our Christmas pages. Hopefully, I can have them ready to put online by this coming weekend. I'll start rewrapping gifts after that. Sometimes computering isn't fun; this is one of those times. :-| At this point the deadline is still December 8th, but if you've already sent your present in and still have it in your machine, please resend it right away. I'm afraid I'm going to be very backed up here, but I promise not to lose them again. :( I wish you all a wonderful rest of the Wednesday evening. :) Colleen

My apologies to all of you -- this was meant to be a private message to Colleen, not to the entire list! Jean At 09:24 PM 11/27/01 -0600, you wrote: >Colleen --------- > >I was the recipient of Badtrans this morning BUT it didn't come via an >attachment. There was no attachment to be found. In reading your lengthy >:-) post this morning and everything else I've read concerning viruses, >they come in attachments. So how did I get this "guest" this morning? >Please explain it to my non-techie brain!! > >Thanks, Colleen! I really appreciate how you look out for all us Bowers >"cousins"! > >Jean R. Legried, CGRS >Norwegian-American research specialty ><jrl@smig.net> > >Freeborn Co. MNGenWeb Coordinator: http://www.rootsweb.com/~mnfreebo >Beginning Genealogy lessons: http://www.rootsweb.com/~newbie >Co-editor, VESTLANDET > > >==== BOWER Mailing List ==== >Please avoid flaming (attacking) any single person or the group. This >infraction will earn you immediate removal from the list. >

Hi - I have a little more information on the Bower(s) line I'm researching and thought MAYBE it would be the piece that connects my line to someone else's out there..... I began researching Laura Bower(s) my g-g-grandmother with only the record from her 1892 Muncie, IN wedding which sadly did not list her parents names. Then with the great help of a connection in Muncie who obtained some legal documents for me, I was able to find out her parents names - Thomas who was born about 1846 in VA and Anne E (or Mary E...still some confusion about the exact name....) who was born about 1847 in VA. On the 1880 census they are found in Salem Twp of Delaware Co, IN with 5 daughters (Mary, Annalaura (my g-g-grandmother), Alminna "Mintie", Alta P "Pearl", and Mattie. The girls were all born in IN between 1869 and 1880. Thomas also had a brother, William living with them. William was born about 1849 in VA. The girls all married men from Delaware Co between 1892 and 1908. Mary (the mother died in Delaware Co, IN on 5/30/1913 but was buried in adjoining Henry Co, IN). Thomas must have preceded her in death because he is not listed as a survivor. Does this click with anyone out there researching the VA to IN Bowers? I'd sure love to hear from you if you see a connection!! Marilyn Shields

Colleen --------- I was the recipient of Badtrans this morning BUT it didn't come via an attachment. There was no attachment to be found. In reading your lengthy :-) post this morning and everything else I've read concerning viruses, they come in attachments. So how did I get this "guest" this morning? Please explain it to my non-techie brain!! Thanks, Colleen! I really appreciate how you look out for all us Bowers "cousins"! Jean R. Legried, CGRS Norwegian-American research specialty <jrl@smig.net> Freeborn Co. MNGenWeb Coordinator: http://www.rootsweb.com/~mnfreebo Beginning Genealogy lessons: http://www.rootsweb.com/~newbie Co-editor, VESTLANDET

Hi Again Colleen, I made it to the end this time and see that apparently you CAN get infected by opening a blank e-mail -- even though I was told repeatedly that you cannot. I do have Windows ME, though, and as a precaution I wold like the information on how to remove any infected backup files. Thanks Lynne Colleen Pustola wrote: > Hi everyone, > > You know the saying, "Forewarned is forearmed?" Well, here's your > opportunity to "get smart" with regard to this insidious and dangerous > virus that's going through all of us right now. I've been doing some > heavy research for the past two days in addition to communicating with a > lot of you. Hopefully, this message will clear up a lot of the > confusion that's been going around. It's also probably going to be a > "longie," so you might want to grab your coffee cups, tea glasses, or > soda cans and sit back to have a rather extensive read. I won't do > another update unless this virus mutates again and does something > drastically weird. > > I'm sure everyone knows by know that the current virus we're all dealing > with is a SECOND strain to the original Bad Trans worm we had to weather > through. If you'll remember, the first Bad Trans warned us by way of > double extensions on an attachment plus the giveaway instruction, "Take > a look to the attachment." Not completely so with this second strain! > > This insidious little mutant has so many people confused that they're > unwittingly opening messages and getting infected. Rather than go into > it all again, please read my warning message of the night before. From > there I'll update here... > > This section is a composite of information found at > <http://www.symantec.com>, <http://www.mcafee.com>, and > <http://www.viruslist.com>. After this section I'll pass along some > comments from the field (us)... > > The W32.BadTrans.B@MM is a worm that spreads under Win32 systems. The > virus sends email messages with infected files attached, as well as > installs a spying Trojan component to steal information from infected > systems. The worm itself is a Win32 executable file (PE EXE file). > Unopened, it's about 29-30Kb in size, but decompressed the worm file > length becomes about 60Kb in size. > > The worm consists of two main components, the Worm itself and a Trojan. > The "Worm" component sends infected messages, and the "Trojan" component > sends out information (user's info, remote access service data, cached > passwords, keyboard log) from infected computers to a specified e-mail > address. It also keeps a keystroke-log program body in its code, and > installs it into the system while infecting a new machine. > > INFECTING THE SYSTEM > > When a user clicks on an attached file and activates the code, the worm > gains access to the computer. First of all, it installs its components > to the system and registers in the system registry. > > Once running, the Trojan attempts to mail the victim's IP address to the > author. Once this information is obtained, the author can connect to the > infected system via the Internet and steal personal information such as > user names, and passwords. In addition, the Trojan also contains a > keystroke-log program which is capable of capturing other vital > information such as credit card and bank account numbers and passwords. > > The worm also drops an additional keyboard hooker (Win32 DLL file) to > the system, and then uses this to spy on text entered by a keyboard. > > If programmed by the hacker to do so, the worm may delete the original, > infected file once installation is complete. > > SPREADING > > McAfee reports, "If the attachment is opened, the worm displays a > message box entitled, "Install error" which reads, "File data corrupt: > probably due to a bad data transmission or bad disk access." But this > isn't happening to me, or a lot of other people (at least not that I've > seen, anyway). What IS happening follows: > > When a user becomes infected, the next time s/he reboots the computer, > the virus goes through the user's email program and looks for unread > messages in all the mailboxes. To send infected messages, the worm uses > a direct connection to an SMTP server. A victim's email address is > obtained in two different ways: > > 1. through your address book > 2. by the worm reading all your e-mail in your inbox, and obtains > e-mail addresses from here. > > Next, the worm generates replies and sends infected messages. The > message body contains HTML format, and uses a system breach to spawn an > infected attachment on vulnerable machines. > > The worm uses the infected computer owner's email address as the sender, > BUT it adds "_" (underscore) before the real address. The subject line > may OR MAY NOT have a subject line of nothing but "RE:" (nothing else). > For most of us, the body of the email is completely blank. There are no > attachments, so there is nothing to click. That's because the virus is > embedded in the body, with code that hides it. The recipient receives > what appears to be a totally blank message. It's actually 29-30K long. > > Are you a list manager who's receiving reports that > <_aperson@thisisp.com> has been sending out infected messages to your > membership? Let's see if I can explain this one for you ... > > A SCENARIO TO EXPLAIN MOST OF IT > > You're a listowner of the ABC-l list. In your membership is Ima Doe. > She uses Microsoft Outlook and has a HUGE address book filled with peers > doing genealogy from all the lists she belongs to. In real life, Ima > has a daughter, Sheeza. :) Sheeza isn't part of any list, nor does she > do genealogy. However, Sheeza's computer is infected. Her infected > machine emails Mom (Ima), and Mom seeing a message from her beloved > daughter Sheeza, immediately opens the message! That's all she wrote! > Ima's computer is now infected. You, the listowner of the abc-l list, > and anyone else in Ima's address book, is now vulnerable to receiving > the infection. List members start reporting that Sheeza Doe > <_sheeza@isp.com> is sending out virus messages! Being a terrific list > manager (and you are, aren't you?) you head for your utilities page to > unsub this poor woman till she gets her machine cleaned up, but alas!... > there is NO sheeza in the membership, nor is there anyone from isp! The > message everyone received said it's from Sheeza Doe <_sheeza@isp.com> > simply because Sheeza was in Ima's computer! Get that??? <g> (I've > been working at this for a while folks, and am feeling a little uhm... > "creative" here! If the Ima's and Sheeza's get you all fouled up, > change the Ima to Jane and the Sheeza to son, John.) > > Symantec reports: If SMTP (user) information can be found on the current > computer, then it will be used for the From: field. Otherwise, the From: > field will be one of: > > "Mary L. Adams" <mary@c-com.net> > "Monika Prado" <monika@telia.com> <--- I've had this one several times > "Support" <support@cyberramp.net> > "Admin" <admin@gte.net> > "Administrator" <administrator@border.net> > "JESSICA BENAVIDES" <jessica@aol.com> > "Joanna" <joanna@mail.utexas.edu> > "Mon S" <spiderroll@hotmail.com> > "Linda" <lgonzal@hotmail.com> > "Andy" <andy@hweb-media.com> > "Kelly Andersen" <Gravity49@aol.com> > "Tina" <tina0828@yahoo.com> > "Rita Tulliani" <powerpuff@videotron.ca> > "JUDY" <JUJUB271@AOL.COM> > "Anna" <aizzo@home.com> > > However, we're all receiving messages from a host of other names, > including those we don't know (like <_sheeza@isp.com>?). > > >From a message in the field: "I just discovered a problem when searching > for FROM: addresses that start with <"_">. There is a problem with > people who have their email program set to show both their name and > email address in the FROM: header. If such a person is infected, mail > from him/her will show, in the header, something like the following: > > "John Doe" <_johndoe@wherever.com> > > "The FROM: element in the header you see before you open the email will > show only "John Doe". That's a problem. Either set up a filter to > divert infected emails to a separate mailbox, or make sure your system > is COMPLETELY protected before you open or preview any more emails.)" > To notify the person who has the infected machine, simply remove the > leading '_' from their email address. > > WHAT CAN YOU DO? > > 1.) Insure that your antivirus software has been updated since November > 25, 2001. Anything before that will not give you the protection you > need from this strain of BadTrans. Because of the mutations this strain > appears to be doing, most people are updating DAILY now. > > 2.) Keep your antivirus program running at all times. You just never > know when you'll be the next "recipient." > > 3.) Stay calm. Realize and remember that N0 virus is currently capable > of passing through a RootsWeb list. Rootsweb's filters are set to very > high. However, BadTrans.B makes it *APPEAR* that this is happening, and > uses list messages as a source for new targets. Unsubscribing from the > list will do you no good if your email address is already in someone > else's computer and that machine becomes infected. > > MICROSOFT OUTLOOK USERS BE SURE TO READ THIS! > > Particularly vulnerable to the BadTrans.B virus are those users of > Outlook (not Outlook Express). It's imperative that Outlook users NOT > open suspicious emails, or even preview them. Outlook users will infect > their computers simply by opening or previewing infected email. Since > these infected messages have no attachments to click on in order to > activate the virus, just opening the message activates the virus through > HTML coding embedded in the post. Again, the message size is 29-30K, > but what you see is a blank message. At the point of seeing the blank > message, the computer has been infected. > > Outlook users are advised to view the headers. If a header reports a > sender's address as similar to <_somebody@someisp.com>, DO NOT OPEN IT! > As stated above, opening or even previewing an infected message through > Outlook will activate the virus and cause your system to become > infected. > > Available since May 16, 2001 is a patch for Outlook versions 5.01 and > 5.5 that should be downloaded and installed immediately. MSIE 6.0 > appears not to be affected because the patches for previous versions > have been incorporated into it. You can check to see which patches your > system needs by going to > <http://windowsupdate.microsoft.com/>. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > WINDOWS ME USERS READ THIS! > > Windows ME utilizes a backup utility that backs up selected files > automatically to the C:\_Restore folder. This means that an infected > file could be stored there as a backup file, and VirusScan will be > unable to > delete these files. I have the instructions on how to remove the > infected files from the C:\_Restore folder if you need/want them. > > IDEAS AND COMMENTS FROM THE FIELD (US): > > 1. Are you concerned about even receiving infected messages? Here's an > idea that _might_ work: > Set up a special folder specifically for "Infected Mail." > Then, use your email program's filter to watch and transfer all messages > with the "_" in the header to that "Infected Mail" folder. Make sure > this is the first of your filters. > > 2. Are you emailing people telling them their computer is infected and > that person writes back that it's not? > This is because of the virus sending out the infected messages > without the PC owner's knowledge. The person's machine is "definitely > infected, whatever they may say to the contrary. Keep in mind that the > virus is only contained in the messages that their computer is sending > without their knowledge - not the ones they are sending you > legitimately. That is why you are receiving some virus infected > messages and some virus free. Unless their virus definitions are > up-to-date they could run a virus scan & find nothing. Norton only > updated their definitions to include the latest Badtrans virus this > weekend." It's important that you impress on these owners that their > computer IS indeed, infected and they need to take care of it. > > 3. "In your address book ADD NEW Contact..... !0000 exactly like this. > It puts this address first in your book and STOPS the virus from sending > to your list..." > This is a hoax, I'm afraid. It doesn't work. You'll find > information about the "!0000" hoax at > <http://antivirus.about.com/library/weekly/aa082801b.htm>. > > 4. Have you heard of MailWasher <http://www.mailwasher.net>? Though I > haven't tried it, here's a user's comment regarding that FREE program: > "I can view, identify and delete the viruses while they are > still on the ISP server. They never get to my computer." > Hmmm... perhaps it's worth checking out? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > You've done it! You've made it to the end! > > Once again let's keep this off the list. If you have any questions > you're welcome to email me <ladyaudris@earthlink.net>. > > I wish you a TERRIFIC Tuesday! :) Stay vigilant; stay alert ... keep > your computer safe! > > Colleen > > ==== BOWER Mailing List ==== > Please do not send messages with attachments, HTML, MIME, or any other > enhanced text to the list. RootsWeb does not allow messages with those > settings through their servers and will only return them to you.

Hi everyone, You know the saying, "Forewarned is forearmed?" Well, here's your opportunity to "get smart" with regard to this insidious and dangerous virus that's going through all of us right now. I've been doing some heavy research for the past two days in addition to communicating with a lot of you. Hopefully, this message will clear up a lot of the confusion that's been going around. It's also probably going to be a "longie," so you might want to grab your coffee cups, tea glasses, or soda cans and sit back to have a rather extensive read. I won't do another update unless this virus mutates again and does something drastically weird. I'm sure everyone knows by know that the current virus we're all dealing with is a SECOND strain to the original Bad Trans worm we had to weather through. If you'll remember, the first Bad Trans warned us by way of double extensions on an attachment plus the giveaway instruction, "Take a look to the attachment." Not completely so with this second strain! This insidious little mutant has so many people confused that they're unwittingly opening messages and getting infected. Rather than go into it all again, please read my warning message of the night before. From there I'll update here... This section is a composite of information found at <http://www.symantec.com>, <http://www.mcafee.com>, and <http://www.viruslist.com>. After this section I'll pass along some comments from the field (us)... The W32.BadTrans.B@MM is a worm that spreads under Win32 systems. The virus sends email messages with infected files attached, as well as installs a spying Trojan component to steal information from infected systems. The worm itself is a Win32 executable file (PE EXE file). Unopened, it's about 29-30Kb in size, but decompressed the worm file length becomes about 60Kb in size. The worm consists of two main components, the Worm itself and a Trojan. The "Worm" component sends infected messages, and the "Trojan" component sends out information (user's info, remote access service data, cached passwords, keyboard log) from infected computers to a specified e-mail address. It also keeps a keystroke-log program body in its code, and installs it into the system while infecting a new machine. INFECTING THE SYSTEM When a user clicks on an attached file and activates the code, the worm gains access to the computer. First of all, it installs its components to the system and registers in the system registry. Once running, the Trojan attempts to mail the victim's IP address to the author. Once this information is obtained, the author can connect to the infected system via the Internet and steal personal information such as user names, and passwords. In addition, the Trojan also contains a keystroke-log program which is capable of capturing other vital information such as credit card and bank account numbers and passwords. The worm also drops an additional keyboard hooker (Win32 DLL file) to the system, and then uses this to spy on text entered by a keyboard. If programmed by the hacker to do so, the worm may delete the original, infected file once installation is complete. SPREADING McAfee reports, "If the attachment is opened, the worm displays a message box entitled, "Install error" which reads, "File data corrupt: probably due to a bad data transmission or bad disk access." But this isn't happening to me, or a lot of other people (at least not that I've seen, anyway). What IS happening follows: When a user becomes infected, the next time s/he reboots the computer, the virus goes through the user's email program and looks for unread messages in all the mailboxes. To send infected messages, the worm uses a direct connection to an SMTP server. A victim's email address is obtained in two different ways: 1. through your address book 2. by the worm reading all your e-mail in your inbox, and obtains e-mail addresses from here. Next, the worm generates replies and sends infected messages. The message body contains HTML format, and uses a system breach to spawn an infected attachment on vulnerable machines. The worm uses the infected computer owner's email address as the sender, BUT it adds "_" (underscore) before the real address. The subject line may OR MAY NOT have a subject line of nothing but "RE:" (nothing else). For most of us, the body of the email is completely blank. There are no attachments, so there is nothing to click. That's because the virus is embedded in the body, with code that hides it. The recipient receives what appears to be a totally blank message. It's actually 29-30K long. Are you a list manager who's receiving reports that <_aperson@thisisp.com> has been sending out infected messages to your membership? Let's see if I can explain this one for you ... A SCENARIO TO EXPLAIN MOST OF IT You're a listowner of the ABC-l list. In your membership is Ima Doe. She uses Microsoft Outlook and has a HUGE address book filled with peers doing genealogy from all the lists she belongs to. In real life, Ima has a daughter, Sheeza. :) Sheeza isn't part of any list, nor does she do genealogy. However, Sheeza's computer is infected. Her infected machine emails Mom (Ima), and Mom seeing a message from her beloved daughter Sheeza, immediately opens the message! That's all she wrote! Ima's computer is now infected. You, the listowner of the abc-l list, and anyone else in Ima's address book, is now vulnerable to receiving the infection. List members start reporting that Sheeza Doe <_sheeza@isp.com> is sending out virus messages! Being a terrific list manager (and you are, aren't you?) you head for your utilities page to unsub this poor woman till she gets her machine cleaned up, but alas!... there is NO sheeza in the membership, nor is there anyone from isp! The message everyone received said it's from Sheeza Doe <_sheeza@isp.com> simply because Sheeza was in Ima's computer! Get that??? <g> (I've been working at this for a while folks, and am feeling a little uhm... "creative" here! If the Ima's and Sheeza's get you all fouled up, change the Ima to Jane and the Sheeza to son, John.) Symantec reports: If SMTP (user) information can be found on the current computer, then it will be used for the From: field. Otherwise, the From: field will be one of: "Mary L. Adams" <mary@c-com.net> "Monika Prado" <monika@telia.com> <--- I've had this one several times "Support" <support@cyberramp.net> "Admin" <admin@gte.net> "Administrator" <administrator@border.net> "JESSICA BENAVIDES" <jessica@aol.com> "Joanna" <joanna@mail.utexas.edu> "Mon S" <spiderroll@hotmail.com> "Linda" <lgonzal@hotmail.com> "Andy" <andy@hweb-media.com> "Kelly Andersen" <Gravity49@aol.com> "Tina" <tina0828@yahoo.com> "Rita Tulliani" <powerpuff@videotron.ca> "JUDY" <JUJUB271@AOL.COM> "Anna" <aizzo@home.com> However, we're all receiving messages from a host of other names, including those we don't know (like <_sheeza@isp.com>?). >From a message in the field: "I just discovered a problem when searching for FROM: addresses that start with <"_">. There is a problem with people who have their email program set to show both their name and email address in the FROM: header. If such a person is infected, mail from him/her will show, in the header, something like the following: "John Doe" <_johndoe@wherever.com> "The FROM: element in the header you see before you open the email will show only "John Doe". That's a problem. Either set up a filter to divert infected emails to a separate mailbox, or make sure your system is COMPLETELY protected before you open or preview any more emails.)" To notify the person who has the infected machine, simply remove the leading '_' from their email address. WHAT CAN YOU DO? 1.) Insure that your antivirus software has been updated since November 25, 2001. Anything before that will not give you the protection you need from this strain of BadTrans. Because of the mutations this strain appears to be doing, most people are updating DAILY now. 2.) Keep your antivirus program running at all times. You just never know when you'll be the next "recipient." 3.) Stay calm. Realize and remember that N0 virus is currently capable of passing through a RootsWeb list. Rootsweb's filters are set to very high. However, BadTrans.B makes it *APPEAR* that this is happening, and uses list messages as a source for new targets. Unsubscribing from the list will do you no good if your email address is already in someone else's computer and that machine becomes infected. MICROSOFT OUTLOOK USERS BE SURE TO READ THIS! Particularly vulnerable to the BadTrans.B virus are those users of Outlook (not Outlook Express). It's imperative that Outlook users NOT open suspicious emails, or even preview them. Outlook users will infect their computers simply by opening or previewing infected email. Since these infected messages have no attachments to click on in order to activate the virus, just opening the message activates the virus through HTML coding embedded in the post. Again, the message size is 29-30K, but what you see is a blank message. At the point of seeing the blank message, the computer has been infected. Outlook users are advised to view the headers. If a header reports a sender's address as similar to <_somebody@someisp.com>, DO NOT OPEN IT! As stated above, opening or even previewing an infected message through Outlook will activate the virus and cause your system to become infected. Available since May 16, 2001 is a patch for Outlook versions 5.01 and 5.5 that should be downloaded and installed immediately. MSIE 6.0 appears not to be affected because the patches for previous versions have been incorporated into it. You can check to see which patches your system needs by going to <http://windowsupdate.microsoft.com/>. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WINDOWS ME USERS READ THIS! Windows ME utilizes a backup utility that backs up selected files automatically to the C:\_Restore folder. This means that an infected file could be stored there as a backup file, and VirusScan will be unable to delete these files. I have the instructions on how to remove the infected files from the C:\_Restore folder if you need/want them. IDEAS AND COMMENTS FROM THE FIELD (US): 1. Are you concerned about even receiving infected messages? Here's an idea that _might_ work: Set up a special folder specifically for "Infected Mail." Then, use your email program's filter to watch and transfer all messages with the "_" in the header to that "Infected Mail" folder. Make sure this is the first of your filters. 2. Are you emailing people telling them their computer is infected and that person writes back that it's not? This is because of the virus sending out the infected messages without the PC owner's knowledge. The person's machine is "definitely infected, whatever they may say to the contrary. Keep in mind that the virus is only contained in the messages that their computer is sending without their knowledge - not the ones they are sending you legitimately. That is why you are receiving some virus infected messages and some virus free. Unless their virus definitions are up-to-date they could run a virus scan & find nothing. Norton only updated their definitions to include the latest Badtrans virus this weekend." It's important that you impress on these owners that their computer IS indeed, infected and they need to take care of it. 3. "In your address book ADD NEW Contact..... !0000 exactly like this. It puts this address first in your book and STOPS the virus from sending to your list..." This is a hoax, I'm afraid. It doesn't work. You'll find information about the "!0000" hoax at <http://antivirus.about.com/library/weekly/aa082801b.htm>. 4. Have you heard of MailWasher <http://www.mailwasher.net>? Though I haven't tried it, here's a user's comment regarding that FREE program: "I can view, identify and delete the viruses while they are still on the ISP server. They never get to my computer." Hmmm... perhaps it's worth checking out? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You've done it! You've made it to the end! Once again let's keep this off the list. If you have any questions you're welcome to email me <ladyaudris@earthlink.net>. I wish you a TERRIFIC Tuesday! :) Stay vigilant; stay alert ... keep your computer safe! Colleen

-----Original Message----- From: Porter [mailto:porterockwell@if.rmci.net] Sent: Monday, November 26, 2001 12:58 PM To: **WILLIAMS L; **vermont-l; **nystlawr-l; **nygenese-l; **kinney-l; ** miingham-l Subject: Take note! The Canadian government plans to permanently lock up or destroy all census records made after 1901. Genealogists throughout Canada and in many other countries have been fighting this plan. This week genealogists received a major setback in their efforts. For more information see: http://globalgenealogy.com/Census (in English) and at: http://globalgenealogy.com/Census/Index_f.htm (en fran=E7ais).

Hi everyone, In light of this new wave of the BadTrans, I'm now requesting that any of you who have presents to send for our family Christmas to please let me know first that you're sending me a file. Give me the exact name of the file and please don't send it until you've heard back from me that I'm ready to receive it. This is my only way of protecting my computer. Saturday, December 8th, is the deadline for Christmas gift submissions. I haven't received many for the size of family we are, so I hope we just have a lot of last-minute people here. :) I wish you all a MAHHHVELOUS Monday! :) Colleen

Hi everyone, It appears there's a new strain of the Bad Trans virus running rampant through the lists. This one is the <W32.Badtrans.B@mm>. For benefit of you newbies, the BadTrans is a nasty little worm that gets into your computer and mails out messages without your knowledge. This new version of the worm also drops a backdoor trojan that logs keystrokes. Those messages contain an attachment with the virus. A quick lesson here for those of you who don't know ... 1. You should ALWAYS be extremely cautious when it comes to opening opening attachments. If you receive one that you didn't expect, before opening it write back to the sender to see if s/he mailed something to you and find out what it is. 2. You will NEVER receive a virus through the list, but if listmembers get infected, their computer may send you the virus, which *may* have a list subject line. 3. This new strain of BadTrans is going to make life difficult for a LOT of people. Note the differences: The first wave of BadTrans virus messages always had a standard "Take a look to the attachment." at the end of the message but above the attachment. Also, those messages had double extensions (for example: filename.exe.pif OR filename.doc.scr OR filename.txt.exe OR any other combination of extensions), know immediately that your message is holding a virus. Do not open the attachment, but delete it immediately. According to people who have already received infected messages this newer strain of BadTrans virus is even nastier than the first because the attachment may not show or there is a false (second) extension. It appears to have filename.doc or filename.txt BUT THE REAL EXTENSION ( .scr or .exe) IS 59 SPACES TO THE RIGHT. Also, the message size will be around 29 or 30k even if no words shows up. One other clue, the email addresses of the sending computers is altered by having an underline character preceeding the address <__xyz123@someisp.com>. You are strongly encouraged to keep your virus protects updated on a daily basis ~ or at least every other day. If you receive an infected message please do two things: 1. advise the family of the fact you've received an infected message and from whom. 2. send me the name and email address of the person with the infected computer as well as the list name If YOU have the infected computer I will unsubscribe you from the list until you've cleaned your machine and let me know about it. This is for protection of the cousins' computers. You can read about this virus and how to remove it from your system on the Norton Symantec site ... http://www.symantec.com/avcenter/ http://www.symantec.com/avcenter/venc/data/w32.badtrans.b@mm.html Let's NOT turn this to a virus discussion on the list. If you have any questions you're welcome to email me <ladyaudris@earthlink.net>. Stay alert, everyone. Colleen

>From the St Lawrence Co, NY Genweb page: "St. Lawrence County Civil War Rosters 20th Cavalry - "McClellan Cavalry", Company H (Captain J. Bower Preston Jr.) ... NOTE: This data was transcribed from the History of St. Lawrence County, New York published by L. H. Everts & Company in 1878. Comments can be directed to: Anne M. Cady " ============================================================================ ============== Bower sighting: Morrison County, MN -- Historical Sketches of Royalton & Vicinity http://www.mipaca.com/tburrows/royal1.html " One of the best know of the early settlers at the south end of the Prairie was John Higgins, born in New York in 1836. Mr. Higgins came west in 1854, settling near the Robert Russell place in what is now the town of Langola, Benton County. He followed teaming as well as farming in the early days, and during the Sioux Indian outbreak in 1862 joined General Sibley's expedition in the war against the redskins. He was always prominent in public affairs, and held many local offices. He was well posted in the events of the early days, and the writer is indebted to him for much data of this history of early settlement. Mr. Higgins died about 25 years ago. A daughter, Mrs. M.J. Bowers, is a resident of Royalton ============================================================================ =============== 1856 Census: Mitchell County, IA - Osage Twp: page 672 dwelling #40 Bowers Cyrus E. age 22 Male 1yr in IOWA born in MI occupation: Carpenter X (in the militia) enumerated with Hiram S Libby, Geo.W Camp, and Geo. Myers ============================================================================ =============== IOWA 1895 CENSUS, Mitchell County -- Sorted by Surname and Given Name SURNAME GIVEN NAME AGE LINE TOWN/TOWNSHIP ------------- --------------------- ------ ------ ------ ------------------ Bowen John F 34 149 OSAGE, Wd 4 Bowen Lizzie 20 152 OSAGE, Wd 4 Bowen Mary E 56 150 OSAGE, Wd 4 Bowen Sarah 24 151 OSAGE, Wd 4 Bower Alice J 4 377 BURR OAK TWP. Bower Anna C 8 375 BURR OAK TWP. Bower Caroline 43 373 BURR OAK TWP. Bower John * 17 374 BURR OAK TWP. Bower John G 46 372 BURR OAK TWP. Bower Robert C 6 376 BURR OAK TWP. Bowers Albert 13 25 ST. ANSGAR Bowers Amanda 10 26 ST. ANSGAR Bowers Amiel 2 28 ST. ANSGAR Bowers Charles 45 22 ST. ANSGAR Bowers Hulda 36 23 ST. ANSGAR Bowers Richard 5 27 ST. ANSGAR Bowers William 15 24 ST. ANSGAR Bowes Lizzie 19 369 BURR OAK TWP. Note: Only the Burr Oak Twp Bower family is mine... Brenda Bower-Klehn

-------- Original Message -------- Subject: [BAUER] ISTG Resent-Date: Sat, 24 Nov 2001 18:56:02 -0700 Resent-From: BAUER-L@rootsweb.com Date: Sat, 24 Nov 2001 20:55:55 EST From: Caffecupz@aol.com Reply-To: BAUER-L@rootsweb.com To: BAUER-L@rootsweb.com Ship Mortonhouse Rotterdam, Netherlands via Cowes, England to Philadelphia 19 August 1729 20* Hans Muller 54* Gerhardt Muller 57* Johannes Muller Ship Allen Rotterdam, Netherlands via Cowes, England, to Philadelphia 15 September 1729 28 Georg Vetter 34 Christian Schneider 41 Matheis Schneider Ship Alexander and Ann Rotterdam, Netherlands via Cowes, England to Philadelphia 5 September 1730 4* Martin Muller 7 Jacob Muller 32 Martin Bucher Ship Loyall Judith Rotterdam, Netherland via Cowes, England to Philadelphia 25 September 1732 38* Han[n]s Jerch Burk[art] 41 Johann Georg Obermuller 44 Friedrich Kohler 46 Hans Jerg Wagner 62* Hans David (O) Ely 89 George Muller 114 Hans Martin Bau[er] Ship Harle Rotterdam, Netherlands via Cowes, England to Philadelphia 1 September 1736 19 Johannes Schnieder 61 Cornelius Weygandt Snow Thane of Fife Rotterdam, Netherlands via Aberdeen, Scotland to Philadelphia 7 November 1741 16 Anthony Schneyder Europa Rotterdam, Netherlands to Philadelphia, PA 20 Nov 1741 9 Mathias Bower 25 10 John Paul Bower 23 11 Michael Bower 20 44 Hans Jurigh Schnyder 40 45 Jacob Schnyder 16 56 Christp Waganer 20 59 Nicolas Waganer 20 ==== BAUER Mailing List ==== Please do not send messages with attachments, HTML, MIME, or any other enhanced text to the list. RootsWeb does not allow messages with those settings through their servers and will only return them to you. ============================== Visit Ancestry.com for a FREE 14-Day Trial and enjoy access to the #1 Source for Family History Online. Go to: http://www.ancestry.com/rd/redir.asp?targetid=702&sourceid=1237

Keep in mind that the south part of Adams Co. at that time was considered to be a part of MD! We spent a lot of energy looking in PA records for folks who's every move was in the records in Frederick Co., MD. Gil mailto:gilcarrick@home.com web page: http://www.members.home.net/gilcarrick/ Gil Carrick, 1012 Portofino Dr., Arlington, TX, 76012 > -----Original Message----- > From: dkschmid [mailto:dkschmid@wcnet.org] > Sent: Sunday, November 11, 2001 5:40 PM > To: BOWER-L@rootsweb.com > Subject: Re: [BOWER] SUNDAY MORNING COFFEE > > > Mary, > I saw your response to Marilyn and I am wondering if you know > who your Thomas's father was or if your Thomas had any > brothers or sisters. My gggrandfather Joel Bower was born in > 1794 in York Co. but now it would be Adams Co., Pa. Joel had > a brother Thomas, a brother Michael, a sister Mary Ann and a > sister Jane who married Moses Myers. Their father was > Jonathan whose wife was Martha. I really don't know anything > about Joel's sisters and brothers. The birth date of 1808 > for Thomas would fit well with Joel's 1794. In Jonathan's > will Thomas has a middle initial of R. > > I too am probably grasping at straws. Let me know if we have > a match or > not. Thanks! ...

Hi cousins, The turkey has been on since 10:00 a.m. and I finished watching the Macy's Thanksgiving Day parade over an hour ago ... The holidays have arrived! :) While I was watching the parade though, I gave quite a bit of thought to what I, or anyone in the U.S. right now, had to be thankful for. We're still healing and in recovery, but there MUST be something for us all to be happy about. What, though? 1. We're still free! The U.S. was attacked all right, but we weren't annihilated. Lady Liberty still stands. 2. Our flag still waves with pride and our eagle still soars in determined resolve! The U.S. was slapped but good; it's just too bad those who did this to us didn't realize just who they were messing with. They probably would have given second thought to their actions. You'd have thought history would have taught them, though. 3. Our country came together as ONE voice, one family, and the world joined us. 4. Most of us still have our inlife family and friends ~ our inlife support systems ~ our inlife reasons for being... 5. We still have each other! Some of us may still feel broken, we may be struggling for answers, we may still be filled with anguish, pain and/or anger ~ but we still have each other to turn to ... global cousins who have found each other and come together as the ancestral family that we are. 6. We still have our health ~ shaky though it may be for some of us, it's brought us all to today and each other. And there are 5 more things I'm thankful for, but they're more personal more to me... 7.) My husband and children - he's getting older and so are the kids. I think I'll keep them all. 8.) The love of my cherished husband, Bruno, and our five children. 9.) Brenda, my very bestest friend! She's the sister of my soul without whom I think more of my inlife "tragedies" would be much worse! 10.) Every day that I wake up; one day I won't. Can you add at least five of your own "personal thankfuls" where I've added mine? I hope so. I wish each of you a bountiful Thanksgiving filled with inner peace, love and joy! Colleen

-------- Original Message -------- Subject: [BAUER] http://istg.rootsweb.com Resent-Date: Tue, 20 Nov 2001 19:51:26 -0700 Resent-From: BAUER-L@rootsweb.com Date: Tue, 20 Nov 2001 21:51:24 EST From: Caffecupz@aol.com Reply-To: BAUER-L@rootsweb.com To: BAUER-L@rootsweb.com Brig Herschel Bremen, Germany to Galveston, Texas 24 January 1850 34 Christoph Bauer 42 male farmer 35 Johanna Bauer 44 female 36* Johanna Bauer 17 male farmer 37 Jacob Bauer 14 male 38 Johannie Bauer 11 female 39 Christolph Bauer 10 male 40 Catherine Bauer 8 female 41 Wilhelm Bauer 5 male 42 Chrissene Bauer 2 female Ship GF Patton Bremen, Germany to New York 3 Oct 1851 43 Henrick Bauer 36 male Farmer Humendorf United States Ship Hermine Bremen, Germany to New York 3 November 1851 101 C Bauer 28 F Servantgirl Bavaria New York 102 C Bauer 63 F Bavaria New York Bark Edmund Bremen, Germany to New Orleans 23 June 1852 73 H. Baurichter 2 M Farmer Germany Admiral Branning Bremen, Germany to New York 1 November 1852 16* friedr. Neubauer 17y 6m m tanner Gotha New York 201 Jos Bauer 18 m tailor Beissesletz New York 263 Barbara Bauer 19 f servant Neustadt New York ==== BAUER Mailing List ==== Please avoid flaming (attacking) any single person or the group. This infraction will earn you immediate removal from the list. ============================== Visit Ancestry.com for a FREE 14-Day Trial and enjoy access to the #1 Source for Family History Online. Go to: http://www.ancestry.com/rd/redir.asp?targetid=702&sourceid=1237

Dear Colleen and others, I used to use FTM, but I don't anymore and I'm not going back to it. I use a much better program now. I use FTM only to read those FTM CDs. However, your warning about v.9, I think, is *perhaps* off-base. I wouldn't put it past them, but in this case, I *think* they are innocent. What I think happened is that they put the aqueduct file into the program to help track the beta-testers. The testers knew about it. Somebody didn't remove it when betatesting was done. There's been a downloadable file available for several months that corrects this problem. See what Paul Burchfield, who provides tech support for FTM, said about this file at: http://genforum.genealogy.com/using/messages/21682.html At the very least, it's a monumental screw-up on their part. But I think that might be all there is to it. Chuck Wolfram FAMILY TREE MAKER, VERSION 9: A WARNING It has come to my attention that Family Tree Maker may be up to no good with the latest version (9) of their genealogy program. Since I don't use FTM with any degree of proficiency (I use PAF), I'm passing along this warning by way of copy and paste. Those of you who use FTM will want to read this carefully: "Mattel, the parent company of FTM has included tracking software in Version 9 which keeps track of everything you do on the internet and sends a log of your surfing habits to Mattel every time you log on. The log file is called "aqueduct" and can be found in the root directory of your C drive. I have deleted the file and gone back to version 8. "I discovered {this] quite by accident. In an unrelated attempt to fix one of my screwups on my hardrive, I discovered the file called "aqueduct" and opened it as I didn't know what it was. I discovered that it was a log of all my surfing habits and I now know, it covered the period from when I installed the FTM 9 upgrade to the date I discovered it and deleted it. I didn't realize it was a FTM by product until I tried to open FTM (after deleting aqueduct) and I got an error message saying "Aqueduct" was missing -- it seems that without the file, FTM version 9 will not run at all. Since I detest tracking software of any kind, I uninstalled FTM version 9 and reinstalled FTM version 8. Note: You will have to open and rename your database backup copy as any database file that you opened and stored in version 9 will be useless." I won't mention the person's name here since our messages go into public archives. However, if you use FTM and want to know who has issued this warning, please write me offline and I'll pass the address along to you. Or, if there are many of you wanting the name and email addy, will send your names and addies to the person so s/he can post to you. One way or another, you will be put in contact, if that's your desire. :)

-------- Original Message -------- Subject: [BAUER] http://istg.rootsweb.com/ Resent-Date: Mon, 19 Nov 2001 22:29:43 -0700 Resent-From: BAUER-L@rootsweb.com Date: Tue, 20 Nov 2001 00:29:44 EST From: Caffecupz@aol.com Reply-To: BAUER-L@rootsweb.com To: BAUER-L@rootsweb.com Galliot Johanna Elizabeth Bremen, Germany to Baltimore, Maryland 6 June 1834 Columns represent: name, occupation, last dwelling place, total number of people with each group. 17 Bauer Caspar shoemaker Poppenlauer 1 male, 1 female, total 2 18 Bauer John shoemaker Poppenlauer 1 male, 2 females, 4 children above 5 years, 2 children below 5 years, total 9 20 Ba??r Valentin mason Volkertshausen 1 male, 1 female 2 children below 5 years, total 4 24 Neugebauer John peasant Feckersfeld 1 male, total 1 Galliot Themis Bremen, Germany to Baltimore, Maryland 24 July 1834 32 Joh. Bauer Niederstetten 1 adult 49 G. F. Bauer Wertheim 1 adult Ship Lucilla to Steamboat Norfolk Bremen, Germany via City Point, Virginia, to Baltimore, Maryland 17 August 1835 24 John Bower 22 male farmer 25 Elizabeth Bower 23 female 26 Elizabeth Bower 1y3m female ==== BAUER Mailing List ==== Bower Cottage, sister site to the Bauer Family Homestead, homesites of the Bauer research group -- http://bowercommunity.com/cottage ============================== Search over 1 Billion names at Ancestry.com! http://www.ancestry.com/rd/rwlist1.asp

-------- Original Message -------- Subject: [BAUER] http://istg.rootsweb.com/ Resent-Date: Mon, 19 Nov 2001 22:27:27 -0700 Resent-From: BAUER-L@rootsweb.com Date: Tue, 20 Nov 2001 00:27:21 EST From: Caffecupz@aol.com Reply-To: BAUER-L@rootsweb.com To: BAUER-L@rootsweb.com Ship Aurora >From Bremen to Baltimore September 19, 1833 82 K. Bauer 40 farmer Holshausen Baltimore 83 Catrina Bauer 35 farmer Holshausen Baltimore 84 Conrade Bauer 12 farmer Holshausen Baltimore 85 C. Bastian Bauer 10 farmer Holshausen Baltimore 86 Elisab Bauer 4y9m farmer Holshausen Baltimore 87 Catrina Bauer 3y6m farmer Holshausen Baltimore 88 Maria Bauer 1 farmer Holshausen Baltimore 89 Joseph Bauer 47 farmer Shtockdart Baltimore 90 Elisab Bauer 36 farmer Shtockdart Baltimore 91 Anna Bauer 21 farmer Shtockdart Baltimore 92 Elisabeth Bauer 15 farmer Shtockdart Baltimore 93 Catrina Bauer 12 farmer Shtockdart Baltimore 94 Maria Bauer 9 farmer Shtockdart Baltimore 95 Dortia Bauer 6 farmer Shtockdart Baltimore 96 Eva Bauer 4 farmer Shtockdart Baltimore 97 Anna Maria Bauer 1y6m farmer Shtockdart Baltimore 98 Adam Bauer 41 farmer Shtockdart Baltimore 99 Anna Bauer 38 farmer Shtockdart Baltimore 100 Elisab Bauer 13 farmer Shtockdart Baltimore 101 Peter Bauer 11 farmer Shtockdart Baltimore 102 Johann Bauer 8 farmer Shtockdart Baltimore 103 Angelhene Bauer 4y6m farmer Shtockdart Baltimore 104 Enganete Bauer 2y9m farmer Shtockdart Baltimore ==== BAUER Mailing List ==== To post messages to the Bauer discussion list, send them to BAUER-L@rootsweb.com

Hi everyone, I've just received the following message from Paul Burchfield, Genealogy.com Technical Support in response to the FTM version 9 warning I issued in Sunday's Coffee. It seems that the information I was given and passed along to all of you was inaccurate. I do apologize for "causing a lot of unnecessary angst among people." (see below) Please understand, mine was meant only to warn and alert FTM users about yet another possible attempt to encroach in our personal lives by a commercial enterprise. Most of you already know how deeply I feel about our "watching out" for each other as family, peers, cousins, friends, etc. I received the alert from someone I trusted, and still do. As an already reported non-user of FTM, I believed my informant had already done his/her "homework." Please forgive. As I stated earlier, my intent was purely to be helpful and alert you; that was all. I post Paul's message to you in its entirety. I wish you all a WONDERFUL week! :) Colleen -------- Original Message -------- Subject: Family Tree Maker 9 warning Date: Mon, 19 Nov 2001 20:34:48 -0800 From: "Paul Burchfield" <Paul_Burchfield@genealogy.com> To: <ladyaudris@earthlink.net> Colleen, A member of the ORTON-L list passed along a copy of a message you sent to the list where you passed along a warning about Family Tree Maker version 9. Unfortunately, what you saw and passed on is inaccurate. With one person seeing it on one list an then passing it along to another and so on, it's causing a lot of unnecessary angst among people. The issue is not a nefarious one at all. That software is used during beta testing as a tool to help us know what our testers have been doing (to make sure we test enough in all of the areas of the program). it also helps us identify what was happening and what went wrong if during testing the program crashes. During the beta testing period, we periodically ask our beta testers to send to us by attaching the file that is created showing this information to an email. It is not sent to us automatically. Usually when we are done testing and create the final version used to duplicate for sale, we replace the active program file that creates the file that gathers the testing information with an inactive version that doesn't gather the information. Somewhere along the line that part was not done when we shipped version 9. We found this more than a month ago and at that point in time created a knowledge base article. We also made the replacement, inactive program file available for download so people could use it to replace the active one. When we later discovered a problem with Family Tree Maker and created a downloadable update for it, we also included as a part of that the inactive aqueduct file. Because someone didn't ask us about this nor did they look at the existing information we had on this topic, incorrect and inflammatory messages have been created and passed around. It's unfortunate that the originator of the message nor those who are passing it along didn't come to us and ask about it. I would appreciate knowing from whom you received the message. I would like to make sure that they understand what the real issue is. Sincerely, Paul Burchfield, Genealogy.com Technical Support Online Help Center - http://www.genealogy.com/help/index.html