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

Kaypro 10 & CoPower 88

  • Filter
  • Time
  • Show
Clear All
new posts

    Originally posted by shirsch View Post
    I have one of the newer 'Universal' CP88 interface boards that uses a PAL for decoding. Fortunately the security link was intact and I was able to read out the programming. After tracing the PCB I have produced an annotated source for the PAL. One important difference between this and the older interface: The original board fully decodes address bits A1-A7 (A0 selects between the two adjacent ports). The high nibble can be chosen by shorting a combination of four pins, while the low nibble is always 'E'. The newer board treats A1 as "don't care" so with the SWPKAY4E PAL it responds to 7C or 7E for port 0 (7D or 7F for port 1). It's not clear whether the software is taking advantage of this, but if so it explains a lot of the issues I'm having. Here's the PLD source in PALASM4 format.

    Great work. I'm still confused why Larry's MSDOS.COM addresses port 1A/1B. There is probably an older version of the hardware for KayPro that selects at these ports. So, what I have is the KayPro hardware which addresses at 7E/7F. You have the SWP PAL Version which selects at the same 7E/7F ports. As in my previous e-mail, what ports do MS.COM from AdamAnt316 use? We need this file.

    Chris V.


      ROM disassembly

      I have the disassembly of the ROM far enough along to be usefull.
      It wasn't what I expected at all. I expected a striped down BIOS.
      What I got is the communication routines for the interface and a loader.
      No interrupt vectors loaded at all!

      Attached Files


        Thanks to the kind help of someone in the Kaypro hobby community we have unearthed the distribution diskettes for all CP/M Kaypros. I have the diskettes imaged, along with photos of the original labels. The person with the software has a pile of documentation to scan.

        I have learned a lot in the past few days and a lot of blank spaces are now filled in. In no particular order:
        • There are two generations of support software. Originally SWP licensed MS-DOS from Microsoft, but later found the licensing fees to be excessive and started requiring the user to have an official DOS 2.11 master diskette. Distributions with a CP/M startup program called MSDOS.COM have the boot loader, DOS.SYS and IO.SYS (with driver for K10 hard disk) embedded in that code and require only COMMAND.COM on the boot volume. The MSDOS.COM program is around 40k in size. When they changed course, the startup file became PCDOS.COM and was around 20k in size. The later code required an OS in the boot tracks of the startup volume and loaded a hard disk driver during bootstrap.
        • Port addresses are different depending on machine type. The original K10 uses 0x1A and 0x1B. The K2 and K4 use 0xFE and 0xFF. K4E and later K10s with the "universal" motherboard use 0x7E and 0x7F. You can see these values near the start of PC/MSDOS.COM right after a JMP or (JR) instruction. The older Z80 daughterboards were hardwired for the lower nibble using bodge wires and had jumpers to set the upper nibble. Later "universal" boards (must have been a popular term) had the addressing baked into a PAL10L8. I have reverse-engineered the fuse map and it's very simple to modify for arbitrary addresses. The original board fully decoded the address, but the PAL version ran out of pins and treats Bit 1 as a don't care. Apparently the aliasing is not an issue.
        • The older MSDOS.COM based environments always map the boot disk to the same letter as the CP/M drive where the DOS volume lives - regardless of whether it's hard or floppy. I believe the newer code properly maps hard drive volumes starting at C:. But, we have not yet found the newer code for anything other than the K4E (universal board).
        When I have the files and docs all pulled together I'll arrange to make them available to the world. In the meantime it would help if folks can keep an eye out for the PCDOS.COM flavor for K2/4/10.


          why are you guys posting to the old dead POS forum still? What are you guys still doing here? were all over on the new forum..


            It was an accident - sorry. Cannot understand why the admins don't either pull this down or - at least - make it read-only.