Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. Hehe, "a lot" of pixel art is a hard commitment right now - but I will definitely reach out to see what you'd need.
  3. I mean, it would be awesome if there was an "official" luggable case, but I think that's quite far fetched. I do however like the idea of designing a case that can be made on your own (like the SX-64 mini I linked above, or many other projects from the maker community). My only industrial design expertise is limited to 3D printable stuff, but I bet the community could come up with some unofficial case somewhere down the line
  4. If you are interested in doing pixel art, I am working on a project that needs a lot of pixel art, and you wouldn't have to be involved on the programming side. DM me if you want details.
  5. Also have to settle on which size CX16 board. The mini-ITX would be the best bet for finding an existing compact case and then modding it.
  6. Hi all! I'm Fred, I started my computing journey with Commodore 64, went through Atari ST, Amiga 500, with a side of a famiclone somewhere in the middle, and finally PC. I'm originally from Poland, but I moved around a bit and now I live in US. I am not much of a programmer, I come from a graphic design background, but I tinker around. Started by playing around with QBASIC in the 90s, and in last few years got back to programming with PICO-8. Discovered that I really enjoyed lo-fi aesthetic and programming within constrains, so I am really looking to trying my hand at x16 (although assembly still scares me - worst comes to worst, I can join a group project as a pixel artist).
  7. Today
  8. I agree with you there, and I'm definitely looking to flesh the idea out more. After all, it's easy to present an idea and find a method to make it, but refining and perfecting that idea and getting it where you want it to be is where the hard part comes in.
  9. I appreciate the ideas. But it's the details where this sort of idea falls apart. As mentioned in the FAQ, if you look at other retro projects that went with a bespoke case, they had over a year, nearly 2 years delay added to the project due to problems with their own manufacturing. It isn't something the X16 team wishes to take on. 3D printing, as you mention, also isn't viable. I'm happy to leave this here as a feature request however. Never say never. Feel free to noodle on ideas, and we can see what the future brings. Thanks.
  10. I honestly hadn't put much thought into the production of the case, as the idea is still very much new to me, but I did consider 3d printing, but knew it'd be impractical to print the whole case. The bent metal would definitely be a great idea for the top and side cover. As for manufacture, I would consider it limited run, as I consider it a sort of niche thing for a luggable.
  11. Hi @Lambda_BM, I've moved this to feature requests. We've avoided bespoke cases for reasons detailed in the FAQ. I'd have one question for you at this stage: How would you manufacture it (considering the points detailed in the FAQ)?
  12. I have tinkered with games, electronic, and computer from a kid. I when to collage for computer and electronic. As a father I help my daughter with learning computer hardware and with my son i volunteer with his local robotic club. In my work life i have worked with electronics, control boards, desktop support, general server administration, firewalls, networking, Web server administration, vulnerable management, siems, and much more. At home I nerd out on games new and retro, electronics, computers, robotics, and 3d printing.
  13. While I would personally love a luggable form factor x16 (I am still somewhat thinking of making myself a SX-64 mini) - I am somewhat considered about a cost. Machining a case would be quite expensive, and 3d printing a whole case of this size doesn't feel right. Maybe a bent metal could be done cheaper? Then 3d printing just the front and back panels and the handle? Not sure. How were you thinking of making it?
  14. I'm David Rose and looking forward to getting my mitts on this machine!!!
  15. MY first computer was a VIC20, with 16k memory expansion and tape drive. In 1985 I bought a Commodore C128 as soon as it was available. I am very interested in getting an X16 when it is ready.
  16. I just finished watching Perifractic's video on the Commodore SX64, and had an idea tha I would like to "get out there", so to say. What if there was a luggable form factor X16? I'm willing to attempt to design a luggable case in the style of the SX-64 for the X16, and by extension, any µATX board one would want to add. It would feature a either 5 or 7 inch 4:3 ratio LCD, 2 5 1/4 inch slots for whatever drives one might want to add, and the standard stuff on the back. I plan on doing this, at least for my X16 when I get one, but depending on the interest here, I might post further updates on the design or even sell them, but sales would likely be a distant future type thing. Also, key word in the designing is attempt; I'm not too good at 3D design, and this would be the literal 3rd 3D modeling project I'll've done, but I'm willing to give it a go and improve along the way.
  17. No reason not to. Regarding the "Approach 3", the point of that approach is typically that you are using both modes, and an expansion card is cheaper than a whole new system ... which would certainly be the case. It's nothing I would be in the market for, but it would be beneficial for the "Approach 3" type expansion board, since there would then be more Z80 code targeting Vera.
  18. Yesterday
  19. It's specific to CBM prg Studio. There was no standard convention for handling screen codes.
  20. What kind of magic syntax nonsense is that? Is this something specific to CBM prg studio, that it'll translate from ASCII to the appropriate screen codes? Or is/was this a standard convention for C64-type software?
  21. Yep. But in this case, it's three steps back. There are two encodings: PetSCII and screen codes. We print PetSCII to the screen. But, we poke screen codes into screen RAM. Therefore, you must change the text lines that you copy into VERA's VRAM. Change the quotation marks into apostrophes. text 'In a wild and rough scrubland.'
  22. There is also https://style64.org/petscii/ which is good for exploring the relationships between different character encodings Sent from my iPhone using Tapatalk
  23. Thank you very much! Yes that sounds very probable. Something concrete for me to work on.
  24. That I think is the problem. When writing directly to vera you need to use screencodes rather than petscii values. However, PRINT uses petscii. For a discussion of this, see https://retrocomputing.stackexchange.com/questions/7529/why-the-disparity-between-the-screencodes-and-the-character-codes . The assemblers I've tried have all had a mechanism to translate text to screencodesfor you, but I couldn't find documentation for c64 studio (which I believe is what you're using). Maybe search in the help for screencodes and see what you can find.
  25. Nice to see more Danes :) I can't wait to teach my son coding on the CX16 - he is only 4 now but by the time I have my second machine he will be ready :)
  26. I've not done that deliberately - I'm the only one writing this so the screw ups are all mine it is definitely something to do with how the character sets are being handled, so I'm going to dig a little deeper down that tunnel. Perhaps the kernel calls from print do something clever to make the correct characters appear on screen that my hard-coded vera calls ain't doing.
  1. Load more activity
  • Create New...

Important Information

Please review our Terms of Use