Thanks for the video. I would sit in front of my c64 for hours writting programs from books and magazines and never knew what I was really doing at time. I always wanted make better programs, but never knew how and information wasn't available like it is now. Just got my C64 back out the other day and trying to get my 1541 back up and running. I also got some parts to build the X1541 cable so good times are ahead.
Compute Magazine had a small program that you could enter and save to your floppy or tape... You’d run that program before typing in one of the programs in their magazine. Each line of the program in the magazine ended in a colon and a 5 digit number. It was a checksum (I know that now - didn’t know that then). The small program you ran before typing in one of their programs would replace a tiny part of the C64 BASIC screen-editor, and would use the checksum number at the end of the line to ensure you entered that line correctly. It would let you know, via a very displeasing “buzz” sound, that you had entered the line incorrectly, so you knew immediately to check that line and correct your mistake. It made entering programs a *lot* easier - and whoever came up with that idea deserved a big pay-raise! Really made my life a lot easier, back in the day.
This is crazy. One of the best explanations in the world. And only so few pay attention to these three videos. I thank you very much for your effort. I hope you would bring more to the table.
Love the shout-out to Real Genius! As someone who grew up on the C64, Atari 400, and Atari 2600, I often have been given to wonder why we don't have 64 bit versions of the 6502 today, perhaps a WDC W65C864. The answer is probably, "because Steve Jobs", thinking of his war against the Apple II gs in favor of the Mac. I've mused about having a 64 bit 6502 descendent and Adrien Kohlbecker, W65C816 maven, has commented in response: it would be in a DIP-40 and they'd make us time demultiplex the 64 bits off the address/data pins.
I learned much more watching this one video than I ever did poring through those issues of COMPUTE! magazine and typing random examples into my VIC-20.
i just found your channel today and im absolutely loving it! thank you for your concise explanations for someone just getting into this stuff. You are easy to listen to and follow!
Great video. This really takes me back to my youth. I had a program published in a magazine when I was a teenager. It also was just a page of data statements. Helped me buy more computer bits :)
Jeff Yea, I quickly found BASIC to be very limiting. Even today I still find assembly programming to be quite enjoyable coding for pic16 MCUs. There is an element of code craft and artistry that is lost writing in higher level languages.
Axel Werner I think it depended a lot on your location. If there weren’t kids around in your home city that could introduce you into that stuff, you were fucked. I also would’ve liked to know more about this. Could have bought a book or so. But didn’t have enough passion, I guess.
Fun channel :) I grew up on Commodore boxes too. This video perfectly explains how I wrote my first assembler programs, manually converting every single bit. I would also type in those magazine programs and in a retro fit a cpl years ago I dug one out and reimplemented Eliza for Android. Not that it hadn't been done before, but hey...
I cannot really recall how I ended up programming 6510... I think I just went into the machine code monitor in the Action Replay mk V and got a little interested in what I saw. Never really had any books help me, just the games I took apart... also never had an assembler, just the ARmkV.... man keeping all the JSR routine locations on paper was fun and refactoring to make space was... interesting.
I used a cartridge based assembler, I think it was called Mikro Assembler. It would let you write assembler like a basic program with line numbers and it added commands to assemble it.
@@gregorymalchuk272 Like I said. I didn't have anything other than the Action Replay machine code monitor. I didn't know of any other tools until later and I really didn't learn much about them until I was writing on other machines, like the Acorn. All I really had was pieces of paper to write down my routine locations and remembering the important addresses on the C64 myself, mostly in hex.
The C=64 has a glitch in the Kernel where if you type 350800 into basic, as if to remove that line from a basic program, the computer jumps to the RESTORE mode. Can anyone please explain this, I've been wondering for the last 35 years.
Great video, I've been messing about with computers for over 30 years but never really understand what the DATA and READ commands did. Watching this video makes it all clearer :-) Really enjoying the series so far, although I'm trying to learn Z80 I'm guessing the basics are fairly similar regardless of what machine you use. Times like this I wish I had TH-cam back in the 80s to explain this stuff to me :-)
Rob Beard There are commonalities between most the assembly language of most processors but there are sometimes very different paradigms in how the processor architecture is set up -- especially with how memory addressing works. That said, Z80 assembly is almost like a superset of 6502 assembly. The big difference is that you have some general purpose registers to work with so you don't have to be so dependent on constantly loading addresses into the index registers every time that you need to work with a value.
![The [Fill in the Blank] Programmer](http://yt3.ggpht.com/cS66J1MTcSHArKeR1P55Jb0jf8Za5UvU1pVmZwAneXkIgv5zbt4spiHD2SXNwfEhkkDXTvF77g=s48-c-k-c0x00ffffff-no-rj)
![PASULOL รามเกียรติ์ ตอนที่ 4 นนทกพบรัก [Ramakien Ep.4: Nonthok in love]](http://i.ytimg.com/vi/tMUQgmZzf_A/mqdefault.jpg)
![Programming Like It's 1979: 6502 Assembly language on the Apple ][](/img/n.gif)
Excellent! I could have really used these videos back in the 80's!
Thanks for the video. I would sit in front of my c64 for hours writting programs from books and magazines and never knew what I was really doing at time. I always wanted make better programs, but never knew how and information wasn't available like it is now. Just got my C64 back out the other day and trying to get my 1541 back up and running. I also got some parts to build the X1541 cable so good times are ahead.
Compute Magazine had a small program that you could enter and save to your floppy or tape... You’d run that program before typing in one of the programs in their magazine. Each line of the program in the magazine ended in a colon and a 5 digit number. It was a checksum (I know that now - didn’t know that then). The small program you ran before typing in one of their programs would replace a tiny part of the C64 BASIC screen-editor, and would use the checksum number at the end of the line to ensure you entered that line correctly. It would let you know, via a very displeasing “buzz” sound, that you had entered the line incorrectly, so you knew immediately to check that line and correct your mistake. It made entering programs a *lot* easier - and whoever came up with that idea deserved a big pay-raise! Really made my life a lot easier, back in the day.
This is crazy. One of the best explanations in the world. And only so few pay attention to these three videos. I thank you very much for your effort. I hope you would bring more to the table.
Love the shout-out to Real Genius! As someone who grew up on the C64, Atari 400, and Atari 2600, I often have been given to wonder why we don't have 64 bit versions of the 6502 today, perhaps a WDC W65C864. The answer is probably, "because Steve Jobs", thinking of his war against the Apple II gs in favor of the Mac.
I've mused about having a 64 bit 6502 descendent and Adrien Kohlbecker, W65C816 maven, has commented in response: it would be in a DIP-40 and they'd make us time demultiplex the 64 bits off the address/data pins.
It can be fun to revisit the past for the nostalgia but I'm glad we no longer have to compile assembly code by hand lol
It's actually a pretty good exercise for getting familiar with the opcodes... even if you typically use an assembler.
I learned much more watching this one video than I ever did poring through those issues of COMPUTE! magazine and typing random examples into my VIC-20.
This explanation was so great. Assembly is not an easy thing to understand, and you made it very clear. Nicely done!!!
i just found your channel today and im absolutely loving it! thank you for your concise explanations for someone just getting into this stuff. You are easy to listen to and follow!
The C64 used the 6510 whose instruction set was almost identical to the 6502.
Great video. This really takes me back to my youth. I had a program published in a magazine when I was a teenager. It also was just a page of data statements. Helped me buy more computer bits :)
The $ means it’s a hexadecimal number.
Wish I had these videos 40 years ago.
really nice tutorial. i wished i would have understood all that back then when i was a kid.
Same here :)
I actually did. I used to play around with machine language a lot when I was about 12.
Jeff Yea, I quickly found BASIC to be very limiting. Even today I still find assembly programming to be quite enjoyable coding for pic16 MCUs. There is an element of code craft and artistry that is lost writing in higher level languages.
Axel Werner I think it depended a lot on your location. If there weren’t kids around in your home city that could introduce you into that stuff, you were fucked. I also would’ve liked to know more about this. Could have bought a book or so. But didn’t have enough passion, I guess.
Fun channel :) I grew up on Commodore boxes too. This video perfectly explains how I wrote my first assembler programs, manually converting every single bit. I would also type in those magazine programs and in a retro fit a cpl years ago I dug one out and reimplemented Eliza for Android. Not that it hadn't been done before, but hey...
Nice. I can relate to pretty much everything you´re saying regarding deduction and the complexities of machine language!
Compute! was a favorite of mine. It had more IBM/PC stuff (which I had because that's what my parents bought).
What I never understood back then is why was the main text printed nice and clear but the code in the magazines and books was always printed poorly.
My guess is: more expensive paper for the pages that more expensive ads appear on
Nice video. The two so far as well as a machine code book ive been reading have really helped me. Cheers
I cannot really recall how I ended up programming 6510... I think I just went into the machine code monitor in the Action Replay mk V and got a little interested in what I saw. Never really had any books help me, just the games I took apart... also never had an assembler, just the ARmkV.... man keeping all the JSR routine locations on paper was fun and refactoring to make space was... interesting.
Did the Commodore 64 have a built-in assembly monitor like the Apple II did?
@@gregorymalchuk272 no. Had to use extra tools.
@@Meow_YT
Which ones? TurboMacroPro?
I used a cartridge based assembler, I think it was called Mikro Assembler. It would let you write assembler like a basic program with line numbers and it added commands to assemble it.
@@gregorymalchuk272 Like I said. I didn't have anything other than the Action Replay machine code monitor. I didn't know of any other tools until later and I really didn't learn much about them until I was writing on other machines, like the Acorn. All I really had was pieces of paper to write down my routine locations and remembering the important addresses on the C64 myself, mostly in hex.
Computes Gazette was what I used!
I used to subscribe to that!!
Is this commodore basic or assembly language. Assembly comes with instructions like Lda, sta etc
This series has been great! Keep going, I've learned so much!
Oh of course! I've liked every video simply on how great they are!
RYAN_CHAPELLE dude your handle is the guy off 24
16:37 I think that's red... might need to adjust the hue on the monitor.
awesome, thank you very much :-)
I'd love to see a similar video about the Apple IIe.
The C=64 has a glitch in the Kernel where if you type 350800 into basic, as if to remove that line from a basic program, the computer jumps to the RESTORE mode. Can anyone please explain this, I've been wondering for the last 35 years.
Verry interesting. Keep up with good work 😊
Ah yes typing in programs in the basement every weekend for hours.
For them to fail due to a typo! :)
Just finding your videos now, these are great. Do you still check this channel? Would love to see more. Subbed.
I do! I posted a new episode not that long ago, actually. I have a long series planned and am slowly putting it together now.
c64 keyboard was horrible, did exactly this hundreds (perhaps thousands) of times: 14:25
LIT
?SYNTAX ERROR
READY.
I loved it. ☺️
At least it wasn't a membrane keyboard.
6:50 "Enjoy the silence" - Lolol
Great video, I've been messing about with computers for over 30 years but never really understand what the DATA and READ commands did. Watching this video makes it all clearer :-)
Really enjoying the series so far, although I'm trying to learn Z80 I'm guessing the basics are fairly similar regardless of what machine you use.
Times like this I wish I had TH-cam back in the 80s to explain this stuff to me :-)
Rob Beard There are commonalities between most the assembly language of most processors but there are sometimes very different paradigms in how the processor architecture is set up -- especially with how memory addressing works.
That said, Z80 assembly is almost like a superset of 6502 assembly. The big difference is that you have some general purpose registers to work with so you don't have to be so dependent on constantly loading addresses into the index registers every time that you need to work with a value.
What's the point of this video? You go back and forth with cursors keys and you type a few lines like a snail. We can look up Wikipedia on our own