X816 Problems?
Moderator: Moderators
X816 Problems?
Hello everyone,
Im having trouble trying to assemble with x816. I have the version x112f and when ever i try to assemble the source code with "x816 st1.asm" i get
" 'x816' is not a recognized as an internal or external command, operable program or batch file"
Ive tried changing directories and ive also tried using "x112f st1.asm" instead with the same results. Can someone help me?
Thanks in Advance,
EL
Im having trouble trying to assemble with x816. I have the version x112f and when ever i try to assemble the source code with "x816 st1.asm" i get
" 'x816' is not a recognized as an internal or external command, operable program or batch file"
Ive tried changing directories and ive also tried using "x112f st1.asm" instead with the same results. Can someone help me?
Thanks in Advance,
EL
Check the command line options to see if there's any you need (try "x112f /?"). I thought it creates a .bin file with the same name as the source. Look in the source, if at the beginning there's some stuff to set up an iNES header (text "NES", $1A, etc.) If not, then it's just a raw ROM that you'll need to copy a header onto. The lazy way is to rip the first 16 bytes off an .NES file that has the same setup (size, mapper, etc), then do a "copy /b header+romname.bin romname.nes".
If the CHR-ROM isn't included in the source also (.incbin or whatever), then you'll need to copy that onto the end, same way as adding the header. I think most x816 progs generally included the CHR-ROM though at the end (when they use CHR-ROM, anyways).
If the CHR-ROM isn't included in the source also (.incbin or whatever), then you'll need to copy that onto the end, same way as adding the header. I think most x816 progs generally included the CHR-ROM though at the end (when they use CHR-ROM, anyways).
EQU should work. You might have to change it to =, which is the same thing.
.asc might be in there, with a different name. You could look in nesasm's docs. It's just for defining your font tiles, if they're not in the usual ASCII position.
x816 pros: simple to use and reliable. I used it to make my SNES NSF player, I had no trouble with the assembler that I can recall.
cons: DOS-only. Assembling my huge SNES NSF player in DOSBox seems to take forever (but more like 30 secs when I used to run it natively).
Noone hardly uses it anymore for new projects. ca65 is better if you want to share and use others people's code IMHO.
When it reports errors you have to view the listing to see where they are. It's a bit different than just having the line number reported.
.asc might be in there, with a different name. You could look in nesasm's docs. It's just for defining your font tiles, if they're not in the usual ASCII position.
x816 pros: simple to use and reliable. I used it to make my SNES NSF player, I had no trouble with the assembler that I can recall.
cons: DOS-only. Assembling my huge SNES NSF player in DOSBox seems to take forever (but more like 30 secs when I used to run it natively).
Noone hardly uses it anymore for new projects. ca65 is better if you want to share and use others people's code IMHO.
When it reports errors you have to view the listing to see where they are. It's a bit different than just having the line number reported.