For me the questions that don't get an answer are the ones that go, "I have a splurge splodge, has anyone written a library for it?"
It is very specific so if you haven't got one there is nothing to say. Also asking for advice on how to write interface code for the splurge splodge is a lot more active and shows a willingness to learn and more likely to prompt a response especially if there are some links where I can find out about the splurge splodge.
Also I will always look at a question with 0 replies so if you add a "is no one going to answer" it looks like their is a reply and I don't always look at it.
It helps if you post to the right board, read the definitions and decide where it should go, their are some boards I hardly ever look at. For example some posts are in Software->Interfacing which would be much better in Hardware->Interfacing. Again read the definitions.
Finally a post during the week is often better than a post at weekends when it is busy.
Hope that helps.