• 14 Posts
  • 58 Comments
Joined 2 years ago
cake
Cake day: July 19th, 2023

help-circle
  • Wine is a compatibility layer, it works as a translator to let windows programs run on linux. You can think of it like having a translator who allows two people with different languages to talk to each other and work together.

    WinBoat is completely different, this is actually running full windows in the background, and then only displaying the apps you want from it. There will be significantly more system resources used, and you won’t be able to run windows apps until the windows VM has started in the background, adding a startup delay. However the advantage is that it will support more software than wine does, with fewer issues.

    Wine will always be the better option when it works, but for stuff that doesn’t work this is a decent option.



  • WinBoat or WinApps might work for you. They’re very similar in function afaik, they both run a windows vm hidden in the background and integrate the windows apps alongside your Linux programs. It’s supposed to be fully compatible with all windows program except kernel anti-cheat.

    WinBoat is newer and I think offers a nicer interface and a lot easier setup, WinApps is older so may be easier to find support/documentation on. I’d probably recommend starting with WinBoat first.




  • I learned a lot by using a less common distro (solus). When I would have a problem, the solutions I could find on forums or arch wiki wouldn’t apply to my distro directly, and I would have to look into the solution for long enough to understand what needed to change in order for the solution to work.

    You can probably do this on any distro, just by not using commands you find online until you understand what they’re doing and why that might fix your problem. Arch wiki is a great resource for any distro, even though it won’t always be accurate for the distro you’re on.






  • No, I straight up had two different installation media’s fail until I went back and shut down windows fully. I’ve never run into that before on an install before.

    First I tried ZorinOS, and it would fail to even boot into the live environment. I tried multiple times and even made a new install media. Then I tried fedora silverblue, it would get into the install environment but couldn’t do any kind of partitioning etc to the drive. I then rebooted to windows, shut it down fully, and tried again. This time fedora could edit the drive partitions, and zorin could load the live environment and install.

    Previously I’ve had issues with shared drives being locked by windows, but this was the first time I’ve ever had an install fail because windows wasn’t shutdown fully. I don’t usually dual boot these days either though (I was setting up this computer for family) so I figured maybe something had changed with newer versions of windows or device security.



  • Fubarberry@sopuli.xyztoLinux@lemmy.mlPrinting on Linux
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Recently ran into an issue with Endeavour OS where the built in printer program would give errors when trying to add my network ecotank printer.

    Tried using cups terminal and it worked the first time, and is still working weeks later.

    So some of the GUI printer apps that distros ship with have issues apparently, but I don’t know the extent of it.