Your welcome, I only wish it had been some help. I kind of figured you
likely would have gone through that since you mentioned you were already in
contact with Apple regarding this, but I thought it was worth a shot. Hope
you can solve this!
Greg
franklinaz wrote:
> I really appreciate this level of detail. Unfortunately, I have gone
> through the process described and then some with Apple tech support
> and on my own. Several guys have replied to the effect it is Apple's
> issue, which is in a sense true. But I firmly believe the basic flaw
> is on the Vista side. My upgrade to Vista is recent and it began
> with Vista not running AutoPlay at all with any flash drive. After
> many hours with Microsoft I get AutoPlay on every other device but a
> flash and I get ReadyBoost on a flash drive - but not both. I get
> iPhone and autoplay in XP. The problem is device recognition in
> Vista, but nobody seems to know how to figure out where. I jope
> someone keeps trying. Thanks for the effort.
>
>> I don't have an iPhone, nor do I have iTunes installed on Vista but
>> I have run into something similar with the iPod on XP. Disconnect
>> the iPhone and then shutdown iTunes. Kill any other
>> iTunes/iPhone/iPod processes still running (you may have to go into
>> the Services to actually stop them). Restart iTunes (you may have to
>> restart any of the stopped services, but they should come up
>> automatically) and plug in the iPhone. If that doesn't work I'd
>> try to completely uninstall iTunes (and remove the iPhone device
>> from Device Manager) and reinstall.
>>
>> That said....iTunes did have some serious problems with Vista so
>> they may not be fully corrected yet.
>>
>>
>> Greg
>>
>>
>> franklinaz wrote:
>>> I have a recently installed Vista Home Premium. It does not
>>> recognize the iPhone for what it is. When you attach the phone it
>>> brings up an AutoPlay message. The device shows up in Computer
>>> under portable devices like a camera. It is called iPhone camera.
>>> iPhone works fine under XP. Tech support tried a million things
>>> with no success. I think it must be some kind of driver issue.
>>>
>>> Any ideas?