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

Help with Procomm Plus on AT&T 6300

  • Filter
  • Time
  • Show
Clear All
new posts

    Help with Procomm Plus on AT&T 6300

    I would like to ask the forum for some help with setting a modem program called Procomm Plus. This version is 2.01. I installed it from floppy disk to my AT&T 6300. The setup procedure covers many topics such as the terminal, modem protocol, BAUD rate, duplex, and much more. Reason for interest was to connect by modem to a BBS being run by a friend, who suggested that I could best see his BBS by modem.

    When I call up the Procomm program, a terminal is displayed. But a line at the base of the terminal is missing. This line houses the help call out, duplex, baud rate, etc. The terminal selected during the installation was VT100. I have chosen other terminals, which displays a similar result. The monitor I am using is an AT&T 319, which does display color even though it is listed as a monochrome monitor. Procomm installation and setup displays were normal that is within the 80xx25 display space; but this terminal and its lower line are below the 80x25 screen. So, I am at a loss to understand why this line is below the 25th line since the installed and setup pages worked. Is there anyway the line can be adjusted back to stay within the 80x25 display?

    Second problem I am having deals with the dialing directory. Again when the Procomm dialing directory displays 21 entries and the keyboard entries are not displayed nor the similar last line of the terminal written earlier. I can make an entry to the dialing directory with the number of the local BBS. However, when I try to dial out using the dialing directory, Procomm program crashes and I have to reboot.

    I ran checkit against the serial port with an external loopback and got two errors on the test modem control, which failed expecting 10h; it received a 00h and the test modem status which also failed expecting F0h, and it received a 00h as well. Chip being used for serial is 8250. I tried a Hayes modem that I have and get the same result. Would these errors be the cause for Procomm to lockup when used with the dialing directory?

    A long winded explanation of the problems with the 6300 display is at
    It also suggests turning the keyboard speedup off. Check the ROM BIOS version too.

    The bulk of the Procomm Plus files can be seen at including what should be a patch for the 6300 problem. I downloaded the 2 KB file and it does look like an EXE but I didn't test it since I don't have a 6300 to verify operation.