I had been using WSL2 for about one year. The experience was terrible compared to a Linux host. (Sadly I can’t change the system on my work laptop). However, it was much better than Cygwin, msys2 and powershell - based on my experience.
If your host OS is windows and you’re interested in Linux, I think WSL2 is a good way to have a try
As a Nix fanboy I would write a Nix expression that downloads the AppImage, and also writes the desktop file with the appropriate path written into it via string interpolation. That can be done either through a NixOS configuration, or in any Linux distro using Home Manager.
WSL has replaced my use of the command prompt in Windows for anything (and I used it more than most, I think).
In my job, I develop Linux applications to support industrial automation, and WSL is capable of building and running most of what I make. It isn’t a full Linux machine, and can behave unexpectedly when trying to do things like changing certain network configurations.
So it’s great for what it’s for, really. But if you want a full VM, this isn’t really for that.
WSL in Windows Terminal is not much different from opening Konsole on any regular desktop Linux distribution. I use openSUSE Tumbleweed on WSL and I think it’s great.
That looks like it might be the monitor's own on-screen display rather than anything Puppy related. My guess is that the monitor hasn't been detected properly and Puppy is putting out a resolution that the monitor can't deal with.
Since the message says 1280x1024, either the monitor is 1280x1024 and can't deal with anything else, or it's not 1280x1024 and is being sent 1280x1024 resolution and is complaining about it.
(Or worse, it's a clock frequency error which was a real problem back in the early days of Linux.)
As for how to fix, the answer is going to be different depending on the age of the base Linux under Puppy and the graphical subsystem.
For X/X11/Xorg it's probably going to need use of the xrandr shell command, perhaps to delete the mode that is causing the problem. For Wayland, it appears that each window manager has its own xrandr equivalent. I see talk of a gnome-randr, for example.
To get to a shell in the first place, try the Ctrl+Alt+F1 key-combo. If the computer isn't frozen, that might get a text-based console login prompt. (Puppy might do things differently here though. Not sure.)
Alternatively, look up how to boot to a single-user shell by modifying GRUB options, that is, if no such option is there already.
Caveat: I am no expert. Take this under advisement. Also try web-searching some keywords. It might be there's a really simple fix for this that I don't know about.
Puppy Linux: It’s a solid live boot environment but it’s not really ideal in comparison to the major distros on a permanent install.
Alpine Linux: Since it uses musl instead of glibc, you’re likely to run into problems
Linux from scratch: Going through LFS is a great way to get a solid understanding of Linux, but unless you want to spend more time maintaining your system than using it, it’s going to be a frustrating experience.
Try one of the distros others have suggested.
Edit: I checked the specs on that hardware and yeah that’s going to struggle. Maybe Alpine would be ok. It’s fairly easy to spin up and might be fun to play with on that hardware. You’ll probably want a fairly large swap if you’re planning on using a desktop environment.
The LXQt DE is a good choice for older devices. The wiki has a guide for it but needs a slight update. It should still work but may require switching to edge.
Puppy Linux is a fine choice too if your computer is a little on the old side. Lite, Peppermint, Trisquel, antiX, and a slew of others are worth looking at.
I find it OK if you must use windows but it was fairly annoying to deal with and those annoyances are what got me to actually go for the whole Linux deal and I’m happy I switched.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.