Monday, January 28, 2008

So as regular readers will know,   I've been using an Old Pocket PC as a caller ID server for about the past 3 years.

For those of you unfamiliar with this mission have a look at -

www.binaryrefinery.com/main/PermaLink,guid,d8f9b0a3-f884-4a81-87e5-448d2beda19c.aspx

Sadly after upgrading my wireless router my old Ipaq 3600 with an expansion jacket with 3com wireless network card  proved itself to be obsolete.    I previously was only using WEP security which the 3com Pocket PC drivers supported nicely.    However now I'm using sparkly  WPA-Personal TKIP encryption, suddenly the Ipaq has no way of seeing my home network.

image

Anyway,  all was not lost.     I've ported the caller ID application to be a Windows Service and it runs fine on the my Small Business Server.    I guess moral of the story,   I could have spent out and got a more up-to-date network card, but the lowest cost option for me was to port the code.  

I achieved the port of the C# application from .Net Compact framework to full framework Windows Service and an ASP.Net application in around an hour.      I guess its this kind of portability that we take for granted makes this type of conversion so easy.

Anyway,   final upshot.   As anyone calls my house.   I get email alerts for who's calling  popup messages on all PC's on home network and the ability to update the names to numbers mapping securely over the Internet.   What a cool geek project.

 

image

Monday, January 28, 2008 8:23:16 AM UTC  #    Comments [2]  | 
Monday, January 28, 2008 4:45:28 PM UTC
Nice project...This would be a perfect add-in for Windows Home Server...
Monday, January 28, 2008 7:48:49 PM UTC
Yes, I was thinking that too. I guess, I'd have to use an XML data store rather than SQL?
Richard
Comments are closed.

Theme design by Jelle Druyts

Pick a theme: