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

SOL-20 parallel port (Register)

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

    SOL-20 parallel port (Register)

    I have been playing around with the parallel port in the SOL. It has separate data in and data out connections. There are two variations depending on the revision of the SOL, for some odd reason on one version they reversed the data input connections, D0 to D7 being on pin 6(D0) to pin 13, and on the other version D0 is on pin 13 and the array is reversed. The schematic in the manual is not correct for my SOL's version and only matches one revision.

    I had used the output data connections before in a program I wrote to put out bytes corresponding to a low frequency sine wave, the output port works well. Since when data is written to the output port, it stays there until updated or the output disabled (there is an input for that) I linked the data outputs to the inputs on a small connector. That way I could test the port. It is like having an additional register, you can write a byte and it is there anytime later !

    In any case what I wanted to do was set up some input sense switches on the port. The SOL does have sense switches but they are awkward to get at. So I made a plug in connector. The input data lines don't actually have any pull up resistors, and there is no 5V available on the 25 pin connector. But in the open condition because they are TTL inputs they assume a high logic state, albeit not very noise immune.

    I once asked about the utility of sense switches. I can see the value of them being able to change data while a program is running. For example, in PT's VDM-1 manual, there is a training exercise to manipulate the switches to see the effects of altering the card's registers on the display. I want to learn that to help me better understand how to scroll displays etc.
    Attached Files

    #2
    I just found out something interesting that could also help repairing a SOL-20.

    PT's VDM-1 card will run in the SOL, along with the other effective duplicate circuitry on the SOL mobo.

    The VDM-1's status port can be manipulated with a small program that reads the parallel port in a loop, then using my switches on the parallel port, the upper and lower nibbles of the byte loaded to the status port of the VDM-1 can be manipulated. The lower nibble selecting the beginning displayed line and the upper nibble the first displayed position. When bit 2 is high (bit 1 = D0, bit 8 = D7), the video output of the VDM-1 card exactly matches the SOL-20's video out. The only difference is that the SOL is not controlling the status port on the VDM-1 so the scroll is non operational.

    However, this made me realize that a VDM-1 card is a very useful "diagnostic tool" to have for a SOL-20, in the event that there was a failure in the video generation/character circuitry on the SOL's mobo, the VDM-1 can be used as a tool to see if the problem is in that sector of circuitry, or elsewhere and if it is in that sector of the SOL mobo, the VDM-1 provides a working hardware reference for scope comparisons.

    Comment


      #3
      Actually it is better when running the VDM-1 in the SOL to deactivate its data output port, since it is normally set up at the same address as the video generator in the SOL, otherwise the 8T97 IC's in the VDM-1 can fight the 74LS367's on the SOL Mobo driving the data lines. It is easily done by insulating the connection to PDBIN on the edge connector with some thin polyamide tape and grounding the IC input that PDBIN was feeding with a 100R resistor. This way no tracks need to be cut. Also on my VDM-1 there are no IC sockets, except the character gen IC.

      Comment

      Working...
      X