ASM Community

I have experienced several nasty problems with Tools menu.
First - Magic number is 20! :) (something about hex-dec error?)
As tools menu reached number 20(masm.ini!MenuTools) - the problems begin!
I noticed it as I tried to add a new item to the Tool menu,
my last item was OllyDgb,5 (in masm.ini 20=OllyDbg,890,T,OllyDbg,5)
And it had been in real tool menu untill I pressed Options\Tools menu
I was surprised to note that there was no OllyDbg item in Tools menu manager. Then I looked to masm.ini and found that here was 20=OllyDbg,890,T,OllyDbg,5.
I pressed cancel in the Tools menu manager, and looked again in real tools menu. There WAS OllyDbg item. Then I opened Tools Menu Manager again and now typed description of new item and pressed OK.
After that both OllyDbg and NewItem desapeared from both real menu and masm.ini. After some experiments I found out that if number of tools in that menu reaches 20 - the problem with addin new item begins.
I looked at Radasm help file and read.
x=MenuText,Accel,T,Command    x is a number between 1 and 32
But the problem boundry was 20 not 32!
Might be something wrong with code? As most significant digit in dec represantation becomes "2" (meaning 2 tens) the parsing code limit it as hex not dec number? Or other explonation can be here? - you tell me - I', complitly lost to find the logic of the error.

The other problem with Tools menu - a decimal number that is passed to command line and actually represnts some project file.
I mean, for example 5 in RadAsm syntax OllyDbg,5. Where 5 means (projectname).exe.
As far as I understood denotion of the numbers comes from section of .ini file and then hereafter comes to project file.

Number 12 here is .com
12=.com
I assumed if I'd use syntax progy.exe,12 it would lead to passing argument
to progy.exe as
progy.exe myproject.com
I was very surprised when first time my "progy" didn't find the file, and next time opened a wrong file. And the file was myproject.rc
In masm.ini
1=.rc
So now, I think, I understand what was happend.
RadAsm took just first digit of "12" in "progy.exe,12" line and looked for
1=.rc instead of 12=.com


And the end I'd like to say about RadAsm - helps.
Desciption
"Section

Used to create new RadASM projects."

is not very informative, is it?
Imaging it some math dictionary you would read:
"integral - used for calculations"
and nothing more :)

Thank you. You are most kind.



Well, it's fair.
Ok, I'll try, and then you correct me if I'm wrong in it.

"The numbers and extentions corresponds to created project files.
The numbers used in internal RadAsm syntax.
Creating command lines RadAsm replaces them with filenames this way:
+[.ext]
is taken from name of your project
and [.ext] is taken from  section
for example if there is line (in )
12=.com
and name of your project is "Google"
then 12 would mean Google.com
And in RadAsm syntax
Hiew,12
Would mean
hiew Google.com"

Oooops... it would mean hiew Google.rc :)
Joking :)
OK, instead of 12 in the above desciption we'd better use 5 :)
After some expert in the English language commands has taken a look,
and after you logical corrections we could enlight a little bit more about those files in , I hope.

BTW. Talking of the description I actually meant to refer to Donkey, since I took the line from his chm file. And there also is contradiction in the very file.

In description of rap file you can read
"Section

Maintained by RadASM project wizard"
then you can follow link in the desciption
and read in Assembler ini section about MakeFiles:

"Used to create new RadASM projects.
Manually maintained."

Is it OK if until your expand I change 8=.txt to 8=.com and 12=.txt, exchanging accordinly all 12 and 8 in make lines?
Or there are some dangers I missed?

Do you mean that project file parameter is limitted 0..9 for tools menu?
I'm asking 'cause  argument parameter "12" is used  in making command line and it seems wokring fine.

Another question:
Are those limits expanded in your betta version of 2208?