xy497 Wrote:
-------------------------------------------------------
> Brilliant！
> I must log in to thank you for your solution!
> I'm in the same situation: Win10, WSL1, Ubuntu18,
> and get stuck at libnode64.
> This works for me!
Happy to hear that.
By the way, after months of struggle with WSL1 I gave up. It was especially bad at my institution - our IT security at random times kills a windows service that underlies WSL, which of course immediately kills Ubuntu and whatever runs in it, like AFNI.
But other things were annoying too.:
- one cannot use Windows mechanisms to write in Linux file system in WSL1, things get corrupted. Because of that, to share files between AFNI and Windows programs I basically had to maintain separate copies of everything, one in Linux and one in Windows, which would be synced using dedicated software
- in WSL2 writing into Linux file system from Windows side works, but then VcXsrv does not, and one has to find other (complicated) solutions to run AFNI GUI (also my institution does not offer Windows modern enough to contain WSL 2)
- there are many other problems with Ubuntu that one gets on WSL
-- it's command line-only out of the box, I get that people like it, and I am not scared by command like, I stared in MS-DOS - but it's 2021 FFS, I want to able to use a mouse and a pretty GUI!
-- it won't run 32-bit executables, and even some modern 64-bit programs have 32-bit installers to ensure that the installer runs on any system and installs either 32-bit or 64-bit version of the program. So installing such a program is impossible or one has to look for hacks.
-- some popular programs won't work, e.g. in Ubuntu on WSL 1 I wasn't able to install Atom, or get Firefox to work properly
So I switched to VM VirtualBox and I am really happy
- I get a modern OS with full GUI if I want to use GUI, but of course I can use Terminal as well
- things generally work out of the box
- including AFNI GUI without any add-ons like VcXsrv or hacks
- sharing folders with windows works perfectly (though they map into different location than in WSL)
- my institutions IT security does not kill anything
- even R installation for AFNI went better, not completely without problems, but the first solution (marutter) worked
The disadvantages is that one has to permanently sacrifice a section of the drive for VM/Linux, and VM/Linux will only utilize up to 50% half of the available CPU cores (unless I cannot find the setting to change that).
Still in my opinion much better experience and comfort than with WSL. I heard that most recent versions of Windows (latest 10 or maybe 11 ?) made significant progress with WSL, but - again thanks to my institution which keeps our Windows pretty old - I don't know how it works with AFNI.
