• 1 Post
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle






  • hactar42@lemmy.mlOPtoLinux@lemmy.mlI tried, I really did
    link
    fedilink
    arrow-up
    30
    arrow-down
    1
    ·
    9 months ago

    All extremely valid points. Especially…

    1. your mindset needs to change: you‘re now a guy responsible for implementing rdp correctly, embrace open source and make it work for everyone. See the amount of influence you can actually have.

    This is the mind set I need. I was most likely so frustrated at the driver issues by this point, I probably didn’t give it the go it needed. Like I said when it came to compiling a dev branch, I just said f it. Hopefully I’ll get some time in the coming days to approach it with a fresh mindset.


  • hactar42@lemmy.mlOPtoLinux@lemmy.mlI tried, I really did
    link
    fedilink
    arrow-up
    12
    ·
    9 months ago

    It certainly made me think back to my early days of fighting IRQ conflicts in Windows ME. Or trying to get a LAN party going with mixtures of 98, 98 SE, and ME. And getting excited about the troubleshooting. I guess all these years later I’ve just gotten salty.




  • hactar42@lemmy.mlOPtoLinux@lemmy.mlI tried, I really did
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    9 months ago

    It was a strange one. I had never seen anything like it before. It could still see the hardware, but listed it as unclaimed. Nothing I could do would get it to start working. When I finally decided to reinstall, I figured I’d try a different distro.






  • I did try using the spam, same issues. I tried only using 2 of them and other combinations. Unfortunately no luck.

    I use multiple monitor RDP in Windows on a daily basis. I want to keep my work and personal systems separate, but love having 4 monitors. So I just RDP into my work laptop from my desktop. It was buggy in the past, but I’ve been using this setup for a few years now and it’s been seamless in Windows 10 & 11.