Joey Z

unfortunately for you, it's far from complete, and is barely usable. Color is supported, maybe clearing the screen, but you can't call it a fully featured terminal emulator by any means. Config is hardcoded, etc. Lots to be done, but I'm busy. Some Day (TM) I'll get around to working on it again and/or posting the source so others can work on it on their own.

Good that you got it figured out. Hopefully Stephen can figure it out too, if he was looking to mess around with it.

manual says pins 3 and 4 http://www.atarimania.com/documents/PR_Connection_Owners_Manaul.pdf

yeah, it was several years of school, internships during the summer, and now employment and moving to my own place. I'm just as busy as ever even with the pandemic. Besides that, I've got a list of projects, things to be fixed, etc. spanning several pages and it's always growing. Several Atari projects have taken the backburner. I really would like to get back to this though. Well, I really should get back to paying work now....

You were using the version from april 7th, 2015? White cursor on a black screen is basically what you'll see when the terminal is working but not hooked up to anything. Do you get keyclick? I can't remember if I left keyclick on or not, think I did. Might even be done in the terminal software itself (or maybe that was the bell character where I was messing with the internal 'speaker'). Try using a piece of wire to short TX to RX on the PRC and see if you get characters echoed back. EDIT: checked the source, no keyclick seems to be implemented. Nevermind that then. See if you can get echo.

I wish I had time

AspeQt is the software that RespeQt was forked from. AspeQt was originally created by Fatih Aygün (cyco130 here IIRC) as an open source software for SIO2PC based peripheral emulation. At some point, cyco130 stopped working on AspeQt and the project got handed off to Atari8warez who worked on it for a while after that. Several years ago, Atari8warez got himself banned from Atariage and decided shortly after those events to attempt to close the source of AspeQt (outside his rights to do so, but nobody was about to take someone to court over it). At that time, I forked AspeQt to form RespeQt so that the community could continue development on the software separately.

Assuming you mean the icon that looks kinda like a funky R, I think it was supposed to be an R styled kinda like half an atari fuji maybe. It was contributed by a member here IIRC.

I'll correct you here, the original author was Fatih Aygün, not the Ray Ataergin you're thinking of. EDIT: to clarify, ray AKA Atari8warez was the 2nd maintainer of AspeQt, after Fatih passed it on.

I don't think it's possible at this point to simply fold it back into the original project. Nobody here has access to the sourceforge repos since the last AspeQt maintainer is banned, unless the original creator of the software still has repository rights and can be contacted. I believe the original creator was Fatih Aygün.

While I see where you're coming from, at this point I think RespeQt is a name a lot of people know in the Atari 8 bit computer community. To a newcomer, I don't think AspeQt has any more initial meaning than RespeQt, and it doesn't really make the software any easier to find by using the old name. Changing it now would just add confusion, I feel. Obviously at the time it was forked, RespeQt was selected as a name to poke fun at the events concerning the primary maintainer of the old AspeQt software. It accomplished the goal of setting the project out as a different piece of software, maintained by different people. It was important to differentiate it then, which is why so many of the initial changes I made were geared towards removing references to the AspeQt name and replacing with RespeQt where the project was referred to. References to AspeQt remained, and may still exist, where they made sense to refer to the separate project. Beyond that, AspeQt does still kind of exist in it's original form, though it doesn't seem to have been updated in a while. The existence of multiple projects with the same name would only add to any resulting confusing IMO.

And now we've fixed this. Today I transferred the official RespeQt repository to ebiguy. Several years ago, I forked AspeQt into RespeQt after the AspeQt maintainer decided to try and close an open source project (not within his rights, but that's a story for another time). At the time, I mentioned several times publicly that I thought it would be a good idea if someone would fork AspeQt and create a new project under a different name, but nobody took the bait and I was forced to do it myself ? I maintained RespeQt for a while, implementing a handful of features and handling a few bugs, but eventually college and then later employment continued to get more and more in the way of maintaining it, as well as other projects I was more motivated to work on. It's been clear to me for a while that it would be better to hand the project off to someone else, and ebiguy seems as good a person as any. I hope RespeQt will continue to get worked on as one of the free alternatives for SIO2PC peripheral emulation. It may not have every feature you could want, but it still worked last time I checked, and you certainly can't beat the price ?

Found the logs, cleaned up to have just the PLATO stuff, here they are: https://pastebin.com/2E429mfK I first connected on January 7th using TLP, took me a bit of fussing around with a sniffer to figure out that shift+SUB sent the right code to do what should have been shift+STOP and actually get logged in. I had trouble reading some of the screens though, because the color codes got in the way a lot.

Well, I'm glad to see much has been accomplished already since I initially logged in to my account back sometime in january (account created the 7th, probably logged in 9th or 10th, I'd have to check the IRC logs). I guess I beat you all to the first signon from an (unfortunately emulated) Atari in 35 years I would like to be able to use the 800XL, but my 850 is 150 miles away... Hopefully somebody can hack in support for disk loaded R: drivers, and then I can figure something out (or else I might have to see if the APE trial will fire up in wine or a VM). Also, I guess I'll see if I can get my group changed to the atari one.

OK, well the only other way to go about this is for me to start building from various commits and trying to narrow this down. I'm not doing that now, I have to get some sleep and move my stuff down at school tomorrow, I can't get around to it until next week at the earliest.

Try this. RespeQt-r4-test-win32.zip

Ray's SIO2PC is just an FTDI chip, except that it has the VID/PID changed. This prevents the normal FTDI drivers from detecting the chip as an FTDI serial converter. Somewhere on Ray's site, I think there is the program to set the VID and PID back to the normal ones so the FTDI drivers will recognize it normally.

what kind of serial SIO2PC are you using? I don't suppose you happen to know if it requires DTR and RTS to be in a specific state? the behaviour of these lines was changed between r3 and r4.

Also, which handshaking method? Are there any messages in the log window? Lastly, we changed the method of serial port selection in RespeQt with this latest release. Please try selecting a different serial port in the options menu, save the settings, then again select the correct serial port in the options menu, and save the settings again. I don't remember off the top of my head how the serial port selection works in handling invalid settings in the configuration file, but it's possible there may be two entries in the list which appear to be correct, in which case you should attempt to use the other one. That's really the only change I can think of that would cause this, is that you're not successfully opening the serial port. This is why you need to post the contents of the log window, there may be an error about this there.

The Atari SIO bus is what's known as 'open collector' on the RX line (device --> Atari computer). This allows multiple devices to use the line without interfering with each other. The diode is a kludge that converts a normal push-pull signal into an open collector signal, and is generally good enough in this case. Without the diode, the FTDI can drive the line high and, if it drives hard enough, prevent the real disk drive from communicating.

Not to mention, these *are* atari *computers* we're talking about here, dunno why you are all trying to use them on TV's anyway

What, you mean you don't like writing drivers? I figured they were your favorite thing in the whole world, based on how much time and effort you put into APT drivers, for example.

well, I also meant the text above each button, and the text on the lower part of each button. You also need to be reminded which is which there.

How much will you pay me? PCB design work usually goes about $100/hr.

yes, that looks great. At least the graphics appear to be more than capable, I'm assuming this is just a mock-up? EDIT: I know it'd be difficult, but it would also be great if we could get some color in there for the orange and blue f- and g-shifted functions. it's a bit hard to tell them apart otherwise. Maybe there's some kind of trick that could be used? RE-EDIT: oh, this is the GUI thread, so there's not really a way to do any of that planned for the GUI.