vim-win32-installer VS Sandboxie

There are official 64-bit Windows builds, you can find them here, for example: https://github.com/vim/vim-win32-installer/releases

I have no idea, but why wait? There's nothing tricky about installing nightly (I called them current in my original reply) versions. Here's a link to a Windows executable. https://github.com/vim/vim-win32-installer/releases

gVim

This is with gvim builds from vim-win32-installer?

This is already part of the official Vim (through the patches). The various Linux distributions and MacOS ship Vim with various patches. So this will be available whenever these distributions decide to include this patch. If you want to use the latest Vim without waiting for the official distribution, you can download it from: Windows: https://github.com/vim/vim-win32-installer/releases MacOS: https://github.com/macvim-dev/macvim/releases Linux: You can build the latest sources.

You can install the latest Vim release from https://github.com/vim/vim-win32-installer/releases. This installation includes vim.exe (terminal Vim for MS-Windows).

Yes, filesystem redirections are generally in place for 32-bit programs on 64-bit Windows. Another option instead of using sysnative is to install the 64-bit version of vim. That's what I do anyway. You can get it at https://github.com/vim/vim-win32-installer/releases and download the 64-bit versions.

Windows Releases: https://github.com/vim/vim-win32-installer/releases/tag/v9.0.0000

I used to use sandboxie so I could emulate multiple browser sessions without worrying about cached creds or the different portals screwing up my context. It works decently.

Use Sandboxie on Windows. It's open source these days, and isolates processes from making changes on your system. It's perfect to install and run potentially unsafe programs. Sandboxie exists since 2003, and yet we still have people in business worlds running viruses from mail attachments.

Sandboxie

You can allow applications inside a Sandboxie to communicate with each other through sockets even when network access by Sandboxie is blocked1. You can enable Sandboxie network access and use Windows firewall outside Sandboxie to block all applications inside the Sandboxie from accessing the network1. It is also possible to specify ports that cannot be accessed by boxed applications2. However, it is not possible to specify IP’s or IP ranges that cannot be accessed by boxed applications2.

In addition to just taking all privileges way from the process, like Chrome does, there's also Sandboxie [1] and the official Windows Sandbox [2]

1: https://github.com/sandboxie-plus/Sandboxie

2: https://learn.microsoft.com/en-us/windows/security/threat-pr...

2b: https://learn.microsoft.com/en-us/windows/security/threat-pr...

VirtualBox dropped 3D acceleration for old OS like XP a while back, you can see it it running "dxdiag" on your windows XP and running the tests, it will do DirectDraw only since the game is a 32 bit windows game it should run on modern windows like 10 and 11, I saw that the main problem is the DRM, so you will need a "cracked/pached" exe, I can't help with that, but do your own search, if you want to be "safe" you can try running it using something like SandBoxie-plus https://github.com/sandboxie-plus/Sandboxie/releases

With those pre-reqs, is there anything Windows Sandbox can do that Sandboxie can't?

https://github.com/sandboxie-plus/Sandboxie

Could you pls. test if the vulnerability can be mitigated by using Sandboxie-Classic (that is the free version)?

I also want to recommand this piece of small software but it's very neat, Sandboxie: https://github.com/sandboxie-plus/Sandboxie