Announcement

Collapse

Forum 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.


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.


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.



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.


"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.

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 doesn't store ALL of its CP/M in the reserved track

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

    Kaypro doesn't store ALL of its CP/M in the reserved track

    I was analyzing all the downloadable disks on the web that I could find for my Kaypro 4/83 and I found something interesting. First the one says "KAYPRO II 64k CP/M vers 2.2" and the other says "KAYPRO IV 64k CP/M vers 2.2". They are virtually identical other than that difference and about 20 bytes at the end which could be configuration maybe.

    The first track is reserved (10 sectors * 512 = 5120 bytes). Then if on a flat image, another 2048 bytes beginning at 0x1c00 is a continuation of CP/M. It is actually block 1 in the file system and is the 2K following the directory (64 entries * 32 bytes). I then noticed on some disks with files that they begin at "2" and not "1". Would they possibly have patched CP/M not to use block 1 as to keep this area from being overwritten? How does this work with tools like cpmtools? The kpiv diskdef seems unaware of this unless I'm not getting it.

    #2
    Yes, I got a "fix" for this in the latest cpmtools. Basically, Kaypro reserved two full blocks for the directory, but only used the first 64 entries. The diskdef for the latest cpmtools version is:
    Code:
    diskdef
        seclen 512
        tracks 80
        sectrk 10
        blocksize 2048
        maxdir 64
        dirblks 2
        skew 0
        boottrk 1
        os 2.2
    end
    Note the new parameter "dirblks" that tells cpmtools to reserve two blocks even though only 64 entries are used.

    In the CP/M DPB this is accomplished by having DPB.DRM=63 and DPB.ALV0=11000000B

    and, yes, this all came after trashing several formerly-bootable Kaypro disk images by using cpmtools on them.
    - Doug

    Comment


      #3
      Where can I download/find that latest cpmtools?

      Comment


        #4
        I had thought these got merged, but alas no action from Michael Moria, official owner of cpmtools http://www.moria.de/~michael/cpmtools/, or on pull request at https://github.com/lipro-cpm4l/cpmtools. You can take cpmtools-2.21 from github and either add the commit from my pull request or apply this patch (attached).

        This commit/patch also fixes the Kaypro diskdefs, but does not change any other possible formats that might suffer from this (the only ones I know of are Kaypro).

        If you're not fluent in git/github, let me know and I can make a tarball of the source for that commit. I only have Ubuntu 20.04 Linux on x86_64, so if you need binaries for a different platform we'll have to work something out.
        Attached Files
        - Doug

        Comment


          #5
          I could use win32 binaries, but I don't want you to have to go through a lot of work. Will Michael eventually get it integrated?

          Comment


            #6
            I don't have any way to produce Windows binaries. I will push on the https://github.com/lipro-cpm4l/cpmtools (which is not Michael) pull request to get the integrated, but I don't believe that that repo is used to distribute binaries so someone with a Windows C development kit would need to do that (maybe cygwin is all that's needed?)
            - Doug

            Comment


              #7
              No worries - in the meantime I suppose I can just expand maxdir to take up the area, but never copy more than 64 files to it!

              Comment


                #8
                Originally posted by alank2 View Post
                No worries - in the meantime I suppose I can just expand maxdir to take up the area, but never copy more than 64 files to it!
                Yes, in theory. But you have to watch out for files that overflow the first directory entry, as each entry consumed by a file works toward that "64".
                - Doug

                Comment


                  #9
                  Ahh yes, that is right.

                  Comment


                    #10
                    Still thinking about how to "workaround" this issue without having to recompile cpmtools. My other thought was to just create a directory entry that holds that block used. It could even be named CPM22.BIN or something.

                    Comment


                      #11
                      Originally posted by alank2 View Post
                      Still thinking about how to "workaround" this issue without having to recompile cpmtools. My other thought was to just create a directory entry that holds that block used. It could even be named CPM22.BIN or something.
                      Yes, that's what I did for awhile with my simulator disk images before fixing cpmtools. It works best when creating new blank images, for existing images with files it is a bit trickier. But if you are manually "editing" the directory you can just create the entry and list the block(s) in the appropriate part of the entry. Keep in mind that DS disks use 2K block size and thus the reserved block is 01. For the SS disks (1K block size) it is blocks 02 03. Might just be easier to tell cpmtools that you are using 128 directory entries and just be cautious not to overflow 64.
                      - Doug

                      Comment


                        #12
                        I made a quick disk tool to convert disks or extract/import cp/m on them, so maybe I'll just add a "protectfile" option for it that adds a file that protects it. For DSDD it would only have to have one allocation block 01, but for SSDD it sounds like it would need two, for 02 and 03. I think 00/01 are still taken up by the directory. I suppose I could even put the protectfile in user 15 where no one is likely to find it.

                        Comment


                          #13
                          Thanks for this patch. As a Kaypro owner, I had occasionally trashed a Kaypro cpm disk image but never investigated further.

                          Comment


                            #14
                            Doug - I emailed Michael and he said that he got some changes from you. He gave this link:

                            http://www.moria.de/~michael/cpmtool...napshot.tar.gz

                            Comment


                              #15
                              Originally posted by alank2 View Post
                              Doug - I emailed Michael and he said that he got some changes from you. He gave this link:

                              http://www.moria.de/~michael/cpmtool...napshot.tar.gz
                              Yes, looks like all of my current patches are included in the latest snapshot, except an enhancement that we are still discussing (a way to embed the entire (single) deskdef in the -f parameter).
                              - Doug

                              Comment

                              Working...
                              X