|
||||
Re: norton 2010 screwed something up!
after cursing out my pc, and phone, and everything gadget insight....i finally got it. i went into the device manager, and erased the diamond driver in the portable directory...and did another hard reset and re installed the drivers and that was how i got it to work, im unsure as to what specific step did the trick, but all that matters is that i got it to work. so thanks to the one other person that read my post, and if the moderators would like to delete this, then go ahead, if not then......... dont. lol.
|
|
||||
Re: norton 2010 screwed something up!
I think its cool that you figured it out and shared with the community.
might save someone from a hard reset or a computer format |
|
||||
Re: norton 2010 screwed something up!
Just joined the forum to say thank you olgreg20 . . . and to kind of confirm the fix. I, too, accepted Norton's invitation to upgrade from NIS 2009 to NIS 2010 and -- BAM! -- the very next day I could no longer connect via Windows Mobile Device Center to my AT&T Tilt (HTC 8925). Since Norton was my top suspect, I began investigating ways to poke through 2010's firewall, which I presumed had monkeyed up the works (WMDC had been working flawlessly for months and months and months). Microsoft actually publishes pretty good instructions for how to create the right rules in Norton to get ActiveSync to work . . . except ActiveSync does not perfectly equal Windows Mobile Device Center -- slightly different executables/locations involved. Needless to say, the firewall tweakage did not work. Still could not connect. Yeah, I was "cursing out my pc, and phone, and everything gadget insight" . . . and quite vehemently Norton, too.
Tonight I happily Googled across your post, olgreg20. But I went straight to the delete the portable device driver in Device Manager step (and if it will save anybody some head scratching -- you have to have your handheld USB'd to the PC for the portable device to show up in Device Manager (at least I did -- running Vista)). I deleted the driver, and then re-booted (keeping the handheld still plugged in via USB). Immediately upon re-boot -- voila! -- connected! So, thanks, olgreg20. I had already spent WAY more time on this than I cared to, and it is nice to have this functionality back. I'm off to snag a couple of podcasts for the Tilt! |
|
||||
Re: norton 2010 screwed something up!
Eww get rid of Norton then. That'll fix it. *snicker*
If you want a good AV get Microsoft Security Essentials and the built in firewall for Windows is just fine for a firewall anyway. |
|
|
|