We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I KEEP GETTING FATAL ERROR WHEN I TYPE A51 AT MY COMMAND LINE.
I GET TERMINATED.
WHY?
TNX FOR THE HELP. I WILL READ THE MANAUL AND FIND LIST OF HOW TO WORKAROUND BUGS.
I WILL READ THE MANAUL AND FIND LIST OF HOW TO WORKAROUND BUGS.
Then you will be looking in the wrong place.
What you call a "bug" is actually a completely normal behavior of the A51 compiler, and a typical reaction to insufficient or wrong command line arguments given by the user (that means "by you").
You need to read the parts of the manual concerning the normal usage of the A51 compiler - i.e. what command line options it expects and needs to do its job (convert an assembly file to an object code file).
HI AGAIN.
DOES ANYONE KNOW WHERE IN THE MANUAL IT HAS A INDEX OF BUGS?
I LOOK AND CANNOT FIND. SO I DON'T KNOW HOW TO WORK AROUND THE PROBELM.
Err ... nowhere. That wouldn't really make sense, since documenting a bug would make it an undesired feature, wouldn't it ?
And once again, what you are seeing is not a bug. It is a normal, expected reaction of the assembler to wrong or insufficient input data. It then prints an error message.
Yyou can find a list of error messages in the manual.
http://www.keil.com/support/man/docs/a51/a51_errors.htm
More precisely, the error message you are seeing can be found on this page, along with a description of what causes it.
http://www.keil.com/support/man/docs/a51/a51_er_messages.htm
Begone heathen! You are not seeing the result of a bug - you have a "*** bekind the keyboard" problem. YOU did wrong, and the program complained. When you start to feed reasonable command-line parameters, the program will stop complaining!
THANX FOR YOUR ALL YOUR ADVICE.
I WILL CHECK THE MANUALZ AGIAN.
BUT I AM HAPPY TO SPEAK THAT I HAVE NEVER HAD A *** BEHIND THE KEYBOARD. I ALWAYS GO BEHIND THE BUSH!
your humor is appreciated, however, that does not reduce the anoyance of reading what you are typing in all CAPITALS which makes your posts difficult to read.
In addition, many consider CAPITALS 'shouting' and consider that very impolite.
Erik
PS "*** bekind the keyboard" is a phrase more modern than "garbage in = garbage out" i.e. if you do not use the proper command line you will not get the expected result.
"anoyance of reading what you are typing in ALL CAPITALS"
Especially as it's been pointed out to you at least twice already!
1. The Keil A51 manual, to tell you how to correctly form an A51 command line;
2. The Ultraedit manual, to tell you how to get it to run a 3rd-party command line such as A51.
Note that uVision shows you the command options that it sets up - so, if you like GUIs and IDEs, you could try configuring your projuect in uVision first to tell you what command-line options to use!
See: http://www.keil.com/support/man/docs/uv3/uv3_dg_a51.htm (read the very last line of the text)
I TRY AND FAIL USING ULTEREDIT BCOZ I THINK THERE ARE TO MANY BUGS.
IVE BEEN TOLD THAT VS CODEWRITE ARE BETTER EDITOR. I SEE IF IT WORKS.
TANKS FOR YOUR SUPPORT.
Given your complete inablility to understand simple instructions like do not write in ALL CAPTALS, I very much doubt that this is anything to do with any inadequacy of the Ultraedit documentation - let alone bugs in the product!
"IVE BEEN TOLD THAT VS CODEWRITE ARE BETTER EDITOR."
I certainly like it - but I have no idea how it compares to Ultraedit, as I've never tried that.
"I SEE IF IT WORKS."
Yes, it does work. But you are still going to have to follow the same process of reading both manuals and following their instructions!
"IVE BEEN TOLD THAT VS CODEWRITE<sic> ARE BETTER EDITOR." I have never used Ultra Edit, but I can wouch for CodeWright not "CODEWRITE" being just great, I would use no other. When I change location, it is my first statement: "If you do not have a CodeWright for me, (I will not bootleg) order it"
PS Given your complete inablility to understand simple instructions If you persist in using CAPITALS, I will not try to help you any more.
But you will still have to do one more favor, Erik. You will have to scan through the manual for the page with the list of bugs in CodeWright - it shouldn't take too long until you get a request for it :)
I DONT KNOW CODEWRIGHT.
IT IS VS CODEWRITE THAT I AM GOING TO TRY. APERENTELEY IT IS FREE AND GOOD AND NOT SO BUGGED!
I LET YOU KNOW MY RESULT WHEN I TRY.
IF NO GOOD I LOOK AT CODEWRIGHT. BUT IT LOOKS VERY OLD AND EXPENSIFE I THINLK/.
TNANX FOR YOUR PHELP.
from my post before the garbage above Given your complete inablility to understand simple instructions If you persist in using CAPITALS, I will not try to help you any more.
PS all capitals does not become garbage till requests to desist are ignored
the story of CodeWright
a group of great people made an excellent editor called 'brief' (anyone remember that one?).
Borland got upset that so many stated that 'brief' was much better than the pitiful Borland editor and the solution was to buy the company that made 'brief' and discontinue 'brief'.
Some of the people from 'brief' then started to make CodeWright with all that 'brief' could and more.
Borland got upset that so many stated that CodeWright was much better than the pitiful Borland editor and the solution was to buy the company that made CodeWright and discontinue CodeWright.
That created such an uproar that Borland started shipping it again, but AFAIK they have now reverted to their old habits and discontinued it again.
PS: if you want the, in my opinion, best editor ever, Amazon has 3 left - hurry.