Preview Folders

[nas8e9]

Let's see if I understand this correctly....

XYPlorer is a 32 bit application and therefore can only load 32 bit extensions -- Yes?

VSO Resizer is a 32 bit application (written in 2007/2008 for the version I am using) so it could load in XYPlorer if XYPlorer wanted to load it (based on its "bittedness")-- Yes? BTW, This app ran quite well on my XP 32 bit system and I simply copied the file over to my Win 7 64 bit system so I KNOW it is 32 bit.

I am thinking that there must be some other reason besides "bittedness" that XYPlorer has decided not to load this particular shell extension. Does that seem logical?

Spud

The problem, based on you not installing the application but just copying it over, is most likely the registration of the shell extension: the setup program would normally do that.

If you can identify the .dll-file containing the shell extension, you could try registering it manually through running:

Code: Select all

regsvr32 ShellExt.dll

...from an elevated command prompt in the folder containing that file. Failing that, "officially" installing the application through its setup program should do the trick.

[j_c_hallgren]

The problem, based on you not installing the application but just copying it over, is most likely the registration of the shell extension: the setup program would normally do that.

I believe that nas8e9 is on the right track...because unless the extension has been registered, it's just another file on disk and is sorta like an appl w/o any shortcuts to it...you know it's there but Windows doesn't.

[daSpud]

The problem, based on you not installing the application but just copying it over, is most likely the registration of the shell extension: the setup program would normally do that.

If you can identify the .dll-file containing the shell extension, you could try registering it manually through running:

Code: Select all

regsvr32 ShellExt.dll

...from an elevated command prompt in the folder containing that file. Failing that, "officially" installing the application through its setup program should do the trick.

I tried that and it made no difference after registration.

But, would it not have been registered if Windows Explorer could show it in the context menu? Also if it were not registered would it still show up in NirSoft's Shell Extension Viewer: http://www.nirsoft.net/utils/shexview.html? It also shows in the context menu of Directory Opus just as I expected.

The only place so far that it has not shown up is XYPlorer's context menu for a JPG file.

Spud

[nas8e9]

The problem, based on you not installing the application but just copying it over, is most likely the registration of the shell extension: the setup program would normally do that.

If you can identify the .dll-file containing the shell extension, you could try registering it manually through running:

Code: Select all

regsvr32 ShellExt.dll

...from an elevated command prompt in the folder containing that file. Failing that, "officially" installing the application through its setup program should do the trick.

I tried that and it made no difference after registration.

But, would it not have been registered if Windows Explorer could show it in the context menu? Also if it were not registered would it still show up in NirSoft's Shell Extension Viewer: http://www.nirsoft.net/utils/shexview.html? It also shows in the context menu of Directory Opus just as I expected.

The only place so far that it has not shown up is XYPlorer's context menu for a JPG file.

Spud

On 64-bit Windows, only the 64-bit version of Directory Opus can be installed. Combined with Windows Explorer being 64-bit by definition in that case, your app:
1. has a 64-bit shell extension;
2. and has only that one registered.

Things get a bit complicated at this point, because some 32-bit apps install only a 64-bit shell extension when installed on 64-bit Windows, meaning a setup-based install may not solve this. You could try checking your 32-bit Windows installation, determining the .dll containing the 32-bit shell extension and copying that over and registering it.

[daSpud]

On 64-bit Windows, only the 64-bit version of Directory Opus can be installed. Combined with Windows Explorer being 64-bit by definition in that case, your app:
1. has a 64-bit shell extension;
2. and has only that one registered.

Things get a bit complicated at this point, because some 32-bit apps install only a 64-bit shell extension when installed on 64-bit Windows, meaning a setup-based install may not solve this. You could try checking your 32-bit Windows installation, determining the .dll containing the 32-bit shell extension and copying that over and registering it.

When the resizer runs it shows in the Task manager with *32 beside its name. I don't know how to tell if the DLL itself is 32 or 64 bit, but this is a simple little resizer that I seriously doubt was ever written or considered for 64 bit (it is from 2007 and 64 bit systems were not as prevalent then).

I did copy the resizer from my 32 bit system and I did register it as you suggested.

From a MS page on 64bit:
No Mixed 64-Bit/32-Bit Processes
64-bit programs cannot load and call 32-bit MDAC.
64-bit Microsoft Internet Explorer cannot load 32-bit ActiveX controls.
The 64-bit shell cannot load 32-bit Inproc shell extensions.
32-bit installer programs cannot load and register 64-bit DLLs.

"Inproc shell extension" implies that there is another kind? If there were not any other kind would they then say "32 bit shell extensions"? I don't know. This has just passed my limits of understanding.
- - - - - - -
Time passes with a new report....

I just tried XYPlorer on my XP laptop (32 bit) and it does load the very same resizer in the context menu. I also noticed that Search Everything's context menu will not load the resizer on my 64 bit system, but will load it on XP 32 bit.

I don't know what is going on, but I do now know that XYPlorer is not being totally anti-VSO Resizer.

I see that a number of my favorite extensions are not loaded (no Ultra Edit for example) by XYPlorer (64 bit UE is installed). I guess all I can do is wait for the world to catch up to 64 bits (and then 128 will be starting).

Spud