10 years is a life time in field of computers. Companies which started 10 years ago are now billion dollar corporations.
You have to eventually move to newer version of VS as Microsoft is not going to support VS6 forever. It would be easier to port X2 code from VS6 > VS2008 > VS2011 rather than VS6 > VS2011.
Help! I'm an AI running around in someone's universe simulator.
Update - I returned the HP machine I bought earlier and built my own Core2QUad machine with much better hardware - but I still miss those shell extensions....
Any possibility of you garnering the help of one of the more code savvy 64 bit users here (and by that I mean *not* me) to help you 'port' / develop a 64bit version?
It might prove worthwhile if it allows you to move out from under the VS6 umbrella into VS2008 - I have a free copy of it from Microsoft Dreamspark because I am a student....
*I* am not missing much - I have just entered the world of 64bit processing so most of the extensions I use are 32 bit extensions - and one of which is no longer working with Vista 64bit (though it worked quite well with 32bit) - PropertiesPlus 1.65 (very very old extension).
nikos wrote:notwithstanding the dodgy things i'm doing that will port to 64 bit only after a lot of trial & error, the biggest problem is i don't have any 64-bit test machine
one day!
Send an alpha version my way. Running a quad core on winXP64/Vista64 dual boot.
Bender wrote:Well i just ended my trial of xplorer² and simply put:
Great piece of software :D and i would register it right away if there was a 64-Bit version
I really need my shell extensions since i have multiple applications which i really need in the context menu.
[cut]
Someone got any recommendations for a replacement of xplorer² until the 64 Bit version is hopefully reality? The Explorer under Vista is simply hell.
...
I went searching for a 64-bit file manager since I recently switched to 64-bit Vista and missed my shell extensions. I found SpeedCommander http://www.speedproject.de/enu/speedcommander/ .
It's very similar to xplorer2, with its own layer of idiosyncrasies and strengths. I like it very much but hope I don't have to register it. It's very expensive and I already have xplorer2! Also, if you like having a help file, you need to know German.
Count me among those hoping for 64-bit xplorer2 ...
Just to keep information in one place about 64-Bit:
Its not only extensions anymore. With an issue of failing to display certain folders and files it becomes a liability to use x² within a 64 Bit OS now.
Just a snippet from johngalt - for more head over to the thread:
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....
Bender: check the first page in this thread, about halfway down (search for kernel32.Wow64DisableWow64FsRedirection) - that shows how xplorer^2 can "show the filesystem correctly" without having to go 64-bit.
