Yes OS errors can be vague, but no, you’re not going to just get “disk error error” for such disparate errors.
Do a search for “errno”, and specifically the POSIX error section. There are separate errors for “permission denied”, “device unavailable”, “bad file descriptor”, etc. Windows API calls have a whole host of their own error codes, plus functions to examine what’s going wrong specifically.
This is most likely caused by a higher layer in the code catching errors when it doesn’t know what to do with them, and then just showing a generic message.
setsubyou@lemmy.world 3 days ago
That’s true, but it could still be more specific.
For example there’s a comment about symlinks on exFAT. Steam could say “failed to create symbolic link” instead of “disk write error” in that case.
There typically are a few different error conditions for normal writes too that Steam could pass on. E.g. on Linux there are separate errors for out of quota, files becoming too large for the fs they’re on, the fs being out of space, and low-level I/O errors.