Jump to content


  • Content Count

  • Joined

Community Reputation

197 Excellent

About SvOlli

  • Rank

Profile Information

  • Gender
  • Location
    Hannover, Germany

Recent Profile Visitors

8,504 profile views
  1. And they use a different wiring for this? Why? The trick with connecting the buttons also to the paddles has to work on a 2600 as well.
  2. I don't think there is any chance for a simple reason: speed. The audio signal was fed directly into the AVM chip to be processed instantly, while it can take several frames to get a reading from the potentiometers. The magic about the AVM is that it's pure analogue technique, and for this, if you want a reproduction close you should rather go for current FPGA hardware instead of the 2600. I also had to have one a couple of years ago to make this: The backstory for this is here: https://xayax.net/trsi/atari_video_music-the_demo/
  3. @doubledown What is the 2600/7800 switch for? The two button joysticks / pads that came with the 7800 worked perfectly on both 2600 and 7800 systems, so replicating that wiring should eliminate the need for the switch, or is there something I'm missing?
  4. Hello, I've promised Al_Nafuur that I'll take care of a Demoscene section for the PlusCart environment. Well, now we've got 125 files in there, which makes up for more than 100 demos worth watching. (Some of them are PAL/NTSC variations, a very few of them are more like proof-of-concept/compofiller quality.) The collection reflects the "defacto official" list of demos as provided by Pouet.net. The version of "Bang!" also has a custom PlusCart Easter egg (just different text). The Easter egg is described here. Have fun, SvOlli
  5. Then please reflect that in the version number. Most probably this change will not justify a dasm 3.0, it will at least justify a version 2.21.0, instead of bumping up to 2.20.14.
  6. At this point of discussion, I would suggest if you RIOT is socketed you swap it out for another chip. There's still new old stock available on ebay. The RIOT is the only chip that has died on me so far in my collection of 2600s. I've still got one with a broken RIOT, but it's a jr, so it's not socketed, and I lack the skill and tools of soldering that out.
  7. There always was something that I wanted to know: would this demo work without a Harmony cart? Or any other cart that includes a microcontroller? So I asked @Albert to sell me one of those "old" boards that use a GAL for bankswitching and an original SARA RAM chip. I added my own memory chip (I used a flash chip 27SF256, since I expected to add some workarounds), but it worked the first time I tried. So I can now finally state that the hardware requirements are the same as "Fatal Run". Well, except for the ROM contents.
  8. Let me throw in my 2 cents as well, as the definition of "real-time" was something that I took a deeper look into being at the university and also worked for QNX for about two years, who sell a "real-time" operating system. The term "real-time" is rather blunt. It just means that you can guarantee a response time. If this response time is one hour, it is still "real-time" as long as you can guarantee it under all circumstances (asides from power-loss, obviously). This includes software as well as the operating system. For the 2600, there is no OS, so only the software running to consider. And I would define "real-time" in this context as the response to the console switches and joystick, paddle, etc. If this happens within a couple of frames, the 2600 is "real-time". ...unless you take games into account a game like Chess, which takes a lot of time to calculate the next move. When during this period the switches are not evaluated, then it suddenly isn't "real-time" anymore. So the answer is neither "yes" or "no" more like "it depends, but typically yes". (In the operating system world "real-time" typically means that the notification of an input, like an interrupt, reaches your code in a "few milliseconds". And "few milliseconds" is a guaranteed precise number, that differs from system to system.)
  9. Hmmm... It seems that I can't update the file in the post, so I've got to add the updated version here. I went with 2mm more space for the jumpers and 1mm on the SD card reader, just to be sure. UnoCart-2600_case.zip
  10. Hmmm.. mine is a tight fit, but it works. Would adding another millimeter "on the inner side" be enough?
  11. SvOlli

    2600 new PCB?

    I started doing my first little project using KiCAD. But now I want to go for something slightly bigger. Since quite some time, I also want to do my very own flavoured 2600. So instead of going for a route like Ben Heckendorn with his super soldered 2600, I want to design a new PCB for the three original chips with options for changes like replacing the 6507 with a 6502. And maybe replace the cartridge slot with a soldered in UnoCart 2600. To accomplish this, I'd like to get some circuit diagrams. I know the original ones are around (I have them on my harddisk somewhere), but those contain some stuff that I don't want to replicate like the HF modulation stuff. Has already someone done some trimming done on the original diagrams or created some stripped down version? As with all my stuff, if I really get something done, it will be completely open, so anyone can modify it and order new 2600 PCBs.
  12. I know this is rather far from firmware, but I chose this space for easy finding... As @Andrew Davie asked for my modification of a thingiverse design of a 2600 cartridge shell done for a UnoCart 2600, I decided to pick them up from my tinkercad account. So here they are, happy printing. UnoCart-2600_case.zip
  13. SvOlli


    Then look at your hard drive or mail/atariage inbox. I sent you the design, at the time I did it. If you can't find it, let me know and I'll send it again.
  14. Taking a look at the compendium at http://www.ataricompendium.com/faq/vcs_tia/vcs_tia.html , it looks to me like the same chip from a different manufacturer. Or let me put it this way: if these chips / machines in question, I'd do it. But there's still a very very small chance, that this either would not work or at an even smaller chance break something. So, it's your call.
  15. I would have to double-check by running in an emulator, but my guess is, that the games not producing any sound do not run on plain 262 lines per frame. And in this case the TV mute the sound as it assumes that the picture is faulty. Something like this usually happens when loading supercharger games, or when running a demo that does not produce any sync.
  • Create New...