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

Compuadd 386sx with a corruption on screen and ctrl-alt-del doesn't work

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

    Compuadd 386sx with a corruption on screen and ctrl-alt-del doesn't work

    So this is something of a strange fault.

    The system posts fine, I can enter the bios etc. It will boot to floppy without issue and everything seems fine except for 2 things.

    Firstly once its booted a soft reset by use of ctrl-alt-del crashes the system but only once its booted to DOS, at the bios it works fine. When it does hang the screen stays on whatever it was, occasionally the PC speaker will give a single long tone. The only way to resolve this is a hard reset, power on/off.

    The other issue then is that text on the command prompt will corrupt the entire screen once it gets to the last line. By that I mean you can fill the screen with text no problem but once you enter anything on the last line and hit enter everything above corrupts, it almost as if it happens only once the screen is asked to scroll.

    For testing so far:

    - I've changed the system memory, its fine.
    - I've tried disabling the onboard graphics and using 2 different ISA cards but no difference (I initially though the onboard vram might be bad)
    - I've done some probing around the board and found a floating pin on 1 of the F04 logic chips, replaced that, the signal returned but problem persists.
    - I've tried reseating the BIOS (its the only socketed chip)
    - also tried another PSU.

    Now the fact that one of the logic chips on the board has a failure makes me thing there might be more, but then again if the logic was bad would the system boot and run?

    I'd be open to any suggestions.

    #2
    I've made some progress.

    Ignoring the reset issue and on the advice of some folk on another vintage computer group I learnt that the CPU addresses the scrolling of the screen. So went looking across the bus and sure enough I found a bad 245, it had a good strong signal in and next to nothing out. Swapped that and sure enough the problem seemed fixed, well fixed for a good 10 minutes anyway but when it surfaced again the corruption isn't anywhere near as bad. Oddly swapping this also fixed the reset issue.

    After some more poking I've found a duff looking 244 (in the same manor as the245 was). I'm going to swap that out later and hopefully thats the end of the problems!

    Comment


      #3
      It sounds as if the problem appears once the OS is loaded. If it persists after the 244 replacement you may want to consider that the OS installation may have become corrupted and needs to be reinstalled.

      Comment

      Working...
      X