Unfortunately this is kind of the point. If someone can't even figure out what to search for, then obviously they're trying to do something beyond their abilities, which will likely result in them causing problems for someone. It might be just that they mess up their own system or network, but it's also very likely that they mess up a system or network at work or at school. Worse yet if they interfere with a Gov't or business system.Originally Posted by halfdone
Edit: I started to list the proper uses of commas, but as my list got to 5 it occurred to me that there are a fair number of instances where commas are applicable, and that it would simply derail this thread to list them all. Instead I dug up this link which I'll simply provide as reference:
Rules for Comma Usage
Agreed. If someone is using BT (or trying to) and can't search or figure out "man <command>", "<command> --help", to read the "README" or to check the actual main site of a particular tool, sorry but you're in the wrong place trying to use the wrong thing. (Be it BT, the tool in question, or an OS other than Windows).Almost every tool has a website, a man page or some other set of instructions and there are plenty of blogs and websites with tutorials for these tools. Its for this reason that I could care less to answer any of these types of questions. Thats not to say I will not help but only if the poster has demonstrated that they are having a real problem and have truly searched.
I equate such situations with something like visiting a car enthusiast forum and asking how to: put gas in your car, check your tire pressure, change your tires, top up your oil, etc.