Thanks for the links DJLinux, I finally got test.subwithparam to run on windows without error.. by adding and subtracting 24 to the stack pointer at the beginning and ending of the subroutines respectively, but that is a whole 3 bytes of waste on the stack for each call! Did finally realize that the problem the whole time was printf wiping out the memory address for the call on the stack.. posted on stackoverflow about it but for the most part just got "you're an idiot" so, apparently, I'm not using printf correctly... not all that easy to find 64bit examples for windows assembly, I acheived the same result in linux with system calls, but unfortunately that isn't doable with windows anymore. Also, all the links in your first post are blue but don't seem to go anywhere. As an update, I have a very limited support for variable types and am getting ready to better align them with the way basic4GL handles variables internally, then onto arrays and eventually strings..
also, if fasm supports intel syntax, you should be able to use fasm instead of nasm
so... to be honest, i have been vegging out in front of the tv. but I have 2 different ideas.. should I convert the asm to 32 bit and make all the variables 32 bit like the virtual machine does? or should I continue with 64 bit ( i found out I have been using 32bit style c function calls and that has probably been the whole issue... it shouldn't take much to fix) what do you guys think i should do? Also, after that is decided any help you guys would offer would be greatly appreciated (if you think this project is a good idea) i hated assembly in college, and I have to admit.. i am quite bad at it
I suppose you'll probably learn more by writing the 64-bit version, so I'd stick with that if I was you.
When I was a teenager I was interested in Assembler for Motorola processors (didn't do anything about it though) and I've been tempted to take a look into assembly for RISC. But as for Intel processors, it's never appealed to me. It always seemed like too much hard work.