Tek 4051 firmware listing

In article <AANLkTim7ZZwBrsgkA-OwRc3+QpWXaO4w6CQxUeX95Vkk at mail.gmail.com>, William Donzelli <wdonzelli at gmail.com> writes: I agree. I did a few pages myself just to see what it would be like. If I were to do mechanical turk, I would use what I learned from doing it myself to create an instruction guide to reduce the amount of errors introduced by those who don't know assembly language and/or the quirks of this system. For instance, there's quite a few chunks where they do something like: JSR DOFP .BYTE FHEX .WORD COSTHA .BYTE FLEX .WORD SINTHA etc. This is from memory of the few pages I did, so I may have it slightly wrong, but it still illustrates the point. This looks to me like a transition from assembly code into the ROM BASIC code, but that is just a guess. If I were to ask other people to do this, I would bother with the assembled opcodes (in many cases they are useless as global symbols all show up as 0000G with the linker filling in the resolved address later, making comparisons to a disassembly listing rather fruitless), or the listing line numbers (which aren't on every line of every source code) or the page header or footer. Its the source code mnemonics and comments that are important. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/> Legalize Adulthood! <http://legalizeadulthood.wordpress.com>