tejekion, We can port BBS programs from the C64 without too much trouble once we have a good working BASIC. I can basically write it in Fortran especially if I provide a POKE and PEEK implementation (non-standard) that has long addresses and up to 16 bit data value. There is also some BBSs written in assembly so in theory, they can be modified for 65c816. PLEASE NOTE: In Assembly language, you are not compiling the program. You "assemble" which would take your ASCII source and assemble them to binary value. A goal for an ML Monitor would be so you can plug in actual ML instructions in hexadecimal format just like found on the Commodore 128 and the Plus/4 when you type Monitor. That's the basic goal on that front. This means you will want to learn the ML hex value for EACH Opcode in the particular addressing mode. In assembly, they may have the same mneumonic but with actual ML Monitor they are hexadecimal representation of pure binary. In the CPU a long jump to subroutine on the 65c816 would be a different opcode value than a short jump to subroutines even if they had the same mneumonic in assembly. This is old school machine language programming.
So, low and behold. I pull out an old Dell laptop, I had been using when I had nothing else to use. I put it up when I got better equipment. Well now I can't use those computers anymore, and was forced back onto the Dell laptop in order to use the WDCTools. Well something wonderful may have happened as a result. Of course you guys know, I have been harping on about wanting to run a BBS on the C256. I had recently came across what appears to be a linux version of my favorite C64 BBS. What's more, is that I may have been able to download the source code for the BBS as well. I should be able to compile it using a 65816 assembler shouldn't I? and also, isn't one included in the WDCTools? I wouldn't know, I'm literally clueless about programming.
tejekion, We can port BBS programs from the C64 without too much trouble once we have a good working BASIC. I can basically write it in Fortran especially if I provide a POKE and PEEK implementation (non-standard) that has long addresses and up to 16 bit data value. There is also some BBSs written in assembly so in theory, they can be modified for 65c816. PLEASE NOTE: In Assembly language, you are not compiling the program. You "assemble" which would take your ASCII source and assemble them to binary value. A goal for an ML Monitor would be so you can plug in actual ML instructions in hexadecimal format just like found on the Commodore 128 and the Plus/4 when you type Monitor. That's the basic goal on that front. This means you will want to learn the ML hex value for EACH Opcode in the particular addressing mode. In assembly, they may have the same mneumonic but with actual ML Monitor they are hexadecimal representation of pure binary. In the CPU a long jump to subroutine on the 65c816 would be a different opcode value than a short jump to subroutines even if they had the same mneumonic in assembly. This is old school machine language programming.
So, low and behold. I pull out an old Dell laptop, I had been using when I had nothing else to use. I put it up when I got better equipment. Well now I can't use those computers anymore, and was forced back onto the Dell laptop in order to use the WDCTools. Well something wonderful may have happened as a result. Of course you guys know, I have been harping on about wanting to run a BBS on the C256. I had recently came across what appears to be a linux version of my favorite C64 BBS. What's more, is that I may have been able to download the source code for the BBS as well. I should be able to compile it using a 65816 assembler shouldn't I? and also, isn't one included in the WDCTools? I wouldn't know, I'm literally clueless about programming.
I would tell you my ideaas, but I have to learn how to at least help make them. That way I could have SOME involvement with building them.