Tuesday, May 10, 2011

Solar Pool Heater DIY Leak Repair

Mighty Putty is one of the last products sponsored in part by the late Billy Mays.



Boasting the ability to bond numerous materials with the holding power of epoxy, including water pipes, I wondered whether this stuff could tackle a problem with some leaking HiTec solar pool heating panels.

Some years ago, I had a HiTec solar system installed to heat my swimming pool with solar energy. Consisting of a series of black panels of tubes which convey pool water up and onto the roof, given enough sunlight the system makes an otherwise chilly pool very swimmable.

Made of a rigid, ultraviolet-resistant plastic, the panels can be damaged by, say, falling tree branches or, as my contractor claimed, squirrels. The contractor who installed the system claimed that leaks that had developed in a couple of the panels recently were attributable to "squirrel damage" which conveniently for them is one type not covered by the manufacturer's limited warranty. 

Aside from the fact that no plastic-hungry squirrels nor squirrel spoor laden with plastic shavings had been discovered on my property, making determining the actual cause of the damage a difficult enterprise to say the least, this also meant that the contractor would be able to collect a roughly $135 service call fee to service the system for an out-of-warranty repair. How convenient that the contractor could fall back on these dastardly, elusive squirrels as the cause and not something actually covered by the warranty!


Commonly found, uncommonly evil, or so the contractor claims...



I wondered whether Mighty Putty might be able to save me some money.

I had basically two types of defects that had arisen in one of the panel arrays. One was a section of one of the tubes that appeared to have cracked off, a structural defect about 2" long.


Before application... a huge chunk of tube is missing.


Another consisted of pinhole leaks caused by abrasions to the plastic tubing, whether by falling tree branches impacting the panels, or the aforementioned scrabbling squirrels. Generally, since a solar system benefits from as much sun exposure as possible, installation under trees is inadvisable, but sometimes unavoidable. Unfortunately, a pine tree, a few of whose branches overhang the roof, probably were the culprit, both as a result of falling debris and as a squirrel habitat.

Following the instructions, I sliced about a 1" wide section of Mighty Putty, and kneaded it thoroughly for several minutes until it became a uniform, grayish consistency indicating that it's ready for use.

I roughened the area around the breach with some sandpaper and blew the resulting dust away. Then, I molded the putty into roughly the shape of a drinking straw cut in half lengthwise, large enough to encompass the hole and replace the missing plastic. Finally, I molded the putty patch onto the empty area and took care to apply even pressure all along the seam to ensure maximum contact with the plastic.

After application, covering the gap.


The pinhole leaks required slightly less putty to fix, but a similar process. To these I applied small dabs of putty sufficient to completely cover the holes.

For plumbing repairs, the makers of Mighty Putty boast a cure time of as little as 30 minutes before pressure is restored. HiTec states that their panels are pressure tested up to 90 psi, but that typically a swimming pool solar heating system will hover around 20 to 40 psi. I figured that this pressure is probably less than that of household plumbing. I would soon find out for sure. I climbed the roof, applied the putty, and allowed it to set for a full 24 hours just to be safe. The result? 

Success! The putty stopped the leaks in their tracks. 

It remains to be seen whether the putty will stand up to daily exposure to sun and chlorinated, pressurized pool water, but for now, the putty fully filled my expectations for far less than the cost of a service call, as well as saving me the time and trouble that would necessitate getting the perforated panel replaced outright.




Well done, Billy Mays. R.I.P.

Wednesday, April 27, 2011

Reddit-Headed Step Child?

Once again, Reddit has suffered a temporary meltdown.

CAPTAIN'S LOG, LAGDATE 6/24/2011... A brief emergency read-only mode last night, duplicate comments, sporadic 502 and 504 errors, and the occasional overloaded notification. Things bode ill for the weekend, but stay tuned.

Condé Nast Digital, parent company of Reddit, is one of several corporate entities owned by Advance Publications, Inc., a communications and print conglomerate.

Featuring among its ranks major sites like Wired, Vogue, Ars Technica, and others, many Reddit users, myself included, find it hard to believe that a site with upwards of one billion monthly pageviews seems to not get the creddit it deserves, in the form of infrastructure, staff, and just plain funding.

In short, why is Reddit seemingly Condé Nast Digital's red-headed step child?


Granted, since the diggsaster some months ago, Reddit has had an influx of new users which perhaps outpaced its anticipated growth. Further, Reddit recently dealt with some issues attributed to Amazon's Elastic Block Service (EBS) as well as a failure of a server which hadn't been updated to benefit from the redundancy of RAID. 

I really enjoy Reddit, it's a great site to find news, interact with people, and throw out horrible puns without threat of being stabbed with a narwhal tusk. Uptime, however, hasn't been it's strong point, so here's hoping things improve with help of some new and returning staff

Every site has issues occasionally, but given enough squeaking, the wheel gets greased...


ToCondé Nast Digital
     Advance Publications, Inc.

From: The Reddit Users

RE: Grease

Squeak!




UPDATE (5/6/2011): Another emergency downtime for most of the day, preceded by sporadic 0 / 502 / 504 errors and apparent database corruption (including misdirected comments and private messages) in addition to the usual sluggishness around midday EST. Eep!









Sunday, April 17, 2011

Motorola Razr meets PCI Simple Communications Controller

I picked up a used Alltel-branded Motorola Razr v3b for $2 at a yard sale recently. After reeling for a moment that new this phone probably ran for $150+ and now lay abandoned among pots and pans and power tools and other discarded housewares, I decided to charge it up and see whether any ringtones and other crap were on the phone.

I installed Motorola Phone Tools in an effort to transfer the data to my PC.



