Vic20
65SC21 Programmable Interface Adapter chip info
Submitted by ctalkobt on Mon, 09/24/2007 - 22:02.65SC21 Programmable Interface Adapter chip info
Learning ML - Part 4
Submitted by ctalkobt on Sun, 09/23/2007 - 07:17.Learning Machine Language - Part 4 by Craig Taylor (ctalkobt@gmail.com) Originally written for C= Hacking Issue 4 (c) 2006 Craig Taylor ============================================ +---------------------------+ | Space Invasion - Part 1 | | | | Programming: Craig Taylor | | Graphics : Pasi Ojala | | Music/Sound: | | |
Learning ML - Part 3
Submitted by ctalkobt on Sun, 09/23/2007 - 07:13.Learning ML - Part 3 by Craig Taylor (ctalkobt@gmail.com) Originally written for C= Hacking Issue #3 (c) 2006 Craig Taylor ============================================= Last time we used a routine at $FFD2 which would print out the character code contained within the accumalator. That location will always print the character out regardless of VIC-20, C=64, C=128 and even PET because Commodore decided to set up some locations in high memory that would perform routines that are commonly needed. Take a look now at the KERNAL 64/128 article and glance over some of the
Learning ML - Part 2
Submitted by ctalkobt on Sun, 09/23/2007 - 07:07.Beginning ML #2 by Craig Taylor (ctalkobt@gmail.com) Originally written for C= Hacking Issue #2 (c) 2006 Craig Taylor ============================================= Last time we introduced the definition of what exactly Machine Language / Assembly Language is along with an example of clearing the screen in Machine Language. Now, in this issue let's print my name (and later your name). Looking at the code from last time the following assembly source jumps to mind: ------------ print_1.asm: lda #147 ; clr/screen code
Learning ML - Part 1
Submitted by ctalkobt on Sun, 09/23/2007 - 07:06.Beginning ML - Part One (C) 1992 by Craig Taylor Originally written for C= Hacking Issue 1 All Rights Reserved ========================================= The best way to learn machine language is to actually code routines that you don't think will work, hope that they work, and then figure out why they don't work. (If they do work, you try to figure out why you didn't think they'd work). Ie: THE BEST WAY TO LEARN ANY PROGRAMMING LANGUAGE IS TO PROGRAM IN THAT LANGUAGE. And Machine Language is a programming language.
