msgbartop
Web 2.0, eCommerce, SEO, SEM, gadgets, and all that other cool tech stuff.Looking for the Majumdar Family? Tristan, Zachary & Robin ? Click here!
msgbarbottom

21 Aug 10 Touchality finally releases new WinMoSquare Beta 1.5.0 Windows Mobile Foursquare client – many features & … stability !

Touchality has finally released a new beta version of WinMoSquare – the Windows Mobile client for Foursquare.

WinMoSquare Logo

Updated August 22 to include a video of the new features with screenshots… see below after the break

If you’re not yet familiar with WinMoSquare or Foursquare ; 4SQ is a location based service that allows people to check-in to venues from their mobile devices (Smartphones, Net-books, Laptops, etc.) equipped with a GPS.

The idea is that you check-in to venues (originally restaurants, bars and that sort of thing but now pretty much everything including elevators, highway intersections and who knows what) and see if the venue offers “specials” for regular visitors. The more frequently you visit a venue, the more chances you have of becoming “Mayor” of a venue. Being the Mayor of a Foursquare venue gets you nothing from 4SQ themselves – except for status & recognition on the Foursquare website. A venue manager or owner can, however, decide to promote repeat business to their venue by offering specials to people who check-in and perhaps extra perks for a mayor. In addition, any Foursquare user can leave tips about a venue (try the steak, arrive before midnight, free parking in the back, etc) that other members can see and add as a “to-do” or “done this” item.

Foursquare have native client applications for the Android, iPhone, Blackberry and Palm smartphones. All other mobile devices can connect to the Foursquare Mobile website at m.foursquare.com.

Up until a few months ago, there was *no* client software for users with mobile devices running Windows Mobile…. That changed several months ago when Touchality released a beta version of WinMoSquare – a graphical client to run on WinMo phones … it required Windows Mobile 6.5 and the .NET compact framework (3.5 or higher)…
(more…)

Tags: , , , , ,

02 Jun 10 Protected: RETScreen 4 Test Download Page de téléchargement Test

This post is password protected. To view it please enter your password below:


17 Jun 09 Sharepoint / MOSS licensing – do we need MOSS CALs for users with access only to WSS sites in a separate site collection

Whew, that’s one crazy long title.

OK, I’ve been dealing with licensing reps from MSFT, fellow Sharepointers in the twittersphere, and I’m still not 100% sure about this particular Sharepoint licensing scenario.

Let’s say I have a Sharepoint farm, with MOSS 2007 installed. I have 100 regional users for whom I have 100 MOSS standard CALs.

I wish to have non-CAL users access sites in a separate site collection on the same Sharepoint Server. The non-CAL users would not have access to the MOSS portal site, no My Sites, etc. They would only have access to the separate site collection.

In this latter scenario, am I still within the licensing requirements? My 100 users for whom I have CALs would have access to everything. The non-CAL users would have access only to site collections and no MOSS portal site access.

It annoys me when MSFT reps say that licensing is “simple” and “straight forward”… sorry; not. I spend 15% of my time trying to explain licensing to my C-level executives… (and I have a hard time grasping all the finer elements of MSFT licensing soup myself… after 10+ years working with MS enterprise software.)

18 May 09 Windows Live Messenger 9 unable to connect with error 81000306 – solution ?

So, after installing Windows 7 Release Candidate (Build 7100) and trying to connect to Windows Live Messenger (14.0.8064.206), I kept getting error 81000306 and could not connect.

It’s important to note that these errors (on a Dell Latitude D620 with 2GB of memory) were on a dial-up modem connection although I doubt that was part of the error.

I found some potential advice over at the Windows Live Messenger Live Spaces blog which suggests doing some adjustments to the WLM proxy settings. The problem is that the advice provided seems to presume that WLM can be started normally in order to access the Tools menu ; this, in my case, wasn’t possible; I couldn’t even start Windows Live Messenger!

Those very instructions also suggest disabling the Windows Vista Auto Tuning Networking feature using the command line and entering “netsh interface tcp set global autotuninglevel=disabled“.

I made that change (using Run as Administrator, of course) and attempted to reconnect using Windows Live Messenger. After about 90 seconds of the rotating WLM graphic… no dice. I got the 81000306 error once again.

The instructions at the WLM Live Space say to revert the disabling of Auto Network Tuning using the “netsh interface tcp set global autotuninglevel=normal” command… so this is what I just did.

Amazingly, after REVERTING to Auto Network Tuning BACK on, I was able to connect using Windows Live Messenger. So, if this topsy turvy method of disabling Auto Network Tuning, and then reactivating it as I instructed above, worked for you – please do leave a comment below!

Tags: , , , , , ,

28 Jan 09 Windows Live Messenger unable to connect with error code 80040200 – solution in Windows 7

windows-live-messenger-logo-errorAre you unable to log in to Windows Live Messenger and getting the error code 80040200 ? If so, you may wish to try the following which worked for me on Windows 7 (beta, build 7000) with Windows Live Messenger 2009 (final build 14.0.850.1202):

DISCLAIMER: make sure you have a backup of everything before proceeding, and use this information at your own risk and peril.
(more…)

Tags: , , , , , , ,

Robin Majumdar technology blog