Olly Question

I dunno how it happened but it seems to have fixed itself.

I was all set to upload the .asm as an attachment, when I noticed that I had used an .inc file to clean up some of the code, and it would no longer build.

As it happens, overnight I had managed to delete the file while fiddling with different versions of Masm to see if that was the culprit.

Trouble is I cannot for the life of me remember what else was in the .inc file. all I can remember is that I had changed around the original example to be easier to read, by following the structure of another simple program I had found online (can I remember what it was called, can I &%$# !!)

eg putting the "RegisterWindow" bit in its own procedure. and the same for the message loop, making the whole thing look a lot cleaner.

From what I can tell from what is in the .asm file now, I had put a lot of the includes and a procedure to Show/update the window into the .inc.

So just now when I quickly just added the includes, and put back the separate calls to Show/Update window. I built the executable, and had a quick look in Olly to check that it was still doing the same thing...voila! it had magically fixed itself.

So I think it must have been something in the way that I had used the includes, or called the procedure that had caused Masm to somehow make Olly think portions of the code section were really data. (however the code that would have been in the .inc file was not the code that was displayed incorrectly in Olly)

I just wish I could remember what else I had put in the .inc file. I had thought to start adding useful routines that I might use across different programs into one place, and so put the file along side the other includes that come with Masm32, and then promptly forgot all about it.

So thanks for your answers, to my NON-question. I think perhaps I had better just shut up for now, and stop bothering you nice people.

B

PS Thought I might as well attach the source