That is a good option as well, but for experienced users only and only if you have a lot of RAM and a UPS (or on a laptop with a working battery). Otherwise, power failiures mess that thing up.

You can make a swap file on the main partition where Linux is installed, that’s not a problem.

For Linux, if you’re a beginner, EXT4. Experienced users - BTRFS.

And ntfs-3g is even better at writing on NTFS than Windows is. There are fragmentation examples online, Windows makes a fragmented mess while ntfs-3g takes great care regarding fragmentation. Plus reads/writes a lot faster than Windows does.

Yep, use NTFS. You can access it in both Windows and Linux. You’ll need to install ntfs-3g in Linux. It comes bundled in most mainstream distros, but just in case.

Windows: 150GB. Linux: 100GB. The rest: Data.

And don’t forget to disable hybrid shut down in Windows.

Don’t opt for an LTS distro for gaming (or even for regular desktop use), opt of a rolling release one… or at least one that has 2 or 3 regular yearly releases.

It’s grainy. Grain always takes a lot in size.

The prompt doesn’t run as admin. Try this command, should open up a second command prompt as admin: runas /username:{AdminUsername} cmd.

Sorry, chkdsk.exe /f C:… it was late, I was tired 🤷.

Error: 87 cleanup-image option is unknown

Try it without the cleanup-image switch.

Holding back packages can do that. Not in sync with what the AUR has to offer is just asking for trouble.

🙏

It may be just file corruption. Try running chdsk.exe /f C: in the command prompt. If that doesn’t work, try dism.exe /online /cleanup-image /restorehealth. Keep your virtual NIC online for the second command, it may try to download updates from MS if local files are corrupt and the WinSxS backups are corrupt as well.

If you were defrauding people, it wouldn’t matter what tool you used.

Stays silent while coding the JezuzLovezU worm…

Feel the pain 😂.

Luckily, none of us will be there.

I have the original source for some of them, but very few, like maybe 1 or 2%.

Doesn’t matter, I’m just gonna redownload them in flac, store them on optical media as flac and keep them as HE-AAC on my NAS for local playback. It’s the only option that’s acceptable in my mind.

Well, it’s not a hardware problem in that case 😉. Good thing you fixed it 👍.

You should also probably try and see if the same thing happens in a VM. The flash drive might be failing and I don’t think Void does CRC checks of files when copying them… definitely not when funning them, like the installer for example.

EDIT: I remember the installer bringing me back to the partitioning setup, but that’s because I partition manually, not through the Void installer, so the installer thinks that that step is skipped. No worries though, just go to the end of the installer setup and continue with the provided settings. If an adequate target partition has been set, it will install Void.

What, they don’t offer binaries 🤨?

Well, at least there is one thing that makes building on Void easier. xbps-src works with templates, so you could just write the template or write on GitHub for help from someone in the Void community. I’ve asked for help many times and people are usually very helpful ☺️. Once you have the template, updating the VST is a matter of just chaging a few things in it (version, hash, etc.) since things like UI dependencies or libraries don’t change that often in releases, those are major changes and usually come with a prior warning by the developer. Meaning, you could just make the template and just change the version numbers and hashes, recompile it and most of the time, that will be just that, bam, you’re up to date ☺️. Sure, there are major updates, but let’s face it, there are very rare. And, you can share the template with others on the official void xbps-src repo or your own repo, however you like 😉. Hell, you could even share the binaries so that other people don’t have to go through the trouble of compiling them manually 😉.

Just use nofail in the fstab.

Really? Didn’t know about this switch, thanks for the info ☺️.

If your fileshare is accessible to you, it is also accessible to malware running as your user. Mounting the share via a filemanager doesn’t change this.

It does, it’s not mounted on boot.

In general, mounting a netwok lication at boot is a bad idea in any OS, unless you know exactly what you’re doing (all of the rigs that mount it are on a separate network, limited internet access through specific ports, none of them have users working them like daily drivers doing whatever on them - bascially, a server cluster is the only scenario that mounting a network share on boot makes sense). Why do you think that nowadays Windows users generally avoid mounting shares as network drives, but instead access them through shortcuts. The exact same reason, except in Windows, the share is mounted on logon (as far as I know, I might be wrong and the share might be mounted at boot, just reports that the share is missing when a user logs in). It’s safer if the location of the share is not known at boot, period. When the user logs in and decides to copy something to the share (unknow period of time after the login), that is a different story. Sure, well written malware will find a way to replicate itself and infect other rigs even if you don’t mount the share at boot, but at least you’re shielding yourself from the badly written ones.