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

NEC APC: RDCPM and a CP/M-86 formatted diskette?

  • Filter
  • Time
  • Show
Clear All
new posts

    NEC APC: RDCPM and a CP/M-86 formatted diskette?

    So, I'm trying to load the NEC APC version of MS-DOS KERMIT on a DOS 2.11 floppy for my NEC APC, and I had to get the executable on a 8" diskette via KERMIT86 on the machine's CP/M-86 port. Now I'm trying to use DOS 2.11's RDCPM.COM to grab the MS-DOS KERMIT executable off the CP/M-86-formatted diskette, but even a simple RDCPM DIR B: gets me a "HARD DISK ERROR reading CP/M disk" after a good ten seconds of trying to read the CP/M-86-formatted diskette in Drive B:. Can NEC's OEM RDCPM not read APC CP/M-86 formatted disks properly, for some reason? Am I doing something wrong?

    Unfortunately, NEC seemingly didn't see fit to license GW-BASIC so a remote load via that isn't an option. CP/M-86 does have a BASIC interpreter, but that'd leave me in the same fix.
    General Failure Reading Drive C -
    Abort, Retry, Ignore?

    You won't be able to read the CP/M Floppy with MS-DOS, unless you use 22DISK. Chuck(G) on the VCF still sells and supports
    22DISK. Just Register with him, and then use 22DISK to access the Floppy with 22DISK. 22DISK has a definition for the NECAPC
    BEGIN NECC NEC APC CP/M-86 - DSHD 8" - 256 x 26 ..........

    If your system is a One Floppy ONLY system you likely won't be able to access it this way. You can always connect the 8" floppy
    to a DOS Computer, and then use 22DISK from DOS to access the floppy, or Imagedisk (IMD) to Grab an Image of the Floppy.
    With the Image you can then create a Raw Sector Dump, and access the files with cpmtools (Linux or Windows).

    This definition should work for cpmtools:
    # NECC NEC APC CP/M-86 - DSHD 8" - 256 x 26
    diskdef necc
    seclen 256
    tracks 154
    sectrk 26
    blocksize 2048
    maxdir 256
    skew 3
    boottrk 2
    os 2.2



      Is 22DISK going to be able to run? The APC isn't IBM compatible. Also, it's odd that NEC even bothered including RDCPM and tailoring it with their OAK if it won't work with their tailored CP/M-86 distro...
      General Failure Reading Drive C -
      Abort, Retry, Ignore?


        Does the NEC RDCPM utility actually read diskettes? I think the error "HARD DISK ERROR reading CP/M disk" may indicate it only reads hard disks.
        CP/M-86 Software Repository


          I think the wording is more meant to refer to a "hard error" than anything, the utility itself goes back to 86-DOS in various forms and DOS versions that early didn't have integrated support for fixed disks. The version included with NEC's APC-specific DOS 2.11 distribution has been customized (being 9k vs. some other OEMS's versions of RDCPM) but unfortunately NEC APC DOS documentation isn't on the web at all making it difficult for me to rtfm.
          General Failure Reading Drive C -
          Abort, Retry, Ignore?


            Originally posted by MrArgent View Post
            ... but unfortunately NEC APC DOS documentation isn't on the web at all making it difficult for me to rtfm.
            Did you check here?
            Maintainer of


              Yup. Unfortunately, the DOS documentation they have is all programming-focused - nothing more general purpose that would exposit on command syntax and usage.
              General Failure Reading Drive C -
              Abort, Retry, Ignore?