I am using happily Keil PK51 package for more than a year. Suddenly, I experience a very strange problem: When running a code on Silabs C8051F321 processor - the debugger interpretes an Assembler command in the wrong way: jump bit performs a jump to wrong address. Practicaly, no code can run now and I can't work with the system.
Did any of you experience such issue? Any idea?
I personally don't see too much problems with cross-postings. But a cross-posting should _always_ contain a link or reference saying that it is a cross-posting, and to which other forums. And after a good answer has been received in one forum, that should be relayed back to the other forums too.
The problem isn't the people who read all boards, and knows that they (or someone else) have already answered on another forum. The problem is the people who spend the time to answer, without knowing that the OP has already received a good answer on another forum.
This is a question of netiquette, just as not SHOUTING, making sure that a question contains enough information, describing what corrective actions that has been already tried, etc.
You have to remember that people who answers questions in forums does that because they are nice. If people donate time to solve other peoples problems, the questioner is responsible for making sure that the hive-mind is not abused.
That is also the reason why people who specifically formulate their questions in bad or vague ways - resulting in a lot of wasted time figuring out the real problem - often can receive quite harsh answers. If someone wants other people to spend time answering questions, they should themselve make sure that they have spent enough time correctly and completely describing the problem.
The problem isn't the people who read all boards, and knows that they (or someone else) have already answered on another forum.
sometimes it is. I have sometimes answered a question and then when seeing the cross posting found that someone else had spent the time to find the same answer amking the time I spent wasted.
Of course when the cross=posting is detected, that does not happen any more, but is it too much to ask that the OP states in the first postthat the subject is cross-posted.
I have, myself, cross-posted when which group might have a member with the answer was in doubt, but ALWAYS stated in both posts "this is cross posted at ..."
Erik
Yes, but I meant that only people who have already answered the question in another forum - or have already seen the answer in another forum - knows that it is a waste of time to answer it again.
The nice thing about reading multiple forums is the possibility of finding out that an anwer has already been supplied. The wasted time is always a source of great joy ;-)
Fair enough... I just wondered if there was a sound rationale. It sounds like there is--more or less.
Cross-posting is like sending a request to every sales office you can get the address of, expecting them all to individually answer your identical requests.
That is one of the reasons why big companies has a strict policy that the world is divided into regions and that only the "owner" of a region may handle customer requests. If you get in the wrong way, you (or your request) is forwarded to the owner.
The web is a "controlled anarchy". There is no control mechanism to catch multiple concurrent request.