fisherjohnr

Hi folks- I somehow have myself with two threads on the forum with similar topics so I'll link here for everyone to see my progress as noted in the other thread. Sorry about that-I know its bad form to have two posts with the same subjects...I think I lost track of the other thread when I posted this one. Still all great help but sucks to get old:) http://atariage.com/forums/topic/275553-indus-gt-problems-not-reading-dd-maybe-more/

Update: Well the WD40 did make a big difference! Who would have thunk...except for rusty bolts never been a big WD40 fan but now........??? I had previously reseated the chips but will do that again and look closer for any oxidation etc this time. So that and using the info on the typical position for the zero flag have got me to the point by trial and error where I can reliably boot the original Indus DOS disk and the other dos disks that I have. Looking closely at some of the floppies I have I can see some have some kind of "mung" on the surface, probably a mold of some kind from what I read. So I know now I need to be careful about getting the head dirty again. I've separated the dirty looking floppies off to a pile of their own. Any tips on cleaning a disk? I have read some stuff on actually cutting the floppie open .....Not sure about that. So now my next problem, which may just be my needing to get an sio2 cable working and doing the zero adjust with the diag software. I am able to get it to complete a format on a new disk but while formatting it will give some F9 errors but it will eventually complete. Does this software keep trying until it gets it done successfully or does it error and then move along? I have been able to take the formatted disk and using Disc Copy get it to successfully copy my original Indus dos disk but the new copy will not boot yet doing a search shows all files are on it in the directory. It seems to again get hung up on its first try with the zero flag so I'm wondering if I just need to do some more adjusting of the zero flag with the new disc? Reluctant to touch it with the progress I made. So thanks again folks...major progress. I look forward to your continued guidance. John

You guys are great. Now I have the link to the software and a vid on making the cable. And I just finished with a round of the flu so now I'm back at it! Couple of questions...all the cables for sale for this have some active electronics on them and this one is hard wired. Are the active electronics simply isolators? Trying to understand all that as far as the cables I can buy for $50 or so with some active stuff on it vs my making one like this vid hardwired. I am learning some good stuff though both for my old Atari friend and USB cables...... Also..... for following this gents video......instead of cutting a good SIO cable can I, when finished, wind up with the original cable with both ends connected and the USB basically in parallel off the wires he says to connect the USB to? Hope that makes sense. What I'm thinking is if I can parallel the USB onto the existing cable I could still have that cable available for hooking up a second drive some time when I do not need the USB connection ... and I can use the USB part by only connecting the SIO cable on one end to the Atari and the other end left loose. (I see no problem with that of course but next is the real question) Or is there any harm in say having this cable connecting the Atari computer and the Indus drive together and at the same time having the USB cable connected to my PC? Not sure if that would drive the software on either end crazy??? I'm confusing myself trying to type this and hope I'm not doing the same to all here:) Thanks John

Thanks a ton guys. Been sick with this stinkin flu...but I used one of my extra lives and I'm back! I'm going to do the WD 40 head cleaning tomorrow and will let all know how it works. I got some good advice on another thread on making a SIO2USB cable and software so hopefully I can get the diagnostic software usable. Also thanks for the tip on the flag only supposed to be entering about half way as my eyeballing it has been trying to get it fully in. And thanks for all the other helpful tips- printed them out and have them on my workbench. Much appreciated John

Yes yes should have said 30+ years. Just feels longer from my seat:) Just discovered that I bought the wrong usb adaptor - I bought one with a connector for an Arduino and not USB. Damn. So can someone look at this cable and tell me if this will work? I ask on this one specifically as this seller is within walking distance of me and I could get it in my hands today and getting something like this will save me some time if it is the right type. https://www.ebay.com/itm/FTDI-USB-RS232-WE-1800-BT-5-0-USB-to-RS232-Serial-Converter-Cable-Wire-End/202053061542?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2055119.m1438.l2649 Otherwise I need to find something else or break down and buy a package from Atariware or such. Thanks Mark that link looks like the one I was looking for as far as the software goes. Cool beans. Thanks for the tips Xbrevin. I have been able to get it to load Disk Doctor 2 and was able to adjust the RPM down from 292 to 288 but have not noticed improvement. I'm thinking besides reseating the chips again perhaps I should remove them one at a time and use some contact cleaner on the sockets and make sure the chip leads are clean also? And for everything else I need to get an Sio2PC going so I can have the capability but also so that I can download some diagnostic software. Not to beat a dead horse but when I watch the drive error either on a read or when I try to format a new disk its always happens when it goes to the zero sensor. Perhaps that is the wrong conclusion but as I said I think since I have been messing with the zero sensor a lot I need to get that back to where it belongs while perusing other possibilities. I guess I should also start looking at my Happy 1050 also........... So many projects but having fun - I'm going to try some more google searches - if I could just stay away from this sites with Olivia Munn cosplay photos thanks all and I'll update as I make progress......John

Thx Dr for the ideas. Indus is powered via a clean 12vdc supply I also use for ham radio. Fortunately I read about the problems with those old supplies and the 12vdc for the Indus and the 9vac for the 1050...... also tried first the cleaning of the sensor and head and also pulling and reseating the chips and connectors. I am with you that I may have caused more problems by messing with the zero sensor but that ship has sailed as they say so I figure my first thing is to get that sensor set correctly. Hence my trying to find a way to use the sio2usb to get the diag program to get the zero sensor back where it should be... or if anyone has any "tricks" to set the zero sensor without software. Thx much john

