|
Posted by Ahmed Smahi [MSFT] on March 5, 2007, 8:38 pm
Please log in for more thread options I think I am able to repro the issue you hit, when I copy \My
Documents\Templates\Blank Document.etc to my desktop, I am not able view the
file. Though when I attempt to copy it again, the shell prompts me saying
that the file already exists. If this is the issue you are hitting, it is
caused by an inconsistency between how the windows explorer handles files
and the way the ActiveSync shell extension does.
By Default, the shell explorer does not display system files while the
ActiveSync shell extension does, when the file gets copied it is
automatically filtered on the desktop which makes it seem that it disappear.
Thanks,
Ahmed Smahi
AhmedSmahi@online.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
> Hi Ahmed,
>
> No they dont, the only way to actually physically see the file, is when i
> copy to the desktop but from within the same explorer window, where they
> automatically appear once the copy process is complete.
>
> regards,
> Paul
>
>> Do the files appear after pressing F5 to refresh the desktop folder?
>>
>> Thanks,
>> Ahmed Smahi
>> AhmedSmahi@online.microsoft.com
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>> hi there,
>>>
>>> im sure this is an introduced bug into MS ActiveSync (im using 4.5) as i
>>> know it worked in previous versions.
>>>
>>> My problem is that i am trying to copy some generated files from my PDA
>>> to
>>> desktop via activesync connection, and although it shows as copying, the
>>> files just dont appear on the desktop.
>>>
>>> To replicate: open windows explorer, go to "mobile device", find some
>>> files,
>>> then drag them directly to the desktop. it will look like its copying
>>> but
>>> the files dont appear.
>>>
>>> The workaround: in the same windows explorer window, drag the "mobile
>>> device" files into another folder within the windows explorer, or drag
>>> onto
>>> the desktop icon, and it works.
>>> I've tried both with disabling/enabling file conversion, and its the
>>> same
>>> effect.
>>>
>>> this surely looks like a functionality bug to me. Has anyone else
>>> noticed
>>> this?
>>>
>>> regards,
>>> Paul
>>>
>>>
>>>
>>>
>>
>>
>
>
|