I think this is a bad idea, but I’ve never had any problems with errors in the past. Here, I’m going to try to correct your problem by saying that my best use of my time has been to have some of the same things you’ve mentioned.
I have to agree that I have never had any problems with errors so I tend to chalk them up to my general laziness. I have had a few small ones though, like if I try to save a file which doesn’t exist, I will get a generic error message saying “save file is missing”. I think it’s because I have a lot of files and directories and I tend to check for them before continuing but I’ve never had any problems with them.
There are errors of this sort that happen quite often. I have had some that were very obvious to me and I wonder if they are errors in my file system, but I haven’t had any problems with them. I have had one error where if I saved a file and tried to load it later, I would get a list of all the files I had saved and would have to scroll through them to find the one I wanted. This was with Windows 7, I think.
Another common error is when a file is being read as a binary file and has an error in it. This could be a bad file or a bad character in it, but it could also be that the operating system doesn’t like binary files. Usually this error is a warning that the file is in a different encoding and is not a good file to work with.
A good example of this is a file that has an error reading as a binary file. Most will have a warning that it is a binary file but will still read it normally. Unfortunately this is not always the case. This is caused by the fact that many binaries are actually in ASCII, a binary file format. You can read this as an ASCII, binary file, or whatever you want to call it, but most operating systems just ignore it.
The only way to fix this error is to rename the file to something that’s ASCII. If you rename the file to a.ASCII file and it still reads it as a binary file, then it is a good example of binary files that will cause problems.
The reason that many people are actually reading these files is because they are not ASCII. AFAIK, ASCII is a binary format, not ASCII. If you just use a real binary file and read the file as ASCII, then it is a good example of a binary file.
Binary files are a problem for two reasons. First, when you open the file with a file editor, it will have all sorts of weird characters in it, and your file editor might not be able to process it correctly. It can also, if it is a text file, have different lines in it with different characters. The second problem I have with binary files is that binary files are easier to read than ASCII files. An ASCII file is 4 bytes and a binary file is 8 bytes.
Binary files are probably the easiest to read but the hardest to delete. ASCII files can be deleted by deleting the last character but binary files cannot. The two ways around this are to write an ASCII file with a new line at the end and delete the last byte. The first method would be the most convenient, but it requires a bit of extra effort when editing binary files.
