You can just use an activation script. Even though technically Windows won’t be activated using the OEM license in a VM, the license is still present on the machine. So legally Windows is still licensed. To get around the thing not automatically activating, an activation script is an easy fix.
This is a good activation script:
Imagine gate keeping Linux, the irony…
Steam works absolutely perfectly on EndeavourOS. No tweaking or anything required, just install and run. It also runs just about any game I ever tried, with troubleshooting as easy as choosing a different version of Proton from the dropdown.
The annoying thing is, a lot of modern battery protection circuits will brick themselves once they read a too low battery voltage. So not only will they not charge anymore, they will never charge, even with new cells. It’s so dumb and meant to prevent 3rd party refurbished battery packs.
Betteridge strikes again
Agreed. The downside of community developed software is it can very easily die. All too often almost all of the work is done by one or a few very active people. When they stop working on the project it’s a matter of luck if someone is willing to take it on. I’ve lost more than a few good tools that way.
The technical term is Heisenbug: https://en.wikipedia.org/wiki/Heisenbug
Obviously, there is True, False and FILE_NOT_FOUND
Most anti-cheat doesn’t take kindly to running in a VM as well, so if that’s the reason it won’t work.
Yeah I’ve had that one happen. Big team, more than a year of work, thousands of hours, over 1500 of my own hours. Internal presentation to the team at the customer end, they loved it and couldn’t wait for actual launch day. We were all so proud and everyone was happy.
Alas that day never came, the customer went bankrupt due to one of the investors pulling out. Nothing to do with us, just some bean counter did the math and decided they were better off letting the company fold.
I spoke to one of the people at the customer we had worked with throughout the project. She was devastated it was all for nothing and she lost her job as a result. By the time a new investor came around to pick up the pieces, she had found a new job. Spoke to the former ceo of the customer, he had a new job for a couple of days a week at the company that bought up the remainders. He fought to get the project going again, but the new company is very non IT focused, oldskool. So they vetoed it. I later found out one of the project leads was consulted and he had pretty much killed any chance. I always disliked that dude, but he got a pretty good deal out of it or so I’m told.
That’s just the way the cookie crumbles sometimes.
My computer is like “Kernel panic” and I’m like “Same man, same…”
Like the insect/spider kind or in my code?
Just because it works, doesn’t mean it’s right.
Including relevant XKCD as demanded by internet law: https://xkcd.com/10/
I started with Suse 5 when it came out, as something I was interested in fucking about with. I didn’t have internet access at that time, but I did had a couple of books about it (the distro came with a book as well). It was a couple of CDs and a boot floppy disk (booting from CD wasn’t really a thing).
I used it for years for software development and simple tasks like Word processing. Getting my printer working on the thing was a chore, as was basically anything. Especially without internet solving issues was sometimes simply impossible. My scanner simply didn’t work. Getting the desktop environment to run was very hard, I struggled with it for a long time. And once I got it working properly, I got a new videocard and it broke the whole thing again.
The system was very painful to use, it was super cool, but almost nothing ever worked right. And trying to fix shit usually made it worse. But once you did get it working right, it was simply awesome. And the feeling of accomplishment was awesome after finally getting something right. For software development on the terminal it was pretty awesome though. Back then I did almost everything in text mode, as I was used to DOS before that. Going into Windows was something you did only sometimes with Windows 3.11 (and even 95) and I did the same in my Linux environment. The desktop environment used up a lot of memory and was pretty slow, so I preferred the console. It was only later booting into the desktop became the norm (around the Windows 98 era).
I used Suse till version 6.1 (still have that box). I bought version 7 (still have that box as well), but never really used it.
Back then I used Debian to create small internet routers for my friends. I got an old compact computer, put in a floppy with Debian, a couple of network cards and created small NAT boxes like that. This was before NAT routers were the norm, people just had internet on 1 machine, connected directly. But as computers became cheaper, a lot of folk had more than 1 computer in the home. With no real way to share the internet connection between the different computers. Microsoft created the Internet Connection Sharing feature, but that was pretty slow, disconnected often and ate resources on your “main” PC. So my little boxes worked great, I helped people setup a home network, connected my magic box to get every system online. Also helped them setup some port forwarding for the stuff they used.
Because I used Debian a lot, I switched over to Debian for my main rig when Suse 7 released. Used Potato, Woody, Sarge and Etch a lot. Switched around between Debian and Ubuntu in the Lenny and Squeeze era. Have been using Ubuntu ever since, never really had a reason to switch. Debian compared to Suse was so nice, I really liked the way Debian did things. It made a lot more sense for me in my head compared to Suse.
As I fucked around with computers a lot, I always had both Linux and DOS/Windows machines running and even had a couple of dual boot systems. For any kind of gaming DOS/Windows was required back then and I did love to game. I do think Windows 10 will be my last Microsoft OS, since Windows 11 absolutely sucks (use it at work, I hate it). Work stuff has become less and less of an issue to get stuff done on Linux just as well as on Windows. And gaming has come leaps and bounds due to the work on the Steamdeck.
So hope to fully ditch Microsoft in the near future, even though my first ever computer in 1984 ran Microsoft firmware with Microsoft Basic being the default user interface.
As someone who has worked on embedded systems for the past 30 years: It used to be a real big deal, but for the past 10-15 years it hasn’t. We now have fully fledged multi core systems running everything. Even small embedded sensors or actuation controllers are 100+ MHz microcontrollers with oodles of flash and ram.
Now there has been an interesting turnaround with the whole chip shortage for the past years. All the young folk are at a loss, being used to just putting powerful chips all around willy-nilly. So they turn to the old folk like me to figure out designs with less chips, running busses all over and connecting dumb sensors/actuators to a central processing unit.
One thing to note, if you are using UEFI this is very unlikely to happen. It was designed from the start to have multiple boot options and Windows itself often has multiple entries. It is very rare for a Windows update to mess with any other boot options in UEFI.