Discrepancy in system directories showing up

[Mesh]

In Windows 7 x64, if you use Explorer and go to C:\Windows\System32\Drivers, you will see many drivers, along with the "etc" directory which contains the system "hosts" file.

However, if you go to the same directory in XY, you'll see three files:

gm.dls
gmreadme.txt
wimmount.sys

... and *no* "etc" directory.

Now, I know that Windows 7 throws a lot of voodoo into its file system (Junction Points, etc...), but can someone help me understand what's going on and where the "etc" folder really is? Or if it is really there, why can't XY see it?

[admin]

WOW64-Redirection...

[Mesh]

WOW64-Redirection...

Is that the same as a Junction Point? Because I have Junction Points showing up in a different color on the tree and list, but there's no indication that there's anything special about this directory.

If it is different, it would be nice if XY had some way of showing it, and an option to view it with the redirect on, or to see it how it actually is (context menu choosable, so it can quickly be toggled). Otherwise, XY can't be used as a replacement for Explorer.

[TheQwerty]

Take a look here: http://www.xyplorer.com/xyfc/viewtopic.php?f=3&t=3833

It's some Windows magic going on in the background because in reality there are two "System32" directories one for 32-bit files and one for 64-bit files.

As Explorer is a 64-bit app it opens the 64-bit version.
XYplorer cannot become a 64-bit app yet so it depends on whether or not WOW-64 redirection is enabled to determine which one it opens.

As I described in that other thread you can use "Sysnative" to easily access either version without having to change your redirection settings.

[Mesh]

As I described in that other thread you can use "Sysnative" to easily access either version without having to change your redirection settings.

I'm familiar with that Microsoft article. That was intended to route calls from that address - for example, if you use AutoHotkey, or are specifying a command line somewhere. I'm not sure they ever intended for you to actually *create* that directory. I'd be worried that it would screw something up. Are you aware of any Microsoft articles describing that procedure?

[TheQwerty]

I'm familiar with that Microsoft article. That was intended to route calls from that address - for example, if you use AutoHotkey, or are specifying a command line somewhere. I'm not sure they ever intended for you to actually *create* that directory. I'd be worried that it would screw something up. Are you aware of any Microsoft articles describing that procedure?

No but, I've been using it without issue for months now and cannot find any mention of problems with actually creating the directory.

Though I'm curious why you reported this discrepancy if you're familiar with that article?

[Mesh]

Though I'm curious why you reported this discrepancy if you're familiar with that article?

Because I wasn't aware that it could be used for *browsing*. I thought it was only useful for command line calls.

[Mesh]

Okay, I need a bit of help.

On Win 7 x64, if you want to edit the "hosts" file, and you use Windows Explorer, it's in "C:\Windows\System32\drivers\etc".

However, if you use XY, that directory doesn't exist. Okay, probably just some directory redirection. However, when using XY to do a search of the entire C Drive, you can't find it. There is a "hosts" file that shows up, but it's not the same one.

I used Windows Explorer and added a custom named text file in that directory to use as a homing beacon for XY (to make sure I got the correct directory). But XY couldn't find the file at all!

What's going on here, and why is XY not capable of accessing this folder and the files in it?

[Mesh]

Has anybody had any luck in finding the "hosts" file on Win 7 x64 using XY? I still can't find it.

[TheQwerty]

Disable WOW64 redirection and you'll find it.
Or if you applied the steps from the other thread it's in sysnative.

[Mesh]

Disable WOW64 redirection and you'll find it.
Or if you applied the steps from the other thread it's in sysnative.

I'm not convinced the steps from the other thread are safe, as sysnative was never intended to be an actual directory, only a redirection pointer.

As for disabling WOW64 redirection, to be done safely, it has to be done by the calling thread, and not having the source code for XY, that's beyond my means.

[TheQwerty]

As for disabling WOW64 redirection, to be done safely, it has to be done by the calling thread, and not having the source code for XY, that's beyond my means.

What, you don't trust View->Show Items->WOW64 Redirection in XY either?

[Mesh]

What, you don't trust View->Show Items->WOW64 Redirection in XY either?

<facepalm>

I didn't know XY could do that. I only recently moved to 64 bit, and I don't recall ever seeing that option in XY before.

Thank you for pointing that out. That did the trick perfectly.

[j_c_hallgren]

<facepalm>
I didn't know XY could do that. I only recently moved to 64 bit, and I don't recall ever seeing that option in XY before.

Even I, who is still on W2K, knows about that option...but that's maybe cause I've had to point it out in replies here to others...

[admin]

What, you don't trust View->Show Items->WOW64 Redirection in XY either?

<facepalm>

I didn't know XY could do that. I only recently moved to 64 bit, and I don't recall ever seeing that option in XY before.

Thank you for pointing that out. That did the trick perfectly.

But thanks for the word facepalm! I didn't know one could say that.