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

Apple iie Platinum Garbled Screen Part 2

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

    #16
    I made sure it was dry...

    Comment


      #17
      Are Platinums rare enough to warrant fixing this one?

      Get some good contact cleaner, and burnish all the IC legs and socket pins. If that doesn't fix it, start replacing sockets. Surely this will fix it.
      Be polite and I may let you live.

      https://www.youtube.com/playlist?lis...5NBVfKX5471R9U

      Comment


        #18
        cleaning the pins helped quite a bit. I even got it to beep! With the keyboard disconnected, it will now display a checkerboard pattern and beep seven times every 15 seconds or so.

        https://photos.google.com/photo/AF1Q...k6wKbOekQB-sbs

        Comment


          #19
          Your link leads to a sign-in page.

          I expect that all you have to do to get it fully functional is clean the pins and sockets even better.

          If you have a multimeter, you can check the resistance between chip pins and the solder pads on the bottom of the board to see where you have bad connections.

          By the way, it sounds as if it's doing the self-test, so it may already be fully functional minus the Apple keys. If you have the keyboard plugged in, verify that those keys are working. (You may have corrosion on the keyboard connection as well as inside the keyboard).
          Be polite and I may let you live.

          https://www.youtube.com/playlist?lis...5NBVfKX5471R9U

          Comment


            #20
            After seeing the photo's I'd be replacing the sockets for sure, even if its currently working when you plug the keyboard back in.

            Those sockets will not be reliable, you are also going to have huge issues with plugin cards intermittently not working due to the corrosion on the slot connectors.

            Comment


              #21
              With the keyboard plugged in, it just displays the horizontal bars so the keys are unresponsive. I'll replace the sockets and get back to you when complete.

              Comment


                #22
                You really do have to address that keyboard, too, sooner or later. I'd do that before replacing sockets, at this point.

                There should be a simple way to simulate the Apple keys, too, (in addition to using joysticks). They are discreet inputs that need to be pulled up or down, that's the part I don't remember. I recommend doing that, so you can see if you can at least get a BASIC prompt.
                Be polite and I may let you live.

                https://www.youtube.com/playlist?lis...5NBVfKX5471R9U

                Comment


                  #23
                  I finally finished soldering all the sockets today, tested it and it works! The only problem is half of the keys don't work probably from corrosion. But besides that, it boots into the BASIC prompt with a cursor and lets me type.

                  Comment


                    #24
                    Very nice!
                    Be polite and I may let you live.

                    https://www.youtube.com/playlist?lis...5NBVfKX5471R9U

                    Comment


                      #25
                      Originally posted by masterpigeon View Post
                      I finally finished soldering all the sockets today, tested it and it works! The only problem is half of the keys don't work probably from corrosion. But besides that, it boots into the BASIC prompt with a cursor and lets me type.
                      Sounds good, now that the mainboard is sorted it will be much easier to solve the keyboard issues, which is why I suggested replacing the sockets first. Your problem could be just dirty contacts in the individual keys or open circuits in the scan rows and columns. That should be pretty simple to deduce from the schematic. To do it methodically, for every key that works locate its position in the scan array and mark its row and column as working. Before too long is will become apparent if any rows or columns in the scan array are faulty. Any key that doesnt work that is on a good row and column then the key itself is the problem.

                      Comment

                      Working...
                      X