I've been tying the Glo Bible (www.globible.com) recently. It has some great content and functionality; and a new way of filtering and slicing the various aspect of it's content in a powerful way. There are clients for Windows, Mac, iPhone and iPad and a license allows you to install on 5 devices and sync your notes, etc between them. If you haven't seen it check out the features.

Ran up against an issue recently after allowing my mesh to upgrade to r2693 - the pro units updated fine and reconnected to the mesh with no problems, but the standard unit would not update from r2671, and would no longer check in even when wired directly to the internet and left for a few days . The power and the internet lights would light up, but the WLAN light would never come on. The solution was to manually flash the firmware to r2695 using these instructions . Fifteen minutes later, I connected the unit back to the wired LAN and the low-cost unit was back up and meshing! Hope this helps!

*** See Update below ***

I have a table new_table that has 2 cols: ID - nvarchar (5), and Value - nvarchar(20)
the table has 7 a rows:
ID, Value
E1, yes
E2, 32.3
E3, 9
R1, 151
R2 40
R3, 20
R4, 99

I need to get the count of the rows where the values are in (R1, R2) and Value >= 151

If I select count(*) from new_data where ID in (R1, R2) it returns '2'
If I select value from new_data where ID in (R1, R2) it returns 151 and 49
If I select value from new_data where ID in (R1, R2) and Value >=151 it tells me it can't convert 'yes' to integer.

Tried making a CTE to tempData where ID in (R1, R2) then doing a select count(*) from tempData where Value >= 151 I get the same error.

However, select count(*) from tempData gives me the correct 2 and select value from tempData gives me 151 and 40 as you would expect. Any ideas?

Tried adding a convert, isnumeric, etc, no change.

The real issue is why is it even seeing the "yes" row when I add in the Value >=151 condition since any rows without valid values should have been filtered out of the tempData table?

An over looked strength of the MS platform is interoperability. See my post about it here.

Some thoughts and observations on the Open-Mesh wireless routers:

General Info about the units:
Pilot Hardware Purchased:
2 Open-Mesh Pro's ($49), 1 standard (aka lowest cost - $29) .

Pros:

• Cost obviously.
• Open Source nature of firmware (http://www.open-mesh.org/).
• Support for 3rd party hardware from Ubiquity and others.
• Good accessories such as higher gain antennas, indoor and outdoor enclosures, PoE injectors ($5!), etc.
  interesting support for Captive Portals, redirects on access, Private and Public SSIDs, RADIUS support, bandwidth limiting (up and down) on the Public network, ACL's, public network status page, etc. See my previous post on the DashBoard configuration screenshots.

Cons:

• Can't do VLANing out of the box with these - all traffic from Private or Public flow trhough the same subnet (unless you do something like MAC filtering at your switch, but nothing built in)
• Seemed to get a little warm.
• Changes to configuration resets the AP. Connectivity is lost until the updates propagate throught the AP's which would be expected. The more hops from the wired connection the longer it takes, seems to be about 10 - 15 mins a hop. Recently however, Open-Mesh released a new update, and they set the "Disable Automatic Update" option in everyone's dashboard. so that administrators could plan for the outage that occurs. When I turned off that option, the update was pushed to the first AP in just a couple of minutes.
  

Thoughts on Best Practices:

• Note that the standard and the pro use two different A/C adapters - Std = 5v/2a, Pro = 12v/1a, so don't plan on compatibility for the wall warts.
• Before you build out the network, connect each node directly to the internet connection individually with the others shut off to allow it to flash the new firmware.This is for safety (so you don't pull the plug on it accidentally while it might be flashing - requiring a manual re-flash) and for time savings while testing, setup, etc. The same holds true any time you are adding a new node to your mesh - plug it in and connect it to the internet somewhere where it can't see the mesh, let it get the latest firmware, then add it to your mesh.
• Use inSSIDer (free), Ekahau HeatMapper (free) or Wi-Spy ($99-$199) to verify your coverage
  

Other Notes:

• Several members of the Church IT Roundtable group are using them in production. Tweet to the #citrt hastag or com to the #citrt IRC channel on freenode if you want to talk about them.
• See my other post on the DashBoard Configuration and options
• I'll write my findings as I go into production with them.
• There is a nice Google Maps mash up showing the status of your mesh an key data such as users, throughput, data sent, AP's with issues, etc. See my previous post for a screen shot.
• Open Mesh will email daily notices (or hourly if you like) on the status of your mesh. Here is a sample:
  "The following nodes are down at Tenth Presbyterian Church:
  Delancey 3rd fl . Last Check-in: 10 Hours, 4 Minutes.
  Reception Hall . Last Check-in: 9 Hours, 34 Minutes.
  Delancey 1st fl. Last Check-in: 9 Hours, 38 Minutes.
  
  This is an automated once-per-day message. Please don't reply to this address.
  You may view your network status at http://www.open-mesh.com/overview.php?id="
  

Testing the Open-Mesh wireless mesh routers
Testing Config:
Set them up in a Pro-Std-Pro linear mesh. Tested with the standard attenna that is included with the unit, higher gain and directional antenna are available.

Signal strength:
Set up in my house, typical construction, brick front. I did some ad-hoc range testing. Seemed comparable to most consumer level APs, and actually performed better than my FiOS ActionTek router (I put a Pro AP directly on top of the ActionTek). I was Able to listem to Pandora and do other streaming though My entire yardm, and was able to remain connected across street, approximately 100 feet away.

Speed Tests:
I will publish my findings on speed testing shortly.

Open Mesh wireless configuration screens, for those who are interested. See some more detailed info on testing, etc here. Click for larger images.
General, SSID #1, SSID #2:


Advanced, Network Status: