Two folders same name???

I have this issue that keeps happening on a brand new hard drive, new
partition.. etc.
It's very odd I can recreate it from time to time I think its when I extract
files to the lower case of e:\temp or e:\Temp (see the difference).

There's no errors on the hard drive, memory has been checked multiple
times.. I just don???t get it!

Yes Windows Explorer shows both folders as if nothing is wrong! Except they
both have different Date, Date Modified, Date Accessed, Date Created time
stamps in detail view.

Command Prompt DIR cmd:
Volume in drive E is Downloads
Volume Serial Number is 82BE-52F5

Directory of E:\

06/10/2010 12:05 AM <DIR> Android
06/10/2010 12:08 AM <DIR> Cygwin
07/11/2010 11:13 AM <DIR> Downloads
06/10/2010 12:08 AM <DIR> Drivers
06/09/2010 11:59 PM <DIR> Emu
07/13/2010 12:14 AM <DIR> FrostWire
07/13/2010 12:17 AM <DIR> Incomplete
03/31/2009 09:44 PM 810 Nipsco.txt
06/10/2010 12:01 AM <DIR> Service CD
06/10/2010 12:08 AM <DIR> Shareaza
07/13/2010 03:14 AM <DIR> Temp
07/13/2010 03:12 AM <DIR> temp
06/16/2010 10:14 PM <DIR> To-Be-Burned
06/10/2010 12:03 AM <DIR> Virtual Machines
1 File(s) 881,231,658 bytes
13 Dir(s) 688,319,868,928 bytes free

ChkDsk output:
The type of the file system is NTFS.
Volume label is Downloads.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
0 percent complete. (0 of 51648 file records processed)
1 percent complete. (5165 of 51648 file records processed)
2 percent complete. (10330 of 51648 file records processed)
3 percent complete. (15495 of 51648 file records processed)
4 percent complete. (20660 of 51648 file records processed)
5 percent complete. (25824 of 51648 file records processed)
6 percent complete. (30989 of 51648 file records processed)
7 percent complete. (36154 of 51648 file records processed)
8 percent complete. (41319 of 51648 file records processed)
9 percent complete. (46484 of 51648 file records processed)
51648 file records processed.

File verification completed.
0 large file records processed.

0 bad file records processed.

0 EA records processed.

0 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
11 percent complete. (895 of 60678 index entries processed)
12 percent complete. (1789 of 60678 index entries processed)
13 percent complete. (2683 of 60678 index entries processed)
14 percent complete. (3578 of 60678 index entries processed)
15 percent complete. (4472 of 60678 index entries processed)
16 percent complete. (5366 of 60678 index entries processed)
17 percent complete. (6261 of 60678 index entries processed)
18 percent complete. (7155 of 60678 index entries processed)
19 percent complete. (8049 of 60678 index entries processed)
20 percent complete. (8944 of 60678 index entries processed)
21 percent complete. (9838 of 60678 index entries processed)
22 percent complete. (10732 of 60678 index entries processed)
23 percent complete. (11627 of 60678 index entries processed)
24 percent complete. (12521 of 60678 index entries processed)
25 percent complete. (13415 of 60678 index entries processed)
26 percent complete. (14310 of 60678 index entries processed)
27 percent complete. (15204 of 60678 index entries processed)
28 percent complete. (16098 of 60678 index entries processed)
29 percent complete. (16993 of 60678 index entries processed)
30 percent complete. (17887 of 60678 index entries processed)
31 percent complete. (18781 of 60678 index entries processed)
32 percent complete. (19676 of 60678 index entries processed)
33 percent complete. (20570 of 60678 index entries processed)
34 percent complete. (21464 of 60678 index entries processed)
35 percent complete. (22358 of 60678 index entries processed)
36 percent complete. (23253 of 60678 index en

Post in reply to: Joseph N. Stackhouse
The NTFS file system supports features of Unix, one of which is case
sensitivity. Rules preventing it only apply to Windows programs. Unix
programs running on Vista are case sensitive (see
http://en.wikipedia.org/wiki/Microso...vices_for_UNIX about
running Unix programs.)

Windows programs can bypass Windows file naming rules by prefacing filenames
with \\?\ (eg \\?\c:\folder\file.ext). Perhaps you have a program doing
that.

--
..
--

Post in reply to: Joseph N. Stackhouse

I had SUA installed once and removed it, I wonder if something is left
behind and causing it??? Wow wonder how I would find out what the hell it
is :/


The NTFS file system supports features of Unix, one of which is case
sensitivity. Rules preventing it only apply to Windows programs. Unix
programs running on Vista are case sensitive (see
http://en.wikipedia.org/wiki/Microso...vices_for_UNIX about
running Unix programs.)

Windows programs can bypass Windows file naming rules by prefacing filenames
with \\?\ (eg \\?\c:\folder\file.ext). Perhaps you have a program doing
that.

--
..
--

Post in reply to: Joseph N. Stackhouse

If you can recreate when it happens a program like
http://technet.microsoft.com/en-us/s.../bb896645.aspx may help.



--
..
--

Post in reply to: Joseph N. Stackhouse

Try dir /x to see the folder's short names. When
deleting one of them ensure that the one with
the short name TEMP remains. Maybe then the effect
is gone.

Uwe

Post in reply to: Joseph N. Stackhouse

Well I'm pretty sure the culprit is explorer.exe.. I think when you install
SUA it enables some kind of advanced file system function, but I have no
clue how to disable it or reverse it.

Perhaps I'll reinstall SUA then uninstall to see if that fixes the issue..
just happened to me again on a different drive this time, I'm surprised my
C: drive isnt riddled with duplicate folders yet.

wrote in message news:...

If you can recreate when it happens a program like
http://technet.microsoft.com/en-us/s.../bb896645.aspx may help.



--
..
--