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

Resurrecting a IBM 5150: 601 code at POST. Need some help.

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

  • madmaxamdam
    replied
    Originally posted by generic486 View Post
    With your working drive you might want to run Imagedisk to check drive speeds and alignment.
    http://www.classiccmp.org/dunfield/img54306/imd118.zip
    That's definitely the tool I'm in need of! The only problem now would be to transfer it on a 5.25" floppy disk from my super-modern PC that "only" has DVD/RW drive, USB Ports, and ethernet connector. I've got an old PC with CD reader and 3.5" floppy drive. But I do not own a PC with 3.5" and 2.25" drives for the last transfer.

    First thing I'll try to do is to dig into the huge 5.25" disk pack I inherited with the PC itself. If I'm very lucky I may find that tool (or an equivalent one) into one of those...

    Leave a comment:


  • generic486
    replied
    With your working drive you might want to run Imagedisk to check drive speeds and alignment.
    http://www.classiccmp.org/dunfield/img54306/imd118.zip

    Leave a comment:


  • madmaxamdam
    replied
    Wait a minute!

    A speed difference would actually affect the outer tracks MORE than the inner ones, wouldn't it?

    I mean, a given angular speed diff (rad/s) will be trasformed in a geater linear speed diff (m/s) if the radius is greater: therefore the outer tracks (i.e. greater radius) should be more difficult to read - which is countrary to what I have experienced.

    *scratches head*

    Leave a comment:


  • madmaxamdam
    replied
    I'd bet on #2 (drive speed), for the following reasons:

    - the behaviour of the FDD is absolutely deterministic: for any given diskette it always perfectly reads outer tracks and gives the data error when accessing inner tracks. I wouldn't expect this pattern for dirty heads (which I cleaned thoroughly beforehand) or wrong azimuth;

    - when the disk spins, this drive is a bit more noisy than the other one (on the YouTube video, if you listen carefully you will hear it) - this noise may be due to some kind of friction inside the unit?...

    Would it make sense trying to lubricate the wheel axis from the bottom of the unit?

    Leave a comment:


  • Chuck(G)
    replied
    "Data error" has a very specific meaning in floppy diagnostics. The sector containing the data has been located by the controller, but the computed CRC after reading the data field doesn't match what's recorded on the disk. Probable causes (in the order that I'd consider them):

    1. Dirty heads
    2. Drive speed (less critical on outside tracks, more critical on inside ones)
    3. Alignment/azimuth

    The good news is that the drive basically works.

    Leave a comment:


  • madmaxamdam
    replied
    Originally posted by Chuck(G) View Post
    Well, that's not the "original" 5150 floppy controller. The original one has a number of metal-can IBM hybrid circuits on it. The one you have is a later version of the controller.
    Sure! That has already been clarified. This PC has been manufactured in 1984, so it has a newer revision of the controller.
    It's "original" in the sense that it has been assembled by IBM at production time (as opposed to being assembled/replaced by a third party later on).

    Btw, playing with the old lady I found there's still a residual issue.

    One of the FDD (I chose to be A) is totally OK, while the other (B) works fine until the header stands on track 1 (e.g. issuing a DIR command), but it fails if the header has to seek any file. In such a case the FDD header bounces up and down a few times, and after a while an infamous "Data error reading drive B" is issued.

    If you have 1'40" to waste, here's what happens: https://www.youtube.com/watch?v=OBXOZCXOVZ4

    You will first see the elegant drive A: header nicely and flawlessly performing its job, and then the disgraced drive B: header miserably failing.

    Leave a comment:


  • Chuck(G)
    replied
    Well, that's not the "original" 5150 floppy controller. The original one has a number of metal-can IBM hybrid circuits on it. The one you have is a later version of the controller.

    Leave a comment:


  • madmaxamdam
    replied
    A little gift for you guys, for all the help you gave me.

    THE RESURRECTED IBM PC IN ALL ITS GLORY

    5150 Ok.JPG

    (in the backgroud, my multimeter and the bottle of alchool used for cleaning the old lady)

    Cheers,
    Max

    Leave a comment:


  • Stone
    replied
    Yup, that's the one I've got, too.

    Leave a comment:


  • madmaxamdam
    replied
    Closing the jumper "fixes" the controller. Now the PC is fully functional again!
    Thanks for all your help!

    @Chuck:
    The controller I found in the PC actually looks very similar to the one in the XT: chip vendors and part numbers are different, but the PCB layout and components are exactly the same (see pic below - PC controller is on top).
    Please consider my PC is a 1984 version, not an "original" from 1981. May be IBM mounted a newer version of the controller on later PCs?

    FDD_Controllers.jpg

    Leave a comment:


  • Stone
    replied
    Originally posted by Chuck(G) View Post
    But this is a 5150! The original 5150 controller has no jumpers.
    Seems like this one does.

    Leave a comment:


  • madmaxamdam
    replied
    Found!
    The jumper is there.
    It's named P3 and it's near the back end of the board (next to the cable connector).

    Guess what? On the working controller the jumper is shorted, while on the original (faulty) one it's open!

    I'm going to close that jumper and test again the original board.
    Holding my breath until next post...

    Leave a comment:


  • Chuck(G)
    replied
    Originally posted by Stone View Post
    That jumper, P3, enables/disables the controller. Closed = enabled; open = disabled. I just tried it on my XT with that card.
    But this is a 5150! The original 5150 controller has no jumpers.

    Leave a comment:


  • Stone
    replied
    Originally posted by vwestlife View Post
    Something simple to check: the original IBM PC/XT floppy controller has one jumper on it. I forget whether the jumper is supposed to be installed or not (I haven't had one in years), but either way, if you don't have that jumper in the correct position, the controller may not work. Hopefully someone can chime in with the correct answer -- I tried searching, but couldn't come up with anything specific about it.
    That jumper, P3, enables/disables the controller. Closed = enabled; open = disabled. I just tried it on my XT with that card.

    Leave a comment:


  • Stone
    replied
    IF I had to take a wild guess I would say a bad capacitor, not IC.

    http://www.ebay.com/itm/Vintage-IBM-...10947421654%26
    Last edited by Stone; October 26, 2012, 09:59 AM.

    Leave a comment:

Working...
X