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

5170 occasionally boots with no color?

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

    5170 occasionally boots with no color?

    Have noticed that my 5170 will now occasionally boots up and have no color, just black and shades of gray. Curious if anyone has run into this before? Looking for recommendations on where to start troubleshooting. Usually if I just reboot the machine it comes back with color. Thanks, Chris

    #2
    Does it have a VGA card?

    Old VGA cards assigned some pins on the connector to detect if a mono or color monitor is detected. Those pins were reassigned for different purposes in the 1990’s, if you have a newer monitor connected to a sufficiently ancient VGA card it may once in a while get confused. (Specifically, pin 12 is now used for an I2C communication channel, but back in the day it being grounded meant “mono”.)
    My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

    Comment


      #3
      I am running a 256K Trident video card and using a Zenith Data Systems monitor. I will have to make better notes of the frequency. Seems like it didn't happen at all for the first few months after I got the computer up and running. Seems like the frequency of the events was increasing and that is what caught my attention. Thought it might be an indication of a component heading south.

      Comment


        #4
        Originally posted by Eudimorphodon View Post
        Does it have a VGA card?

        Old VGA cards assigned some pins on the connector to detect if a mono or color monitor is detected. Those pins were reassigned for different purposes in the 1990’s, if you have a newer monitor connected to a sufficiently ancient VGA card it may once in a while get confused. (Specifically, pin 12 is now used for an I2C communication channel, but back in the day it being grounded meant “mono”.)
        Hmm... I guess that’s why my PS/2 machines don’t like my KVM to be in color. So perhaps disconnecting pin 12 should do it? I’ll have to give that a try. Thanks!

        Comment


          #5
          Originally posted by rvdbijl View Post
          Hmm... I guess that’s why my PS/2 machines don’t like my KVM to be in color. So perhaps disconnecting pin 12 should do it? I’ll have to give that a try. Thanks!
          I'm reasonably sure that pin 12 n/c is the valid/correct config for a color monitor attached to a VGA card old enough to use the old ID sense line layout, so pulling pin 12 out of the end of the cable you connect to the PS/2 should be fine. But my memory could be rusty. All my working retro-computers either pre-or-post-date this era of VGA, oddly enough.
          My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

          Comment


            #6
            Originally posted by Eudimorphodon View Post
            I'm reasonably sure that pin 12 n/c is the valid/correct config for a color monitor attached to a VGA card old enough to use the old ID sense line layout, so pulling pin 12 out of the end of the cable you connect to the PS/2 should be fine. But my memory could be rusty. All my working retro-computers either pre-or-post-date this era of VGA, oddly enough.
            Just tried it today with a VGA "extension" cord. I didn't want to yank pins out of my expensive and hard to find KVM cable. No dice though! I was fully expecting this to work, but it doesn't -- during bootup, my Model 80 (with 8514 board) spits out blue text. Once DOS boots, it's white, but the system will not output color from that moment further. I wonder if I need to ground pin 11 perhaps to ensure it's not thinking that there is no monitor connected. Haven't tried my PS/2 model 30 yet, but that one hasn't had any issues with color output, just its default is grayscale with the KVM connected....

            Comment

            Working...
            X