Monday, June 29, 2009
Thursday, June 25, 2009
The good news is that at this point of the install, napclientprov.mof should already be installed on the machine. You can click on Browser, then navigate to C:\Windows\system32\WBEM. You should see the napclientprov.mof file there, which you can then select and click OK to get the installer to continue. I don't have much more of an explanation than that, but it solved the issue for me so I'd expect it to do the same for you.
Wednesday, June 24, 2009
Update: If this doesn't work for you try resetting your phone, then uninstall iTunes, reinstall iTunes, then plug your phone back in. It sounds like a hassle, and it is, but if it'll fix your phone then it'll be well worth it. To restore and reset your phone, check out my previous post. If you can't reset using the normal method you may have to use recovery or DFU mode, which are covered in previous posts as well. Once the phone has been restored to factory defaults (which means you need to choose to set it up as a new iPhone during the restore process), then go ahead with uninstalling iTunes. To do that, follow the uninstall directions in the Apple KB. Once you've uninstalled iTunes, go ahead and reinstall it while making sure to restart your computer in between the uninstall and reinstall. Once iTunes has been reinstalled, plug your iPhone into your computer and let the computer recognize and install it. If this works properly then you can go ahead and use iTunes to restore your phone to the most recent backup of the old settings. If this doesn't work then I'd suggest going right into a DFU mode restore if you didn't have to already, then trying to plug the phone in again. If that still doesn't work then I would say it points at a hardware failure. Be sure to verify your connection cable is working correctly before completely giving up, but if that's not it either then you're stuck relying on the warranty (if you still have one) or using the iPhone as a paperweight.
Tuesday, June 23, 2009
Monday, June 22, 2009
Wednesday, June 17, 2009
Tuesday, June 16, 2009
Sunday, June 14, 2009
Wednesday, June 3, 2009
|Sent:||Wed 6/03/09 3:08 PM|
|When:||Wednesday, June 3, 2009, 9:00PM to 9:30PM|
When: Wednesday, June 03, 2009 4:00 PM-4:30 PM (GMT-06:00) Central Time (US & Canada).
Where: Test site
Note: The GMT offset above does not reflect daylight saving time adjustments.
Notice that there is a When and Location field in the subject displayed in Hotmail, and then there is a When and Where within the body of the message. The body shows the correct time, while the subject section has a time that is 5 hours later than when the meeting is meant to happen. After thinking about this I believe I figured out the answer.
When the appointment is sent to Hotmail, it must use Greenwich Mean Time (GMT) rather than your current time zone setting. Also, since I'm currently located in a place that is in Daylight Savings Time (DST), our time zone is one hour different than it normally would be. I'm in the Central time zone, which is 6 hours earlier than GMT normally, and 5 hours different currently thanks to DST, which would mean a meeting I schedule at 4pm would appear as 9pm in GMT.
I thought this same issue affected Gmail appointments that originate from Outlook too, but after testing it the correct time did seem to be showing in my Gmail account. I'm not sure of any workaround, but submitted this information to Hotmail to see if it's a known issue (support ticket #1103641366). At least this should explain why it's happening for any of you who may have noticed but couldn't quite nail it down.
UPDATE 6/10/2009: This issue is still pending, but I've been working with Windows Live Support to try to solve it. The problem is that I've received emails from 4-5 representatives and have had to practically start over with each of them. The last was them asking for the ok to access my account, which I believe they did today, so I'm hoping to have some type of resolution, or at least acknowledgement soon. If you're having the same problem leave a comment so I can use it to help prove that it's not limited just to my accounts, because that's what they've tried hinting at.
UPDATE 7/2/2009: After many, many emails back and forth with Windows Live support, with them having me repeat the same troubleshooting steps over and over so they could try to blame my time zone settings, I finally received this message:
We receive a feedback from our product team with regards to your issue on time zone. They mentioned that it is by design that the time zone in the event details came from the time zone of the exchange server. While the time zone in the calendar view appears correctly. Windows Live Calendar shows the event in the event time zone.
Apparently that means that they couldn't figure out how to program Windows Live Mail to change the time zone to match that of the Windows Live Calendar settings. Gmail does it, so why doesn't Windows Live? Looks like it is because they don't want to. All appointments are going to be sent out in GMT in order to make sure there is some type of consistent time zone setting. That way the receiving end can look at the time, then reconfigure for their specific time zone settings since everything is based off of GMT anyway. Regardless, it looks like this one was put to bed with a result of Windows Live Mail acknowledging the problem, but then stating it's functioning exactly as designed.
One sidenote to anyone who happens to read this far and is involved in tech support in one way or another. READ an entire question before starting to answer. Sometimes a person just may be smarter than you think, and may have tried their own troubleshooting related to the problem. That can save a lot of time, but only if you bother to read it. I run into this all too often when I am trying to get questions answered by tech support at various places. I know there are a lot of people who don't have a clue out there because I'm in tech support myself, but assuming everyone is clueless makes it very frustrating for those who know what is going on and actually have a legitimate issue with whatever you are supporting.
Monday, June 1, 2009
If you somehow found this page and are looking for tethering software for the Verizon network, download the VZ Access Manager from vzam.net. That is what Verizon uses for tethering. Again, make sure you call Verizon and set yourself up with a tethering plan first.