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

Vtech Laser 386SX/2E

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

    Vtech Laser 386SX/2E

    This is the first computer I purchased from Micro Center in 1992. I also bought a Laser 486DX2 purchased from Micro Center later. After upgrading to faster computers I packed both up in plastic wrap and placed in storage for a verrry long time. I recently retrieved them both from my storage locker. The 486 worked great but the 386 posted a beep code indicating keyboard controller failure. I pulled everything out of the computer and found the motherboard is clean with no corroded traces. Both units have new BIOS batteries. I have included photos of this computer and have no idea where I could find a new keyboard controller. Need suggestions on a fix please or a replacement availability. Thanks, Larry
    You do not have permission to view this gallery.
    This gallery has 3 photos.

    #2
    Originally posted by lschect View Post
    The 486 worked great but the 386 posted a beep code indicating keyboard controller failure.
    Regarding POST codes. People are often misled, because they go to the Internet and see something like, "List of AMI POST codes", and not realise that AMI/Phoenix/IBM, and the like, changed their POST codes periodically. Unless you have a list that you know for for fact matches the particular BIOS, then you could be being misled.

    Originally posted by lschect View Post
    I pulled everything out of the computer and found the motherboard is clean with no corroded traces.
    Something worthwhile to do is to re-seat all socketed chips.
    Also, a thorough visual inspection can sometimes reveal a problem.

    Originally posted by lschect View Post
    I have included photos of this computer and have no idea where I could find a new keyboard controller. Need suggestions on a fix please or a replacement availability.
    Assuming a faulty keyboard controller:

    There is a good chance that your controller is an Intel 8042 (or 8742) chip that has been suitably programmed for what the motherboard needs the controller to do.

    IBM's keyboard controller (IBM part number 1503033) may work. A common way for people to obtain one, is by acquiring a blank Intel 8742, then using an EPROM programmer to program the 8742 with the code used in IBM's controller (code at [here]). Or see if a person/company at [here] can provide that service.

    In the thread at [here], a member successfully used an P8242 chip.

    Comment


      #3
      I did remove the 2 BIOS chips and the keyboard controller chip. I cleaned the contacts and reseated them. The post code is listed in the manual for the Laser 386. Yes, I do have all the original paperwork and accessories for this computer since it is a one owner. It did work before it went into storage. I removed the external batteries before storage So I don't know what happened, just age of the chip I guess. So I will try to get a chip and get it programmed for the computer. I will check the solder around the motherboard before I reinstall it again. This computer is seemingly kinda rare, I have only seen one more like it for sale. Thank you for the reply.

      Comment


        #4
        How are you coming along with the keyboard controller? I have a Laser 386SX model (Also from Microcenter) that may have a compatible controller. If time permits, I could tear it down and check the controller type. Unsure on the specifics or ability to dump and reprogram these controllers however.

        Comment


          #5
          Originally posted by lschect View Post
          I did remove the 2 BIOS chips and the keyboard controller chip. I cleaned the contacts and reseated them. The post code is listed in the manual for the Laser 386. Yes, I do have all the original paperwork and accessories for this computer since it is a one owner. It did work before it went into storage. I removed the external batteries before storage So I don't know what happened, just age of the chip I guess. So I will try to get a chip and get it programmed for the computer. I will check the solder around the motherboard before I reinstall it again. This computer is seemingly kinda rare, I have only seen one more like it for sale. Thank you for the reply.
          I would look at things that tend to go bad with time: Batteries and capacitors are two of the most likely culprits. You've already eliminated the former so I would look at the latter, especially electrolytic capacitors. Don't forget those in the power supply. Chips can fail but I would focus on the capacitors first and, once eliminated, investigate the keyboard controller. If the supporting circuitry is not functioning properly you could be misdiagnosing the problem.

          Comment

          Working...
          X