Some files not visible in X2 on Windows Server 2003 R2 64

Discussion & Support for xplorer² professional

Moderators: fgagnon, nikos, Site Mods

ClayGoss
New Member
Posts: 8
Joined: 2005 Mar 07, 20:50

Some files not visible in X2 on Windows Server 2003 R2 64

Post by ClayGoss »

I am setting up a WS2K3 R2 64 box.  Some files/folders are not showing in X2 that show under Windows Explorer.  Specificaly, c:\windows\system32\drivers.  Under X2, it has one file and no folders.  Under Windows Explorer, there are 153 files and two folders.
User avatar
fgagnon
Site Admin
Site Admin
Posts: 3737
Joined: 2003 Sep 08, 19:56
Location: Springfield

Post by fgagnon »

Are they 'hidden' items?
(check your setting for Show Hidden files and folders on the General tab under Tools | Options... )
User avatar
nikos
Site Admin
Site Admin
Posts: 16296
Joined: 2002 Feb 07, 15:57
Location: UK

Post by nikos »

i guess this is another limitation that a 32 bit file manager cannot do anything about
ClayGoss
New Member
Posts: 8
Joined: 2005 Mar 07, 20:50

Post by ClayGoss »

fgagnon,

No, they are not hidden in this example, but even if they were, I can "see" other hidden files and folders on this same box using X2 and on other systems using X2.

Perhaps nikos is correct and this is a limitation of 32 bit X2.

Nevertheless, I will not be using it on 64 bit - too risky.
User avatar
johngalt
Gold Member
Gold Member
Posts: 651
Joined: 2008 Feb 10, 19:41
Location: 3rd Rock

Post by johngalt »

I went to go verify this, and initially, I thought that it was just hiding files from Microsoft - but then I realized - nope - because the items I see in X2 aren't even in C:\Windows\System32\drivers.

Then it hit me - 32bit file manager / 64bit OS.  Believe it or not, X2 treats C:\Windows\System32\drivers as a 64bit path (or, at the very least, something along those lines) - and it cannot access it.  When you tell X2 to display C:\Windows\system32\drivers, it is actually displaying C:\Windows\SysWOW64\drivers.

Don't ask me why - but I just verified - the number of items, the items themselves - all match 100%.

So, Nikos, you're right - the limitations of using a 32bit app in a 64 bit OS....

[EDIT:  Added the following]

@ClayGoss - another thing - since that is a protected folder *anyway* I wouldn't recommend using any other file manager when working in there - I doubt you'll be in there that often, and when you actually need to be (such as hosts file editing, etc) then use an elevated Explorer window.
Image
ClayGoss
New Member
Posts: 8
Joined: 2005 Mar 07, 20:50

Post by ClayGoss »

The funny thing is, if I map a drive to the administrative share (C$) on this box from another system, I can see the contents of \\<machine name>\c$\windows\system32\drivers correctly USING X2!  So, this is something 64 bit windows is doing to X2 when it is run directly on the box.

Be assured, being a 27+ year IT vet, I only go into forlders for a reason.  The real questions is having a tool you can depend on.  I have "depended on" X2 for a number of years and with the exception of the 64 bit Windows, I will continue to depend on it.  

I hope the information helps someone improve X2.
User avatar
johngalt
Gold Member
Gold Member
Posts: 651
Joined: 2008 Feb 10, 19:41
Location: 3rd Rock

Post by johngalt »

Now that I didn't try - but that is interesting....

I suppose it has some sort of way of redirecting the output because it is a local copy and Windows can verify whether it is a 64bit app or not...

And as for knowing when to go into the folders- well, I didn't know you were in the field even longer than I have been - but I have to always include the caveats whenever I provide assistance or see someone doing something that could be potentially harmful - better safe than sorry.

I'll continue to depend upon X2 except for those rare occasions I need access to protected folders, it seems.
Image
snemarch
Bronze Member
Bronze Member
Posts: 94
Joined: 2008 Jan 15, 10:08

Post by snemarch »

64bit windows does a bunch of sandboxing for wow64 (ie., 32bit apps) - including redirecting certain folders for compatibility options.

See here (search for "kernel32.Wow64DisableWow64FsRedirection") for a fix... would requires Nikos to do some (trivial) updating of the sourcecode, though.
lbossom
New Member
Posts: 1
Joined: 2008 Aug 17, 22:16

Post by lbossom »

Was the suggested fix ever implemented?  I just ran into an issue where i couldn't find termserv.dll in the Windows\system32 folder.  drove me crazy trying to figure out why.  thanks!
namsupo
Member
Member
Posts: 49
Joined: 2007 Aug 29, 02:02

Post by namsupo »

You can get to the real System32 folder using Sysnative instead (eg c:\Windows\Sysnative). The folder won't appear in the tree but you should be able to type the path in manually to get to it.
User avatar
WimdeLange
Gold Member
Gold Member
Posts: 416
Joined: 2004 Aug 16, 08:41
Location: NL

Post by WimdeLange »

namsupo wrote:You can get to the real System32 folder using Sysnative instead (eg c:\Windows\Sysnative). The folder won't appear in the tree but you should be able to type the path in manually to get to it.
Whatever I try, there is no such directory on Windows 7 64 bits.
Groetjes,
  Wim de Lange
Kilmatead
Platinum Member
Platinum Member
Posts: 4797
Joined: 2008 Sep 30, 06:52
Location: Baile Átha Cliath

Post by Kilmatead »

WimdeLange wrote:Whatever I try, there is no such directory on Windows 7 64 bits.
As namsupo said, this directory will not show up on the display so you can't navigate to it; if using the x86 version of x2 type "C:\Windows\Sysnative" into the addressbar and the so-called "real" System32 folder contents will be displayed.  It's kind of a redirection around the redirection, if you catch my drift.

If using the x64 version of x2, this is not necessary.

I don't think it has a truly practical purpose other than making something visible to x86 which it shouldn't be seeing - like a 12-year-old sneaking in to see an 18's-rated film in the cinema - he may be able to watch the images on the screen, but he won't be able to make sense of the contents.