Jump to content

cathrynm

Members
  • Content Count

    71
  • Joined

  • Last visited

Everything posted by cathrynm

  1. I've been poking around the Mister Atari 8bit core, basic since I kind of still know the hardware, and I'm curious about FPGA. It's mostly VHDL. I'm just tweaking easy things for now, making simple changes. There's some of this that is just sequential, like programming, really, and obviously there are bits that are not. Main thing that's a hassle is that the compile times are pretty brutal. I have medium-new PC here, 8 cores, and it still takes 10s of minutes to build. Right now, just dealing with syntax issues. I still keep typing '==' instead of '=' and '=' instead of '<='.
  2. I already have XEP80, and a way to display it that basic functions, but plan to buy just for the switching between Atari and XEP80 video, and for one more Atari gadget to tinker with, basically.
  3. Well, I don't know about you guys, but I voted for LightGun to PS2 mouse interface. Not even sure what this is, but I like to see started projects get finalized, and looking forwards to some Bug Hunt, maybe even on an HDMI monitor?
  4. Looks like this is supposed to work with Game pads/Atari 8-bit. I remember now, RJC did a video about this. I think this is it, maybe. I see a 2600 in a video. https://retrohax.net/shop/amiga/mouster/?alg_currency=USD
  5. Oh okay, thanks, sounds like this thing I'm imaging doesn't actually exist then. I can figure this out.
  6. Does anyone make a dongle for using USB gamepads on Atari 8-bit, 2600s, C64, etc. I try searching for this, but I get too many results for the reverse, for using 9-pin joysticks on modern PCs/emulators. I can't figure out how to do the other way around. Am I missing something obvious here?
  7. Don't know the story or timing on this one, but the bottom dropped out of the Atari 8bit games market pretty suddenly. Wouldn't surprised if some games got dropped, just because there wasn't a market anymore.
  8. Maybe an Atari ST Computer Eyes, but the label fell off? https://www.biocomp.net/o30808.htm
  9. Needed another SIO cable, bought one from EBay and it came from myatari. Still doing business as of a few days ago.
  10. To me, gets points for doing it over the parallel bus interface rather than joysick ports or SIO. Could do mass storage, or 80 column video this way too, maybe. Something like a parallel bus fujinet maybe, maybe could get good speed this way?
  11. Oh I know the answer to this. Because making a game, any game, is a lot of work, and the audience for this is small. That said, if the Incognito Atari 800 adapter gets released, I'll consider getting one for 80 column with Spartados. I did peek at the docs. I think 2d games are possible with the blitter. You store all your art in VBXE memory, and then draw the entire screen with the blitter. Maybe fake 3d games are possible? Not sure if anyone has made any fake 3d demos with VBXE. I don't have one, so I don't pay much attention, tbh.
  12. Nope. XEP has a seaparate connector on the back, hooks to an 80 column screen only. This looks like a nice feature. Fussing with two monitors or switching monitors just for XEP80 is awkward.
  13. I see, yeah, sounds like this is already optimized. I'm still stuck on the 'two versions' idea, I'm afraid. Would it be possible to build an SIO2BT version with the old tools, and the main version with the new tools? If so, then at least you could get unstick for now, and though the SIO2BT would be stuck on the old tools until you ripped out enough stuff to make it function,SIO2BT wouldn't be totally orphaned -- maybe it becomes a pain to build. The main version could continue developing on new tools as before.
  14. It sounds like the effort of this is to figure out what exactly can skip initialization if SIO2BT is still around, and then hard to know if that's enough to save SIO2BT. N:, R: do they really use that much RAM? I wouldn't think they need such big buffers, maybe something I don't know about here.
  15. I see. Does the platform support DLLs or overlays or anything like this? Or is it just compiled as one big blob? Would it make sense to build two versions, an SIO2BT version and a regular version, with a bunch of #ifdef separating one from the other? I've never used SIO2BT mode myself, do people who use this tend to switch back and forth?
  16. I do see this getting posted on company chat where I work. HR people are hearing about it. Someone posted the 'Cosby Room' image, which is pretty cringe. I do think the angle here, is trying to hire away employees from them.
  17. Trying to understand here. That would fix it for no Bluetooth, but then what do you sacrifice when Bluetooth is active? Would there be any obvious 'memory cows' around to shut down to have enough RAM in this case?
  18. Yeah, that's it. Honest, I was just confused about which midi interface worked with what. I'm sorting this out brewingacademy right now.
  19. This kind of thing, memory usage, also performance and random bugs, is actually more difficult to work on than adding new features -- unless there's some kind of 'big stupid' to find, but that's luck, a large part.
  20. I'm trying to get a MIDI XEL II working with my Atari800, just bought from brewing academy. I just wire the SIO cable to the same labeled pins, right? Or does anything have to go between the Atari Data IN and the DI connector on the device? It can float, right, for when other stuff is using the bus? I thought I hooked it up correctly, but it's stopping anything else on my SIO bus from working when I do. Going to check once again to make sure everything is right. I do see the LED go on with the motor command, so at least I didn't wire it backwards.
  21. Does the fat32 allocation unit size matter for these? Should I format at 512 for Atari, or are other sizes fine too?
  22. Oh I see, does that mean it'll be able to, say, stop data coming into the Atari, do some other SIO commands, and then resume back where it left off without missing a byte?
  23. What this sounds like. That this would be like Atari 850 with all the buffer overrun trickiness.
  24. With Fujinet if you run with the usb logging on, I believe it shows what speed it's using.
  25. I guess it's missing bytes due to interrupts being disabled in the XEP80 driver for too long a period, or there's some other kind of weird interrupt issue going on. And yeah, CPM in Fujinet is hard coded at 9600 baud in the source. If you rebuild from source, you could try changing the baud rate, but not sure if that's all that's needed to slow it down. Might just work.
×
×
  • Create New...