The kit is great and so far seems to work without any issues. Placement of the iPhone is a little different. The other charging kit is practically form-fitted so the case fits in easily. On the larger charging mat it takes slightly more work to place the iPhone properly but it doesn’t take long to get used to figuring out the proper alignment to charge.
It does suffer from the same issues the other Powermat has – annoyingly bright LEDs (to indicate charging) and the sounds that it makes when the mat begins to charge a device. Those issues aside it’s excellent. I like the convenience of not having to plug and unplug every time I want to charge – this should help prolong the life of the connectors for when I do need to charge with a cable.
I migrated our MobileMe accounts to iCloud the day it was released, after updating my iPhone to iOS 5. I was using two accounts. One account is my primary and I synched mail, calendars, contacts, etc using it. I had another account that I only used for e-mail.
Overall, my transition to iOS 5 and migration of the accounts went without any major issues.
Well, that was the case until I tried to use Pages, Numbers, and Keynote on the iPhone with the new iCloud sync capability. For each app I turned on the “Use iCloud” option but every time I opened one of the apps the setting reverted back to off and in the iCloud Website it just showed the intro pages for the apps.
Perhaps I was aware of this restriction a long time ago, when I used a Windows system as my primary desktop, but I completely forgot this. Windows does not permit accessing two different shares that use different credentials when they exist on the same system. There may be more to it than that. For example, it may only apply to a Windows user account logged into a desktop system.
Regardless of the details, I wasn’t able to access two shares on a network drive from the ASUS (Windows 7). Every time I tried to connect to the second share I’d receive a vague error message stating that the connection couldn’t be made. I knew the credentials I was using were correct.
One solution is to disconnect the first share and then connect to the other one. However, I was using that share for the Windows system backup and I didn’t want to bother with having to remove the connection and then re-establish it.
After searching a few pages and forums I came across one post in the Microsoft TechNet forums that explained a workaround. That this even works is laughable, but it really does. User Mustafa Radha explains that using the IP address for one share, and then using the network name for the other share, will work. Indeed it does.
For example, assume I’m trying to connect to a machine named “Server” with an IP address of 192.168.1.2, and it has two shares named “Photos” and “Documents”. You could access both shares at the same time by using these paths:
Of course, you could swap the IP and name as desired.