On Sat, 3 Oct 2015 07:29:00 -0700 (PDT), Tim
wrote:

Wayne, for some reason the first link only provides me with digital hash. Second worked great. I saw the pole and camera. That worked really well

It is an HTML file. Maybe your phone won't open that

On Sat, 03 Oct 2015 12:09:10 -0400, wrote:

On Sat, 3 Oct 2015 07:29:00 -0700 (PDT), Tim
wrote:

Wayne, for some reason the first link only provides me with digital hash. Second worked great. I saw the pole and camera. That worked really well

It is an HTML file. Maybe your phone won't open that

===

I think the problem is with the "space" character in the directory and
file name. Can you rename the directory and file to eliminate the
spaces?

On Sat, 03 Oct 2015 12:17:56 -0400,
wrote:

On Sat, 03 Oct 2015 12:09:10 -0400, wrote:

On Sat, 3 Oct 2015 07:29:00 -0700 (PDT), Tim
wrote:

Wayne, for some reason the first link only provides me with digital hash. Second worked great. I saw the pole and camera. That worked really well

It is an HTML file. Maybe your phone won't open that

===

I think the problem is with the "space" character in the directory and
file name. Can you rename the directory and file to eliminate the
spaces?

It is not a space, it is a %20 which does meet the standard. This must
be a google problem, I seem to be doing a lot to patch the flaws of a
service I don't like and will not use. I am already letting them
archive my posts.

If it was just the space, I would expect it to "404". It is just not
opening the HTML right.

On Saturday, October 3, 2015 at 1:03:42 PM UTC-5, wrote:
On Sat, 03 Oct 2015 12:17:56 -0400,
wrote:

On Sat, 03 Oct 2015 12:09:10 -0400, wrote:

On Sat, 3 Oct 2015 07:29:00 -0700 (PDT), Tim
wrote:

Wayne, for some reason the first link only provides me with digital hash. Second worked great. I saw the pole and camera. That worked really well

It is an HTML file. Maybe your phone won't open that

===

I think the problem is with the "space" character in the directory and
file name. Can you rename the directory and file to eliminate the
spaces?

It is not a space, it is a %20 which does meet the standard. This must
be a google problem, I seem to be doing a lot to patch the flaws of a
service I don't like and will not use. I am already letting them
archive my posts.

If it was just the space, I would expect it to "404". It is just not
opening the HTML right.

I think its a google problem. It didn't work on my phone or at home.

On Sat, 3 Oct 2015 11:35:58 -0700 (PDT), Tim
wrote:

On Saturday, October 3, 2015 at 1:03:42 PM UTC-5, wrote:
On Sat, 03 Oct 2015 12:17:56 -0400,
wrote:

On Sat, 03 Oct 2015 12:09:10 -0400, wrote:

On Sat, 3 Oct 2015 07:29:00 -0700 (PDT), Tim
wrote:

Wayne, for some reason the first link only provides me with digital hash. Second worked great. I saw the pole and camera. That worked really well

It is an HTML file. Maybe your phone won't open that

===

I think the problem is with the "space" character in the directory and
file name. Can you rename the directory and file to eliminate the
spaces?

It is not a space, it is a %20 which does meet the standard. This must
be a google problem, I seem to be doing a lot to patch the flaws of a
service I don't like and will not use. I am already letting them
archive my posts.

If it was just the space, I would expect it to "404". It is just not
opening the HTML right.

I think its a google problem. It didn't work on my phone or at home.

===

Did you try the tinyurl that Greg set up?

Yep. Same result. I think it's Google

On Sat, 3 Oct 2015 14:30:58 -0700 (PDT), Tim
wrote:

Yep. Same result. I think it's Google

===

Maybe. I'll send you the URL in an EMAIL.