Recent Posts

ATS

Hi, everyone! 

I’m new to the forum and am just starting to get into arcade controls, especially building and configuring joysticks and buttons. I still have a lot to learn, so I’d appreciate any recommendations on components, simple projects, or resources for beginners.

I look forward to learning from your experience and getting involved in the community. Cheers!
I also have a blog that I’d like you to check out https://fortuneoxguiacompleto.jimdosite.com/

Thanks for your reply.

What tools/resources (e.g. hardware, software) are you using the flash the chips? How do you program them?

No bad thing using AI to help. It seems well-adapted to programming as it can automatically integrate obscure rules, syntax and formatting stuff that gets boring for humans.

I don't mind programming myself either and, "at a glance", what I saw of gambaman's original work seems fairly straightforward. The only thing holding me back from using PICs more is knowing how to get started. My questions are the dumb & specific ones, like what hard/soft tools do you use. I should probably stop asking and just look harder for myself. Or ask AI. I guess Youtube awaits too.

Instead, I ended up solving 15khz sync filtering (for GreenAntz) by using an analog frequency/tone-decoder approach. I used AI to help, but 90% of its suggestions were completely useless. That 10% was worthwhile though as it helped give me ideas to progress further.

I wasn't talking about TV-level csync vs TTL sync, I don't think I need that for my current projects. I was talking about TTL-level Csync input to a csync generating circuit (like your 15khz dongle, which is great at doing csync BTW, but does not accept csync as an input).

Anyway, thought "comparing notes" might help you with your own projects in this space.

I am embarrassed to admit i'm using AI to write the code, it's something i wasn't going to be able to do quickly. If at all TBH. And i've moved chipsets a few times, due to limited features and then lack of flash-mem space.

I am embarrassed to admit i'm using AI to write the code, it's something i wasn't going to be able to do quickly. If at all TBH. And i've moved chipsets a few times, due to limited features and then lack of flash-mem space.

These aren't silly questions; getting started with PICs can be confusing. I use a PICkit 5 with the MPLAB X IDE and MPLAB IPE. I connect the chip via ICSP, select the model, load the HEX file, and program it.

I also agree with you about AI: many suggestions aren't helpful, but some might give you the idea you need to move forward.

Now I understand the clarification about C-sync as a TTL input. Thanks for sharing your notes; I’m interested in learning more about your solution for GreenAntz, and I’m glad to hear that the adapter is working well.

Thanks for your reply.

What tools/resources (e.g. hardware, software) are you using the flash the chips? How do you program them?

No bad thing using AI to help. It seems well-adapted to programming as it can automatically integrate obscure rules, syntax and formatting stuff that gets boring for humans.

I don't mind programming myself either and, "at a glance", what I saw of gambaman's original work seems fairly straightforward. The only thing holding me back from using PICs more is knowing how to get started. My questions are the dumb & specific ones, like what hard/soft tools do you use. I should probably stop asking and just look harder for myself. Or ask AI. I guess Youtube awaits too.

Instead, I ended up solving 15khz sync filtering (for GreenAntz) by using an analog frequency/tone-decoder approach. I used AI to help, but 90% of its suggestions were completely useless. That 10% was worthwhile though as it helped give me ideas to progress further.

I wasn't talking about TV-level csync vs TTL sync, I don't think I need that for my current projects. I was talking about TTL-level Csync input to a csync generating circuit (like your 15khz dongle, which is great at doing csync BTW, but does not accept csync as an input).

Anyway, thought "comparing notes" might help you with your own projects in this space.

I am embarrassed to admit i'm using AI to write the code, it's something i wasn't going to be able to do quickly. If at all TBH. And i've moved chipsets a few times, due to limited features and then lack of flash-mem space.

I am embarrassed to admit i'm using AI to write the code, it's something i wasn't going to be able to do quickly. If at all TBH. And i've moved chipsets a few times, due to limited features and then lack of flash-mem space.

No problems in syncing to 25kHz, it was more about what's out there that i would want to cater to. No point updating the code with a 25kHz band if it's not going to work for someone with a 25kHz monitor

