Hy,
Also how can I see in OllyDbg the variables from memory ? (oneWord, oneByte,oneDword)?
The data of your variables (oneByte, oneWord,...) you can find in the data segment. So in Olly you'll have to watch the memory where that variable resides. The names of those variables(labels) are gone but...
In that screenshot you can see the value of those variables in the left bottom window(Hex Dump)... There you can see
00404000 "78 34 12 87 D6 12 00 00 ....."
You have a Watch Window in Olly where you can enter the offset of those variables and watch them
Byte Ptr [00404000]
Word Ptr [00404000 + 1]
DWord Ptr [00404000 + 3]
Anyway the variable names (labels) are gone but you can also add them again in Olly,...
Click in the HEX viewer on the offset and select ADD LABEL. Give it the name of your variable. Now you can use this name also in the Watch Window :t
After adding your labels this should work...When you use EasyCode you have the "Add symbolic debug info" option in your project properties. When you set this option the names of your labels are known and you can just add them to the watch window. When you don't have debug info in your executable then you can label them in Olly manually. (Like i first wrote, i didn't know myself that the symbolic debug info add's the names of labels in your PE).
Open the watch window in Olly and add your labels...
Byte Ptr [oneByte]
Word Ptr [oneWord]
DWord Ptr [oneDword]
To add a breakpoint with Olly, hit F2... To step F8, step into F7... Restart CTRL+F2,...
And to see the program running, hit CTRL+F7, ...
When you add a DebugBreak or Int3 to your code and run the program. That program will show like it crashes in some windows versions but you'll have the chance to click "Debug" (after a while that button shows)... Then you can also debug with Visual Studio. (Make sure in visual studio you have "Native" checked where are the JIT options before you try).
You can also use (set) Olly as JIT debugger (carefull, can be some trouble to get your VS JIT settings back to normal)
There's also a debug library in the MASM package with some handy features...
See the native code, source and watch in this screen shot.

Greetings