Finally have the new MS LifeCam up and fitted with both polarizing and UV filters - I found little difference with or without the UV filter - so left in it place as protection from the elements (wind, rain, sand from the Sahara (carried by the wind from Africa and delivered by rain, and locally called "Fang" in Catalan.) The first problem appeared last night in a very heavy rain when water entered between the two filters. That is solved, I hope, now with more silicone sealant. By the way Gina, I mounted the camera in a small plastic enclosure similar to yours. Initially due to the enclosure being exposed directly to the sky the lens fogged over during temperature and humidity changes. That has been solved with a 35mm hole in the top of the enclosure. I fashioned a ventilated cover from a section of PVC pipe cut length wise in half and mounted over the enclosure & hole as a hood. There is, of course, a hole in the bottom to exit the USB cable. So far it has solved that problem. Next time on the roof I will take a photo for the Forum.
The Polarizing filter really brings out the blue sky and all other colors are enhanced. Take a look for yourself at:
http://www.wheelocknet.net/cam/index.htm?gb . The best views are noon to 19:00 camera local time which is UTC + 2 as the camera faces almost directly east into the morning sun.
ImageSalsa is the ftp source and works flawlessly - Yawcam was ditched due to consistent problems with "timeout" errors.
ImageSalsa at first refused to install on my Windows Home Server box but Jason at ImageSalsa sorted that out within a few hours. I know a few of you are using WHS (I know Steve does) so here is the solution:
All I had to do was add ImageSalsa.exe to the DEP exclusion list in System Properties/Advanced/Performance Setting/Data Execution Prevention.
Here are the instructions passed on by Jason at ImageSalsa:
The issue is with DEP - Data Execution Prevention. I could go into it but I will just give you the URL to the Support article.
http://support.microsoft.com/kb/875352/en-us#6
As well here are the important parts of that article:
Per-program DEP configuration
For the purposes of program compatibility, you can selectively disable DEP for individual 32-bit programs when DEP is set to the OptOut policy level. To do this, use the Data Execution Prevention tab in System Properties to selectively disable DEP for a program. For IT professionals, a new program compatibility fix that is named DisableNX is included with Windows XP SP2. The DisableNX compatibility fix disables Data Execution Prevention for the program that the fix is applied to.
The DisableNX compatibility fix can be applied to a program by using the Application Compatibility Toolkit. For more information about Windows application compatibility, see Windows Application Compatibility on the following Microsoft Web site:
http://technet.microsoft.com/en-us/wind ... 05066.aspx (
http://technet.microsoft.com/en-us/wind ... 05066.aspx)
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
912923 (
http://support.microsoft.com/kb/912923/) How to determine that hardware DEP is available and configured on your computer
Perhaps this will work with other problem installs om WHS.
George