XYplorer Beta Club

I'm wondering what are the advantages to using the 64 bit over the 32 bit version? As far as I can see, XYplorer is making minimal use of memory/cpu, so wondering why/when this would make a noticeable difference?

1. Quick opening of the context menu, which is modified using the Nilesoft Shell.
2. A fast script parser.
3. No need to open new windows (perform syscalls) to copy and open menus (everything is integrated into one binary).
4. The ability to use more than 4GB of RAM for heavy operations.
5. There is less impact on the system size and CPU. 32-bit applications on 64-bit Windows run on a virtual machine from MS that is stored in SysWOW64. This folder is growing with the need to run 32-bit applications.

I have successfully tested these options over the last 7 days in x64.

The biggest single reason to go 64-bit is exactly because of physical address space. Your virtual address space needs to bea multiple of the physical one:
when you hit 1GB of RAM, 32-bit virtual memory is no longer acceptable. You literally do need more virtual memory than physical.

Potentially x64 will allow to focus on expanding old limitations, focus on fixing old bugs that may have arisen due to VisualBasic limitations.

As a developer, I can say that working in a language with many limitations usually leads to the need to fix and circumvent the limitations of the LANGUAGE (and spend weeks on it) instead of having to fix the limitations and problems of the USER. And so, over time, the motivation to pull these programming problems towards yourself decreases.

Raf wrote: ↑15 Sep 2025 10:24 No need to open new windows (perform syscalls) to copy and open menus (everything is integrated into one binary).

Can you explain what this means. I don't get it..

The helper apps XY64xxx are no longer necessary to interact with 64bit Win.

k

A big reason for me is that 32-bit is legacy, has been for a long time. It's only a question of time when Windows restricts 32 bit apps.
If I was looking for a new Explorer replacement, on principle, "32bit" would be an instant NOPE.

Well, looking at the list posted by Don, I think the first and last point are - kind of - the most important for Don... First: There will be no need for work-arounds to interact with 64bit applications anymore... which are definitely going to increase in percentage rather than decrease. Less unnecessary work for him.

And well... Visual Basic (x32 version) is dead and is likely not going to be part of many future versions of Windows... actually, even the next instance of Windows might already not contain VB anymore. Best case, Don can't code anymore, worst case XY won't even run anymore.

XY64 is coded under TwinBasic. Close enough for Don to not do everything from scratch (he still had a lot of recoding to do, mostly because VB needed a lot of code to circumvent VB limitations which Don is now able to remove/recode more efficiently). Second: TwinBasic is still in active development and Don is in contact with them. So "issues" can be fixed on both sides, XY-Code and TwinBasic-Code. This is a huge plus as well.

The final release version of XY64 is supposed to be a single file (if I got Don right) which will contain the entire code necessary for XY64 (configs excluded). Which is a huge plus for users too... speaking of portablility.

A native 64-bit version is great for Windows PE as well, for example an "out of the box" ADK 64bit PE. No need for elaborate WOW64 implementations (which would otherwise be necessary to run 32bit apps in 64bit PE).