Awesome! A grocery store opened within biking distance from me this winter and I’ve been considering something like this for grocery runs. I’ll check out the playlist over the next few days.

What improvements are you considering?

Then call out the bullshit, don’t just call the whole thing bullshit with nothing to back it up. That just makes you look like a cynical asshat.

More than 15 years ago I ended up with one of those in a C++ program.

I’m sure the real ssue was somewhere else in the code, but if I removed one specific comment (or maybe it was a print to console, it was forever ago) it would segfault, otherwise it ran fine.

Sounds like it’s on its last legs, especially if one of the partitions locked up file explorer to that degree. Too much messing with it could kill it for good.

Your best bet would be to do a low level backup of the whole drive using something like dd. That’s a Linux utility, but I believe there are open source equivalents that you can run on Windows. You might see them called sector level backup tools. Basically, they don’t care how fucked a drive is, they won’t try to make any sense of it, they’ll just copy it exactly to a .ISO file. Corruption and all. That should be the last time you actually plug the physical drive in.

Then make a copy of the ISO file to tinker with without risking losing any data. You can always go back to the original ISO copy if you fuck something up.

There are a ton of different tools you could use to attempt to recover data from that ISO, but the first step is to make sure you aren’t trying to build your workbench on top of a time bomb.

It’s only a thing if you leave smartscreen on. Think it might also only apply to stuff downloaded through Edge, but don’t quote me on that.

Depends on the program. I’ve got a handful of that old on CDs that still install fine. Checked when I was backing them up to ISO. There’s little bits of weirdness and unintended behavior while running them now, but they still install and run to a fairly acceptable degree.

That experience varies wildly though. Wine tends to handle things better and more consistently.

If you’re not active on the comms on awful.systems, I think you’d like it. Most users are aware of Yarvin etc.

!techtakes@awful.systems

I know you’ve been told as responses to your other comments, but for anyone else browsing, he didn’t just swap drives. He did fresh installs of the correct versions for the hardware.

It seems that he likely did this during a period where the nVidia drivers were not supported, which still isn’t a mark in the favor of Bazzite that something like that can be easily missed by the end user.

I think he got hung up on how long this took him personally when he was editing, and used that to justify a long fucking edit. I have no idea how he managed to strecth this into a freaking hour.

It’s definitely a waste of time that he should have stopped after the first one or two where they obviously weren’t working.

I still think it’s an important demonstration of where things could (and should) be made clearer to the end user.

Like a lot of technical stuff, there’s kind of an absurd expectation that caveats can be completely omitted and it’s on the end user to figure out. I make tons of documentation at my job as a sysadmin. I get that you can’t possibly catalog every edge case and caveat, but from what I can tell, this issue with the Bazzite images was known and happens often enough that the cause is well known. It’s a failing by the maintainers that they don’t have a basic warning mechanism built in for this scenario.

A warning on the download page. A warning in the updater. Better controls in the release tools so the nVidia release can stay on the last supported version until the new drivers work.

Anything besides just expecting the end user to magically know that the thing labelled as working for their situation does not in fact work at the moment.

Yeah, I hope he does a part 2 where he gets some help to get it working, summarizes how, and re-runs the benchmarks.

Sounds like useful post-install steps that should be made clear for the nVidia release of Bazzite ;)

Yeah, the video’s length is absurd. I enjoy his content, but an hour of watching clips of the same damn benchmarks isn’t particularly interesting. Definitely should have been cut down further, imo.

Anyway.

I think as people with technical background, we need to understand that for Linux to eventually overtake Windows it needs to work for the average knuckledragger.

Wade didn’t have to google how to install the driver on Windows in advance (as far as we know, that’s some important clarification that’s needed).

Bazzite is supposed to be the distro for minimum hassle gaming, and they even have specific distro releases for these old nVidia cards, which he used.

What is the point of having a specific release for that hardware if it doesn’t work? If users have to take extra steps after the install, there should be something that pops up on first boot to direct them to it, or a warning about this when you download the iso.

It shouldn’t be on the user to have an issue first, then guess at what they need to search to get useful info.

I get that Linux maintainers are loathe to turn the experience into “Windows Lite” where it reminds you to wipe your own ass with their proprietary paper, but at some point I think we need to accept a bare minimum level of hand holding can be useful for user experience.

How hard would it be for a message box to pop up: You’re using NVM/llvmpipe and you may not be getting the full support for your GPU. Click here for more info. Click here to never show this again.

I think he does regular drumming streams too.

The change to “Microsoft 365” has been the case for years now. I had hoped the context made it clear that this was regarding the claim they had changed the name to Copilot.

Edit: Since there’s nothing that goes together quite like Linux enthusiasts and pedanticness, here’s a correction-

Microsoft split off a subscription based version of their Office suite of programs a number of years ago, calling it Microsoft Office 365. They maintained more standard non-subscription versions for a few years alongside 365, while very clearly trying to push people to the subscription model.

After that, they stopped releasing new standard versions, leaving Microsoft Office 365 (the subscription) as the only option for ongoing support.

After that after that, they renamed Microsoft Office 365 to just Microsoft 365, although the Office branding/tagline/wording is still present in a number of places (just not on office.com itself, apparently).

One of the 365 license options allows for access to only the webapp versions of the suite instead of the native program versions. Apparently they offered a “Microsoft Office App” specifically for users on this license that would simply link to the webapp versions of the suite.

This “Microsoft Office App” that served as a link to the webapps is what has been renamed to Copilot whatever the fuck, not the suite of webapps and native programs themselves. That remains named Microsoft (Office) 365.

