Quote:
|
Originally Posted by linxis
it is because that file isn't a MASM file it is probably a nasm or a Binary
|
Why dredge up a 3 week old thread that has been solved?
It seemed pretty obvious to me that is was masm32 seeing as that is in all of the path names.
You need to read ALL of the posts in a topic before replying, not just the first one (this is the second time I've seen you do this).