I am monitoring the FPL project in the bay for my DEP folks
http://gfretwell.com/electrical/DIRE...al%20bore.html
and I came up with this rig to get some pictures of the bottom where
they are "jetting" to assess the damage. Unfortunately it was blowing
about 20 out of the west today and the water was so churned up I
couldn;t see anything.
It is a stick of gray PVC conduit, reworked with the help of a heat
gun.

http://gfretwell.com/ftp/Go%20Pro%20stick.jpg

Held over the side, pointing down, I should be able to get some decent
pictures when the water clears up.

Cool idea Greg but the first link was gobbldy-gook

On Sat, 3 Oct 2015 05:54:56 -0700 (PDT), Tim
wrote:

Cool idea Greg but the first link was gobbldy-gook

===

It opens for me. Try this:

http://gfretwell.com/electrical/DIRECTIONAL%20BORE/Directional%20bore.html

On Saturday, October 3, 2015 at 1:49:04 AM UTC-4, wrote:
I am monitoring the FPL project in the bay for my DEP folks
http://gfretwell.com/electrical/DIRE...al%20bore.html
and I came up with this rig to get some pictures of the bottom where
they are "jetting" to assess the damage. Unfortunately it was blowing
about 20 out of the west today and the water was so churned up I
couldn;t see anything.
It is a stick of gray PVC conduit, reworked with the help of a heat
gun.

http://gfretwell.com/ftp/Go%20Pro%20stick.jpg

Held over the side, pointing down, I should be able to get some decent
pictures when the water clears up.

Very interesting, Greg, thanks.

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

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

===

OK, try this one:

http://gfretwell.com/electrical/directional bore/Directional
bore.html

The problem is that there are spaces in the directory and file name.
HTML interpreters don't like that.

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, 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

Maybe this will work
http://tinyurl.com/q6uq2zt

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.