[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
paf-digest V2000 #2
paf-digest Tuesday, January 11 2000 Volume 2000 : Number 002
In this issue:
[PAF] my y2k glitch (g)
Re: [PAF] my y2k glitch (g)
[PAF] Y2K compliance and backup sytem
Re: [PAF] my y2k glitch (g)
Re: [PAF] Y2K compliance and backup sytem
[PAF] Primary records, BAH!
Re: [PAF] Primary records, BAH!
Re: [PAF] Primary records, BAH!
See the end of the digest for information on subscribing to the PAF
or PAF-Digest mailing lists and on how to retrieve back issues.
----------------------------------------------------------------------
Date: Sun, 2 Jan 1972 21:09:38 -0500 (EST)
From: Cheryl Singhal <csinghal@CapAccess.org>
Subject: [PAF] my y2k glitch (g)
OK, here's the scenario, as Noah used to tell Robert Wagner -- our
desktops and laptops were checked out, and all rolled over on demand. So,
New Year's Eve, two of them were on at midnight, and sure'nuff they
rolled over without a whimper. We turned them off a little after 1 am
the 1st and the sysclocks were right with the wall-clock.
Come 10 am the 1st, and we rebooted one and I ran a DOS-based app, which
reset its internal date to 31 Dec 1999 (I have _NO_ clue how it did
that!). As soon as I realized it, I terminated and checked the sysclock;
it said 1992. I booted the other computers, and each had reverted to its
personal default date. (Sigh) Note for the curious: no, none of them
said 1962. (g)
Sooooo, we reset the sysclock by DOS and again by WIN, and they have
been ticking along nicely ever since (well, except for the laptop whose
clock battery is terminally ill).
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@innernet.org or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 02 Jan 2000 19:41:10 -0700
From: Shanna Jones <sjones@redrock.net>
Subject: Re: [PAF] my y2k glitch (g)
Hi Cheryl,
You still have a glitch, as this e-mail came through as though you had written
it on January 2, 1972!
Shanna
Cheryl Singhal wrote:
> OK, here's the scenario, as Noah used to tell Robert Wagner -- our
> desktops and laptops were checked out, and all rolled over on demand. So,
> New Year's Eve, two of them were on at midnight, and sure'nuff they
> rolled over without a whimper. We turned them off a little after 1 am
> the 1st and the sysclocks were right with the wall-clock.
>
> Come 10 am the 1st, and we rebooted one and I ran a DOS-based app, which
> reset its internal date to 31 Dec 1999 (I have _NO_ clue how it did
> that!). As soon as I realized it, I terminated and checked the sysclock;
> it said 1992. I booted the other computers, and each had reverted to its
> personal default date. (Sigh) Note for the curious: no, none of them
> said 1962. (g)
>
> Sooooo, we reset the sysclock by DOS and again by WIN, and they have
> been ticking along nicely ever since (well, except for the laptop whose
> clock battery is terminally ill).
>
> ============================================================================
> For assistance and help for the PAF Mailing List please contact
> ed.rogers@innernet.org or http://www.innernet.org/paf/
> ============================================================================
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@innernet.org or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Sun, 02 Jan 2000 21:34:38 -0700
From: Peter Van Schaik <peter.van.schaik@T8000.com>
Subject: [PAF] Y2K compliance and backup sytem
To: All
Subject: y2k backup system
While we believe we will be fully Y2K compliant by January 1, 2000,
and most of our subsidiary units and contractors claim they will also
be fully compliant, we obviously need to make some preparations in
case unexpected challenges impair our ability to meet the needs of our
customers.
Enclosed with this memo is a "Y2K Backup System" device designed to
meet short time emergency needs in case of a computer operations
failure, or operational delay. This device is the company's Primary
Emergency Network Computer Interface Liaison device (P.E.N.C.I.L.).
This device has been field tested extensively, including certification
testing, as well as volume and stress testing. Properly maintained,
the device meets all the requirements for coding and data input.
Prior to use, the (P.E.N.C.I.L.) will require preparation and testing.
Tools and supplies required will be: A sharpened knife or grinding
device; and a supply of computer paper (with or without holes).
Gripping the device firmly in your hand, proceed to scrape or grind
the wooded end until it has a cone-like appearance. The dark core
area must be exposed to properly function. (Left-handed employees
should read this sentence backwards, and then go to your supervisor
for assistance.)
Place a single sheet of computer paper on a smooth, hard surface. Take
the backup device, place the sharpened point against the paper, and
pull it across the paper. If properly done, this will input a single
line.
CAUTION: Excessive force may damage components of the device or
damage the data reception device. If either the P.E.N.C.I.L. or
the paper are damaged, go back to the preparation instructions above.
Proper use of the device will require data simulation input by the
operator. Placing the device against the computer page forming symbols
as closely resembling the computer lettering system you normally use.
At the completion of each of the simulated letters, lift the device
off the page, move it slightly to the right, replace it against the
page, and form the next symbol. This may appear tedious, and somewhat
redundant, but, with practice, you should be able to increase your
speed and accuracy. The P.E.N.C.I.L. is equipped with a manual
deletion device. The device is located on the reverse end of the
P.E.N.C.I.L. Error deletions operate similarly to the "backspace" key
on your computer. Simply place the device against the erroneous data,
and pull it backwards over the letters. This should remove the error,
and enable you to resume data entries.
CAUTION: Excessive force may damage the data reception device.
Insufficient force, however, may result in less than acceptable
deletion, and may require re-initialization of action as above.
This device is designed with user maintenance in mind. However, if
technical support is required, you can still call your local computer
desk supervisor at (800)-YOU-DUMMY.
Happy New year .......may all your resolutions become reality!!!!!
Groetjes.............Peter!!!!
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@innernet.org or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Mon, 3 Jan 2000 01:44:36 EST
From: Mlharline@aol.com
Subject: Re: [PAF] my y2k glitch (g)
In a message dated 01/02/2000 6:43:04 PM Pacific Standard Time,
sjones@redrock.net writes:
> Hi Cheryl,
> You still have a glitch, as this e-mail came through as though you had
> written
> it on January 2, 1972!
> Shanna
My e-mail came through with the time 01/02/2000. Which end of the message
sets the time? Does that depend on the ISP?
Mary Lou on AOL.
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@innernet.org or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Mon, 03 Jan 2000 22:16:19 -0500
From: nalla <alljohn@northnet.org>
Subject: Re: [PAF] Y2K compliance and backup sytem
Pete:
That was the best Y2K story I heard. I am still laughing.
Peter Van Schaik wrote:
> To: All
> Subject: y2k backup system
>
> While we believe we will be fully Y2K compliant by January 1, 2000,
> and most of our subsidiary units and contractors claim they will also
> be fully compliant, we obviously need to make some preparations in
> case unexpected challenges impair our ability to meet the needs of our
> customers.
>
> Enclosed with this memo is a "Y2K Backup System" device designed to
> meet short time emergency needs in case of a computer operations
> failure, or operational delay. This device is the company's Primary
> Emergency Network Computer Interface Liaison device (P.E.N.C.I.L.).
> This device has been field tested extensively, including certification
> testing, as well as volume and stress testing. Properly maintained,
> the device meets all the requirements for coding and data input.
> Prior to use, the (P.E.N.C.I.L.) will require preparation and testing.
> Tools and supplies required will be: A sharpened knife or grinding
> device; and a supply of computer paper (with or without holes).
>
> Gripping the device firmly in your hand, proceed to scrape or grind
> the wooded end until it has a cone-like appearance. The dark core
> area must be exposed to properly function. (Left-handed employees
> should read this sentence backwards, and then go to your supervisor
> for assistance.)
>
> Place a single sheet of computer paper on a smooth, hard surface. Take
> the backup device, place the sharpened point against the paper, and
> pull it across the paper. If properly done, this will input a single
> line.
>
> CAUTION: Excessive force may damage components of the device or
> damage the data reception device. If either the P.E.N.C.I.L. or
> the paper are damaged, go back to the preparation instructions above.
>
> Proper use of the device will require data simulation input by the
> operator. Placing the device against the computer page forming symbols
> as closely resembling the computer lettering system you normally use.
> At the completion of each of the simulated letters, lift the device
> off the page, move it slightly to the right, replace it against the
> page, and form the next symbol. This may appear tedious, and somewhat
> redundant, but, with practice, you should be able to increase your
> speed and accuracy. The P.E.N.C.I.L. is equipped with a manual
> deletion device. The device is located on the reverse end of the
> P.E.N.C.I.L. Error deletions operate similarly to the "backspace" key
> on your computer. Simply place the device against the erroneous data,
> and pull it backwards over the letters. This should remove the error,
> and enable you to resume data entries.
>
> CAUTION: Excessive force may damage the data reception device.
> Insufficient force, however, may result in less than acceptable
> deletion, and may require re-initialization of action as above.
> This device is designed with user maintenance in mind. However, if
> technical support is required, you can still call your local computer
> desk supervisor at (800)-YOU-DUMMY.
>
> Happy New year .......may all your resolutions become reality!!!!!
> Groetjes.............Peter!!!!
> ============================================================================
> For assistance and help for the PAF Mailing List please contact
> ed.rogers@innernet.org or http://www.innernet.org/paf/
> ============================================================================
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@innernet.org or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Tue, 4 Jan 1972 15:45:38 -0500 (EST)
From: Cheryl Singhal <csinghal@CapAccess.org>
Subject: [PAF] Primary records, BAH!
OK, so what do I do with this mess!
1880 census lists a man, his wife, and a son.
County records show wife died in childbed in January 1880; couple
married in 1876; couple had a daughter in 1872 and another in '74. (These
records are NOT extracts or typescripts, but the real McCoy.)
1900 census shows the man and the son.
Before you think of it -- surname is highly unusual; given names are not
common in the area and the wife is particularly identifiable. County in
question is small and I've got the records on everyone of that surname.
And, for the so-inclined, both families are "respectable".
Any other suggestions what's going on with these records???
Cheryl
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@innernet.org or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Tue, 4 Jan 2000 17:34:08 -0500
From: "Kenneth Lary-Jr" <klary-jr@hannaford.com>
Subject: Re: [PAF] Primary records, BAH!
This is pure speculation, but here goes:
1. Whoever provided the 1880 census info included the wife even though she was
dead, perhaps because she had been alive during the year.
2. The son was the child that was born when she passed away.
3. The 1880 census does not show the daughters because with no mother to raise
them, the father sent them to live with relatives (female relatives with a
different surname.)
4. The 1900 census does not show the daughters either for the same reason, or
because they have gotten married and left home.
5. Finally, the daughters were simply born before the marriage took place.
Frankly, it is not that rare. Common law marriages were a fact of life, even
among "respectable" people.
Having said all of this, my opinion is that some, or all, of the records are
simply wrong and that without new evidence you will not be able to determine
which ones are wrong. I tend to rank census records below birth and marriage
records in terms of reliability, but who knows in this case.
I once found birth records for four consecutive children born in the 1930's.
All four records gave different information for the father's birth location.
And I'm not talking about four different names for the same town; I'm talking
about four widely scattered areas of the state. The only conclusion I could
come to is that whoever was providing the information was deliberately lying for
whatever reason. I never was able to determine his place of birth.
I have had many other instances where multiple primary records (typewritten and
very legible) have totally different information on them. As a result I have
downgraded my opinion of "primary" records. I still rate them higher than
secondary records, of course, but I do not necessarily assume that when a
primary record and a secondary record disagree that it is the primary that is
correct. The same recording errors creep into primary records, just as in
published genealogies: someone is providing the information (oftentimes
verbally) and someone else is transcribing it onto the record. Errors happen.
I once found a marriage where the wife's name was listed as Waneta. This was a
clerk's attempt to record a name he had never heard before (Juanita.) Do I have
any proof that the wife's name was actually Juanita? No. Did I enter it that
way into my database? Yes (with the note that the primary record had it as
Waneta.)
Good Luck,
Chip Lary
Cheryl Singhal <csinghal@CapAccess.org> on 01/04/72 03:45:38 PM
Please respond to paf@innernet.org
To: paf-list <paf@innernet.org>
cc: (bcc: Kenneth Lary-Jr/Info Tech/Corp/HBC)
Subject: [PAF] Primary records, BAH!
OK, so what do I do with this mess!
1880 census lists a man, his wife, and a son.
County records show wife died in childbed in January 1880; couple
married in 1876; couple had a daughter in 1872 and another in '74. (These
records are NOT extracts or typescripts, but the real McCoy.)
1900 census shows the man and the son.
Before you think of it -- surname is highly unusual; given names are not
common in the area and the wife is particularly identifiable. County in
question is small and I've got the records on everyone of that surname.
And, for the so-inclined, both families are "respectable".
Any other suggestions what's going on with these records???
Cheryl
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@innernet.org or http://www.innernet.org/paf/
============================================================================
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@innernet.org or http://www.innernet.org/paf/
============================================================================
------------------------------
Date: Tue, 04 Jan 2000 17:50:32 -0800
From: Rob & Heather Williams <will7370@tao.sou.edu>
Subject: Re: [PAF] Primary records, BAH!
Instructions for 1880 census enumerators told them to include a person in the
family count if they died within the first six months of the year (Jan-June).
If they died in the last six months (July-Dec), they were not to include them.
See the pamphlet "Twenty Censuses" published by the US Census Bureau in 1980.
Rob
Cheryl Singhal wrote:
> OK, so what do I do with this mess!
>
> 1880 census lists a man, his wife, and a son.
>
> County records show wife died in childbed in January 1880; couple
> married in 1876; couple had a daughter in 1872 and another in '74. (These
> records are NOT extracts or typescripts, but the real McCoy.)
>
> 1900 census shows the man and the son.
>
> Before you think of it -- surname is highly unusual; given names are not
> common in the area and the wife is particularly identifiable. County in
> question is small and I've got the records on everyone of that surname.
> And, for the so-inclined, both families are "respectable".
>
> Any other suggestions what's going on with these records???
>
> Cheryl
>
> ============================================================================
> For assistance and help for the PAF Mailing List please contact
> ed.rogers@innernet.org or http://www.innernet.org/paf/
> ============================================================================
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@innernet.org or http://www.innernet.org/paf/
============================================================================
------------------------------
End of paf-digest V2000 #2
**************************
To unsubscribe to PAF-Digest, send the following command to
majordomo@innernet.org:
unsubscribe paf-digest
At this point there is no direct method to receive back issues other than
to email ed.rogers@innernet.org. Happy PAF'ing!