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

XTIDE Universal BIOS v2.0.0 beta testing thread

  • Filter
  • Time
  • Show
Clear All
new posts

    aitotat, can I ask about the BIOS initialisation and how things work with other option ROMs? I wondered how the system BIOS determines when to run each installed option ROM, and how control is passed between them, and finally how the (bootstrap?) code is called. Cheers!


      I just ran Debug and the result is:
      -i 307
      -i 30E
      I had another look at my silicon valley ADP 60/70 16-bit Ide/Floppy controller and found i messed up when i built the bios for it, I rebuilt the bios r504 and reflashed the onboard chip, the card now works again in my XT 5160, ie: bios see's the CF card and works fine.

      With bios enabled, CF Adapter / Card plugged directly into the IDE header, CF as Master i ran both idedtct ver:1.00 and ver: 1.0.1 and the result was " Standard IDE Controller found at port 1F0h/3F0h ".

      Tried a different CF adapter connected via an 80 core ide cable, CF as Master / no slave and ran both versions of idedtct and the result was " Standard IDE Controller found at port 1F0h/3F0h ".

      CF as slave / no master ran both versions of idedtct and the result was the same " Standard IDE Controller found at port 1F0h/3F0h ".

      With bios disabled both versions of idedtct reported " Standard IDE Controller found at port 1F0h/3F0h ". for CF as master / no slave and CF as slave / no master.

      Originally posted by aitotat View Post
      That is quite unexpected. I would have thought the same controller card + drive combination would work the same on all systems. I don't know why non modded XTIDE rev 1 is detected as modded rev 1.
      Can you do a quick test with DOS debug (on the IBM 5160)? Since the XTIDE is at port 300, read what is returned from ports 307h and 30Eh like this:
      i 307
      i 30E
      That reads IDE Status Register and Alternative Status Register. They should be the same and usually 50h when things work as they should.

      Auto Configure in the xtidecfg uses excactly the same detection code as idedtct so it has the same problem as well.


        Today I reverted back to " r497 " when auto configure was added, from r497 up to and including r503 when i run xtidecfg and the auto configure option the result is " Found 1 Controllers ".

        With r504, running xtidecfg and auto configure results in " Found 0 Controllers "

        This is on my IBM XT 5160 and XT-IDE rev 1 card with no mods.

        Originally posted by aitotat View Post
        Auto Configure in the xtidecfg uses excactly the same detection code as idedtct so it has the same problem as well.


          Thanks for all the testing. r504 does not change anything in the BIOS. It contains some code cleaning related to xtidecfg Auto Configure (and idedtct uses the same code). I'll try to find what the problem is.


            Beta 3 is now released.
            This is the first official release with full XT-CF v2 support and 8-bit mode for 16-bit controllers. There are also many small improvements and optimizations.


              Just updated to r518 and getting an error when trying to build xtidecfg which results in xtidecfg not getting built, error is:

              IdeAutoDetect.asm:209: error: symbol `CompareIdeStatusRegistersFromALandAH.InvalidStatusRegister' undefined
              IdeAutoDetect.asm:211: error: symbol `CompareIdeStatusRegistersFromALandAH.InvalidStatusRegister' undefined


                Originally posted by Malc View Post
                Just updated to r518 and getting an error...
                Oops! It is now fixed.


                  Has anybody tested the 16bit controller in 8bit mode on a 5150?



                    That's something I've been meaning to try on my 5150, will dig it out when i can and try it. IIRC the 5150 will need the 3rd rev Bios.


                    I dug my 5150 out today and gave it some exercise, I also tried several 16-bit controllers / CF card adapters in 8-bit mode with the XTIDE universal bios and the CF card was not detected, The Controllers / CF card and adapters all work fine in my 5160 in 8-bit mode. My XTIDE Rev 1 board works fine in the 5150. Anyone have this working in a 5150 ?
                    Last edited by Malc; March 6, 2013, 12:32 PM.


                      Excellent r519 - xtidecfg's "Auto configure" now detects my XTIDE Rev 1 card and correctly configures it in my IBM XT 5160, Super job, Thank You.

                      Originally posted by aitotat View Post
                      Oops! It is now fixed.


                        On my 386DX 33, running XTIDE ide_at.bin 2.0.0B3 on a Kingston NIC, I get "Error 80h!" if I set the first boot device as "00h" (shows as 0h in XTIDECFG).
                        In other words, when I don't have a floppy in the drive, I get the above error but it will continue to boot on the HD.


                          My application takes 30 more seconds to initialize than usual with this XTIDE/Kingston KNE20T NIC (D8000 for ROM) setup. I am using the same JC1120E Winbond W83757AF controller and the same model of Seagate HD for the tests.
                          The normal setup is an 80GB Seagate with a WD 9.06 overlay and it takes 3 minutes to get the application initialized. With XTIDE and another Seagate 80GB w/no overlay, it takes 3.5 minutes.

                          What XTIDE performance tweaks are recommended for this setup of 386DX with a 16 bit controller?
                          Any other suggestions?

                          Last edited by UPI; March 7, 2013, 11:08 AM.


                            Error 80h means timeout and that is normal in this case since you try to boot from floppy drive (00h = Floppy Drive A) without any diskette in it. Next in line is first hard disk and that works.

                            About the performance issue. Have you enabled shadow RAM? Overlay software is run from 32-bit RAM but XTIDE Universal BIOS is run from 8-bit ROM unless you enable shadow RAM.


                              Having an error pop up may be disconcerting to my customer.

                              I have "Shadow System BIOS" and "Shadow Video BIOS" enabled. Is this the same?



                                I am also having lockups with the application. It doesn't always initialize when running on XTIDE.
                                It is a resource hog running Pharlap Memory Manager and a custom High Speed ISA 8 Channel Serial board.

                                I am running a 27C256 with a ROM address of D8000 because that at least works some of the time.

                                I wish I knew what I was doing because overlays are a PITA and also PATA drives are getting harder to find. The equipment this is running in is worth approx $70k and there are hundreds in the field. Long term support is key.