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

XT Clone trouble - no boot, no post

  • Filter
  • Time
  • Show
Clear All
new posts

    XT Clone trouble - no boot, no post

    Dear Experts

    first a thanks to you all here as i could find a lot of information and already have at least a picture on the screen. But now I'm somehow stuck. As mentioned it's a clone and i did check already Power Supply (also swapped with known good one) desoldered the leaking battery (traces are still good) removed all cards - nothing. Thougth on the Bios Eprom failed and luckily found some images that should match (COPAM TD3.86 from Thomas Lao)
    I read about the Supersoft Rom to diagnose - so i programmed and installed. First Success i have something on screen telling me that the 8253 Timer Channel 1 failed and Memory. I setup an Arduino to test the DRAM's ( so far all good or not that faulty as the Diag Rom tells me. Tried also to just populate Bank1 with good tested M5M4256 with no success. Not sure if i understood that correct but the Timer also is related to the Memory ? if so, it would explain that many errors.
    Searching for the 8253 on the Board ... nothing but there's an MM57167AN.

    Now to my question before i start to solder this one out. Could this be the one causing the Timer and Memory Failure ?

    BR and thanks for any hint to bring this back to life
    You do not have permission to view this gallery.
    This gallery has 4 photos.

    No, that is the realtime clock. It has nothing at all to do with the 8253 programmable interval timer.

    In this case, this motherboard does not have a 8253 chip. Instead all of that is implemented in that big VLSI chip. It may even be that a failure on that channel 1 test is normal for this chip - but there is no way to be certain unless it was compared to a known good clone of the same model.

    Now, the ram test should darn well pass if the chips are good. So there is something wrong there. If your original ROM was damaged by the leaky battery, then I would still strongly suspect a broken or shorted connection in that general area. Although from that picture, it looks in very good condition.


      Thanks for the information. Just looked at the Datasheet of the FE2010A and read this : Channel 1 is directly connected to the DMA channel 0 request line and provides timing for the Dynamic RAM refresh. Seems pretty what I expirience from the test. So i will try to get hands on a known working one.


        Originally posted by wonder View Post
        I setup an Arduino to test the DRAM's ( so far all good or not that faulty as the Diag Rom tells me. Tried also to just populate Bank1 with good tested M5M4256 with no success.
        I am certainly not an expert but did you test for proper voltage on every dram socket? I had an issue once where one dram socket wasn't getting voltage and it took forever to figure out - all I had to do was reflow the socket. Sorry I can't be more helpful - I am certainly not an expert like others here.


          Thanks chjmartin2, i will also check on this. In the meantime i could test a DRAM's and one was marked as bad. Hope that i can test them in deep when i get hands on a FE2010A - not that easy to find here in Switzerland. Looking currently in the US


            I am working on a couple clones with the fe2010a I got one of the boards working 100% and it fails the timer 1 test so I believe that is normal for the fe2010a, so now I am trying to get the second board going , unfortunately all the dram is soldered. It will freeze anywhere from the dma test to the end.
            Last edited by Klyball; October 10, 2021, 07:49 PM.