OK pulled all this fun stuff out of the closet. Probably have 40 Floppies of games each probably 5 to 8 games each plus quite a few original Floppies with games such as a 15 and software such as VisiCalc also. . The 800 XL works fine after a keyboard change out. The 1050 with the happy had the drive seized I bought a non working 1050 of eBay to swap out but that did not fix it so that's on the back burner. The Indus works sometimes and doesn't work other times either loading DOS or try to load a game and observing it I am convinced it's just a zero Track sensor. I have all my original indus gT Floppies but that diag prog is not on them and I have tried just randomly fooling around with the zero track sensor but I can't get it consistently to work. So I saw some stuff about these SIO2USB gadgets and thought perfect I could use that to get this DIAG program running on the 800 XL so I can get it to set up correctly so I ordered one of those cheapo five dollar interface cards online but now I'm questioning whether I need an operational floppy drive to make all that work or can I connect the Atari 800 XL via USB to my PC and somehow get that DIAG program running without an operational floppy drive. Thought I understood it but today I can't get my brain around it. And I thought I had found links to freeware for the software to do this but I'm not even find a link today so if you guys could point me in the right direction I would appreciate it. Pretty sure I got plenty a cool software that I could share with folks once I get all the stuff up and running. I am I technically OK been but out of it for many years (think being a real estate agent for 20 years caused some "drain bamage"! so go easy on this old guy you young uns<g>. John

Hello all, New member who is trying to resurrect his original Atari 800XL and accessories. Here's the short version but pls read as I explain what I have done so far or ideas I pulled out of my little ole brain! 1) Random read/boot fails 2) Indus power supply issues as they aged? 3) Recap the Indus? 4) Why can't I read DD? 5) Translator program? Fired up the Indus and have been able to use one my floppies to boot up DOS ok. Which comes to problem number 1. It will sometimes read the directory when I ask it too and sometimes it will error. I have cleaned the rails and first tried white lithium grease and then cleaned against and put some silicone spray pointed into a cup and used Q tips to apply the liquid. Neither made any difference. Cleaned the head also but it looked clean. All has been stored in a closet and in a closed box. Note: I did read in my indus manual about sliding the disc in and closing the lever like its one move and that did cut down on the number of boot/read fails I have. Watching it it looks like it always errors when it is looking for track 0 then it goes to 20 (which I sort of remember is where the directory index is but would not bet the Ferrari on it (if I had one:) Thinking this may indicate the sensor for that track zero point but looking at it the flag does completely cover the sensor when it goes to that position. I see in the manual there is a diagnostic program that can specifically look at this and I thought I had all the original discs but no go on finding it. 1) so problem one is the random fails. Usually no more than 3 tries and Dos will boot. Sometimes when checking the Dir of other discs it will work and sometimes I have to try 3 or so times so I do not think its the disc(s). When it fails on any one disc it seems like it will likely fail on the next random disc but a pwoer down power up seems random on if it will work or not. It will also give a G5 or G4 error on a dir read but sometimes it will keep trying and eventually get the read and display the directory contents. I have run a speed check and its solid at 290 which I think is ok. No variation. I am somewhat suspicious of the DC power supply. Without it plugged into the Indus it is at 15.3 v stable and plugged in and the drive on, motor not moving its 13.8 VDC and with the drive and the head moving it varied quite a lot with the lowest I see is around 12.2 VDC. Unfortunately I do not have an oscilloscope at this time. Anyone have the experience to tell me if that voltage should be rock solid or is this variation typical? 2) Any history with the Indus original power supply having problems with age? 3) Should I recap the Indus? I see a 4600 micro F cap c26 that is on the supply + to ground per schematic and some smaller ones on the analog board and from my experience with old short wave and ham stuff and audio stuff the rule of thumb is test and/or replace old electrolytic but I have not seen anything about that with old computer stuff like this. I did not want to get into disassembly to test these caps if its not a likely issue but if its a potential problem of course I will. Now my next problem is I have upwards of 70 to 80 floppies mostly copies utilities and games. Some would allow me to see the directory and some would not. I realized that it was what I think are only SD ones and that it was not reading the DD ones. I have some DOS copies that I labeled DD (about 35 years ago!) so I know for sure they are DD and I have about 30 discs with games on them- not one game per disc either- thinking each disc had maybe 2 to 8 games each??? (from my memory I filled them up one day at work with my boss at the time who was an Atari hound and would get games from some of our customers when he went on the road- how cool was that? and I am 90% sure I would have done that in DD and I cannot read any of them so again I doubt all of those discs are bad and believe its the drive not reading DD. I have the dip switch on the rear panel set for DD and reading the manual it should be able to read each type of disc and switch itself as needed. I have also manually switched it to both 1B and 1C density and put in a known DD disc and nada. I also believe that I need to load a DD version of DOS _ I have a disc with Smart DOS and its labeled SD for side 1 and DD for side 2. I cannot get it to read DD side two with any version of DOS I have (I have SMartdos, 2.5 Atari and the Indus disc that came with it but when I use smart dos its saying its SD. 4) So any ideas on what I can do next or am doing wrong with reading and or booting a DD disc? That answer will set my heart afire seeing all those old games again:) 5) Final question... I seem to remember there was a program called Translator that was needed on some games that were written for the pre XL machines. I can't find it. I also can't remember if that was something that I might have used when burning those discs and could it be I need translator now to use them? Did Translator have anything to do with the buring of a disc or was is simply something that ran in the background? Well sorry for writing a small book here- I am known to be verbose from time to time....So the short version of the 5 questions.. Thanks much fellow Atari friends.... John