Hazel To help identify and remove any inconsistencies in our instructions Where exactly did you see the instructions to transcribe Mother's name was given as Smith or Jones, you mention *under transcribing, section 13, comment and theory?. Can you please supply the link for section 13, comment and theory? I should perhaps mention the instructions in http://www.freebmd.org.uk/vol_faq.html#6u which mentions #COMMENT(2) entry reads <alternative> for <field> has been in place since at least mid 2007 possibly before you started transcribing for FreeBMD. Thanks Allan Raymond ----- Original Message ----- From: Hazel Kingston To: freebmd-admins@rootsweb.com Sent: Tuesday, March 13, 2012 7:36 AM Subject: Re: FREEBMD-ADMINS Digest, Vol 7, Issue 15 When I started doing transcriptions the wording to follow* was as per this example:- #COMMENT(2)Mother's name was given as Smith or Jones. (Similarly for spouse name and page number altrnatives) Just slightly different but what I always follow. *under transcribing, section 13, comment and theory On Tue, Mar 13, 2012 at 7:00 AM, <freebmd-admins-request@rootsweb.com>wrote: > > Mail for the mailing list should be sent to > FreeBMD-Admins@rootsweb.com > > The website for the mailing list is > http://www.freebmd.org.uk > It contains all the information about the project and its current status. > Archives http://archiver.rootsweb.com/th/index/freebmd-admins > > Today's Topics: > > 1. alternate names (Mike Parker) > 2. Re: alternate names (Allan Raymond) > 3. Re: alternate names (Evan Smith) > > > ---------- Forwarded message ---------- > From: Mike Parker <3185mike@gmail.com> > To: FreeBMD-Admins@rootsweb.com > Cc: > Date: Mon, 12 Mar 2012 19:30:42 +0000 > Subject: alternate names > Hi and i put after the comment(2) wife named as Smith or Jones.....or > mother named as brown or White... This seems to work ok. Is that not > simpler???cheers Mike Parker > > > > ---------- Forwarded message ---------- > From: "Allan Raymond" <allan_raymond@btinternet.com> > To: <freebmd-admins@rootsweb.com> > Cc: > Date: Mon, 12 Mar 2012 20:28:12 -0000 > Subject: Re: alternate names > Nice to hear you are indicating in your transcriptions the entries have > alternative names where appropriate. > > However it is far better if everyone for consistency adopted a standard > approach to dealing with alternative names rather than inventing their own > format > > Hence why we introduced the rule to transcribe alternative names in the > standard format: many years ago. > > #COMMENT(2) entry reads <alternative> for <field> > > So an entry in scan > http://images.freebmd.org.uk/GUS/1961/Births/March/ANC-05/G-O/1961B1-G-0015.jpgsuch as > > GENTLES,Sheena K. E.,GENTLES or LOGAN,Lambeth,5c,2160 > > should be transcribed as: > > GENTLES,Sheena K. E.,GENTLES,Lambeth,5c,2160 > #COMMENT(2) entry reads GENTLES or LOGAN for mother's name > GENTLES,Sheena K. E.,LOGAN,Lambeth,5c,2160 > > This spells out exactly the fact the index shows GENTLES or LOGAN for the > mother's name. > > Allan Raymond
Sorry the link to the TKB para 6q is : http://www.freebmd.org.uk/cgi/highlight.pl?word=theory&word=ref&file=vol_faq.html#6q ----- Original Message ----- From: "D LOWE" <derek_lowe@btinternet.com> To: <freebmd-admins@rootsweb.com> Sent: Tuesday, March 13, 2012 4:11 PM Subject: Re: Page numbers The trouble with this is that you don't know whether the reference to the supplementary Index - 1085/S - applies to the year of the original entry or the Mar 73 Qtr. Thus if the entry is treated as an alternative data entry one entry may refer to the current quarter and the other to the M73 quarter thus creating confusion. It seems to me that the best way to deal with this is to TWYS and, as this will create a warning, simply add a theory ref entry , i.e. #THEORY,REF,see M/73 http://www.freebmd.org.uk/cgi/highlight.pl?word=theory&word=ref&file=vol_faq.html#6q This would mean that any researcher would see what is on the Index page and also be directed to the Mar 73 in the same way as other late entries are. Derek Lowe ----- Original Message ----- From: "Jeff Coleman" <Jeff.Coleman@ntlworld.com> To: <freebmd-admins@rootsweb.com> Sent: Tuesday, March 13, 2012 8:57 AM Subject: Re: Page numbers I would suggest that TKB 6(am) applies. Put the entry in twice, once with M73 ( which can then be used to link to that entry when transcribed) and once with 1085/S In between put #COMMENT(2) entry reads M73 1085/S for Page No. Jeff ----- Original Message ----- From: "Keith Simpson" <simpson@keith1954.orangehome.co.uk> To: <freebmd-admins@rootsweb.com> Sent: Tuesday, March 13, 2012 8:47 AM Subject: Page numbers Hi, I have come across page numbers in the format of M73 1085/S When these numbers are entered you get a warning from Freebmd. I know these are late entries but I can¹t find any reference in the knowledge base to explain them. Help would be appreciated. Keith FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins FreeBMD http://www.freebmd.org.uk/ ------------------------------- To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins FreeBMD http://www.freebmd.org.uk/ ------------------------------- To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message
The trouble with this is that you don't know whether the reference to the supplementary Index - 1085/S - applies to the year of the original entry or the Mar 73 Qtr. Thus if the entry is treated as an alternative data entry one entry may refer to the current quarter and the other to the M73 quarter thus creating confusion. It seems to me that the best way to deal with this is to TWYS and, as this will create a warning, simply add a theory ref entry , i.e. #THEORY,REF,see M/73 http://www.freebmd.org.uk/cgi/highlight.pl?word=theory&word=ref&file=vol_faq.html#6q This would mean that any researcher would see what is on the Index page and also be directed to the Mar 73 in the same way as other late entries are. Derek Lowe ----- Original Message ----- From: "Jeff Coleman" <Jeff.Coleman@ntlworld.com> To: <freebmd-admins@rootsweb.com> Sent: Tuesday, March 13, 2012 8:57 AM Subject: Re: Page numbers I would suggest that TKB 6(am) applies. Put the entry in twice, once with M73 ( which can then be used to link to that entry when transcribed) and once with 1085/S In between put #COMMENT(2) entry reads M73 1085/S for Page No. Jeff ----- Original Message ----- From: "Keith Simpson" <simpson@keith1954.orangehome.co.uk> To: <freebmd-admins@rootsweb.com> Sent: Tuesday, March 13, 2012 8:47 AM Subject: Page numbers Hi, I have come across page numbers in the format of M73 1085/S When these numbers are entered you get a warning from Freebmd. I know these are late entries but I can¹t find any reference in the knowledge base to explain them. Help would be appreciated. Keith FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins FreeBMD http://www.freebmd.org.uk/ ------------------------------- To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message
At # 6u you could be forgiven for thinking there is a space between #COMMENT and (2) or #COMMENT and (3). (though there is clearly no space in Allan's Tip of the Day.) Further, some of the comment on this matter varies in that some use the term "name" and others "surname". Also, when we refer to mother we follow it with an 's but when we refer to spouse we don't. This may seem nit-picking, but if uniformity is important enough to the system that we are advised not to leave a space between #COMMENT and (2) - or (3) as the case may be - may we have these points cleared up. Evan S. ----- Original Message ----- From: "Allan Raymond" <allan_raymond@btinternet.com> To: <freebmd-admins@rootsweb.com> Sent: Tuesday, March 13, 2012 6:28 AM Subject: Re: alternate names > Nice to hear you are indicating in your transcriptions the entries have > alternative names where appropriate. > > However it is far better if everyone for consistency adopted a standard > approach to dealing with alternative names rather than inventing their own > format > > Hence why we introduced the rule to transcribe alternative names in the > standard format: many years ago. > > #COMMENT(2) entry reads <alternative> for <field> > > So an entry in scan > http://images.freebmd.org.uk/GUS/1961/Births/March/ANC-05/G-O/1961B1-G-0015.jpg > such as > > GENTLES,Sheena K. E.,GENTLES or LOGAN,Lambeth,5c,2160 > > should be transcribed as: > > GENTLES,Sheena K. E.,GENTLES,Lambeth,5c,2160 > #COMMENT(2) entry reads GENTLES or LOGAN for mother's name > GENTLES,Sheena K. E.,LOGAN,Lambeth,5c,2160 > > This spells out exactly the fact the index shows GENTLES or LOGAN for the > mother's name. > > Allan Raymond > > ----- Original Message ----- > From: Mike Parker > To: FreeBMD-Admins@rootsweb.com > Sent: Monday, March 12, 2012 7:30 PM > Subject: alternate names > > > Hi and i put after the comment(2) wife named as Smith or Jones.....or > mother named as brown or White... This seems to work ok. Is that not > simpler???cheers Mike Parker > FreeBMD-Admins mailing list - archive > http://archiver.rootsweb.com/th/index/freebmd-admins > > FreeBMD http://www.freebmd.org.uk/ > > > ------------------------------- > To unsubscribe from the list, please send an email to > FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without > the quotes in the subject and the body of the message
Hi Jeff, Is this a change in procedure? If a combination handwritten Page Reference has been inserted, as an amendment to an existing Page Number that has been crossed through, e.g:- CAMPBELL,Mildred,PRICE,Manchester,10e,285 M'69 0385/S then the transcription would be:- CAMPBELL,Mildred,PRICE,Manchester,10e,M'69 0385/S #COMMENT handwritten amendment of crossed out page number 285 #THEORY,REF,See M/1969 Best wishes, Peter Peter M Jones Red Rose Syndicate FreeBMD -----Original Message----- From: freebmd-admins-bounces@rootsweb.com [mailto:freebmd-admins-bounces@rootsweb.com] On Behalf Of Jeff Coleman Sent: 13 March 2012 08:58 To: freebmd-admins@rootsweb.com Subject: Re: Page numbers I would suggest that TKB 6(am) applies. Put the entry in twice, once with M73 ( which can then be used to link to that entry when transcribed) and once with 1085/S In between put #COMMENT(2) entry reads M73 1085/S for Page No. Jeff ----- Original Message ----- From: "Keith Simpson" <simpson@keith1954.orangehome.co.uk> To: <freebmd-admins@rootsweb.com> Sent: Tuesday, March 13, 2012 8:47 AM Subject: Page numbers Hi, I have come across page numbers in the format of M73 1085/S When these numbers are entered you get a warning from Freebmd. I know these are late entries but I can¹t find any reference in the knowledge base to explain them. Help would be appreciated. Keith FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins FreeBMD http://www.freebmd.org.uk/ -------------------------------
I would suggest that TKB 6(am) applies. Put the entry in twice, once with M73 ( which can then be used to link to that entry when transcribed) and once with 1085/S In between put #COMMENT(2) entry reads M73 1085/S for Page No. Jeff ----- Original Message ----- From: "Keith Simpson" <simpson@keith1954.orangehome.co.uk> To: <freebmd-admins@rootsweb.com> Sent: Tuesday, March 13, 2012 8:47 AM Subject: Page numbers Hi, I have come across page numbers in the format of M73 1085/S When these numbers are entered you get a warning from Freebmd. I know these are late entries but I can¹t find any reference in the knowledge base to explain them. Help would be appreciated. Keith
Hi, I have come across page numbers in the format of M73 1085/S When these numbers are entered you get a warning from Freebmd. I know these are late entries but I can¹t find any reference in the knowledge base to explain them. Help would be appreciated. Keith
> At # 6u you could be forgiven for thinking there is a space between > #COMMENT and (2) or #COMMENT and (3). (though there is clearly no space > in Allan's Tip of the Day.) Further, some of the comment on this matter varies > in that some use the term "name" and others "surname". Also, when we > refer to mother we follow it with an 's but when we refer to spouse we > don't. This may seem nit-picking, but if uniformity is important enough to the > system that we are advised not to leave a space between #COMMENT and > (2) - or (3) as the case may be - may we have these points cleared up. I try and make the name of the field match the column in question, for example for 1952 births, the column is headed "Mother's Maiden Surname" so I put exactly that. If it says Mother's Maiden Name in the year I'm doing I would use that. As to which is simpler, I would say the more formal English is clearer and more blandly stating what is observed and leaving most of the interpretation to the user. It's simpler *for me* to have a set wording to work from, the formality of the language makes little difference to me.
A comment has been added to item 6u <http://www.freebmd.org.uk/vol_faq.html#6u> in the Transcribers' Knowledge Base to clarify that there is no space, although, since it is unambiguous what is meant, the system will accept a space (because of usage). Item 6u is very specific about the names that should be used, including "mother's name" and "spouse name". Barrie On 19:59, Evan Smith wrote: > At # 6u you could be forgiven for thinking there is a space between #COMMENT > and (2) or #COMMENT and (3). (though there is clearly no space in Allan's Tip > of the Day.) > Further, some of the comment on this matter varies in that some use the term > "name" and others "surname". Also, when we refer to mother we follow it with > an 's but when we refer to spouse we don't. This may seem nit-picking, but if > uniformity is important enough to the system that we are advised not to leave > a space between #COMMENT and (2) - or (3) as the case may be - may we have > these points cleared up. > > Evan S. > > > > > ----- Original Message ----- From: "Allan Raymond" <allan_raymond@btinternet.com> > To: <freebmd-admins@rootsweb.com> > Sent: Tuesday, March 13, 2012 6:28 AM > Subject: Re: alternate names > > >> Nice to hear you are indicating in your transcriptions the entries have >> alternative names where appropriate. >> >> However it is far better if everyone for consistency adopted a standard >> approach to dealing with alternative names rather than inventing their own >> format >> >> Hence why we introduced the rule to transcribe alternative names in the >> standard format: many years ago. >> >> #COMMENT(2) entry reads <alternative> for <field> >> >> So an entry in scan >> http://images.freebmd.org.uk/GUS/1961/Births/March/ANC-05/G-O/1961B1-G-0015.jpg >> such as >> >> GENTLES,Sheena K. E.,GENTLES or LOGAN,Lambeth,5c,2160 >> >> should be transcribed as: >> >> GENTLES,Sheena K. E.,GENTLES,Lambeth,5c,2160 >> #COMMENT(2) entry reads GENTLES or LOGAN for mother's name >> GENTLES,Sheena K. E.,LOGAN,Lambeth,5c,2160 >> >> This spells out exactly the fact the index shows GENTLES or LOGAN for the >> mother's name. >> >> Allan Raymond >> >> ----- Original Message ----- From: Mike Parker >> To: FreeBMD-Admins@rootsweb.com >> Sent: Monday, March 12, 2012 7:30 PM >> Subject: alternate names >> >> >> Hi and i put after the comment(2) wife named as Smith or Jones.....or >> mother named as brown or White... This seems to work ok. Is that not >> simpler???cheers Mike Parker >> FreeBMD-Admins mailing list - archive >> http://archiver.rootsweb.com/th/index/freebmd-admins >> >> FreeBMD http://www.freebmd.org.uk/ >> >> >> ------------------------------- >> To unsubscribe from the list, please send an email to >> FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without the >> quotes in the subject and the body of the message > > --Certified Virus Free by 4SecureMail.com ICSA-Certified Scanner--
When I started doing transcriptions the wording to follow* was as per this example:- #COMMENT(2)Mother's name was given as Smith or Jones. (Similarly for spouse name and page number altrnatives) Just slightly different but what I always follow. *under transcribing, section 13, comment and theory On Tue, Mar 13, 2012 at 7:00 AM, <freebmd-admins-request@rootsweb.com>wrote: > > Mail for the mailing list should be sent to > FreeBMD-Admins@rootsweb.com > > The website for the mailing list is > http://www.freebmd.org.uk > It contains all the information about the project and its current status. > Archives http://archiver.rootsweb.com/th/index/freebmd-admins > > Today's Topics: > > 1. alternate names (Mike Parker) > 2. Re: alternate names (Allan Raymond) > 3. Re: alternate names (Evan Smith) > > > ---------- Forwarded message ---------- > From: Mike Parker <3185mike@gmail.com> > To: FreeBMD-Admins@rootsweb.com > Cc: > Date: Mon, 12 Mar 2012 19:30:42 +0000 > Subject: alternate names > Hi and i put after the comment(2) wife named as Smith or Jones.....or > mother named as brown or White... This seems to work ok. Is that not > simpler???cheers Mike Parker > > > > ---------- Forwarded message ---------- > From: "Allan Raymond" <allan_raymond@btinternet.com> > To: <freebmd-admins@rootsweb.com> > Cc: > Date: Mon, 12 Mar 2012 20:28:12 -0000 > Subject: Re: alternate names > Nice to hear you are indicating in your transcriptions the entries have > alternative names where appropriate. > > However it is far better if everyone for consistency adopted a standard > approach to dealing with alternative names rather than inventing their own > format > > Hence why we introduced the rule to transcribe alternative names in the > standard format: many years ago. > > #COMMENT(2) entry reads <alternative> for <field> > > So an entry in scan > http://images.freebmd.org.uk/GUS/1961/Births/March/ANC-05/G-O/1961B1-G-0015.jpgsuch as > > GENTLES,Sheena K. E.,GENTLES or LOGAN,Lambeth,5c,2160 > > should be transcribed as: > > GENTLES,Sheena K. E.,GENTLES,Lambeth,5c,2160 > #COMMENT(2) entry reads GENTLES or LOGAN for mother's name > GENTLES,Sheena K. E.,LOGAN,Lambeth,5c,2160 > > This spells out exactly the fact the index shows GENTLES or LOGAN for the > mother's name. > > Allan Raymond > > ----- Original Message ----- > From: Mike Parker > To: FreeBMD-Admins@rootsweb.com > Sent: Monday, March 12, 2012 7:30 PM > Subject: alternate names > > > Hi and i put after the comment(2) wife named as Smith or Jones.....or > mother named as brown or White... This seems to work ok. Is that not > simpler???cheers Mike Parker > > > > ---------- Forwarded message ---------- > From: "Evan Smith" <evanpsmith@bigpond.com> > To: <freebmd-admins@rootsweb.com> > Cc: > Date: Tue, 13 Mar 2012 13:08:27 +1000 > Subject: Re: alternate names > At # 6u you could be forgiven for thinking there is a space between > #COMMENT and (2) or #COMMENT and (3). (though there is clearly no space in > Allan's Tip of the Day.) > Further, some of the comment on this matter varies in that some use the > term "name" and others "surname". Also, when we refer to mother we follow > it with an 's but when we refer to spouse we don't. This may seem > nit-picking, but if uniformity is important enough to the system that we > are advised not to leave a space between #COMMENT and (2) - or (3) as the > case may be - may we have these points cleared up. > > Evan S. > > > > > ----- Original Message ----- From: "Allan Raymond" < > allan_raymond@btinternet.com> > To: <freebmd-admins@rootsweb.com> > Sent: Tuesday, March 13, 2012 6:28 AM > Subject: Re: alternate names > > > Nice to hear you are indicating in your transcriptions the entries have >> alternative names where appropriate. >> >> However it is far better if everyone for consistency adopted a standard >> approach to dealing with alternative names rather than inventing their own >> format >> >> Hence why we introduced the rule to transcribe alternative names in the >> standard format: many years ago. >> >> #COMMENT(2) entry reads <alternative> for <field> >> >> So an entry in scan http://images.freebmd.org.uk/** >> GUS/1961/Births/March/ANC-05/**G-O/1961B1-G-0015.jpg<http://images.freebmd.org.uk/GUS/1961/Births/March/ANC-05/G-O/1961B1-G-0015.jpg>such as >> >> GENTLES,Sheena K. E.,GENTLES or LOGAN,Lambeth,5c,2160 >> >> should be transcribed as: >> >> GENTLES,Sheena K. E.,GENTLES,Lambeth,5c,2160 >> #COMMENT(2) entry reads GENTLES or LOGAN for mother's name >> GENTLES,Sheena K. E.,LOGAN,Lambeth,5c,2160 >> >> This spells out exactly the fact the index shows GENTLES or LOGAN for the >> mother's name. >> >> Allan Raymond >> >> ----- Original Message ----- From: Mike Parker >> To: FreeBMD-Admins@rootsweb.com >> Sent: Monday, March 12, 2012 7:30 PM >> Subject: alternate names >> >> >> Hi and i put after the comment(2) wife named as Smith or Jones.....or >> mother named as brown or White... This seems to work ok. Is that not >> simpler???cheers Mike Parker >> FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/** >> th/index/freebmd-admins<http://archiver.rootsweb.com/th/index/freebmd-admins> >> >> FreeBMD http://www.freebmd.org.uk/ >> >> >> ------------------------------**- >> To unsubscribe from the list, please send an email to >> FREEBMD-ADMINS-request@**rootsweb.com<FREEBMD-ADMINS-request@rootsweb.com>with the word 'unsubscribe' without the quotes in the subject and the body >> of the message >> > > > > To contact the FREEBMD-ADMINS list administrator, send an email to > FREEBMD-ADMINS-admin@rootsweb.com. > > To post a message to the FREEBMD-ADMINS mailing list, send an email to > FREEBMD-ADMINS@rootsweb.com. > > __________________________________________________________ > To unsubscribe from the list, please send an email to > FREEBMD-ADMINS-request@rootsweb.com > with the word "unsubscribe" without the quotes in the subject and the body > of the > email with no additional text. > >
Nice to hear you are indicating in your transcriptions the entries have alternative names where appropriate. However it is far better if everyone for consistency adopted a standard approach to dealing with alternative names rather than inventing their own format Hence why we introduced the rule to transcribe alternative names in the standard format: many years ago. #COMMENT(2) entry reads <alternative> for <field> So an entry in scan http://images.freebmd.org.uk/GUS/1961/Births/March/ANC-05/G-O/1961B1-G-0015.jpg such as GENTLES,Sheena K. E.,GENTLES or LOGAN,Lambeth,5c,2160 should be transcribed as: GENTLES,Sheena K. E.,GENTLES,Lambeth,5c,2160 #COMMENT(2) entry reads GENTLES or LOGAN for mother's name GENTLES,Sheena K. E.,LOGAN,Lambeth,5c,2160 This spells out exactly the fact the index shows GENTLES or LOGAN for the mother's name. Allan Raymond ----- Original Message ----- From: Mike Parker To: FreeBMD-Admins@rootsweb.com Sent: Monday, March 12, 2012 7:30 PM Subject: alternate names Hi and i put after the comment(2) wife named as Smith or Jones.....or mother named as brown or White... This seems to work ok. Is that not simpler???cheers Mike Parker
Hi and i put after the comment(2) wife named as Smith or Jones.....or mother named as brown or White... This seems to work ok. Is that not simpler???cheers Mike Parker
I should perhaps have mentioned how to deal with your query in my Tip of the Day. You are almost correct in that it is #COMMENT(3) rather than +COMMENT(3) (i.e insert # not a + in front of the COMMENT) If you also visit the link I gave in my Tip of the Day i.e. http://freebmd.rootsweb.com/vol_faq.html#6u which mentions "If there are more than two names, enter one record for each and put in one comment covering all the names, e.g. #COMMENT(3) after the first of three entries" Allan Raymond From: Brian Foulger <brilyn1@btinternet.com> >To: freebmd-admins@rootsweb.com >Sent: Monday, 12 March 2012, 17:54 >Subject: Re: Tip of the Day (No. 6) (last updated 12 March 2012) - AlternativeSpouse Names in Marriage and Birth Records > >Hi, could you clarify what to do if a entry has 3 names,i.e. is +comment (3) ok. >Brian Foulger > > >--- On Mon, 12/3/12, Allan Raymond <allan_raymond@btinternet.com> wrote: > >> From: Allan Raymond <allan_raymond@btinternet.com> >> Subject: Tip of the Day (No. 6) (last updated 12 March 2012) - AlternativeSpouse Names in Marriage and Birth Records >> To: freebmd-admins@rootsweb.com >> Date: Monday, 12 March, 2012, 12:00 >> This is the sixth in a series of "Tip >> of the Day" to help volunteers who are transcribing for the >> FreeBMD Project. >> >> This Tip of the Day is being reissued with minor amendments >> for the benefit of our new volunteers plus existing >> volunteers who may have missed it when last issued. >> >> Further feedback is welcomed. >> >> The Transcribers' Knowledge Base at: >> http://freebmd.rootsweb.com/vol_faq.html#6u provides >> the definitive advice for dealing with alternative names in >> records. >> >> I've been carrying out ongoing checks of recent files >> uploaded by a number of transcribers to see how they dealt >> with records containing alternative names. In particular, >> where alternative spouse names are shown against a marriage >> entry the advice in http://freebmd.rootsweb.com/vol_faq.html#6u in a number >> of instances was not being followed >> >> The correct way to transcribe a marriage entry such as >> >> Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 >> >> using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is >> >> Dunn,Charles,Curphey,W.Derby,8b,697 >> #COMMENT(2) entry reads Curphey or Bradley for spouse name >> Dunn,Charles,Bradley,W.Derby,8b,697 >> >> Please note, the #COMMENT(2) line is located between >> the two entries under consideration. >> >> By a similar token the correct way to transcribe a birth >> entry such as >> >> Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 >> >> using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is >> >> Dunn,Charles,Curphey,W.Derby,8b,697 >> #COMMENT(2) entry reads Curphey or Bradley for mother`s name >> >> Dunn,Charles,Bradley,W.Derby,8b,697 >> >> Please note, the #COMMENT(2) line is located between >> the two entries under consideration. >> >> There should be no space between #COMMENT and (2) although >> to cater for the large number of previous instances of a >> space being inserted it is now allowed to include a space. >> >> For standardisation purposes there is no necessity to change >> the format of the wording after the #COMMENT(2) shown >> above and in http://freebmd.rootsweb.com/vol_faq.html#6u . >> >> The audit process checks for the alternative spouse name >> checks and the list of files identified as being suspect is >> listed in http://www.freebmd.org.uk/SuspectFiles.html . >> >> It would be appreciated if transcribers in conjunction with >> their Co-ordinators could check http://www.freebmd.org.uk/SuspectFiles.html to see if >> any of their files are listed and where appropriate correct >> the files by including the appropriate #COMMENT(2) line. A >> warning message will be shown against any suspect files when >> viewed in File Management. >> >> As an aside >> >> A misplaced #COMMENT(2) line can have the wrong outcome. >> >> In the example below an invalid #COMMENT(2) line in the file >> is placed after the two entries under consideration rather >> than between the two entries. >> >> Barbour,John H.,Stephenson,Skipton,9a,79 >> Barbour,John H.,Mitchell,Skipton,9a,79 >> #COMMENT(2) - above line has Stephenson or Mitchell as >> spouse of John H. Barbour >> >> The resultant effect from a search is to place a #COMMENT >> against one related entry and one unrelated entry as shown >> below: >> >> Barbour John H Mitchell Skipton 9a >> 79 >> (related #COMMENT - above line has >> Stephenson or Mitchell as spouse of John H. Barbour) >> Barcinski Philip H Newton Hampstead >> 1a 1513 (unrelated #COMMENT - above line has Stephenson or >> Mitchell as spouse of John H. Barbour) >> >> Allan Raymond >> FreeBMD Co-coordinator of Syndicates >> FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins >> >> FreeBMD http://www.freebmd.org.uk/ >> >> >> ------------------------------- >> To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com >> with the word 'unsubscribe' without the quotes in the >> subject and the body of the message >> > >FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins > >FreeBMD http://www.freebmd.org.uk/ > > >------------------------------- >To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message > > >
Put, after the first of the three lines, something along the lines of #COMMENT(3) Entry reads ALPHA or BETA or GAMMA for spouse surname This will then attach the comment to the one line above it and the two lines below it. Jeff ----- Original Message ----- From: "Brian Foulger" <brilyn1@btinternet.com> To: <freebmd-admins@rootsweb.com> Sent: Monday, March 12, 2012 5:54 PM Subject: Re: Tip of the Day (No. 6) (last updated 12 March 2012) -AlternativeSpouse Names in Marriage and Birth Records Hi, could you clarify what to do if a entry has 3 names,i.e. is +comment (3) ok. Brian Foulger --- On Mon, 12/3/12, Allan Raymond <allan_raymond@btinternet.com> wrote: > From: Allan Raymond <allan_raymond@btinternet.com> > Subject: Tip of the Day (No. 6) (last updated 12 March 2012) - > AlternativeSpouse Names in Marriage and Birth Records > To: freebmd-admins@rootsweb.com > Date: Monday, 12 March, 2012, 12:00 > This is the sixth in a series of "Tip > of the Day" to help volunteers who are transcribing for the > FreeBMD Project. > > This Tip of the Day is being reissued with minor amendments > for the benefit of our new volunteers plus existing > volunteers who may have missed it when last issued. > > Further feedback is welcomed. > > The Transcribers' Knowledge Base at: > http://freebmd.rootsweb.com/vol_faq.html#6u provides > the definitive advice for dealing with alternative names in > records. > > I've been carrying out ongoing checks of recent files > uploaded by a number of transcribers to see how they dealt > with records containing alternative names. In particular, > where alternative spouse names are shown against a marriage > entry the advice in http://freebmd.rootsweb.com/vol_faq.html#6u in a > number > of instances was not being followed > > The correct way to transcribe a marriage entry such as > > Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 > > using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is > > Dunn,Charles,Curphey,W.Derby,8b,697 > #COMMENT(2) entry reads Curphey or Bradley for spouse name > Dunn,Charles,Bradley,W.Derby,8b,697 > > Please note, the #COMMENT(2) line is located between > the two entries under consideration. > > By a similar token the correct way to transcribe a birth > entry such as > > Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 > > using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is > > Dunn,Charles,Curphey,W.Derby,8b,697 > #COMMENT(2) entry reads Curphey or Bradley for mother`s name > > Dunn,Charles,Bradley,W.Derby,8b,697 > > Please note, the #COMMENT(2) line is located between > the two entries under consideration. > > There should be no space between #COMMENT and (2) although > to cater for the large number of previous instances of a > space being inserted it is now allowed to include a space. > > For standardisation purposes there is no necessity to change > the format of the wording after the #COMMENT(2) shown > above and in http://freebmd.rootsweb.com/vol_faq.html#6u . > > The audit process checks for the alternative spouse name > checks and the list of files identified as being suspect is > listed in http://www.freebmd.org.uk/SuspectFiles.html . > > It would be appreciated if transcribers in conjunction with > their Co-ordinators could check > http://www.freebmd.org.uk/SuspectFiles.html to see if > any of their files are listed and where appropriate correct > the files by including the appropriate #COMMENT(2) line. A > warning message will be shown against any suspect files when > viewed in File Management. > > As an aside > > A misplaced #COMMENT(2) line can have the wrong outcome. > > In the example below an invalid #COMMENT(2) line in the file > is placed after the two entries under consideration rather > than between the two entries. > > Barbour,John H.,Stephenson,Skipton,9a,79 > Barbour,John H.,Mitchell,Skipton,9a,79 > #COMMENT(2) - above line has Stephenson or Mitchell as > spouse of John H. Barbour > > The resultant effect from a search is to place a #COMMENT > against one related entry and one unrelated entry as shown > below: > > Barbour John H Mitchell Skipton 9a > 79 > (related #COMMENT - above line has > Stephenson or Mitchell as spouse of John H. Barbour) > Barcinski Philip H Newton Hampstead > 1a 1513 (unrelated #COMMENT - above line has Stephenson or > Mitchell as spouse of John H. Barbour) > > Allan Raymond > FreeBMD Co-coordinator of Syndicates > FreeBMD-Admins mailing list - archive > http://archiver.rootsweb.com/th/index/freebmd-admins > > FreeBMD http://www.freebmd.org.uk/ > > > ------------------------------- > To unsubscribe from the list, please send an email to > FREEBMD-ADMINS-request@rootsweb.com > with the word 'unsubscribe' without the quotes in the > subject and the body of the message > FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins FreeBMD http://www.freebmd.org.uk/ ------------------------------- To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message
Hi, could you clarify what to do if a entry has 3 names,i.e. is +comment (3) ok. Brian Foulger --- On Mon, 12/3/12, Allan Raymond <allan_raymond@btinternet.com> wrote: > From: Allan Raymond <allan_raymond@btinternet.com> > Subject: Tip of the Day (No. 6) (last updated 12 March 2012) - AlternativeSpouse Names in Marriage and Birth Records > To: freebmd-admins@rootsweb.com > Date: Monday, 12 March, 2012, 12:00 > This is the sixth in a series of "Tip > of the Day" to help volunteers who are transcribing for the > FreeBMD Project. > > This Tip of the Day is being reissued with minor amendments > for the benefit of our new volunteers plus existing > volunteers who may have missed it when last issued. > > Further feedback is welcomed. > > The Transcribers' Knowledge Base at: > http://freebmd.rootsweb.com/vol_faq.html#6u provides > the definitive advice for dealing with alternative names in > records. > > I've been carrying out ongoing checks of recent files > uploaded by a number of transcribers to see how they dealt > with records containing alternative names. In particular, > where alternative spouse names are shown against a marriage > entry the advice in http://freebmd.rootsweb.com/vol_faq.html#6u in a number > of instances was not being followed > > The correct way to transcribe a marriage entry such as > > Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 > > using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is > > Dunn,Charles,Curphey,W.Derby,8b,697 > #COMMENT(2) entry reads Curphey or Bradley for spouse name > Dunn,Charles,Bradley,W.Derby,8b,697 > > Please note, the #COMMENT(2) line is located between > the two entries under consideration. > > By a similar token the correct way to transcribe a birth > entry such as > > Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 > > using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is > > Dunn,Charles,Curphey,W.Derby,8b,697 > #COMMENT(2) entry reads Curphey or Bradley for mother`s name > > Dunn,Charles,Bradley,W.Derby,8b,697 > > Please note, the #COMMENT(2) line is located between > the two entries under consideration. > > There should be no space between #COMMENT and (2) although > to cater for the large number of previous instances of a > space being inserted it is now allowed to include a space. > > For standardisation purposes there is no necessity to change > the format of the wording after the #COMMENT(2) shown > above and in http://freebmd.rootsweb.com/vol_faq.html#6u . > > The audit process checks for the alternative spouse name > checks and the list of files identified as being suspect is > listed in http://www.freebmd.org.uk/SuspectFiles.html . > > It would be appreciated if transcribers in conjunction with > their Co-ordinators could check http://www.freebmd.org.uk/SuspectFiles.html to see if > any of their files are listed and where appropriate correct > the files by including the appropriate #COMMENT(2) line. A > warning message will be shown against any suspect files when > viewed in File Management. > > As an aside > > A misplaced #COMMENT(2) line can have the wrong outcome. > > In the example below an invalid #COMMENT(2) line in the file > is placed after the two entries under consideration rather > than between the two entries. > > Barbour,John H.,Stephenson,Skipton,9a,79 > Barbour,John H.,Mitchell,Skipton,9a,79 > #COMMENT(2) - above line has Stephenson or Mitchell as > spouse of John H. Barbour > > The resultant effect from a search is to place a #COMMENT > against one related entry and one unrelated entry as shown > below: > > Barbour John H Mitchell Skipton 9a > 79 > (related #COMMENT - above line has > Stephenson or Mitchell as spouse of John H. Barbour) > Barcinski Philip H Newton Hampstead > 1a 1513 (unrelated #COMMENT - above line has Stephenson or > Mitchell as spouse of John H. Barbour) > > Allan Raymond > FreeBMD Co-coordinator of Syndicates > FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins > > FreeBMD http://www.freebmd.org.uk/ > > > ------------------------------- > To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com > with the word 'unsubscribe' without the quotes in the > subject and the body of the message >
I wonder whether it would be possible to identify files where a transcriber has simply put #COMMENT instead of #COMMENT(2) in an alternative surname situation as described. I have found this in some cases. Also, is it possible to identify files where a transcriber has put a space between # and COMMENT ? Jeff ----- Original Message ----- From: "Allan Raymond" <allan_raymond@btinternet.com> To: <freebmd-admins@rootsweb.com> Sent: Monday, March 12, 2012 12:00 PM Subject: Tip of the Day (No. 6) (last updated 12 March 2012) -AlternativeSpouse Names in Marriage and Birth Records > This is the sixth in a series of "Tip of the Day" to help volunteers who > are transcribing for the FreeBMD Project. > > This Tip of the Day is being reissued with minor amendments for the > benefit of our new volunteers plus existing volunteers who may have missed > it when last issued. > > Further feedback is welcomed. > > The Transcribers' Knowledge Base at: > http://freebmd.rootsweb.com/vol_faq.html#6u provides the definitive advice > for dealing with alternative names in records. > > I've been carrying out ongoing checks of recent files uploaded by a number > of transcribers to see how they dealt with records containing alternative > names. In particular, where alternative spouse names are shown against a > marriage entry the advice in http://freebmd.rootsweb.com/vol_faq.html#6u > in a number of instances was not being followed > > The correct way to transcribe a marriage entry such as > > Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 > > using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is > > Dunn,Charles,Curphey,W.Derby,8b,697 > #COMMENT(2) entry reads Curphey or Bradley for spouse name > Dunn,Charles,Bradley,W.Derby,8b,697 > > Please note, the #COMMENT(2) line is located between the two entries > under consideration. > > By a similar token the correct way to transcribe a birth entry such as > > Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 > > using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is > > Dunn,Charles,Curphey,W.Derby,8b,697 > #COMMENT(2) entry reads Curphey or Bradley for mother`s name > Dunn,Charles,Bradley,W.Derby,8b,697 > > Please note, the #COMMENT(2) line is located between the two entries > under consideration. > > There should be no space between #COMMENT and (2) although to cater for > the large number of previous instances of a space being inserted it is now > allowed to include a space. > > For standardisation purposes there is no necessity to change the format of > the wording after the #COMMENT(2) shown above and in > http://freebmd.rootsweb.com/vol_faq.html#6u . > > The audit process checks for the alternative spouse name checks and the > list of files identified as being suspect is listed in > http://www.freebmd.org.uk/SuspectFiles.html . > > It would be appreciated if transcribers in conjunction with their > Co-ordinators could check http://www.freebmd.org.uk/SuspectFiles.html to > see if any of their files are listed and where appropriate correct the > files by including the appropriate #COMMENT(2) line. A warning message > will be shown against any suspect files when viewed in File Management. > > As an aside > > A misplaced #COMMENT(2) line can have the wrong outcome. > > In the example below an invalid #COMMENT(2) line in the file is placed > after the two entries under consideration rather than between the two > entries. > > Barbour,John H.,Stephenson,Skipton,9a,79 > Barbour,John H.,Mitchell,Skipton,9a,79 > #COMMENT(2) - above line has Stephenson or Mitchell as spouse of John H. > Barbour > > The resultant effect from a search is to place a #COMMENT against one > related entry and one unrelated entry as shown below: > > Barbour John H Mitchell Skipton 9a 79 (related #COMMENT - > above line has Stephenson or Mitchell as spouse of John H. Barbour) > Barcinski Philip H Newton Hampstead 1a 1513 (unrelated #COMMENT - > above line has Stephenson or Mitchell as spouse of John H. Barbour) > > Allan Raymond > FreeBMD Co-coordinator of Syndicates
This is the sixth in a series of "Tip of the Day" to help volunteers who are transcribing for the FreeBMD Project. This Tip of the Day is being reissued with minor amendments for the benefit of our new volunteers plus existing volunteers who may have missed it when last issued. Further feedback is welcomed. The Transcribers' Knowledge Base at: http://freebmd.rootsweb.com/vol_faq.html#6u provides the definitive advice for dealing with alternative names in records. I've been carrying out ongoing checks of recent files uploaded by a number of transcribers to see how they dealt with records containing alternative names. In particular, where alternative spouse names are shown against a marriage entry the advice in http://freebmd.rootsweb.com/vol_faq.html#6u in a number of instances was not being followed The correct way to transcribe a marriage entry such as Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is Dunn,Charles,Curphey,W.Derby,8b,697 #COMMENT(2) entry reads Curphey or Bradley for spouse name Dunn,Charles,Bradley,W.Derby,8b,697 Please note, the #COMMENT(2) line is located between the two entries under consideration. By a similar token the correct way to transcribe a birth entry such as Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is Dunn,Charles,Curphey,W.Derby,8b,697 #COMMENT(2) entry reads Curphey or Bradley for mother`s name Dunn,Charles,Bradley,W.Derby,8b,697 Please note, the #COMMENT(2) line is located between the two entries under consideration. There should be no space between #COMMENT and (2) although to cater for the large number of previous instances of a space being inserted it is now allowed to include a space. For standardisation purposes there is no necessity to change the format of the wording after the #COMMENT(2) shown above and in http://freebmd.rootsweb.com/vol_faq.html#6u . The audit process checks for the alternative spouse name checks and the list of files identified as being suspect is listed in http://www.freebmd.org.uk/SuspectFiles.html . It would be appreciated if transcribers in conjunction with their Co-ordinators could check http://www.freebmd.org.uk/SuspectFiles.html to see if any of their files are listed and where appropriate correct the files by including the appropriate #COMMENT(2) line. A warning message will be shown against any suspect files when viewed in File Management. As an aside A misplaced #COMMENT(2) line can have the wrong outcome. In the example below an invalid #COMMENT(2) line in the file is placed after the two entries under consideration rather than between the two entries. Barbour,John H.,Stephenson,Skipton,9a,79 Barbour,John H.,Mitchell,Skipton,9a,79 #COMMENT(2) - above line has Stephenson or Mitchell as spouse of John H. Barbour The resultant effect from a search is to place a #COMMENT against one related entry and one unrelated entry as shown below: Barbour John H Mitchell Skipton 9a 79 (related #COMMENT - above line has Stephenson or Mitchell as spouse of John H. Barbour) Barcinski Philip H Newton Hampstead 1a 1513 (unrelated #COMMENT - above line has Stephenson or Mitchell as spouse of John H. Barbour) Allan Raymond FreeBMD Co-coordinator of Syndicates
Same here. Dennis Hawkins -----Original Message----- From: Malisemcg@aol.com Sent: Sunday, March 11, 2012 9:07 AM To: freebmd-admins@rootsweb.com Subject: FreeBMD-Admins: Re Closing file Wouldn't upload yesterday and had the closing problem so decided to leave it until this morning. All my files have uploaded successfully and I was able to close them at this end. So whatever it was seems to have gone. M McGuire FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins FreeBMD http://www.freebmd.org.uk/ ------------------------------- To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message
I had a similar problem yesterday. When I sent my file the 'sending message' went on forever - I came back to it after doing something else and it was still sending. I closed all BMD windows and tried to open WinBMD again but it said it was still open. Control Alt Delete didn't show it as an open file. I shut down the computer and when I came back to it later in the evening all seemed to be working as normal. I assume, therefore, that there must have been a blip a the BMD server as today's page went within seconds as usual.Sue Blee From: freebmd-admins-request@rootsweb.com Subject: FREEBMD-ADMINS Digest, Vol 7, Issue 12 To: freebmd-admins@rootsweb.com Date: Sun, 11 Mar 2012 01:01:06 -0700 --Forwarded Message Attachment-- From: dennis.hawkins138@btinternet.com To: freebmd-admins@rootsweb.com Date: Sat, 10 Mar 2012 21:50:02 +0000 Subject: Closing file Something funny has happened to my WinBMD. I can’t exit from it. I’ve tried shutting down the computer to no avail. I can open Win BMD but can’t shut it. Dennis Hawkins --Forwarded Message Attachment-- From: waite.robert@ntlworld.com To: freebmd-admins@rootsweb.com Date: Sat, 10 Mar 2012 22:26:18 +0000 Subject: Re: Closing file ----- Original Message ----- From: "Dennis Hawkins" <dennis.hawkins138@btinternet.com> To: <freebmd-admins@rootsweb.com> Sent: Saturday, March 10, 2012 9:50 PM Subject: Closing file > Something funny has happened to my WinBMD. I can’t exit from it. I’ve > tried shutting down the computer to no avail. I can open Win BMD but can’t > shut it. > Dennis Hawkins > FreeBMD-Admins mailing list - archive > http://archiver.rootsweb.com/th/index/freebmd-admins > > FreeBMD http://www.freebmd.org.uk/ > > > ------------------------------- > To unsubscribe from the list, please send an email to > FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without > the quotes in the subject and the body of the message > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.1913 / Virus Database: 2114/4862 - Release Date: 03/10/12 > Try uninstalling WinBMD and then reboot before re-installing. Bob --Forwarded Message Attachment-- From: Jeff.Coleman@ntlworld.com To: freebmd-admins@rootsweb.com; dennis.hawkins138@btinternet.com Date: Sat, 10 Mar 2012 22:46:15 +0000 Subject: Re: Closing file may be connected to upload problem Did this happen when attempting to send a file to FreeBMD? There may be something temporarily wrong with the web site meaning that uploads are not working properly. One of my syndicate has reported this problem, and looking at the upload report it appears that no-one has managed to submit a file in my syndicate for the last 8 hours or so. (about 14.20 today as shown on Show File) Have you tried these options? 1) In the 'File' menu of WinBMD choose 'Save batch and Exit' 2) using f3 key to save your work then using the little x at upper right of the transcribing grid window to close down 3) selecting the WinBMD icon in the tray at the foot of the screen, right mouse-clicking and 'Close' 4) Holding down CTRL-ALT-DEL keys together, then 'Start Task Manager', select WinBMD in the 'Applications' tab and 'End task'. In the 'WinBMD' folder there should be a small file called uploadlog.txt which is created every time you try to send a file to FreeBMD. You can open this in Notepad or a similar program. The last line should be along the lines of Upload OK - 1948B1A0001 uploaded successfully - or whatever your last file was called If the last line is not of this type then something went wrong during the upload. I can't see why this should make it impossible to close WinBMD at all, but someone else may be able to explain. Jeff ----- Original Message ----- From: "Dennis Hawkins" <dennis.hawkins138@btinternet.com> To: <freebmd-admins@rootsweb.com> Sent: Saturday, March 10, 2012 9:50 PM Subject: Closing file > Something funny has happened to my WinBMD. I can’t exit from it. I’ve > tried shutting down the computer to no avail. I can open Win BMD but can’t > shut it. > Dennis Hawkins > FreeBMD-Admins mailing list - archive > http://archiver.rootsweb.com/th/index/freebmd-admins > > FreeBMD http://www.freebmd.org.uk/ > > > ------------------------------- > To unsubscribe from the list, please send an email to > FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without > the quotes in the subject and the body of the message
I had this problem when trying to save to a media card that had accidentally been locked and not been noticed. It also made it impossible to close files or anything else in Win BMD. It could therefore be associated with a file that has been set to "read only" or some such. Hope this helps. Regards, Dave Geer. (The NWL Syndicate) -----Original Message----- From: guhwuh@rhuddlan.plus.com Sent: Sunday, March 11, 2012 8:58 AM To: freebmd-admins@rootsweb.com Subject: Re: Closing file Just for clarification, when you note that you've tried shutting down the computer, do you mean that you've gone as far as switching the power off at the wall socket, or instigating a reboot within the oprating system? Network cards have a nasty habit of retaining their settings during a reboot. Powering down the computer should be sufficient, switching off power at the wall socket should* be a clincher. * I add this caveat... VOIP phones don't necessarily have power blocks (well, not the ones I use), they draw sufficent power from the network. To discount this effect it might also be worthwhile removing the computer's network cable too; not forgetting to reseat it before powering up again. I tested a force close on WinBMD - not something I like doing on any application. WinBMD does not appear to load dependent modules when it's run, though my test wasn't an exhaustive one. When restaring the program one is faced with a notification... "Error Recovery - WinBMD is reloading the last batch" Forcing close didn't appear to introduce further corruption - the file was as I expected it to be; though I wasn't recovering from an unstable position in the first place. I am unable to check upload connection issues at present as I'm not close to completing a file (insert embarrassed emoticon here) Hope this helps, Grev. > Something funny has happened to my WinBMD. I can’t exit from it. I’ve > tried shutting down the computer to no avail. I can open Win BMD but > can’t shut it. > Dennis Hawkins > FreeBMD-Admins mailing list - archive > http://archiver.rootsweb.com/th/index/freebmd-admins > > FreeBMD http://www.freebmd.org.uk/ > > > ------------------------------- > To unsubscribe from the list, please send an email to > FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without > the quotes in the subject and the body of the message FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins FreeBMD http://www.freebmd.org.uk/ ------------------------------- To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2114/4864 - Release Date: 03/11/12