Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

IBM PC XT 5160 Tandon TM100-2 issue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    IBM PC XT 5160 Tandon TM100-2 issue

    Hi,

    I have an IBM PC XT with a Tandon TM100-2 floppy drive that is having some issues.
    C43 blew upon startup so I replaced that one, and I found another cap that was bad according to my ESR meter. I replaced that cap also and cleaned the heads but it is still not reading disks.

    Upon startup I can see the drive motor spinning, and I also see the stepper motor moving the heads back and forth (as you typically see on a floppy drive) as illustrated in the video below :

    https://drive.google.com/drive/folde...Hk?usp=sharing

    But when trying to access a disk (doing a directory listing, or trying to format a disk), i see the disk spinning but the head is not moving.
    This is then followed by general failure reading drive, or a bad track 0 during formatting.

    The floppy controller / cables seem to be ok as I've tested it with another drive. Drive termination and dip switches also seem to be fine.

    What could be causing the fact that the heads move back and forth on startup, but they aren't doing anything when trying to access a disk ?

    Thx
    Retro enthousiast. Love everything < 486. Learning and sharing on my little channel

    #2
    Not all PCs do a seek at boot. But since yours does, movement is at least a good sign. (What kind of controller are you using, and what exactly is the machine doing when the drive seeks? )

    Most of what DOS needs to start reading a disk is on track zero. So if it can't read at all, it may just sit there.

    Without knowing more, there are a number of possibilities, including read head failure, read head dirty, head alignment, read circuitry failure, read line failure in the cable, drive speed wrong, perhaps index sensor issues (although depending on the machine, DOS may read a disk even without an index).

    I'd sanity check a few things first if you haven't already. Make sure the cable and controller works OK with another drive. Make sure the disk you are reading is known good, low (double) density, and was not written in a 1.2mb drive.

    Try formatting a disk - if it formats but does not read other disks, that indicates an alignment problem.

    Try running ImageDisk, and see what it reports. If it reports no interrupt from controller, that could indicate an index issue. If ImageDisk runs, try running it in alignment mode - you may be able to manually step the heads, and if the head is over the wrong track it may show you which track it is over.

    Comment


      #3
      the track 0 sensors are known to fail on those drives, check that

      it's a mechanical switch not optical

      Comment


        #4
        Originally posted by SomeGuy View Post
        Not all PCs do a seek at boot. But since yours does, movement is at least a good sign. (What kind of controller are you using, and what exactly is the machine doing when the drive seeks? )
        Most XTs seem to do a seek at startup, and i am using the standard IBM floppy controller.

        Most of what DOS needs to start reading a disk is on track zero. So if it can't read at all, it may just sit there.

        Originally posted by SomeGuy View Post
        Without knowing more, there are a number of possibilities, including read head failure, read head dirty, head alignment, read circuitry failure, read line failure in the cable, drive speed wrong, perhaps index sensor issues (although depending on the machine, DOS may read a disk even without an index).
        I'd sanity check a few things first if you haven't already. Make sure the cable and controller works OK with another drive. Make sure the disk you are reading is known good, low (double) density, and was not written in a 1.2mb drive.
        Try formatting a disk - if it formats but does not read other disks, that indicates an alignment problem.
        I've already

        - cleaned the heads with IPA
        - replaced caps that were faulty
        - checked the setup with a working floppy drive to rule out cable / controller issues. And the system can read / format floppies fine with the working floppy drive.
        - tried different disks 360kb disks, attempting to read floppies that work on other systems, but also tried formatting floppies. (to rule out alignment issues)

        Originally posted by SomeGuy View Post
        Try running ImageDisk, and see what it reports. If it reports no interrupt from controller, that could indicate an index issue. If ImageDisk runs, try running it in alignment mode - you may be able to manually step the heads, and if the head is over the wrong track it may show you which track it is over.
        Will give it a try but figure as it doesn't read any of my current floppies that changes are slim that it will read that one. But thx for the tips !
        Retro enthousiast. Love everything < 486. Learning and sharing on my little channel

        Comment


          #5
          Originally posted by maxtherabbit View Post
          the track 0 sensors are known to fail on those drives, check that

          it's a mechanical switch not optical
          That's the microswitch next to the drive motor that is pressed in when the head moves all the way back I guess ? I did spot that one and it did "sound" ok when I clicked it, but will check that one. So this is pressed in when the head moves into the position that it thinks is track 0 ?
          Retro enthousiast. Love everything < 486. Learning and sharing on my little channel

          Comment


            #6
            Originally posted by maxtherabbit View Post
            the track 0 sensors are known to fail on those drives, check that

            it's a mechanical switch not optical
            Took another look at it and noticed that the 2 terminals coming out of the microswitch don't have continuity when I toggle the switch. So this might be the culprit

            2020-07-07 07.45.03.jpg
            Retro enthousiast. Love everything < 486. Learning and sharing on my little channel

            Comment


              #7
              Originally posted by RetroSpector78 View Post
              Took another look at it and noticed that the 2 terminals coming out of the microswitch don't have continuity when I toggle the switch. So this might be the culprit

              [ATTACH=CONFIG]61874[/ATTACH]
              Sounds like it

              Comment


                #8
                A better way to test the switch is to get on the Pullup Resistor(s) and check that it is being pulled "LOW".
                If you are just measuring the two wires, there will never be any resistance from one to the other when
                the NC or NO contacts are "MADE" (CLOSED), unless you are measuring the wire(s) to GND.

                I've attached a .PNG of the actual Schematic.



                Larry

                Track0-switch.png

                Comment

                Working...
                X