Which is reassembleable and bit correct can be found on this page.

Lee.

Cool that's great work (haven't looked into the details, but looks like lot of comments)

Just one thing - ROM routines have some kind of "standard" names, like BSOUT for $FFD2 and so on, same for the variable names. It would be great if that were done as well.

André

I have a similar disassembly available on my Web site...a project I had worked on many years ago. Scroll down to the bottom of the Commodore section. It reassables using TASM and is also binary compatible.

http://www.classiccmp.org/cini/systems.htm

_________________
Rich Cini
Build Master and maintainer of the Altair32 Emulation project
http://cini.classiccmp.org
http://altair32.classiccmp.org

Looking for other kernal disassembly, RichCini is probably nice if you know all those alias:es for every address since they list all the aliases but not the addresses it's hard for a beginner to find their way especially when trying to follow code disassembled from another program.

I was looking for $F27A right now and found it was called CHROUT, also gound a few JSR CHROUT (BCHOUT, MSG, FLNMLP, IOERMS9, LOCLOOP) but there's no "CHROUT" label anywhere so it seems it would assemble if you'd try that.
Vector table last is difficult as there are no addresses - which is what you'd find in raw code.

So if anyone has another disassembly I'd love to have a look at it.

Hi --

The two files (ramvars.inc and krnlrom.asm) are source files and won't have the target addresses in them (other than in the comments). You can use the Table Assembler (or probably other 6502 cross-assemblers) to produce a list file which will have the addresses.

Commodore had a vector table at the end of the ROM and you'll notice that the call to CHROUT actually calls through an indirect JMP to the vector pointer in RAM page 3 (see Line 300). That allows you to redirect the output routine (and was likely used by 3rd party software too). So, calling CHROUT from a user program actually passed from $FFD2 to the address in $0326 which would be $F27A (ICHROT, line 3780).

The locations starting with "I" are the "internal" addresses called by these vectored routines. Again, most of this was to avoid name collisions when reassembling with TASM.

Hope this helps.

_________________
Rich Cini
Build Master and maintainer of the Altair32 Emulation project
http://cini.classiccmp.org
http://altair32.classiccmp.org

It's great work done, I missed some things when trying to use it for disassembly/understand code.

I bet it's very handy being able to assemble the kernal rom from this code, when wanting to make a custom one for example.
The type of disassembly I needed was more for reference, but I managed to work it out, wouldn't have been possible without this.

For the C64 I have used this, it's very handy:
http://www.pagetable.com/c64rom/c64rom_en.html

Thanks very much. It took a long time to create. Updated asm file is attached with location marks added to the comments. The list file is 320k so it's not posting properly.

_________________
Rich Cini
Build Master and maintainer of the Altair32 Emulation project
http://cini.classiccmp.org
http://altair32.classiccmp.org

_________________
Rich Cini
Build Master and maintainer of the Altair32 Emulation project
http://cini.classiccmp.org
http://altair32.classiccmp.org