x=usr(1536)

That's pretty slick We couldn't really automate it too much since we had to use a country-direct operator. AT&T stopped working c.1990 or 1991, IIRC, but Sprint kept going until around the mid-'90s. Overall, it was a lot more efficient to just mail a brick of disks if uploading or downloading was the desired end result, but obviously this didn't work so well if your interest was in messages bases and the like

Entirely possible. The first time I saw the Internet was at UCLA in 1988; my mother has a friend who was a research physicist there at the time, and she showed me USENET. That said, there wasn't much in the way of public access to it at the time.

Adding to the hypothesising: it always struck me as being a support to prevent the keyboard caving in when someone stabbed a console key with the might of a thousand piledrivers

Fixed The suspicion that R53 through R56 may have been flaky was borne out after removing R55 and R56. R56 had a crack underneath where it couldn't be seen easily, and R55 was out of spec. Decided to replace all four with new 1KΩ resistors, which definitely helped but didn't solve the problem entirely. What did solve it was discovering a bad jumper on the UAV. It occurred to me that this was something I hadn't checked - usually, I omit the jumper block completely and just solder the jumpers in place since it keeps the installation much lower-profile. However, on this one I wanted a UAV that could be pulled and reconfigured to work with a different machine for testing if needed, so kept the jumper block in place. It never occurred to me that the jumpers themselves may be an issue during the early parts of figuring this out. In any event, here's what it looks like now: Still need to dial the colour in a bit more accurately, but overall it's a huge improvement. Thanks to everyone for the assistance!

One would hope so, yes

Would you mind posting photos of this? Don't believe I've ever seen one of these before and am really curious about it.

Very possible. For background, macOS typically uses macFUSE to do FUSE stuff. Its version is currently at 4.50, but how that relates to Linux versioning I have no idea. I believe that it's based on FUSE3, but don't quote me on that.

