How come when I call a procedure I made, in the attached code, it never comes back to where it was called from, even though I'm issuing a ret? Don't think I ever had that problem before, then again it's always been a windows based app I would be working on, not a console one. So maybe the stack frames are different or something along those lines?

(I know, it's kinda sloppy, and could really be cleaned up. I figured "make it work first, then worry about finese")

-- StakFallT

[ Post removed by author. ]

Well I originally tried not to be dealing with the stack so much, but it seemed like everytime I dealt with specifying the result, of getprocaddress, in the form of a variable I had problems... Looking at it in going with the notion it definately is a stack problem, I fixed it.. It wasn't [i]exactly]/i] a balance issue. For every two pushes there were two pops, problem was, I double pushed and called a proc that then double popped (the first few lines of code in), which was a problem I guess because the stack frame (ds register right?) changes when you've moved into another procedure or so it seems.. *shrugs* It's fixed, and thanks for the help!

I guess the moral of the story is sometimes when you figure problems out you need to look at it as a definate and see if it fits..

-- StakFallT


EDIT: Yeah that's the part (the wsprintf bit) I left off on and haven't worked on yet.. I stopped when I realized I wasn't getting into those procedures