From roots-in@roots-l.rootsweb.com Sat Feb 18 10:50:59 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k1IHoxjb026305;
	Sat, 18 Feb 2006 10:50:59 -0700
Received: from roots-l.rootsweb.com (roots-l.rootsweb.com [66.43.16.22])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k1IHoxpS025606
	for <roots-approved@rootsweb.com>; Sat, 18 Feb 2006 10:50:59 -0700
Received: from roots-l.rootsweb.com (roots-l [127.0.0.1])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k1IFLtFI005427
	for <roots-approved@rootsweb.com>; Sat, 18 Feb 2006 10:21:55 -0500
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k1IFLtfY005426
	for roots-approved@rootsweb.com; Sat, 18 Feb 2006 10:21:55 -0500
Received: from lists5.rootsweb.com (lists5.rootsweb.com [66.43.27.41])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with SMTP id k1IF8AFI005345
	for <roots-in@roots-l.rootsweb.com>; Sat, 18 Feb 2006 10:08:10 -0500
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k1IHb38F018220
	for roots-in@roots-l.rootsweb.com; Sat, 18 Feb 2006 10:37:03 -0700
X-Envelope-From: pjstef@yahoo.com Sat Feb 18 10:37:03 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k1IHb3jb018211
	for <ROOTS-L@lists5.rootsweb.com>; Sat, 18 Feb 2006 10:37:03 -0700
Received: from web34507.mail.mud.yahoo.com (web34507.mail.mud.yahoo.com [66.163.178.173])
	by mail.rootsweb.com (8.13.4/8.13.4) with SMTP id k1IHaxTq018864
	for <ROOTS-L@rootsweb.com>; Sat, 18 Feb 2006 10:37:00 -0700
Received: (qmail 74243 invoked by uid 60001); 18 Feb 2006 17:36:56 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=3xIK/lUr64FWHCgaGe5ad3aG/XP9/m7ltAko9C3JiVEXwdJQKQZGSmj1rBVmDrtP6EHLJ7nSCR56aDqBU+47KjDYUS96rsoC5Cme6MtTUfX+So75bILX3Ld069FyfeCpRe9k6Z2TaengpE1E2ZUFuJSa8h3G9oeKv6hUDoq58AM=  ;
Message-ID: <20060218173656.74241.qmail@web34507.mail.mud.yahoo.com>
Received: from [156.146.2.221] by web34507.mail.mud.yahoo.com via HTTP; Sat, 18 Feb 2006 09:36:56 PST
Date: Sat, 18 Feb 2006 09:36:56 -0800 (PST)
From: Paul Stefanowicz <pjstef@yahoo.com>
To: ROOTS-L@rootsweb.com
In-Reply-To: <200602181500.k1IF0Uva022976@lists5.rootsweb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
Sender: roots-in@roots-l.rootsweb.com
Subject: [ROOTS-L] WWI Draft Reg. Card Imag   

Dee wrote: <<I'm trying to look up a WWI Draft Reg.
Card for a John
Henry b. June 1889 in Wetzel Co., WV but a blank image
keeps coming up.

I just checked all Wetzel Co. cards beginning with A-K
and NONE of them are loading except for those
beginning with "A".

I'd appreciate it if someone else would check - I
don't know if it's a problem with my computer or
ancestry.com>>

On this topic, there are times that I click past the
index, through to the image  itself, and there is no
image. A black screen. Periodically, in the emails
Ancestry sends the subscribers, it tell you how to
report these kids of things. I have done this in a few
cases, back in October/Novemeber, and they haven't yet
fixed them.

I notice that in several cases, in the WWI cards, the
person's card you click into at the index screen is
not the one whose comes up. They have them a little
mixed up in places. Usually you can find who you want
by going in alphebetical order by name and searching
through the sets of cards. In a few cases I end up
nowhere near the person I want to see, so I can't find
the card I want, even though I have tried to access
from the index screen.

I have also send to Ancestry a few notes telling about
the transcription errors I see for my ancestors. When
I am flipping around I see these triangles where
people have done same. Well it must take a long time
because I sent one of these 6 months ago and it is
still not in the system.

Paul