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

setboard can't setup EEPROM on Intel above board

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

    setboard can't setup EEPROM on Intel above board

    Trying to add some memory to my IBM AT with an Itel above board plus. when I run the setboard program it detects the board but when I try to set things up manually I get the "setboard can't setup EEPROM: error and it asks me to call IBM support. I tried setting things up manually as well several times and get the same error. any ideas? is it possible I can replace the EEPROM?

    #2
    You probably have an old Above Board that uses switches for configuration, not eeprom. Check this out: https://stason.org/TULARC/pc/memory-...-BOARD-AT.html or http://www.minuszerodegrees.net/manu...s%20(1986).pdf (left and middle switch blocks, as the right in this PDF is for COM/LPT that you probably don't have).

    Comment


      #3
      I'm pretty sure my card doesn't have any switch boxes, I'll need to recheck to make sure.

      Comment


        #4
        My recollection is that the AboveBoard uses a little 8 pin DIP for EEPROM, just like a lot of older NICs. So the package should stick out like a sore thumb.

        Comment


          #5
          Post a pic, especially the FCC ID, if available.

          Comment


            #6
            Here are some images of the card. I don't think that the empty socket at the top of the board is the missing EEPROM as every image I have seen of this card has that socket empty. Since I'm using the card in a 286 the small socket near the bottom is empty as well.
            You do not have permission to view this gallery.
            This gallery has 2 photos.

            Comment


              #7
              Empty socket is for the second com port. It should work fine. I have one just like it in my 5170.

              Comment


                #8
                Bummer, guess I'm stumped then, or it's just a bad card. could bad memory chips cause that error or is it definitely an issue with the EEPROM?

                Comment


                  #9
                  I'll need to check my aboveboard documentation. I have one of these in the original box somewhere, but to use mine in an AT system, I needed to have the a small socket jumpered. Removed, it works in an XT system. I'll confirm when I get home from work later today.

                  Comment


                    #10
                    I actually had that backwards. It's jumpered in an XT/PC system, but unjumpered in an AT system. That does not help you any.
                    DSC00134-VS.JPG
                    DSC00135-VS.JPG
                    DSC00136-VS.JPG

                    Comment


                      #11
                      I run one of these on an XT clone. Works fine--no problems. I have the shunt jumper in for 8 bit access; setup using the Intel software was no issue.

                      Perhaps you should try replacing the EEPROM.

                      Comment


                        #12
                        Originally posted by bolex View Post
                        I actually had that backwards. It's jumpered in an XT/PC system, but unjumpered in an AT system. That does not help you any.
                        Sir! If opportunity allows, please kindly scan that manual! Even bloor-ish phone photos are ok if you don't have a proper flatbed scanner. I have this board and would really enjoy reading the manual.

                        Comment


                          #13
                          Originally posted by dhau View Post

                          Sir! If opportunity allows, please kindly scan that manual! Even bloor-ish phone photos are ok if you don't have a proper flatbed scanner. I have this board and would really enjoy reading the manual.
                          I will! I actually purchased an overhead scanner just to scan manuals. It should only take a few minutes. I'll work on that this week.

                          Comment


                            #14
                            Originally posted by Chuck(G) View Post
                            I run one of these on an XT clone. Works fine--no problems. I have the shunt jumper in for 8 bit access; setup using the Intel software was no issue.

                            Perhaps you should try replacing the EEPROM.
                            Looks like every chip is soldered on. which one is the EEPROM? do you have any advice on where I would even find a replacement EEPROM?

                            Comment


                              #15
                              How many 8 pin DIPs do you see on the PCB? (Hint: it's between 0 and 2). That's the EEPROM. Just to be sure, read the numbers off the chip and let's look them up.

                              Comment

                              Working...
                              X