May 24, 2007 | blog
T-Mobile has finally released an upgrade to their popular MDA called the ‘Wing’. I’ve been a happy T-Mobile MDA owner for well over a year and am trying to decide whether to upgrade to the Wing or wait for the next version.
The Wing is a nice upgrade, revamped keyboard with larger keys, Bluetooth 2.0, 2 Megapixel camera, and Windows Mobile 6. What isn’t updated is the RAM/ROM, which really isn’t a problem, and the processor which runs at 200MHz. The MDA has the same speed processor in it an can at times be really slow. The other item that many, including myself, are missing is the 3G portion. Yes, Tmo only has EDGE right now, and will use a different 3G frequency when they do roll UMTS and HSDPA later this year.
Technorati tags: T-Mobile MDA, T-Mobile Wing, UMTS, HSDPA, EDGE, 3G
Feb 19, 2007 | blog
Ah, now this’ll be a great feature for all WM6 based devices. The ability of a free Hotmail account to push mail directly to your device is a great feature. Now if they can retro-fit that back into WM5, I think everyone would be happy. After all, WM5 has had the ability to perform this service with Exchange email systems since it shipped.
At least your next WM phone will have the capability!
Via: Being a new PM at Microsoft – Push Email with Windows Live Hotmail and Windows Mobile 6.0
Jan 31, 2007 | blog
As some may know, I’ve been a longtime PPC user, actually starting with the old “Palm-size PC” back in 1998 or so. But the topic of this post is the parent operating system of the Pocket PC (and Windows Mobile for that matter) called Windows CE.
So we’ve been working on some Windows CE based devices for our warehouse management system at work. The goal, of course, being a fast-booting, lightweight client device to use for a web-based WM tool.
The main trouble with the devices we had, was really the WinCE operating system and its ability (or lack thereof) to be able to use EAP-TLS to secure the wireless network. Eventually a network stack update from the manufacturer did the trick, but it was frustrating to have everything configured correctly, but have the damn software not be able to connect up.
So, it’s one more chapter in alternate operating systems. If it’s not this it would be something else, perhaps Linux of some flavor. I’d actually like to have the ability to work with a Linux system at work – I think there is a huge potential for the OS in what we use PCs for. But that’s another story.
Fortunately its almost over – its been kind of fun, writing some scripts and such. Scripts are something that I don’t get to write as much. We use most tools right out of the box (or try to), so there is as little custom work as possible. Still, once in awhile a need comes along for a good script, and this was one of them for me. 🙂
As much as I’ve liked Windows CE based systems in the past, I’ve had about enough of them at this point. Working with these systems has brought the operating system’s deficiencies to the surface, and they are not pretty.
Oct 14, 2006 | blog
A big thank-you to Kevin Tofel over on jkOnTheRun for posting this fix for teh Windows Live OneCare 1.5 Beta.
You see, when you run the latest beta of Windows Live OneCare 1.5 with the latest beta of Windows Mobile Device Center, the firewall will block the synchronization ports and application. The following firewall settings can be manually entered into the Windows Live OneCare firewall to allow Windows Mobile devices to once again synchronize with Windows Vista.
As the self-proclaimed “King of Google Search”, I quickly got the lowdown on the reason why with this thread over at the OneCare forums of all places. Seems as though the Windows Live OneCare 1.5 Beta is overly protective and I had to configure the Firewall with some additional port openings. I also added two of the WMDC executables and one .dll to the OneCare Allowed programs. If you’re a risk taker too, here’s what you need to do:
Configure these ports in the OneCare Firewall settings:
- port990: open inbound TCP
- port999: open inbound TCP
- port5678: open inbound TCP
- port5679: open outbound UDP
- port5721: open inbound TCP
- port26675: open inbound TCP
Allow these files in OneCare:
- C:WindowsWindowsMobilewmdc.exe
- C:WindowsWindowsMobilewmdHost.exe
- C:WindowsWindowsMobilewmdsyncman.dll
These settings worked for my installation and got my MDA syncing again. Thank you Kevin!
jkOnTheRun: Windows Mobile Device center not playing nice with Windows Live OneCare 1.5?
Sep 18, 2006 | blog
If you’ve been a fan of SBSH Software’s iLauncher software, you should be aware of a newly released version.
Version 3 of iLauncher is available immediately to new and existing users ($14.95 new, $4.95 upgrade).
September 18, 2006 – SBSH Mobile Software released the next major version of the award-winning launcher application, iLauncher version 3! Introducing new integrated task-manager, ‘X’ button that really close, new safe-mode protection, special action shortcuts, multi-language support and much more!
For more information, check out the following links:
SBSH iLauncher Home Page
iLauncher 3 Press Release
T-Mobile has finally released an upgrade to their popular MDA called the ‘Wing’. I’ve been a happy T-Mobile MDA owner for well over a year and am trying to decide whether to upgrade to the Wing or wait for the next version.
