On Sat, 12 Nov 2011 11:10:16 -0500, "Dave \"Crash\" Dummy"
<> wrote:
>Char Jackson wrote:
>> On Sat, 12 Nov 2011 09:16:41 -0500, "Dave \"Crash\" Dummy"
>> <> wrote:
>>
>>> This is more an annoyance than a problem.
>>>
>>> In Windows 7, if I right click in a directory and select
>>> "New>Folder," a new folder is created and the name "New folder" is
>>> highlighted. If I leave it at that and remove the focus, all is
>>> fine, and I have a folder with the name "New folder," which I can
>>> rename as I please. However, if I try to rename the folder during
>>> the creation process, while the name "New folder" is highlighted, I
>>> get an error:
>>>
>>> ------------- Item Not Found ---------- Could not find this item
>>> This is not located in [d:\directory]. Verify the item's location
>>> and try again.
>>>
>>> New folder Date created: [time/date]
>>>
>>> buttons:Try again-Cancel
>>> --------------------------------------------
>>>
>>> which actually makes sense. If I hit the "Try again" button, the
>>> function proceeds and the folder is created with my new name.
>>>
>>> I don't think this has always been this way. An update or something
>>> I installed is causing this. Does anybody else experience this?
>>
>> I've seen that behavior. For me, it began immediately after I used a
>> Registry hack to disable Libraries, along with a few other similar
>> behaviors such as File Not Found (Try Again always worked the second
>> time) when trying to copy or move one or more files.
>>
>> In my case, the fix was simple: undo the Registry hack. Now the
>> Libraries are back and the weird behavior is gone.
>>
>> If yours is like mine, though, the weird behavior is harmless, other
>> than being annoying.
>
>Thank you. That makes sense, since the libraries goof up file locations.
>I also disposed of the libraries. I'd rather be annoyed than put the
>libraries back.
I remember internally visualizing it as the file operation code
jumping to a block of code that determines whether you're working with
a Library entry or not, and it fails if the Library is disabled. Try
Again seems to bypass the Libraries hook and go directly to the file
operation code. Harder to explain properly than to visualize.
--
Char Jackson
|