Microsoft’s original and horribly misleading blog post that started this shit here.

The Verge’s article laying things out more clearly and featuring direct statements from an M$ exec to The Verge trying to clarify things here.

I sure hope that’s true, but I’ve seen more companies switch to lower cost licenses with restrictions like only being able to use the webapp than I have seen switch to LibreOffice.

As long as Microsoft keeps offering ways to easily disable the shit nobody asked for in corporare environments/deployments I’m afraid the stranglehold will persist.

I would have hoped the context made it clear that I’m talking about the claim they renamed it to Copilot.

Nothing “half right” about it, but thanks for the pedanticness I guess.

Edit: Since there’s nothing that goes together quite like Linux enthusiasts and pedanticness, here’s a correction-

Microsoft split off a subscription based version of their Office suite of programs a number of years ago, calling it Microsoft Office 365. They maintained more standard non-subscription versions for a few years alongside 365, while very clearly trying to push people to the subscription model.

After that, they stopped releasing new standard versions, leaving Microsoft Office 365 (the subscription) as the only option for ongoing support.

After that after that, they renamed Microsoft Office 365 to just Microsoft 365, although the Office branding/tagline/wording is still present in a number of places (just not on office.com itself, apparently).

One of the 365 license options allows for access to only the webapp versions of the suite instead of the native program versions. Apparently they offered a “Microsoft Office App” specifically for users on this license that would simply link to the webapp versions of the suite.

This “Microsoft Office App” that served as a link to the webapps is what has been renamed to Copilot whatever the fuck, not the suite of webapps and native programs themselves. That remains named Microsoft (Office) 365.

Microsoft’s original and horribly misleading blog post that started this shit here.

The Verge’s article laying things out more clearly and featuring direct statements from an M$ exec to The Verge trying to clarify things here.

That was horrendously misleading clickbait.

The changed the name of some stupid as shit “app” that only exists to open links to the Office programs on the web as webapps, which was apparently called “Microsoft Office App”. They did not change the name of Microsoft Office.

Simultaneously not as bad, but even dumber.

Edit: Since there’s nothing that goes together quite like Linux enthusiasts and pedanticness, here’s a correction-

Microsoft split off a subscription based version of their Office suite of programs a number of years ago, calling it Microsoft Office 365. They maintained more standard non-subscription versions for a few years alongside 365, while very clearly trying to push people to the subscription model.

After that, they stopped releasing new standard versions, leaving Microsoft Office 365 (the subscription) as the only option for ongoing support.

After that after that, they renamed Microsoft Office 365 to just Microsoft 365, although the Office branding/tagline/wording is still present in a number of places (just not on office.com itself, apparently).

One of the 365 license options allows for access to only the webapp versions of the suite instead of the native program versions. Apparently they offered a “Microsoft Office App” specifically for users on this license that would simply link to the webapp versions of the suite.

This “Microsoft Office App” that served as a link to the webapps is what has been renamed to Copilot whatever the fuck, not the suite of webapps and native programs themselves. That remains named Microsoft (Office) 365.

Microsoft’s original and horribly misleading blog post that started this shit here.

The Verge’s article laying things out more clearly and featuring direct statements from an M$ exec to The Verge trying to clarify things here.

For the desktop app that only opens links to the webapp versions of Office

They did not fucking rename Microsoft Office. It’s dumb enough without everyone uncritically parroting the misleading clickbait.

Why in the fuck was there even a desktop app to just open the webapp links? That’s dumb as shit! Why the fuck would anyone care about it enough to rename it? That’s even dumber! Why would…

You get the picture.

The reality isn’t as bad, while simultaneously being even more dumb.

Edit: Since there’s nothing that goes together quite like Linux enthusiasts and pedanticness, here’s a correction-

Microsoft split off a subscription based version of their Office suite of programs a number of years ago, calling it Microsoft Office 365. They maintained more standard non-subscription versions for a few years alongside 365, while very clearly trying to push people to the subscription model.

After that, they stopped releasing new standard versions, leaving Microsoft Office 365 (the subscription) as the only option for ongoing support.

After that after that, they renamed Microsoft Office 365 to just Microsoft 365, although the Office branding/tagline/wording is still present in a number of places (just not on office.com itself, apparently).

One of the 365 license options allows for access to only the webapp versions of the suite instead of the native program versions. Apparently they offered a “Microsoft Office App” specifically for users on this license that would simply link to the webapp versions of the suite.

This “Microsoft Office App” that served as a link to the webapps is what has been renamed to Copilot whatever the fuck, not the suite of webapps and native programs themselves. That remains named Microsoft (Office) 365.

Microsoft’s original and horribly misleading blog post that started this shit here.

The Verge’s article laying things out more clearly and featuring direct statements from an M$ exec to The Verge trying to clarify things here.

Just run the Windows device using wired internet on a different (and isolated) subnet from everything else of yours and turn off wifi and bluetooth on it. Use a wired headset or a dedicated dongle like Jabra has for their headsets. That would prevent it from identifying other devices nearby.

Beyond that, just don’t do any personal shit on your work device. If you’re providing your own Windows work device, then do it in a VM as already said.

If your workplace allows WSL, then the main benefit is you could use more familiar software/tools through it. Your workplace is likely to be doing a hell of a lot more data collection than Microsoft anyway.

Just going off tech support knowledge:

It’s a configuration parser error, according to the error window title bar. I’d start there. I would expect there’s something messed up with your configuration(s). Maybe back them up and reset to default, see if that stops it.

Given that the error is triggering in a .Net library, a repair/reinstall of those wouldn’t hurt either, but it probably won’t fix your issue.