hi,



Hmm, caanot understand what you asked about exactly, but what I wish to say:
All these
var1 EQU xx
var2 EQU xx
etc
are not good idea. Manual absolute definitions and memory allocations make programming hard - you have control addresses, overrun cases, sanity check etc. When you add a new variable, you must check other definitions, change all EQUs above this address et cetera.
Good assemblers, like Keil, allow us dynamical method for locate data segments. You are free of thinks about where and what is placed. You just ask assembler to locate variables in desired memory type (data, xdata, bdata, idata and so on). Then assembler locates them all itself, checks for overrun cases and memory borders, puts stack at the top of all idata variables (with ?STACK segment). And even you modify your code and add new variables then you may not even think how rest variables change thier locations and where stack is placed in.
Summary: I suggest to drop EQU for memory allocations if your assembler has a feature like I described above. Trust me, this makes programming easy very well.

Regards,
Oleg