Please explain this anomaly - c:\Windows\System32\oobe
Moderators: white, Hacker, petermad, Stefan2
Please explain this anomaly - c:\Windows\System32\oobe
As a bit of time waster, I attempted to modify Win7Pro x64, login picture (http://www.blogsdna.com/2698/you-can-customize-windows-7-logon-background-officially.htm)
However, I noticed an anomaly which I hope someone can explain.
In command.exe (and I see same in Windows Explorer):
c:\Windows\System32\oobe>dir
Volume in drive C is Corsair
Volume Serial Number is 9074-F0E3
Directory of c:\Windows\System32\oobe
01/04/2011 03:22 AM <DIR> .
01/04/2011 03:22 AM <DIR> ..
14/07/2009 12:38 PM 74,240 audit.exe
11/06/2009 08:07 AM 2,359,352 background.bm
21/11/2010 12:27 AM 334,336 cmisetup.dll
14/07/2009 12:41 PM 38,912 diagER.dll
14/07/2009 12:41 PM 158,720 diagnostic.dl
14/07/2009 12:40 PM 91,136 DU.dll
22/03/2011 09:16 PM <DIR> en-US
20/11/2010 02:53 PM 637,042 FirstUXRes.WI
01/04/2011 03:22 AM <DIR> info
21/11/2010 12:24 AM 71,168 msoobe.exe
21/11/2010 12:27 AM 1,161,728 msoobeui.dll
14/07/2009 12:39 PM 59,904 oobeldr.exe
14/07/2009 12:41 PM 81,920 pnpibs.dll
05/11/2010 01:18 PM 1,577 setup.cfg
21/11/2010 12:25 AM 266,240 Setup.exe
14/07/2009 12:39 PM 24,064 setupsqm.exe
21/11/2010 12:27 AM 57,856 spprgrss.dll
14/07/2009 12:41 PM 1,002,496 unbcl.dll
14/07/2009 12:33 PM 3,051,008 W32UIImg.dll
14/07/2009 12:33 PM 260,608 W32UIRes.dll
14/07/2009 12:41 PM 58,368 wdsutil.dll
21/11/2010 12:27 AM 577,536 win32ui.dll
21/11/2010 12:25 AM 109,568 windeploy.exe
14/07/2009 12:41 PM 59,392 WinLGDep.dll
21/11/2010 12:27 AM 2,199,040 winsetup.dll
23 File(s) 12,736,211 bytes
4 Dir(s) 86,529,392,640 bytes free
However, in Total Commander, I only see in directory c:\Windows\System32\oobe\: en-US <dir>, cmisetup.dll and background.bmp
So, that's only 2 files instead of 23 and only 1 directory instead of 2.
(Of course, I have "Show hidden/system files (for experts only!) ticked"
Obviously what Total Commander and Windows is showing is a different location, but how does that work?
However, I noticed an anomaly which I hope someone can explain.
In command.exe (and I see same in Windows Explorer):
c:\Windows\System32\oobe>dir
Volume in drive C is Corsair
Volume Serial Number is 9074-F0E3
Directory of c:\Windows\System32\oobe
01/04/2011 03:22 AM <DIR> .
01/04/2011 03:22 AM <DIR> ..
14/07/2009 12:38 PM 74,240 audit.exe
11/06/2009 08:07 AM 2,359,352 background.bm
21/11/2010 12:27 AM 334,336 cmisetup.dll
14/07/2009 12:41 PM 38,912 diagER.dll
14/07/2009 12:41 PM 158,720 diagnostic.dl
14/07/2009 12:40 PM 91,136 DU.dll
22/03/2011 09:16 PM <DIR> en-US
20/11/2010 02:53 PM 637,042 FirstUXRes.WI
01/04/2011 03:22 AM <DIR> info
21/11/2010 12:24 AM 71,168 msoobe.exe
21/11/2010 12:27 AM 1,161,728 msoobeui.dll
14/07/2009 12:39 PM 59,904 oobeldr.exe
14/07/2009 12:41 PM 81,920 pnpibs.dll
05/11/2010 01:18 PM 1,577 setup.cfg
21/11/2010 12:25 AM 266,240 Setup.exe
14/07/2009 12:39 PM 24,064 setupsqm.exe
21/11/2010 12:27 AM 57,856 spprgrss.dll
14/07/2009 12:41 PM 1,002,496 unbcl.dll
14/07/2009 12:33 PM 3,051,008 W32UIImg.dll
14/07/2009 12:33 PM 260,608 W32UIRes.dll
14/07/2009 12:41 PM 58,368 wdsutil.dll
21/11/2010 12:27 AM 577,536 win32ui.dll
21/11/2010 12:25 AM 109,568 windeploy.exe
14/07/2009 12:41 PM 59,392 WinLGDep.dll
21/11/2010 12:27 AM 2,199,040 winsetup.dll
23 File(s) 12,736,211 bytes
4 Dir(s) 86,529,392,640 bytes free
However, in Total Commander, I only see in directory c:\Windows\System32\oobe\: en-US <dir>, cmisetup.dll and background.bmp
So, that's only 2 files instead of 23 and only 1 directory instead of 2.
(Of course, I have "Show hidden/system files (for experts only!) ticked"
Obviously what Total Commander and Windows is showing is a different location, but how does that work?
Oops.. Does sticky http://ghisler.ch/board/viewtopic.php?t=25743 apply to me? Oh.. bugger, it does.
So... to avoid confusion, wouldn't it make sense to have 64bit version of TC?
So... to avoid confusion, wouldn't it make sense to have 64bit version of TC?
It would make a lot more sense if the sticky's title was not "Explorer + Total Commander: Content of system32 different" but rather "Win x64: Windows Explorer's and Total Commander's content of /Windows/System32 is different".Hacker wrote:We probably need a sticky for the 64-bit version.
Perhaps that'll help reduce "x questions for a TC x64/day" tally. Wonder which takes more effort - complaining or correcting?
Hello, AlexF.
Tried to prefix "Win X64" to the current thread title. Yet, it is not possible, the title would exceed the maximum possible title length (80 characters). This means that it would be necessary to completely rephrase the title.
Basically, nothing wrong with doing so. Yet, whatever the title will be, there will always be readers who will not realize that the problem which they experience when using Total Commander (32-bit) on Windows (64-bit) is covered by this thread.
Hence my question: What to do now? Leave the title as it is? Rephrase it? If so, how?
Kind regards,
Karl
Tried to prefix "Win X64" to the current thread title. Yet, it is not possible, the title would exceed the maximum possible title length (80 characters). This means that it would be necessary to completely rephrase the title.
Basically, nothing wrong with doing so. Yet, whatever the title will be, there will always be readers who will not realize that the problem which they experience when using Total Commander (32-bit) on Windows (64-bit) is covered by this thread.
Hence my question: What to do now? Leave the title as it is? Rephrase it? If so, how?
Kind regards,
Karl
Hi, Sir_SiLvA.
Whatever we do, whatever the title may be, however complete and concise at the same time the content may be, we will never get around the problem that readers
Cheers,
Karl
Whatever we do, whatever the title may be, however complete and concise at the same time the content may be, we will never get around the problem that readers
- will not realize that they use a 32-bit application (Total Commander) on a 64-bit Operation System, i.e. on a 64-bit Windows version
- will not realize this particular sticky applies to them as well
- will not find this particular sticky
- will search for a search string which is not used in this particular sticky
- will not use the forum search function at all
- etc pp
Cheers,
Karl
Karl, since the issue is entirely with x64 OS, it must be in the title. Else, you can't point at the next OP who starts his own thread, like I did.karlchen wrote:Hence my question: What to do now? Leave the title as it is? Rephrase it? If so, how?
No-one is doing anything wrong. Content is just unexpected.MVV wrote:Maybe "Windows x64: Wrong contents of Windows\System32 folder"?
Grammatically incorrect and don't make much sense.Sir_SiLvA wrote:2karlchen
I think best would like Hacker said a Sticky with a Title like:
"TC32Bit & 64Bit OS - the problems there are"
No, it is really wrong. Since Windows redirects folder, it shows contents of another folder - so it is really wrong. Also TC shows some fake folders there that are absent even in SysWow64 folder (I mean folders like drivers/etc in last TC versions) so this folder doesn't shows right contents of any really existing folder. And, I think that if user comes here to post a problem about incorrect contents of this folder, he will understand such title.AlexF wrote:No-one is doing anything wrong. Content is just unexpected.MVV wrote:Maybe "Windows x64: Wrong contents of Windows\System32 folder"?
BTW, we can add a lot of sticky topics with different titles (e.g. in bugs subforum too) that will point to existing topic.
But your 'unexpected' is correct too. Also 'strange' may be used here, all theese titles match title length limit:
Code: Select all
Windows x64: Unexpected contents of Windows\System32 folder
Windows x64: Strange contents of Windows\System32 folder
As there will be an 64 Bit version of TC available in (hopefully) near future and this one will not be touched by redirection:
Regards
Holger
Code: Select all
Explorer(64Bit) <-> TC(32Bit): Content of System32 different
Holger
Hey, guys.
Do you realize that our little discussion just illustrates what I tried to explain before? (And I would be amazed if we really disagreed on this point.): There is not the one and only thread title which can explain beyond any doubt to every reader what the thread is all about. The more so as we are limited to 80 characters.
As stated before: I really do not mind altering the thread title.
From my point of view the current title "Explorer + Total Commander: Content of system32 different" and all the suggestions which you have made are all equally good or equally imperfect - whichever way you prefer to look at them.
So which of the suggested titles should win?
Who should decide? The thread creator? A random moderator? The moderator group?
Cheers,
Karl
Do you realize that our little discussion just illustrates what I tried to explain before? (And I would be amazed if we really disagreed on this point.): There is not the one and only thread title which can explain beyond any doubt to every reader what the thread is all about. The more so as we are limited to 80 characters.
As stated before: I really do not mind altering the thread title.
From my point of view the current title "Explorer + Total Commander: Content of system32 different" and all the suggestions which you have made are all equally good or equally imperfect - whichever way you prefer to look at them.
So which of the suggested titles should win?
Who should decide? The thread creator? A random moderator? The moderator group?
Cheers,
Karl
Hi, guys.
Disregarding the current title, we have got the following suggestions:
Cheers,
Karl
--
Corrected:
The actual title length limit must be 60 characters, not 80.
It is simply impossible to change the thread title to "Windows x64: Explorer(64-Bit) <-> TC(32-Bit): Content of System32 different". The edit box will drop everything starting with the 61st character.
Therefore the title will have to be shortened to "Windows x64: Explorer vs TC: Content of System32 different".
Disregarding the current title, we have got the following suggestions:
- Windows x64: Wrong contents of Windows\System32 folder
- Windows x64: Unexpected contents of Windows\System32 folder
- Windows x64: Strange contents of Windows\System32 folder
- Explorer(64Bit) <-> TC(32Bit): Content of System32 different
Translated into German this title still does not exceed the 80 characters' limit. So the German and the English sticky thread will still have the same title.Windows x64: Explorer(64-Bit) <-> TC(32-Bit): Content of System32 different
Cheers,
Karl
--
Corrected:
The actual title length limit must be 60 characters, not 80.
It is simply impossible to change the thread title to "Windows x64: Explorer(64-Bit) <-> TC(32-Bit): Content of System32 different". The edit box will drop everything starting with the 61st character.
Therefore the title will have to be shortened to "Windows x64: Explorer vs TC: Content of System32 different".