Announcement

Collapse

Forum 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.


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.


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.



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.


"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.

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

RLL drive sampling project

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

    RLL drive sampling project

    The interest in Seagate ST-27x drives revived my intererest in a project I've wanted to do for a while, to collect flux samples of RLL hard disks. A friend of mine got
    a Maxtor XT2190 that appears to have been written with an RLL contoller. The problem is there is very little information on what that encoding actually is, so for the
    last couple of days I've been formatting drives with various AT controllers that I own and have been collecting samples, along with making a list of controller read
    performance. The performance is pretty bad, especially the WesternDigital controllers.
    Data is up here:
    http://bitsavers.org/projects/hd_samples

    #2
    Al,

    I have reformatted an ST277 (60 Mb RLL drive) to think that it is an ST251 (40 Mb MFM drive). I just used XXDP to low level format it on an RQDX3 specifying ST251 parameters and I know that some people have tried reformatting ST251 in RLL to come up as 60 Mb drives. As far as I recollect ST277 is a selected ST251 formatted and certified for RLL use.


    Seems to work fine. It an alternative to reformat IBM drive I have in my Micro PDP11/73.

    Peter


    Comment


      #3
      I've got the DTC and OMTI RLL controllers as well as the WD 1006V-SR2. The latter's performance seems to be fine, as your figures show. But it's been years since I've fooled with ST506 interface drives on these controllers. Ultrastor was apparently the best of the crop, but I don't have one.

      Comment


        #4
        I have a flux samples dump from a ST251 I formatted with a ACB4070 controller many years ago. It is from a ABC1600 and has a DNIX file system. I thought I would adapt the Davids mfm reader any day, but it hasn't happened yet.

        https://drive.google.com/file/d/1616...ew?usp=sharing
        www.datormuseum.se

        Comment


          #5
          Originally posted by MattisLind View Post
          I have a flux samples dump from a ST251 I formatted with a ACB4070 controller many years ago. It is from a ABC1600 and has a DNIX file system. I thought I would adapt the Davids mfm reader any day, but it hasn't happened yet.
          thanks! one of the things that started this is I have a V185/ACB4070 combo out of a 3Com 3Server. I went back and made a transition file of the disk this morning and there is nothing on any of the tracks, so I guess I need to look at the read channel on the drive to see if anything is even coming off of the heads.

          Comment


            #6
            An RLL drive you can perfectly LLFormat to MFM, the other way round not preferable due to dense issues.
            An RLL format squeezes the information more tightly onto the disc and increases the effective areal density by 50%.

            Manual Saegate ST277R with Graphs specs and Flux density.
            And find ST412 Manual with the Track format shown. Seagate ST412 OEM Manual 1982.

            A good site with also Drive Information MFM and RLL, REDHILL MFM-RLL
            Also ST277R manual:
            Recording Method
            ----------------
            The ST251 and ST252 are designed for operation with the ST412
            interface with MFM encoding at 5.0 Mbits/sec. data transfer rate.
            Operation of an MFM drive with an RLL controller is not approved by
            Seagate and will void the drive warranty.

            The ST277R and ST278R are designed to operate with the ST412 Inter-
            face with Run Length Limited (2,7) encoding at 7.5 Mbits/sec. data
            transfer rate.

            Comment


              #7
              People's comments seem to fundamentally not understand what I'm doing here. I'm perfectly aware of the differences between MFM and RLL encoding, their bitrates and limitations using RLL encoding on media/read channels designed for MFM. The point of this is there is no documentation on what the RLL flux-level formats are from controllers that shipped on PCs so you don't have any idea on how to write an RLL decoder for them or be able to tell from a flux-level recording what an unknown disk drive was formatted on. I've also discovered that there is low-level interchangability
              between Western Digital MFM formatted drives and a couple of other controller cards that didn't use Western Digital's chipsets, the Everex EV-346 and NDC5525.

              UNRELATED -- CHANGE THE "Write something..." box to be the same width as what you see here so the line wrap isn't screwed up.
              Last edited by Al Kossow; May 22, 2021, 05:47 AM.

              Comment


                #8
                Al, you've probably already done this, but where I'd start is with the RLL controller chip itself, say the WD50C12. The datasheet seems to have a pretty good level of detail, at least as a starting point. Just remember that even if the encoding is (2,7) RLL, that the recording is still NRZ.

                Comment


                  #9
                  Originally posted by MauriceH View Post
                  An RLL drive you can perfectly LLFormat to MFM, the other way round not preferable due to dense issues.
                  An RLL format squeezes the information more tightly onto the disc and increases the effective areal density by 50%.

                  Manual Saegate ST277R with Graphs specs and Flux density.
                  And find ST412 Manual with the Track format shown. Seagate ST412 OEM Manual 1982.

                  A good site with also Drive Information MFM and RLL, REDHILL MFM-RLL
                  Also ST277R manual:
                  Recording Method
                  ----------------
                  The ST251 and ST252 are designed for operation with the ST412
                  interface with MFM encoding at 5.0 Mbits/sec. data transfer rate.
                  Operation of an MFM drive with an RLL controller is not approved by
                  Seagate and will void the drive warranty.

                  The ST277R and ST278R are designed to operate with the ST412 Inter-
                  face with Run Length Limited (2,7) encoding at 7.5 Mbits/sec. data
                  transfer rate.
                  As far as I remember the ST251 was identical to the ST277R drive hardware wise. The ST277R was selected ST251 drives that were in certain specs. Since what is interesting when storing stuff on a harddrive is how close flux changes occur not the data rate prior to coding meaning that the rate of flux transitions is something else than the data rate prior to encoding. RLL differentiate between a bigger set of flux lengths thus storing more information for each flux transition.

                  The problem that occur then is that jitter in the drive speed would affect the flux length. My understandig is that the selected drives had a lower motor speed jitter which giving better margin for RLL coding.

                  it is perfectly possible to format any ST506/ST412 drive with RLL but it might be hard to read it back in some cases.

                  Back then it was quite common to format ST251 drives in RLL. In most cases it worked just fine and you gained 50% capacity. The rumor was that the selection also was based on demand. If there were big demand for 251 drives simply more of them went into that bin even though they might have passed as 277R.

                  Now thirty years later the drive might not be as good jitter wise as once uppon a time and it possible that is harder to read it.
                  www.datormuseum.se

                  Comment


                    #10
                    Magnetic coating had a fair amount to do with things, also. Plated media tended to work better than older "powdered rust" coatings, particularly when the particle size is larger.

                    Comment

                    Working...
                    X