Yeah, so I can kinda understand Haier’s position here though they probably could have just set/quoted some ToC’s on using their cloud services.
It also means that IMO the plugins weren’t offering much other than integration, and this probably would have been a product I’d have avoided even before they started acting like dicks.
Local control or bust (or ability to reprogrammed with FOSS firmware)
From what I read, this project does help integrate with HA to avoid using the Haier app, but still uses Haier’s cloud. Can anyone confirm if this was true?
There’s also a lot of other stuff that changed over time. New appliances may be more efficient, run on different (more environmentally friendly) coolant, have lead-free solder circuits, etc.
The thing is, a lot of that old stuff which was found to have health or environment issues also lasted longer. Leaded solder didn’t get burrs, for example. The components may also have been easier to repair.
But there’s also survivor bias. For every old freezer that sat in grandma’s basement for 2-3 decades many more ended up in a scrap heap.
Yeah the Docker version hated me, mainly due to it sometimes getting a bit behind on updates and then having schema mismatches if I ran an update in that missed the previous one. No issues with the Snap thus far
There are a ton that have weird fucking usernames. I was confused at first why my Bluetooth was showing BobByJimSmith4345 as the “artist” after telling it to play a song, but yeah they’ll pretty much just look whatever up by name from YouTube and play it.
Glad it worked for you. Your could also try and of the recovery options after booting from a Windows ISO. I think there are a few things that can do there that aren’t in the boot-failure recovery menus.
If not, then at least your data is safe for a reinstall
You can boot the VM from a liveCD ISO and then mount the drives to extract files (share a USB storage device to easily get them off). You could also add a second virtual disk, put an NTFS partition on it (within the VM) and copy to that if you plan to rebuild the OS drive.
If you need the offsets of the partitions you could also mount them from the disk image directly via a loopback device, but that’s a bit more complicated.
When dealing with Windows either on bare metal or VMs, I’ve often found it useful to store my more important data on a second disk so that I can easily back it up and it will survive across a wipe+reinstall of the OS.
So essentially it’s running a single computer we if it were two seperate workstations?
I could see an implementation that’s similar to those running a VM with a DGPU for gaming. User A could run a login against the primary GPU and OS. User B could run a VM with several cores allocated and the secondary GPU dedicated to the VM. If any shared did file resources in the primary OS are needed, KVM has ways to do that as well.
I find your mileage is somewhat dependent on the rest of the system config and how you access it. I kinda hate how WSL2 is based on hyper-V because the network stack for that is a pain in my ass, but tools like NMAP just don’t work on WSL1.
I have found that using something like MobaXterm is pretty awesome. The built-in X-Server lets me run a few useful graphical tools within WSL (GIMP, Wireshark, etc) without needing to install their windows counterparts.