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

Miniscribe 2012 disk defect

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

    Miniscribe 2012 disk defect

    Hello, i have Miniscribe 2012 hard drive connected ONLY to power supply without any data cables connected. Disk LED have recurring blinking, there is video below. Any ideas?

    https://youtu.be/3G5wnVBDRdI
    IBM PC 5150(A): IBM PC 5150(B): IBM PC 5160 (64-256k): IBM PC 5160 (256-640k): IBM PC 5170 (099): IBM PC 5170 (319/339): IBM PC 5140: IBM PC 5162: IBM PC 5155: IBM PC Expansion Unit 5161:
    WANTED!: IBM 5175 monitor, IBM 5145 monitor, IBM PC/XT/AT rear screws, Intel INBOARD 386AT card, IBM 5140 keyboard, very early IBM PC (S/N: under 5000)
    My IBM PC hardware collection

    #2
    In some Miniscribe manuals, the blinking error codes for the drive are explained.
    For example, look at the bottom of the manual for the M8425S, at [here].
    If (repeat: if) it shares the same error codes as your drive, then the pattern is 1000, which equates to code 8.

    Comment


      #3
      Originally posted by modem7 View Post
      In some Miniscribe manuals, the blinking error codes for the drive are explained.
      For example, look at the bottom of the manual for the M8425S, at [here].
      If (repeat: if) it shares the same error codes as your drive, then the pattern is 1000, which equates to code 8.
      Code 8 - Unable to uncover Track Zero sensor

      In some Miniscribe drives that error can be caused by the position indicating flag on the shaft of the head positioning stepper motor having worked its way out of position. On some of the drives where that was the case there was a test jumper block on the controller board of the drive that could be shorted together and then when the drive was powered up it would go into a mode where the position indicating flag could be rotated back into the proper position. The set screwed holding the flag in place on the shaft needed to be loosened, and then the flag could be carefully rotated into or out of the path of the photo detector just until the threshold of the LED turning on or off. Right at that threshold the position indication flag should be back into the proper position and the set screw should be carefully tightened without rotating the flag or the shaft. Then the drive would be powered down and the jumper removed and if everything went just right it would power up normally again after that.

      That was 30 years ago when I had to do that to multiple Miniscribe drives. I'm fuzzy on the details now.

      Comment


        #4
        Hello gslick,
        I have a MiniScribe 8425SA disk from a Macintosh SE restauration project.
        The failure code is the same - Code 8: Unable to uncover Track Zero sensor. You mentioned in your previous answer the "test jumper" to teach the position of the Track Zero. I find the documentation of this hard disk (https://stason.org/TULARC/pc/hard-dr...-SCSI1-SE.html) and there is no "test jumper", except I find one more "pin" (it is like a half jumper, only one pin) on the PCB but this is not documented anywhere.
        Could you remember if this single pin could be the test jumper? if I shorten to GND then this will be the "test jumper" what you mentioned?
        I also find the MiniScribe_III_Product_Manual.pdf (http://www.bitsavers.org/pdf/miniscr...uct_Manual.pdf) there is a flow chart how the initialisation of the disk made at the startup time. On page 44, is the "Code 8" detection.
        I think, with the reset of the position indicating flag could solve my "Code 8" problem.
        I don't think so, the IR LED or the IR sensor is wrong, please correct me, if they could fail.

        Thank you.

        Comment


          #5
          I just did a photo about the PCB of the MiniScribe 8425SA and prepared with few labels - for better orientation.

          Comment


            #6
            Hope it helps. When I have a Code 8 - Unable to uncover Track Zero sensor, many times the stepper motor is a little bit stucked and performs well in the first searching pattern with a low pulse rate, but when put in a high pulse rate (the second part of the seeking power on rutine) motor stucks and not covering track zero sensor. If it is the case and no error in PCB components, you can use Miniscribe exercise routine JP13 (I dont remember which jumper is in 8425SA, maybe your diagnostic pin in your picture). If it is not a mechanical stuck, then always there is a component near the RIFA PBL 3717 (stepper motor controller) that is burned. You need to check also the track zero sensor (4 pin connector near the 4 pin stepper motor connector)

            Comment


              #7
              Thank you. Finally, I was able to set the flag to detect Track Zero. Sadly the disk lost its information about the insode disks - or I don't know why - but it is not possible to format it.
              I will still try different ways with this unit.
              The idea is to do a capacitor renew (recapping) maybe the write amplification and/or the read amplification is not good anymore. It seems the mechanical issues are solved but still something not 100%.
              Stepper motor works (fully lubricated), disk drive motor works nicely, spins up easily, everytime. Track Zero flag set and no more Code 8 anymore.
              Thank you very much to both of you.
              I'll give feedback after the recapping.

              Comment

              Working...
              X