the resulting error messages normally at least give you something to search for

lp0 on fire

And:

#include <errno.h>
#include <stdio.h>

int main (void) {
    errno=ENOANO;
    perror("");
    return 0;
}

Yields:

$ ./a.out 
No anode
$

Yesterday I installed a program to run windows games. The installation through the terminal spat out ten different types of “Error reading the jupitos bus” type messages that I simply could not parse, but they sounded grim and serious.

But it ran just fine afterwards so those messages couldn’t have been that important?