_The Doctor__

Jail bars, Shielding issue of cables, they need to be shielded on each lead and then shielded as a group, then motherboard shielding. Power to video circuit issue. When restricted can amplify another issue. The other issue involve oscillator vs crystal and Freddie decoupling cap routing issues ( I add the cap when missing and complete part of the crystal circuit to clean it up) Some power supplies introduce video issues as well. Lastly make sure all of the system is plugged into same outlet or strip/power controller.

odd in that others use it in past just without issue. looks like something is being over looked as the method the joystick employ are the same the only difference being power pin and return, otherwise dpad is high or low for direction weather it be Sega, C64, or Atari.

Great to see it's working so nicely ! very worried about the static hum bars travelling up the screen on your setup. Ground loop, shield, power, cabling, something in the setup is making it's plight known. Nice to see it all in action and you've started putting it through it's paces.

Looks promising. Keep it coming!

Notes of that nature lead to more software being made, as programmers know what to expect or look to do. It was not all that long ago a nice fellow started posting what they were doing with a few demo screens of pictures and animations as well as 80 column color text displays etc. It would seem others have done the same since and it's leading to some very positive outcomes. It's also good to see what hardware issues have arisen with fixes and workaround methods being employed. All very helpful.

Please update your FujiNet Firmware and you will find a much better experience all around now, as it boots faster and is more reliable with v 1.3.0

looks pliable, it's a possibility at least.

I think the question was, did you isolate the pins before the rewire inside the 8 bit do? An external adapter or pigtail would not require that in theory... make sure you Atari ports are still fully functional and no passive inductors/components have been cooked/damaged. Same check inside the do.

Spies have been know to help spies, even on the opposing team, and let's not forget those double and triple agents... 😮

are you sure of your pin out understanding, as plug and jack are reversed when mating?

might be helpful to show sdrive max settings and what you have in the drive slots. make sure screen saver is off, any speeder should be off, long file names off POST your atr so it can be checked to see what you are using and what combination DOS/xex etc.

what version is that? crashing should never occur. try RI see if the box appears then DTR and see if the check box appears... (just to see if it's in there somewhere) I had mine set at 300 so 250 sounds about right. DTR control is normally used to switch devices between SIO 2 PC computer vs SIO 2 PC drive modes If this is the latest version with the build crashing, you will need to contact JoSch on discord because that's bad and I haven't seen that since AspeQT days. I am using Windows as of late so indicate to the team on discord all the normal information/ Linux build ver etc.

Tools Options Serial port backend make sure the correct flow control handshake is selected for your specific cable a check box exists for edge timing (normal or falling edge) slight at the bottom is further timing in uS for timeouts etc. there are further adjustments for SIO divisor rates as well, greyed out until boxes are ticked. these appear and disappear based on selections already made that pertain to the functions.

For your sector copy use mydos, it should work fine. As to RespeQT, you may have to pick a different edge timing in it's config depending on your port. (while this matters on a real RS232 port, it seems to affect USB timing ever so slightly as well.) The sector copier is MTL at fault. What are you using?

So I should have said traffic cops, someone is taking too long getting the message in or out on the radio/walkie talkie and the stop signs on either end of the single lane are not being turned in sync. So you will have a head on or no cars at all for a bit. Unless there is a glitch in the instruction being executed that is. Anyway faster saves might have been helpful keeping waiting data from occurring or timing out.