Wrathchild

No, that's not really correct. Many of the popular carts are able to run many different formats of cartridge binary images. So whilst you can blow the image to an AtariMax cartridge, you can play the binary from an Ultimate Cart, The!Cart, AVG Cart etc So just continue on as you were and it looks like others with prep the cart version for you

Shame it misses the r/w line as an UNO cart equivalent could be done for it.

You're welcome. For the majority of keys, the A8 is interrupted to say 'this key is pressed'. So if keys are held simultaneously or another is subsequently pressed whilst another is down then the A8 cannot know this. So the obvious exceptions for that are the Shift and Control keys whose statuses are additional bits supplied with the key-code, plus the Console keys. The break key also can be configured to generate an interrupt. So in Elite where you would want to use diagonal directions in flight then this wouldn't be possible, you would toggle quickly between the X and Y direction keys to do this but not ideal. Similarly if you wanted to fire you'd need to release the direction key (although this could be moved to Shift from 'A' for example). None of this is ideal in a fire fight! So the default setup will be to use the joystick as that is what most people would be doing anyway I think.

One for @phaeron but with the options 'Display' and 'Debugger' I'd summize their use would depend on which window had focus (display / non-display) and so 'Global' meaning both. If you're using the debugger or not then Global seems a sensible choice either way based on your use-case.

Here ?

Use 'Tools / Keyboard Shortcuts...' and assign a key

Have been able to revisit some of my Works-In-Progress 5200 ports... with @playsoft as an essential second pair of eyes to spot moments of madness in my coding First release candidate of "Stealth" ready so fingers crossed a binary should be available soon (32K image) @Albert Mr Do! on the list to tackle

No, was in-game saving of progress, but if anyone can just start on any level then it does seem to eliminate the need.

I'm not sure the 2600+H is a necessary dependency, certainly with the STM32F ARM micro in the UNO cart you could easily have a board with no SD socket and provide a title self contained within the firmware and so house in a normal case looking like a normal game. I should think the same applies with an AVG cart and so would imagine that board, components and case cost is not prohibitive (€20-25 ?).

Save states?

The 1050-2-PC cable used with the Pro-System was different to the SIO2PC cable, though I think later cables came as a 2-in-1 solution?

@Yaron Nir Maybe get a moderator to change the title of the thread for you as you've chosen to include new parts within the thread rather than start new ones for each part?

You couldn't do diagonals, e.g. up/right, at the same time. Similar issue with something like Elite from the keyboard, OK on other 8-bit micros as key-scanning breaks keyboard into small sections but A8 is PITA due to the 'one-only' (aside from Shift and Console keys).

The A8 series already has this in the form of the UNO Cart.

From post #57, it's already on the GIT server https://github.com/ascrnet/Joy2Bplus/tree/master/games

Did some games cater for this by confirming with the user, e.g. Dark Crystal

You shouldn't need to do this as the linker should find the config file within the CC65 installation's "cfg" folder. You can override the default by specifying any of the below, e.g. "-C atari-xex.cfg" depending on your requirements. Or, of course, to specify your own rolled config file, e.g. when making a cartridge. But for a newbie I would recommend they don't need to get involved with config's right away and so adding "-C atari.cfg" is not necessary

Nice interview, thanks!

Well if team Hoaxers don't snap you up with a Premier League player's salary then somethings not right with the world

Also, I can attest to using multi-dimensional arrays in C using CC65 and whilst it is good while developing you get to a point where the overheads needed to calc the data access are too much and so you end up refactoring to using a single-dimension array instead, so the grass isn't always greener.

From what I recall, as PotGo is used to discharge the capacitors its basically the time needed for these to settle again. That could be established by using a few fixed value from the paddles, set the Critical flag so that stage 2 routines aren't used and use a Pokey timer routine to set the shadow values and then write to PotGo. Start short and if the values in the shadow registers don't match the expected values then lengthen the timer. Equally you could probably achieve this equally as well with a loop to monitor VCount or use DLIs.

It's just padded to a nice round $60000 bytes and doesn't utilise compression. It was merely a quick throw-together as I'd done a fair amount of investigation toward making an Atarimax cart version.

Not an ATX, Thom was stating that the ATR uploaded loads under RespeQt.

The issue would appear to be down to this section: So the VCOUNT check determines which code path is taken etc. In Altirra I used the trace: bt $b49f "$%02x $%02X" db($14) db($d40b) With PAL accurate timing this gives outputs of: $0b $2C $0b $26 $0b $21 $0b $1C $0b $17 $0b $11 $0b $0C $0b $07 $0b $02 $0b $99 $0b $93 $0b $8E $0b $89 $0b $84 $0b $7F $0a $79 $0a $74 and this stops there and the load continues. Whereas with accurate timing off it returns: $04 $25 $04 $32 $04 $3A $04 $24 $04 $1A $04 $26 $04 $23 $04 $17 $04 $1B $04 $01 $04 $26 $04 $44 $04 $70 $04 $90 $04 $13 $04 $2F $04 $44 $04 $5A $04 $5E ... and so the load is screwing up

So as both crash in Altirra if 'Use accurate timing' isn't checked, then I suspect it's going to be down to not all protection being removed, which would indicate that RespeQt is honouring the timings?