NISMOPC

Still seems odd my other SD-Max works perfectly fine. It's an official ATARI (NOS) serial cable and works just fine with everything previously. Just not this different version SD-Max.

Both the WiModem232 and the SDrive-Max are powered by their own 5V USB power supplies. No power is used by the SIO for these. The nice thing about that is you can select what disk image(s) you want to load on the 8-bit before turning on the computer.

=> SDrive-Max 130XE => 1050 (D1) => 1050 (D2) => P:R:Connection < => WiModem232 (serial port) As stated, my other SDrive-Max (socketed chip with pin#2 bent up and connected to RX, diode on TX) works flawlessly with this same set-up. This new build is using the chip on board with sub-board and is the one I am having the issues with. Only works when the 130XE is powered up OR when the 130XE is powered down and there is no power getting to the WiModem232. Makes no sense to me.

Seems accurate, but the sub board chip is supposed to take care of that as stated. So, not sure what is going on.

Latest saga.... My current SD-Max is based on the socketed chip version, RX connected to bent up pin #2 on chip. Works flawlessly. Just because, I decided to build another SD-Max using an UNO R3 with the chip on board and the v3 sub-board. Set-up using a P:R:Connection with WiModem232 and two 1050 drives all daisy chained. Everything seemed to be working fine and identical results as my other SD-Max until I decided to turn off the computer and tried to load different files on the SD-Max. The touchscreen is non-responsive. After messing around for a bit, I found out that if I remove the USB power from the WiModem232, the SD-Max works as expected. So the problem is if I have my computer on, I have no issues with the current set-up. If I have the computer off, I have to unplug power to the WiModem232 to be able to use the SD-Max. My other SD-Max does not have this issue. Thoughts? Pics of new build... ***brown wire is not being used and is heat shrinked to protect from board

I noticed you do not have a DIODE inline on the TX and are not using the #2 pin up on the socketed chip for the RX signal. Are you using this as your only connection via the SIO or is it daisy chained with other hardware? It will have conflicts with other hardware if you are attempting to use it within SIO daisy chain.

Aha! I did not think to try it alone, but then defeats the purpose of the Navarone, right?

Ha! Actually bought a Navarone NOS in box not too long ago just because I wanted to have it in my collection. Never had one or possibly ever saw one back when I first got my TI in the 80's, so when one popped up for a good price I bought it. ...and no the FG99 does not work in the Navarone. First thing I tried...

About 2+ years back shopgoodwill was a great place to get retro stuff cheap. I would be on there all the time. Things were going for great, reasonable and acceptable prices and I actually added quite a bit to my collection. I have since stepped completely away from that site. Prices are inflated (only assumption is inside job to jack prices up) and sometimes, if you do not check, shipping and handling has become ridiculous as well. Go elsewhere for your goods. They are no longer beneficial to collectors...

SOLVED: Guess you can teach an old dog "old" tricks. I did not pay attention to the sectors on the disk I was attempting to image. Finally took a look and added up all the files. 707 sectors. SOB! I was trying to duplicate a physical SD image to a DD formatted disk on the SDrive-Max. Anyhow, I created a <new> image and formatted it single D and all is well. Duplicated the 1050 physical floppy without any issues. My S-Drive is operating as it should be and I finally figured out what was wrong. Me... ...back to the basics. Guys, I appreciate all the information you provided and to Rybags... ...I should have paid a little more attention to this. I was using 1050, but this should have given me the proper insight into actual issue and I overlooked. EDIT: This was all while using DOS 2.5 for those interested.

SOLVED: Guess you can teach an old dog "old" tricks. I did not pay attention to the sectors on the disk I was attempting to image. Finally took a look and added up all the files. 707 sectors. SOB! I was trying to duplicate a physical SD image to a DD formatted disk on the SDrive-Max. Anyhow, I created a <new> image and formatted it single D and all is well. Duplicated the 1050 physical floppy without any issues. My S-Drive is operating as it should be and I finally figured out what was wrong. Me... ...back to the basics. EDIT: This was all while using DOS 2.5 for those interested.

I did see it (and thank you!), but still had no luck. Same ERROR- 139 no matter what procedure I attempt. Figured I'd have others try same procedure and post their results. Might be an issue, might not. I just haven't seen may posts of individuals duplicating physical floppy images to SDrive-Max atr images, so I don't have much to go on.

This is exactly what is needed. Excellent information for current and future users of SDrive-Max builds!!!

Would you be able to test something for me? Having issues with trying to create <new> image, format it then copy a physical floppy from 1050 drive to the new image. Keeps erorring out ERROR- 139. I started a separate thread with this issue, but figured since you just completed your build (I did the pin to to RX as well, just no switch yet).

Will give it a shot tomorrow. Thanks

These floppies I have (new old stock) are what I've used forever since the 80's. I've copied images from 1050 to 1050 on them a few times. Didn't think it would be any different using them to copy to a SDrive-Max image. I tried to use the 1050 option in the [cfg] menu as well to see if any changes, but nothing.

I am able to do this within the Sdrive-Max. It's when I am trying to copy a physical floppy disk to the newly created image. I didn't see you mention anything about physical floppies in your post.

OK, so now that I have my replacement SDrive-MAX built and working properly, I am trying to image a floppy disk from one of my 1050's to a new ATR image on the SDrive-MAX. All sio communications are working. I am able to switch from drive to drive, load from all drives, read from all drives, etc. (via SDrive-MAX and both 1050's). So I know there are no SIO communications issues. I have tried several different options with below steps and continually get ERROR -139 Load DOS 2.5 via 1050 Drive 1 Create new image and format via SDM Drive 2 Swap DOS 2.5 floppy with floppy I want to image Option (J) Duplicate Disk Source,Destination D1,D2 [ENTER] I've tried duplicating floppy from 1050 Drive 1 to SDM Drive 2, 1050 Drive 2 to SDM Drive 1, etc. etc. I've also tried loading DOS 2.5 from SDM Drive 1, emptying that drive and duplicating from 1050 to SDM Drive 2. Every time it reads the source floppy, then beeps and spits out the error message. Nothing else happens. I have no issues duplicating disks from 1050 Drive 1 to 1050 Drive. NOTE: I always turn off whatever physical 1050 drive I am using in SDM so there are no conflicts with drive #'s Error-133 Device or file not open. This error occurs when truing to access a file or device that has not been OPENed. A common cause of this is a mistake in your file specification, either on OPEN or when trying to access the device.

BigBen - Just to be clear on this. RX to Pin 2 is the correct connection to make. Leave TX as is WITH the diode inline?

Total confusion now 🤪 Glad I did not change mine yet. Will wait for final agreeable pin and wire before doing anything.

Fixed!

Mr Robot - That would be great. I was just reading that portion of the thread when I saw he re-posted regarding PIN 3. I am still not quite comfortable with the direction. It states: "Arduino Uno Atmega put out of the DIL socket and bent out Pin3, put it in the socket and connect with SIO Pin3." Am I to understand that I do not solder the SIO pin 3 connection directly to the board but I will solder it to the pin 3 of the socket that I bent out (with inline diode)? And it does not need reconnected for programming since I will program via USB connection IF I need to? UPDATE: Was posting this same time as above post. Just went and read that link of information Mr Robot. Thank you... THIS clarifies it!

Well hot diggity dog [email protected]! - How did I miss that! Guess I'll build another one with a generic chip on board version with the sub board as a backup then.