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

Just purchased my first IBM 5160

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

    #76
    Originally posted by John's first 5160 View Post
    Then it boots from HDD .
    How do I access the XTIDE ?
    When you see the XUB's hotkeybar, press the 'D' key. That will make the XT-IDE's drive become the first hard drive, and the MFM drive become the second hard drive. The 5160 will then boot from XT-IDE's drive (the first hard drive), with the XT-IDE's drive presented as logical drive C:, and the MFM drive presented as logical drive D:

    Comment


      #77
      Originally posted by modem7 View Post
      When you see the XUB's hotkeybar, press the 'D' key. That will make the XT-IDE's drive become the first hard drive, and the MFM drive become the second hard drive. The 5160 will then boot from XT-IDE's drive (the first hard drive), with the XT-IDE's drive presented as logical drive C:, and the MFM drive presented as logical drive D:
      Thank you.

      Will try that later today.

      Will I need a special program to copy contents of original HDD to CF?

      Thanks again
      Last edited by John's first 5160; November 14, 2021, 10:20 AM.

      Comment


        #78
        Originally posted by John's first 5160 View Post
        Will I need a special program to copy contents of original HDD to CF?
        Assumption: The purpose is to make a backup of the MFM drive.

        In the DOS directory is a program named XCOPY.
        So, one way would be to:

        1. Boot from the MFM drive. ( The MFM drive is C: and the CF is D: )
        2. Enter the command XCOPY C:\ D:\5160 /S /E
        3. When XCOPY asks about file or directory, press the 'D' key.
        4. {copying starts}

        That will result in a directory named '5160' being created on the CF, and the directory and file contents (except for hidden files) of the MFM drive being copied into the '5160' directory.

        Comment


          #79
          xcopy is your friend. Learn all of its magical powers.

          Comment


            #80
            Originally posted by John's first 5160 View Post
            The "1501512" on U18 confirms a revision of 11/08/82. I guess that the contents of your 1501512 differs slightly to my 1501512. I will do further research on that.
            In the following, DEBUG is used to copy the contents of U18 into a file named MYF800.BIN
            Please perform that, then supply the MYF800.BIN file to me.
            The bits in red are what you enter.

            C:\DOS>DEBUG
            -N MYF800.BIN
            -R BX
            BX 0000
            :0000
            -R CX
            CX 0000
            :8000
            -M F800:0 L8000 0100
            -W 0100
            Writing 8000 bytes
            -Q

            Comment


              #81
              Originally posted by modem7 View Post
              In the following, DEBUG is used to copy the contents of U18 into a file named MYF800.BIN
              Please perform that, then supply the MYF800.BIN file to me.
              The bits in red are what you enter.

              C:\DOS>DEBUG
              -N MYF800.BIN
              -R BX
              BX 0000
              :0000
              -R CX
              CX 0000
              :8000
              -M F800:0 L8000 0100
              -W 0100
              Writing 8000 bytes
              -Q
              Ok, will do. Im off this friday , will do it them.

              Thank you.

              Comment


                #82
                Originally posted by modem7 View Post
                Assumption: The purpose is to make a backup of the MFM drive.

                In the DOS directory is a program named XCOPY.
                So, one way would be to:

                1. Boot from the MFM drive. ( The MFM drive is C: and the CF is D: )
                2. Enter the command XCOPY C:\ D:\5160 /S /E
                3. When XCOPY asks about file or directory, press the 'D' key.
                4. {copying starts}

                That will result in a directory named '5160' being created on the CF, and the directory and file contents (except for hidden files) of the MFM drive being copied into the '5160' directory.
                So I copied the MFM drive. Total was 8.48 megs, took almost 40 minutes, lol , crazy!

                Thanks!

                Comment


                  #83
                  Originally posted by modem7 View Post
                  In the following, DEBUG is used to copy the contents of U18 into a file named MYF800.BIN
                  Please perform that, then supply the MYF800.BIN file to me.
                  The bits in red are what you enter.

                  C:\DOS>DEBUG
                  -N MYF800.BIN
                  -R BX
                  BX 0000
                  :0000
                  -R CX
                  CX 0000
                  :8000
                  -M F800:0 L8000 0100
                  -W 0100
                  Writing 8000 bytes
                  -Q
                  I did the ROM capture, but when I try to attach it here a message says I am not allowed to upload .BIN files.

                  Let me know.

                  Comment


                    #84
                    Also, the DeOxit seems to have worked. I can start the PC without fail so far with the quadboard in place.

                    Comment


                      #85
                      Originally posted by John's first 5160 View Post
                      I did the ROM capture, but when I try to attach it here a message says I am not allowed to upload .BIN files.
                      Does Zipping it work ?

                      Comment


                        #86
                        Originally posted by modem7 View Post
                        Does Zipping it work ?
                        Will try that. Thank you.

                        Comment


                          #87
                          Originally posted by modem7 View Post
                          Does Zipping it work ?
                          Here it is.

                          let me know what you find.
                          Attached Files

                          Comment


                            #88
                            Originally posted by John's first 5160 View Post
                            Here it is.
                            let me know what you find.
                            Thanks for that - it's informative. It turns out that there are two versions of the 1501512 ROM.

                            In mine, the copyright string is, "1501512 COPR. IBM 1981". In yours, the copyright string is, "1501512 COPR. IBM 1982".

                            Accordingly, the checksum byte (the final byte in the 1501512 ROM) is also different in order to cater for the '81' versus '82' change.

                            (IBM did the same thing for the final BIOS revision in the IBM 5150 - two versions of the 1501476 ROM - one 1981, one 1982.)

                            I will modify RAYXTMFM so that it recognises the 1982 dated 1501512 ROM.

                            Comment


                              #89
                              Wow, Thats cool. Nice find!

                              Comment


                                #90
                                Originally posted by John's first 5160 View Post
                                Wow, Thats cool. Nice find!
                                RAYXTMFM is now at version 1.6, and will now identify the 1982 dated 1501512 ROM.

                                Comment

                                Working...
                                X