folder name = file name

[Leif]

Create a file C:\abc (i.e. no extension). Create a folder C:\Windows\abc
Copy the file abc to C:\Windows. The file ends up not in C:\Windows but in C:\Windows\abc
Hmmm... There a very tiny bell ringing at the back of my head. Does that mean this subject already has been covered or is just me getting older?

[Vansumsen]

Is it a tiny bug... or a correction ?

When you try the same test with Windows Explorer you get an: Errror message: Impossible to copy ,the acces is denied... Maybe busy ?...

The TC solution is more sympathic.

Have a good day Leif.

Paul

[Clo]

 Hello, bonjour Leif !

• I confirm, that works like this... I tested under Win 98 SE, TC 6.01.
• The same with an old version 5.0...

 Kind regards,
Clo

[Hacker]

Leif,
Well, what behavior do you propose? There can't be two abc's in one dir under FAT (NTFS probably, too).

HTH
Roman

[Leif]

Leif,
Well, what behavior do you propose? There can't be two abc's in one dir under FAT (NTFS probably, too).
HTH
Roman

Well, even I can tell a folder from a file. Why can't FAT or NTFS do that?

[Hacker]

I guess because both of them are files, a folder just being a special one and they differ according to their nemes.

My guess.

Roman

[ghisler(Author)]

Indeed folders are just files with a special file attribute. Since names need to be unique, you can't have a file and folder (or two files/folders) with the same name in the same subdirectory.

When you copy 'abc' to c:\windows, Total Commander proposes the name c:\windows\abc in the F5 copy dialog. When you then click OK, the name c:\windows\abc is interpreted as the name of the existing directory. If you only specify c:\windows\ as target, you will get an overwrite error as expected.

[norfie]

[Black Dog]

[face=courier]On 25-02-2004 08:35:21 +0000 Leif wrote:

L> Create a file C:\abc (i.e. no extension). Create a folder
L> C:\Windows\abc
L> Copy the file abc to C:\Windows. The file ends up not in
L> C:\Windows but in C:\Windows\abc
L> Hmmm...

Sad old story, actually... %)

np: Blackmore’s Night - Catherine Howard's Fate[/face]

[Black Dog]

[face=courier]On 25-02-2004 12:35:18 +0000 ghisler(Author) wrote:

g> When you copy 'abc' to c:\windows, Total Commander proposes
g> the name c:\windows\abc in the F5 copy dialog. When you then
g> click OK, the name c:\windows\abc is interpreted as the name
g> of the existing directory.

OK, let it interpreted filename whatever it wanted to. But why in God's sake it COPY that file there? It's very sad but I should repeat that explorer behavior in this situation is at least predictable. As for me in such a situation I want to be asked, actually %).

np: Blackmore’s Night - Castles And Dreams[/face]

[norfie]

[Black Dog]

[face=courier]On 25-02-2004 17:42:14 +0000 norfie wrote:

n> Because COPY-command has same behaviour?

So what? COPY command can copy folders content to NUL, Commander can't. So save me from that dubious analogies, plz - Commander is not CMD.EXE.

n> See also

What exactly should I see there?

n> copy/TCmd behaviour too - if you know their behaviour.

Don't start it, OK?[/face]

[norfie]

[Black Dog]

[face=courier]On 25-02-2004 22:32:41 +0000 norfie wrote:

n> So I don't understand why you call this a "dubious"
n> analogy.

Didn't I explain why? I guess I did.

n> Unfortunately Christian doesn't share your expectations.

Well, we moved our discussion to other place.

n> What shouldn't start?

"Know" talks - I know how Windows' command processors work in such a situation so what? That doesn't make it good for me.[/face]

[norfie]