CompuServe Messages

I have tried to assemble the files init.asm, printertag.asm, and wait.asm listed in Appendix I of the Rom Kernal Manual with the Aztec Assembler but the assembly always aborts for one reason or another (such as undefined symbols or unknown opcodes/directives). I have also tried converting the code with acvt. I think this works OK but some of the files are converted into UNK00.obj. What the heck does UNK00 mean? Unknown? I am now at the point where I am thinking of returning Aztec-C back to Manx, getting my money back, and purchasing Lattice-C. It may take Lattice-C a little bit longer to compile C source files than Aztec-C, but at least you can use the Amiga Macro Assembler to link together Lattice-C object files and Amiga Macro Assembler object files. After my experiences with Aztec-C I would strongly discourage anyone from purchasing it if they are planning to write device drivers for the Amiga because it doesn't appear that Amiga Macro Assembler object files can be linked to Aztec-C object files. The acvt utility may work but don't forget that you also have to convert amiga.lib on the Macro Assembler disk also if you are going to attempt to link the files together with the Aztec Linker. By the way, Manx has a BBS and their response to this was "this package was developed with C programming as its primary consideration." In my opinion, Manx made a big mistake in having their assembler put out object code that is not able to be linked to Macro Assembler object code. If you have any more suggestions, please let me know.