@pcrow: Something I forgot to mention: under macOS, atr2unix, basicanalyzer, and unix2atr will build successfully using `clang <filename.c> -o <filename>'. As far as I can tell from limited testing, they seem to work fine. This is under macOS Ventura 13.5.1 with whatever the current XCode and commandline tools environments are installed. The FUSE module, binload.c, dcmtoatr.c, and sio2linux.c don't build. However, this looks to largely be a path issue involving header files not being where they're expected to be. Note that I haven't looked into this deeply, so am likely not anywhere near 100% correct as to the issues involved. Not expecting you to do anything about this - just wanted to mention that there is some degree of cross-platform compatibility, and make a note of what I've found.

If you're considering it for testing, pick up a Junior instead. The 2600+ is essentially an emulation box and doesn't operate in the same ways as actual hardware. It's also not compatible with things like the Harmony, etc. More info:

Oh, wow. That is *huge* Thank you! This will make comprehensively cataloguing software much easier.

The title screen looks really nice Unfortunately, I get a hard crash on both my 7800 and 2600 Jr. after starting the game. The maze draws, everything is visible, and right after the tune plays both machines lock up. This is on the 2600 Jr. with a Harmony Encore, and on the 7800 with a Concerto.

You are correct. Apologies for any confusion; I'm running in a massive sleep deficit right now and am not at my mentally-sharpest as a result. Which I have certainly done before. They're not particularly near anything I would've been likely to have touched in terms of installing the UAV and monitor port, but clearly something isn't right with them. In any event, they'll receive Special Attention™ this weekend. Makes sense. Power and ground are both good at the socket and multiple points on the UAV. Got it, and makes sense. My cables are not properly shielded, so I've made my peace with the jailbars for now

I just want to know when the 5200, A8, and ColecoVision ports will be available.

Putting thermal paper through the 1020 isn't really recommended. Depending on type and condition, it may leave residue behind. There's also a chance that it could clog the tips of the pens when they're in contact with it. Best to just use regular paper. I'll give a recommendation for those gear kits; so far they've resurrected two different 1020s for me. Just don't lose the tiny C-clips that hold the other gears on...

I'm looking for two copies of Rev. C BASIC. On cartridge, ROM, or EPROM is fine. If you can help, please let me know. Thank you! Got it sorted out. Thanks!

OK, I may have found something. There are four 1KΩ resistors at R53 through R56. They correspond to LUM0 through LUM3, respectively. R56 is reading 0Ω, but isn't open (i.e., shorted). R55 reads about 850Ω when it feels like it - at other times, it's as though it's going open internally. Both follow the pattern of more uptime = more heat = more obvious failure. I don't have the time to go further with this at the moment, but I'll pull them out-of-circuit this weekend and test them individually just to be sure. Fortunately, I have a ton of 1KΩ, 0.25-watt resistors floating around, so replacement won't be a problem. The version of the 600XL FSM I'm using right now splits the signal path from the GTIA to the 4050 across two pages. This is fine, but the pages were scanned offset, so the circuit lines didn't match across pages. My guess is that I didn't really pick up on this earlier, so mis-read the schematics as a result. Makes a lot more sense now.

Yep, both UAVs are Rev. D units, and both sets of jumpers match. That's actually something I didn't give much in the way of consideration to because I was using the 4050 socket rather than pulling power (and signals) directly to the UAV from the motherboard. Any recommendations on where to pull power from? My knee-jerk thought is to use the main +5VDC and GND rails.

There's some anecdotal evidence to suggest that they may not fit correctly: https://www.msx.org/forum/msx-talk/hardware/reinking-pens-for-the-sony-prn-c41-and-atari-1020-plotter However, 1020 pens can be re-inked. Not ideal, but it doesn't look like there's a ton of call for a replacement drum that can handle something modern and available so may be the best bet.

Good point. I haven't got around to piggybacking the 4050 onto the UAV yet, so it's not in place at the moment.

Had a chance to do some GTIA swapping. Verdict: it's not the GTIA itself. Whatever it is, it's somewhere between the GTIA and monitor jack. My suspicion is that one of the passives in the general area of the 4050 socket (which was tested for shorts / opens with none found) may have been damaged during the UAV's installation. It's nothing more than a gut feeling, but they'll get re-checked. Work's ramping up on me for the rest of the week, but I should have time to pick back up on this over the weekend. Thanks to everyone for all of the suggestions; they are definitely appreciated.

Nothing. None of the Flashbacks, plug-and-plays, or the Nu-VCS had any effect. There's no reason to think that this one will.

Exhuming this thread because I ran across a case earlier today where being able to switch from the Kiloparsec BIOS I'm running to a stock OS ROM would have been extremely useful. As mentioned, this 7800 has the Kiloparsec BIOS installed, which means that a) all 28 BIOS pins are available, b) the BIOS ROM is socketed, and c) there's a 74LS04 piggybacked onto the 74LS08 with attendant wire to pin 22 of the BIOS socket attached. Is there anything in this configuration that may preclude a 4-in-1 OS board from working? I'm guessing that there isn't, since the actual switching is handled on the 4-in-1 PCB. Late edit: decided to just go ahead and order the @Mr Robot 4-in-1 PCBs; they should be here in about 2-3 weeks. Got 10 each of the two different offsets:

There's a version of Berzerk (Berzerk - Voice Enhanced) that adds non-Atarivox speech. This may be based off of that one.

Since there are now multiple threads going regarding this device, I wasn't aware of this until now: Basically, international retailers are being worked on and an announcement should (presumably) happen relatively soon.

Maybe. Bear in mind that ITAR covers both hardware and software, so either one could be a potential block to export. FWIW, I'm not referring specifically to crypto when I say that; just speaking generally. ITAR's had some significant changes over the years and crypto is just one of them. Either way, I can't see why the machine wouldn't be eligible for export: unless the modern equivalent of Henry Thomas' Cloak & Dagger cartridge is hidden in there, it should be pretty easy to certify for an exemption if necessary. Foreign ownership of the company may throw a wrench into the works, though that's more speculation on my behalf. Of course, we are talking about Atari, SA. Competence isn't really one of their strong points.