I am embarrassed to admit i'm using AI to write the code, it's something i wasn't going to be able to do quickly. If at all TBH. And i've moved chipsets a few times, due to limited features and then lack of flash-mem space.

I haven't yet looked into accepting c-sync at TV levels, only at TTL for now. Happy to compare notes though

Hey everyone, it's been a while since I've been logged in.

I just ordered an Atari 2600 clean composite/S video kit I actually ordered two as I have three of the systems between my place and my brother's place. I just got a nonworking one from a vintage resale shop and it was real cheap, as it is not working. I will be recap in that kit when I do this installation hopefully there's still people come in here and check the stuff out. I used to have a lot of fun in this community.

And I know there are cheaper kits. I would rather spending a few bucks more for something that's quality.

https://retrosix.us/products/atari-2600-cleancomp-composite-video-out

Thank you so much, i will try to print it as accurate possible and will let you know the results,
Best wishes
Piotr

want to revive this thread really intrested in this project, OP did you over see it through, and if not would you mind sharing your CAD. I'd love to play around with it. A wall-hung Astro City is EXACTLY what I want in my basement bar.

# ArcadeDOS Introduction

ArcadeDOS is a free system designed for creating, installing, and maintaining arcade computers using FreeDOS as a base. The project was developed with a focus on simplicity, performance, compatibility with older computers, and ease of configuration, offering a complete solution for dedicated arcade machines.

The system uses AdvanceMAME to run games and AdvanceMenu as the main interface, allowing the computer to boot directly into an arcade environment without the need to load modern operating systems or heavy graphical interfaces.

In addition to the arcade environment, ArcadeDOS includes its own tools for system installation, configuration, and maintenance. The SETUPI installer allows you to partition, format, install, and restore ArcadeDOS in an organized manner. After installation, SETUPARCADE offers menus to configure video, audio, keyboard language, controls, system protection, game options, and frontend behavior.

The project supports different types of monitors, including 15 kHz and 25 kHz arcade monitors, 31 kHz VGA CRT monitors, and LCD or LED monitors. It also has options for configuring resolution, vertical synchronization, interlacing, screen orientation, aspect ratio, and other important adjustments for arcade machines.

For controls, ArcadeDOS includes DOSKEY34, a resident driver developed to transform a button matrix connected to the LPT parallel port into keyboard commands. The system allows control of two players, action buttons, tokens, Start, and service functions. The DOSKTEST program is also included to test the button connections and verify the matrix's operation before starting the games.

The SETUPI, SETUPARCADE, DOSKEY34, and DOSKTEST programs were developed in 16-bit DOS C language, and their source code is included with the project. Compilation can be done using Open Watcom C/C++, allowing other users to study, modify, correct, and improve the system.

ArcadeDOS was created as a free, non-commercial community project. Its goal is to preserve the use of old computers in arcade machines, facilitate the assembly of custom arcade machines, and provide an open base for new developments.

Third-party components present in the system remain subject to the licenses and conditions established by their respective authors. ROMs, game BIOS, and other protected content are not part of the original ArcadeDOS code and should only be used when the user has legal authorization.

The system is provided without warranty. Features such as partitioning, disk formatting, video frequency configuration, and electronic circuit assembly should be used with caution, following the project documentation.

Download link: https://archive.org/details/arcade-dos

* I have no affiliation with this project. I simply ran the text through Google translate.

Enclosures will also be available soon, depending on the quality of what I get back from the 3D printers. The first small batch have already been printed to Ond's design and should arrive any day now. I am reluctant to offer them for sale yet until I give them a proper quality check. So here's a deal: if you order a GreenAntz "Sync-off Ant" right now, I will include a free enclosure with the first four orders (I have already received one pre-order, so that leaves three more). Assuming they pass quality check, of course

All free enclosures have been claimed. No more free ones.

Also, they're taking a bit longer than I expected to arrive, which affects everyone.

If you want to order a GreenAntz v2.3 with an enclosure, probably best to wait. Keep monitoring this thread, I will post developments over next for 2-3 weeks.

Apologies to those affected by the delays