Narue

You've commented out all of your labels. There's a reason the code I posted follows this theme:
If you don't jump over the data definitions, they'll be treated as executable instructions, which very rarely works. Also, since you're treating snum as a byte string, you should use db instead of dw. You want something more like this:
You can also place your data definitions after the executable code and save yourself the trouble, if you want:
Now it's a moot issue because you terminate the program before IP gets to the data definitions. By the way, one trick you may have noticed to save yourself two mov's at the end is to mov a two byte value to ax rather than splitting it up into two mov's of one byte to ah and al.

__________________
Even if the voices aren't real, they have some pretty good ideas.

lectricpharaoh

It means you mucked something up. That little window tells you (in this order) the code segment (which is essentially meaningless to you, since it's just an index into a descriptor table), the instruction pointer (ie, address within the segment where the Bad Thing happened), and the actual bytes of the instruction (which you can decode if you have the right references handy). Since my references are at home, and I'm not right now, I can't be much more help than that.

__________________
And once again, Probability proves itself willing to sneak into a back alley and service Drama as would a copper-piece harlot.
- Vaarsuvius, Order of the Stick

kruptof

oh i see so the the first line in my code should always be executable instruction.....another thing you have taught me......................lectricpharaoh.............i read your post and i looked at the error message again and this time i have noticed the error message contained the words IP(Instruction Pointer) and the CS (Code Segment)...........thanks i didn't see that before.

kruptof

when i try to run this code below i keep getting an error saying a "byte or a word". why is this, didn't i already say that these two variables are both bytes by saying define bite (db), or is this error sayingg what do you want to move a byte or a word.if so how can i move a word if both of the variabes are a byte long.

Here is the code:

lectricpharaoh

You can't do memory-to-memory operations on Intel CPUs, except for a few cases, such as movs (move string, not the plural of MOV). You need to move it into a register from the source memory location, then from that register to the destination memory location:

__________________
And once again, Probability proves itself willing to sneak into a back alley and service Drama as would a copper-piece harlot.
- Vaarsuvius, Order of the Stick

kruptof

oh...............thanks i understand now..............another question...........how do i move whats inside my save variable into a register such as ax register because when i do
i keep getting an error

lectricpharaoh

Assuming save is a memory word to which you have read access, this should not be a problem. Double-check your code and make sure it is declared as such (you may need to use an override, like word ptr save). You may be referencing the address rather than the value at the address, depending on your assembler (for example, in NASM, memory references are enclosed in brackets; without the brackets, it would be semantically the same as mov ax, offset save is in TASM/MASM, which is almost certainly not what you want). Lastly, be sure you're not clobbering a register you shouldn't be. This is a concern when using certain APIs, or interfacing with higher-level languages, though it's almost universally safe to clobber EAX and its smaller components.

__________________
And once again, Probability proves itself willing to sneak into a back alley and service Drama as would a copper-piece harlot.
- Vaarsuvius, Order of the Stick