Jump to content

sebassco

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

8 Neutral

About sebassco

  • Birthday July 25

Recent Profile Visitors

66 profile views
  1. Hi everyone! I finished reviewing BASIC and will start writing the first pages of the Wiki. I hope it renders some aid to anyone new to the system as I am Here's the link if you want to check out the examples! https://github.com/sebassco-dp/x16tutorial/tree/master/BASIC I will appreciate your comments!
  2. Have you thought about using the WSL? You can install the extension on VSC and use Ubuntu on Windows, so I think you won't need a VM and could directly use that extension for building/compiling.
  3. Hey guys! Yes, for sure it will not be the same as compiled BASIC. But it helps me getting rid of the gap I have between my knowledge of BASIC and the understanding of the X16 architecture. It may not be my default go-to in the future, but as for now, it is the best angle from which I can start creating some working stuff.
  4. Hi @maktos! Yes, I will! In fact, if everything goes as expected, October will be the month I start looking into C. And yes, that seems the best route for me too, but I wanted to explore the world of BASIC first, and understand a little bit on how to operate this machine in particular. At the moment, I am taking a final look at some graphics tutorials on https://www.8bitcoding.com (Thanks @SerErris for the tip!) and will start writing the BASIC 'noob' tutorial. After finishing that, cc65 is what comes next! You can take a look at my latest code additions here
  5. Hey guys! So, I am starting to upload my code here: https://github.com/sebassco-dp/x16tutorial I have not started with the wiki section, but I hope to do so after I finish the BASIC guide. Since I ran into some trouble at work, my throughput has been a little affected, but hopefully I can make up for that this week. You will see most of the source files have the same examples than the ones on the C64 guide, but I have made some twists to some of them. After finishing to understand memory management, I will upload some stuff of my own there Hope you like it!
  6. Yes! I just saw it. I will put that into my backlog
  7. Dude, if you ever come to Argentina, remind me that I owe you a beer Your answer in the question I made (Well, yours and @Greg King's) really helped me understand a little bit more about memory management. In case anyone's interested, I am writing a tutorial made by a newbie for newbies, hahaha. I am going to cover every aspect of my process learning how to use the x16 and the skills it needs to do so. I will be posting the link as soon as I deem it is not too embarassing
  8. I think I am understanding this issue better with the comments from @Greg King and @SerErris. Thanks for your response @TomXP411, I will also try that! About the first part, as I stated before, this is just in order to understand better what is stored in the different RAM sectors and using that screen color change as a bit of a POC. So yeah, I am reading both the C64 user's manual and the X16 programmer's reference (computer and VERA chip) and yes, I knew what the COLOR command did. I just wanted to change a value in RAM and see the difference. Only because it should be 'doable' as I've seen from what I read, and because I want to learn more on how memory can be accessed/modified. Here is where I am carrying a kind of log of every step I am taking along the way, in case you are interested in giving it a look: Thank you everyone!!
  9. Awesome! Flawless and understandable as always @SerErris! Can I be your padawan? hahahaha Yes, I figured that, in fact I gave the VERA 0.9 doc a review. What strikes me as odd is that there is not a value that sets a default color, I mean, all I managed to do is to paint the screen, but as a temporary meassure. I thought that COLOR x,y was setting that y value somewhere in RAM or VRAM. Anyways, on to the following excercises!
  10. By managing VRAM manually you refer to using assembly code, right? Thanks for the response!
  11. Hi @SlithyMatt! Thanks for the response. What I am trying to do here is to recreate this: That is, to recreate the process by accesing memory and changing that value. I understand that running COLOR 1,x and then entering CLS would do the trick, but it is not my focus at the moment. Just wanted to see if I could do that in a lower level, without using the command that already solves that for me. You could see it like a little POC about handling memory values
  12. Two entries on the same day, I'm happy! lol So I've seen this post had a couple views, and I don't want to be bothering with technical questions here while breaking some forum rules, so I created this question: Also, I decided to keep just posting my advances here, but without asking things because I don't think this is the place. I will super appreciate your advice in the following steps! As for now, I will focus on learning those 3 subjects I was recommended to. Cheers!
  13. Hey guys! I was just reading this: (please bear with me because I am a total noob). While working on learning how to use the X16, I arrived to the section of the C64 manual where it tells you to change the background color. Basically, what you have to do is to run this command: And you should be able to see the background change. I understand this is not the same in the X16 because of the VERA chip, hence the use of the VPOKE/VPEEK commands. I also understand that the addresses here are memory addresses that point to the VRAM. (more info, here). From some of the answers in that question, I found out a way to "paint it" going tile by tile and setting its background to 1. But obviously it lasts for only the time the program is running. After that, blue comes back! The code I ran is the following: 1 REM PAINT THE SCREEN BLACK 10 FOR X = 1 TO 20000 20 IF (X AND 1) THEN VPOKE 0,X,1 30 NEXT 40 END And the result is as follows: Is there a way to achieve that? What should I do to access the address where I can change the background color for good? Thanks in advance!
  14. Hi everyone! So... new log enty today Got through the firsts chapters of BASIC without any problems until I got to the obvious one: Graphics. At first I said Ok, this is not in my scope, I should skip it, but the curious kid inside me started to poke (oh yes, you did see that joke) my brain asking me why not, and it was a good thing he did, specially because I would be able to play around with memory addresses and their values!! So there was I, being a total noob reading my C64 manual when it hit me: I won't be able to use peek and poke that simply because we have the VERA chip. So I went to David's video (Part 2) and saw he did an example with VPOKE 0,0,1. That basically puts a letter in the first character space. While it is something really simple, it could be useful to understand how memory works in the X16 and the VERA. The other thing I knew is that the monitor should let me dump the values stored in the VRAM, so I went and digged a little bit into that. Nothing too special, I knew I had to dust off my hex/binary skills a little bit in order to get something working, I just only took my chance. Well... I think I am failing to do so. I thought the COLOR command should let me change the background color, so I ran it and tried to read the value at $9F35 to see if something change: much to my surprise, it didn't! I am still searching what am I doing wrong, but if in the meantime someone reads this and can give me a hint, I would appreciate it, I think my main issue is that I still don't understand how the tables in the documentation relates to the vpeek and vpoke parameters. Here's a screenshot of what I got until now: That's all for now! I will get cracking this and see if I can solve it on my own (and save my pride while doing that )
  15. Ok, so is not like the computer lays "dormant" until you hit a key, but instead it keeps busy-waiting until you do something?
×
×
  • Create New...

Important Information

Please review our Terms of Use