However, upon connecting the phone to my PC with a compatible USB data cable, one new device appeared in my system's Device Manager, a "PCI Simple Communications Controller" whose driver failed to install.

I opened the Properties of the device and selected the Hardware Ids property from the Details tab.



I searched for hits on the top entry: 

     PCI\VEN_8086&DEV_29A4&SUBSYS_514D8086&REV_02


This revealed that the device is the Intel Management Engine Interface, which lives on my Intel DP965LT motherboard. However, for whatever reason (perhaps just obsolescence) my Windows 7 Ultimate install couldn't find the appropriate drivers.

I downloaded the Intel® ME: Management Engine Driver for Intel 963/965 Chipset-Based Desktop Boards, but the installer supports XP and Vista, not 7. I found various forum posts that suggested working around this by trying to run the installer as administrator and in Vista compatibility mode, but this didn't work; the installer refused to run beyond copying the files to my PC at this location: 

     C:\Program Files\Intel Desktop Board\HECI_allOS_2.1.22.1033_PV 


I found another post that suggested attempting to update the drivers by having Windows search for drivers in the folder created above, and this did the trick. 

I right-clicked on the PCI Simple Communications Controller, clicked Update Driver Software..., then Browse my computer for driver software. I input the path to the drivers unpacked from the management engine package (C:\Program Files\Intel Desktop Board), then clicked Next:





The PCI Simple Communications Controller disappeared and in its place an Intel(R) Management Engine Interface device appeared instead under the System devices category:



When I again plugged the Motorola Razr v3b in via USB, this time the Driver Software Installation dialog reported success across the board, and Motorola Phone Tools could now properly communicate with the phone.






If nothing else, it'll serve me well as a spare digital camera, or maybe as a prop in some twisted video involving the destruction of formerly cutting edge electronics.









Wednesday, April 13, 2011

Malware Redirects Google Search Results

Encountered what appears to be malware with some javascript which caused Microsoft Security Essentials (MSE) to throw errors and almost, but not quite, infect a system.

Popup notifications appeared in the systray every few seconds, and the MSE process MsMpEng.exe was gobbling up 50%+ CPU trying to keep whatever was trying to infect this Windows XP service pack 3 PC under control.

MSE's log showed the following error at the top of the details:
Microsoft Security Essentials encountered the following error: Error code 0x800703e4. Overlapped I/O event is not in a signaled state.

It listed numerous instances of the following as the most recent triggers for the cleanup:
TrojanDownloader:Java/OpenConnection.J
TrojanDownloader:Java/OpenConnection.JJ

Interestingly, the malware kept triggering the alerts from a specific path on the system:
C:\Documents and Settings\User\Application Data\Sun\Java\Deployment\cache\6.0\14\3cb28b8e-3c71bd02->lort/cooter.class

Apparently lort/cooter.class is related to a family of malware dubbed JAVA/Exdoer, based on a log file I found posted here. The system's default browser (Firefox) was redirecting Google search results to various sites with advertising. While MSE seemed to be detecting and responding to whatever active component of this malware, freshly-updated installs of SpyBot, MalwareBytes, and PrevX did not detect it.

I decided first to try to simply close all browsers, then run a utility called GOOREDFIX.EXE as described in this forum post. It returned the following log info:
GooredFix by jpshortstuff (03.07.10.1)
Log created at 15:54 on 13/04/2011 (Jan)
Firefox version 3.6.16 (en-US)

========== GooredScan ==========

Deleting HKEY_LOCAL_MACHINE\Software\Mozilla\Firefox\Extensions\\{A1E5480F-729F-4237-AD8E-2C46BA793DFE} -> Success!
Deleting C:\Documents and Settings\User\Local Settings\Application Data\{A1E5480F-729F-4237-AD8E-2C46BA793DFE} -> Success!

========== GooredLog ==========

C:\Program Files\Mozilla Firefox\extensions\
{972ce4c6-7e08-4474-a285-3208198ce6fd} [18:53 08/03/2011]
{972ce4c6-7e08-4474-a285-3208198ce6fd}(2) [18:19 08/03/2011]
{CAFEEFAC-0016-0000-0017-ABCDEFFEDCBA} [20:30 16/01/2010]

C:\Documents and Settings\User\Application Data\Mozilla\Firefox\Profiles\c06n7342.User\extensions\
adblockpopups@jessehakanen.net [01:37 14/03/2011]
{20a82645-c095-46ed-80e3-08825760534b} [01:08 27/12/2010]
{7b13ec3e-999a-4b70-b9cb-2617b8323822} [19:18 12/04/2011]
{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d} [16:22 27/03/2011]

[HKEY_LOCAL_MACHINE\Software\Mozilla\Firefox\Extensions]
"{20a82645-c095-46ed-80e3-08825760534b}"="C:\WINDOWS\Microsoft.NET\Framework\v3.5\Windows Presentation Foundation\DotNetAssistantExtension\" [20:46 30/09/2009]
"jqs@sun.com"="C:\Program Files\Java\jre6\lib\deploy\jqs\ff" [20:30 16/01/2010]

-=E.O.F=-


However, something seemed to reactivate the malware upon reopening Firefox, and the MSE systray popups began again.

I closed the browser, ensured that neither firefox.exe nor any other suspicious executables were present among the running processes, reran GOOREDFIX.EXE, then simply deleted the following folder:
C:\Documents and Settings\User\Application Data\Sun\Java\Deployment\cache\

Upon reopening Firefox, no further MSE notification popups appeared, and after running a full scan with MSE, no threats in memory nor in the file system were reported. So far, at least, it looks like whatever this malware was has been eliminated, but we shall see!