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

5160 BIOS Source Code

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

    5160 BIOS Source Code

    I recently aquired an EPROM programmer from Chuck(G) (Thanks Chuck!), an el-cheapo Chinese UV EPROM eraser and a hand full of 27C256-20 EPROMS. So, I'm thinking I'd like to tweak the BIOS a little on my 5155. My first goal is to modify the POST to eliminate the test routine that causes the floppy drive head carriage to seek back and forth, this can be pretty noisy on a 5155 and causes unnecessary wear and tear on the stepper motor and carriage rails on both floppy drives. Most non-IBM BIOS's just turn on the motor on drive A and check to see if there is a disk to boot. My second goal is to change the routine that initializes the parallel port(s). I have a parallel port that I modified for bi-directional commuinication which works well with one exception. If the port is left in "recieve" mode when a CNTRL-ALT DEL is performed, the port is not initialized durring the reboot and the only remedy is to cycle the power switch. I've searched HI and low for the source code and have only found it in PDF documents that were scanned from the IBM Tech Ref. Obviously, these can not be compiled, and I haven't found a utillity that can reliably convert a PDF to text with zero errors, and I'm not to thrilled to try to Re-type over 2000 lines of code.

    So, I'm hoping someone could help me find a text file (preferably with comments) that could be compiled with somthing like Microsoft Macro Assembler 3.01. I would prefer the 05/09/86 version of the IBM XT BIOS but the earlier versions would be OK if that's all that's available.

    Thanks in advance

    Greg
    Last edited by ibmapc; February 29, 2012, 10:15 PM.

    #2
    http://www.iee.et.tu-dresden.de/~kc-...01/ROMBIOS.ALL

    Comment


      #3
      Wow,
      That was quick thanks PLASMA! I'll give that one a try.
      Would you be able to direct me to newer releases?

      Edit:
      It appears that the listing isn't quite complete. The file ROMEQU.ASM is needed. Note the "include romequ.asm" statement near the top of the listing. Now I think I can type it in from the IBM Tech Ref. It is about 200+ lines of code. A whole lot less than 2000!

      Also, still looking for later versions.
      Last edited by ibmapc; February 29, 2012, 11:20 PM.

      Comment


        #4
        I don't know of any other plain-text versions of the IBM XT BIOS, sorry. If you don't mind a non-IBM BIOS, I have a documented and modified PC/XT BIOS on my site here:

        http://www.phatcode.net/downloads.php?id=101

        It includes everything you need to build it.

        Comment


          #5
          Originally posted by Plasma View Post
          I don't know of any other plain-text versions of the IBM XT BIOS, sorry. If you don't mind a non-IBM BIOS, I have a documented and modified PC/XT BIOS on my site here:

          http://www.phatcode.net/downloads.php?id=101

          It includes everything you need to build it.
          I've tried that one. Either I'm not building it right, or it's a little buggy. Certain drivers won't load correctly when running with that bios. Namely microsoft's networking client IFSHLP.SYS and sound blaster driver that I can't remember the name of. Complains that IRQ vector is not available. If these problems can be fixed, it would be a great bios for my 5155. But I'm less than a beginner with Assembly programming, so I won't be able to get these buggs worked out for some years to come. That's why I would rather work with IBM source.

          Comment


            #6
            Originally posted by ibmapc View Post
            Edit:
            It appears that the listing isn't quite complete. The file ROMEQU.ASM is needed. Note the "include romequ.asm" statement near the top of the listing. Now I think I can type it in from the IBM Tech Ref. It is about 200+ lines of code. A whole lot less than 2000!
            The entire listing, including what would be ROMEQU.ASM, can be found in the IBM XT technical reference manual. The ROMEQU.ASM-part is only about 2 pages long, and can be typed into a file easily.
            Current systems owned by me:
            Vintage:IBM PC/XT submodel 087 ( 1983 ), [Kon]tiki-100 rev. C (1983), Compaq Portable I ( 1984 ), IBM PC/XT submodel 078 ( 1985 ), IBM PC/XT286 ( ~1986 ), 3x Nintendo Entertainement Systems ( 1987 ).
            Obsolete:Commodore A500 ( ~1990 ), IBM PS/2 model 70/386 type 8570-161 ( 1991 ), Atari Lynx II ( ~1992 ), Generic Intel 486SX PC ( ~1993 ), AT/T Globalyst Pentium w/FDIV bug MB ( 1994 ), Compaq 486DX4 laptop ( ~1995 ).

            Comment


              #7
              Originally posted by ibmapc View Post
              I've tried that one. Either I'm not building it right, or it's a little buggy. Certain drivers won't load correctly when running with that bios. Namely microsoft's networking client IFSHLP.SYS and sound blaster driver that I can't remember the name of. Complains that IRQ vector is not available. If these problems can be fixed, it would be a great bios for my 5155. But I'm less than a beginner with Assembly programming, so I won't be able to get these buggs worked out for some years to come. That's why I would rather work with IBM source.
              If you can give me more details on your setup (expansion cards, IRQs used, DOS version, contents of CONFIG.SYS/AUTOEXEC.BAT, etc.) I will see if I can replicate your problems and find a fix.

              Comment


                #8
                Originally posted by Plasma View Post
                If you can give me more details on your setup (expansion cards, IRQs used, DOS version, contents of CONFIG.SYS/AUTOEXEC.BAT, etc.) I will see if I can replicate your problems and find a fix.
                I'll do that. I really like your BIOS and would be thrilled to get it working completely on my machine, although it might take me a while to compile all the info for you. I might try taking it down to a minimal setup first. Right now there is quite a bit goin on in that old 5155, in the mod department. 640k (actually 1 Meg) on the motherboard, a custom programmed GAL in U44(memory decoder) that that lets me use ram in the D000h-EFFFh range as UMB, Ega wonder version 1, Sound blaster16, Intel Ether-express network card, AST Hotshot 286 accelerater with a 80286 at 10mhz and a 80287, NEC V20, 8087, parallel/serial card, Original floppy controller, Silicon Valley Computer ADP50L IDE CONTROLLER WITH CF TO IDE ADAPTER AND CF Card operating as drive C. As you might guess, this leaves me with no IRQ's left. In fact, the Sound Blaster is useing IRQ 2 and the EGA Wonder is not using an IRQ. This setup works with the IBM 5-86 BIOS and PC DOS 7. But with Super PC/Turbo XT BIOS, Microsoft Network Client for DOS Hangs when loading IFSHLP.SYS in config.sys and Sound Blaster SBFMDRV.COM complains about no interrupt vector available when loading in autoexec.bat and refuses to continue loading. I'll try to get my config.sys and autoexec.bat files posted as soon as possible. Maybe I'm Trying to get to much out of this old machine, but that's the main thing that keeps me interested, trying to push the envelope on performance without replaceing the motherboard or modifying the outward appearance.

                Comment


                  #9
                  Have you tried using the 5160 BIOS as-is? Does it work? Then the printer port issue should be pretty simple to solve.
                  Reach me: vcfblackhole _at_ protonmail dot com.

                  Comment


                    #10
                    Originally posted by Chuck(G) View Post
                    Have you tried using the 5160 BIOS as-is? Does it work? Then the printer port issue should be pretty simple to solve.
                    Yes, I've been using the 05-09-86 version of IBM 5160 BIOS and it works great except for the modified parallel port issue. Also, as I mentioned, I'd like to elliminate the head carriage seeking of the floppy drives durring POST.

                    Comment


                      #11
                      Originally posted by ibmapc View Post
                      I'll do that. I really like your BIOS and would be thrilled to get it working completely on my machine, although it might take me a while to compile all the info for you. I might try taking it down to a minimal setup first. Right now there is quite a bit goin on in that old 5155, in the mod department. 640k (actually 1 Meg) on the motherboard, a custom programmed GAL in U44(memory decoder) that that lets me use ram in the D000h-EFFFh range as UMB, Ega wonder version 1, Sound blaster16, Intel Ether-express network card, AST Hotshot 286 accelerater with a 80286 at 10mhz and a 80287, NEC V20, 8087, parallel/serial card, Original floppy controller, Silicon Valley Computer ADP50L IDE CONTROLLER WITH CF TO IDE ADAPTER AND CF Card operating as drive C. As you might guess, this leaves me with no IRQ's left. In fact, the Sound Blaster is useing IRQ 2 and the EGA Wonder is not using an IRQ. This setup works with the IBM 5-86 BIOS and PC DOS 7. But with Super PC/Turbo XT BIOS, Microsoft Network Client for DOS Hangs when loading IFSHLP.SYS in config.sys and Sound Blaster SBFMDRV.COM complains about no interrupt vector available when loading in autoexec.bat and refuses to continue loading. I'll try to get my config.sys and autoexec.bat files posted as soon as possible. Maybe I'm Trying to get to much out of this old machine, but that's the main thing that keeps me interested, trying to push the envelope on performance without replaceing the motherboard or modifying the outward appearance.
                      I'm fairly certain I found the problem...I'm guessing you built the BIOS with the fast memory check enabled. When this happens the IVT is not "zeroed" out and so SBFMDRV and IFSHLP think there are no free interrupt vectors. (They are looking for vectors set to 0.) I have a turbo system so I don't normally use the fast memory check option and never noticed this. So thanks for bringing it to my attention

                      I have a new version up now if you want to try it out.

                      Comment


                        #12
                        Originally posted by Plasma View Post
                        I'm fairly certain I found the problem...I'm guessing you built the BIOS with the fast memory check enabled. When this happens the IVT is not "zeroed" out and so SBFMDRV and IFSHLP think there are no free interrupt vectors. (They are looking for vectors set to 0.) I have a turbo system so I don't normally use the fast memory check option and never noticed this. So thanks for bringing it to my attention

                        I have a new version up now if you want to try it out.
                        Great, I'll try it out in the next day or two. Your assumption that I had used the "Fast Memory Check Option" was correct. So, should I abandon the fast memory check, or should I try the new version with the "Fast Memory Check Option" enabled? Also, can I put ROM Basic on one 32k chip in U19? If so, does the bios need to be changed to work with Basic on one chip? I have been putting the bios on a 32k chip(27c256) in U18 (using the \xtbios21\EPROMS\27256\PCXTBIOS.ROM). I used \xtbios21\IMAGES\BASICC11.BIN for the 32k chip in U19. But if I press the space bar when prompted durring boot, the system freezes. Not sure if this is because it expects BASIC to be on 4 8k chips or is this another symptom of the interrupt vector problem?

                        Comment


                          #13
                          Either way should work. But I would recommend using the new version with fast memory check enabled since it will boot faster. I just updated the make batch to generate special 32K ROMs for the 5155/5160. Because U19 is mapped to F000h and U18 is mapped to F800h, BASIC is split across U18 and U19 because it needs to start at F600h. The new batch file will generate U18.ROM and U19.ROM for you, in the EPROMS\IBMXT folder.

                          Comment


                            #14
                            Does the 4 here need to be changed to 2, since basic will now be on two roms instead of 4? Sorry, I couldn't get the tabs to work in my reply window. But hopefully you can understand what I'm trying to refer to.


                            @@high_vectors:
                            movsw ; Set interrupt vector offset
                            mov ax, cs
                            stosw ; Set interrupt vector segment (BIOS segment)
                            loop @@high_vectors
                            mov ax, 0F600h ; ax --> ROM BASIC segment
                            mov ds, ax ; ds --> " " "
                            xor bx, bx ; bx = ROM BASIC offset
                            mov ah, 4 ; Four BASIC ROMs to check

                            Comment


                              #15
                              Nope. The BIOS only cares about the location of BASIC in memory, not how many actual chips it is on.

                              Comment

                              Working...
                              X