Problem with X86 assembly

[cdybreez]

Hey, I've just begun learning assembly several days ago using the art of assembly at Art of Assembly Language Programming and HLA by Randall Hyde on Windows XP. The problem is the first program they had me do, the hello world program, it worked fine, but at the end of the compilation it said:
POLINK: warning: /SECTION: .bss ignored; section is missing

The program worked fine when I executed it after that, but when I did another of the example programs, the error message at the end was

error: illegal instruction

When I tried to execute it after that, the the command is not recognized as an internal command, operable program or batch file.

If you need more information I can take screenshots the whole thing and post them up here.

[redhead]

I've moved your post to the Assembly forum, since we now do have one...

[Hamlin]

Originally Posted by cdybreez

Hey, I've just begun learning assembly several days ago using the art of assembly at Art of Assembly Language Programming and HLA by Randall Hyde on Windows XP. The problem is the first program they had me do, the hello world program, it worked fine, but at the end of the compilation it said:
POLINK: warning: /SECTION: .bss ignored; section is missing

The program worked fine when I executed it after that, but when I did another of the example programs, the error message at the end was

error: illegal instruction

When I tried to execute it after that, the the command is not recognized as an internal command, operable program or batch file.

If you need more information I can take screenshots the whole thing and post them up here.

Randall Hyde's code generally assumes you're assembling with Masm32 and linking with Microsoft's linker LINK/LINK32. What tools are you using for assembling and linking?

When you get an illegal instruction error message, the object files won't link at all, which means you're not going to have a result executable. If there's no executable by the name of the command you're typing after the linking process, then XP will definitely tell you that the command is not recognized as an internal command, operable program, or batch file.

If you're not currently using MASM32 and LINK/LINK32 to do your assembling and linking, you should give them a shot - I think you'll find those error messages go away, especially if all you're doing is copying and pasting Hyde code.

I'll watch this space to see how that goes for you.

[redhead]

Hey Hamlin, haven't heard from you in a while.. Nice to see you're still monitoring this section