I've had the issue of trying to run eVB programs on devices with both volatile memory and neither cmd nor wceload present, so I've cobbled together a little tool to help speed things up.
The executable needs to be placed together with above directory named VBCE, which has to contain both all the eVB 2.0 runtime files as well as regsvrce.exe.
All it does then is run regsvrce.exe /u for all DLLs that belong to the runtime. Then, it checks if .vb has been registered as a file extension in the registry, and if not, it associates .vb with the eVB executables in the current directory
This allows for the user to be able to run .vb files very quickly without any installation process. You could have the runtime on a storage card and put a link to this executable into your startup directory to just have it registered and available as soon as the system boots.
Would it make sense to add this to the SCL? It's definitely been a huge timesaver for myself at least.