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

  • Filter
  • Time
  • Show
Clear All
new posts

    Originally posted by Anonymous Coward View Post
    ASPI7DOS does NOT load correctly without any drives connected to the XTIDE. The menu appears to report the size of my SCSI disk correctly. The SCSI drive is listed BEFORE the drive connected to the XTIDE.
    SCSI BIOS indeed initialized before XTIDE Universal BIOS since SCSI drives appear before XTIDE drives. This would mean that INT 13h handler from XTIDE Universal BIOS gets called before SCSI handler and i think that is why ASPI7DOS won't work. XTIDE Universal BIOS restores DS and DI registers to same values they were when entering INT 13h handler. There might be some SCSI specific functions that return something in DS or DI. I have already fixed this to unreleased RC3.

    I did try initializing XTIDE before the SCSI BIOS with drive swapping disabled. In that case the behaviour was slightly different. The floppy drive would not appear on the boot list, and removing all drives from XTIDE would allow ASPI7DOS to load.
    I have no idea why floppy drive was not found. In this case SCSI INT 13h handler gets called first so ASPI7DOS should work. It should have worked even with XTIDE Universal BIOS controlled drives present.

    SCSI BIOS does not have a boot loader since boot menu appears even when SCSI BIOS is initialized after XTIDE Universal BIOS.

    What port are you using for IDE controller? I can give you a customized RC3 if you want to try it right away. It will take at least a week before new is ready.


      I noticed the A: boot option not showing up is intermittent (that's why I revised my post).

      I am currently using my drive on the primary IDE controller IRQ 14, 3F6h and 1F0h

      I wouldn't mind trying the customized RC3 at all!
      "Will the Highways on the internets become more few?"

      V'Ger XT


        Here is the customized RC3. Drive swapping and interrupts are disabled to minimize potential problems. Flash with the previous but do not change any settings.


          The only difference I noticed was that the system locked up rather than reset (with the CF attached)
          "Will the Highways on the internets become more few?"

          V'Ger XT


            Did you try it with before and after SCSI BIOS initialization? What about without any drive attached?


              If I set XTIDE after the SCSI BIOS without a drive attached, then ASPI7DOS loads just fine.
              "Will the Highways on the internets become more few?"

              V'Ger XT


                Anonymous Coward, Here is another build for you to test. I removed all recursive INT 13h calls. I hope it helps. If not, i need to reproduce the problem myself before i can fix it.


                  I have some good news and bad news.

                  Bad news first. I'm not ready to release next version this week or even next week. I found a problem that took a lot of time to figure out.

                  I decided to test polling mode on a 286 with 16-bit IDE controller. I had Quantum ProDrive LPS 340A connected to it (340 MB drive). It had worked fine all this time with and without IRQs enabled but now it had occasional timeouts after i disabled interrupts. I assumed that there was a bug in RC3. I did a lot of testing and results were the same all the time: no problems with IRQs enabled but timeouts in polling mode (this resulted in bad sectors when formatting). This was the only drive with problems on polling mode and it happened on XT clone as well. Then i finally remembered that i hadn't implemented block mode transfers when i last tested that drive in polling mode. All problems disappeared after i disabled block mode. Now i know why block mode can be disabled on many BIOSes. The drive itself had a buggy block mode implementation since it worked only when interrupts were enabled.

                  Some good news too:
                  I tested XTIDE Universal BIOS with Sound Blaster 16 (CT2290) and it works just like any 16-bit IDE controller. No problems at all. Other sound cards with IDE should work too (not sure about PnP sound cards).

                  Next version won't be RC3. It will be v1.1.0. There are so many improvements that i cannot call it 1.0.0 anymore. I will also release source codes. Any recommendations about what open source license i should use?


                    I recommend LGPL, it's GPL-compatible but less restrictive on you.

                    I assume that when you tried it on the SB16 you mean that you replaced the ROM chip on the SB16? Does it still function as a soundblaster? That'd be a fantastic thing to do if so.. :P If you mean that you just plop an XT-IDE card or card with the BIOS into the system and it takes over SB16 IDE control that's even cooler. You could solve some problems I'm having if either of these is the case..
                    More commonly known as "Yushatak" -
                    Focused on 486 and Pentium Machines
                    I collect All-In-One PCs and Keyboard PCs, especially Compaq.


                      There is no ROM on the Sound Blaster that would be mapped to system address space. I used XTIDE and XTIDE Universal BIOS was configured for tertiary IDE port that the SB16 uses by default. XTIDE is not required since the BIOS ROM can be placed to some other card like on a network card.


                        I tried the second custom build that you made for me. Now ASPI can load just fine, but the drive connected to the XTIDE is showing "Not ready reading drive D". I noticed in the BIOS options that it was set to "32 bit" mode by default, but I also remember you mentioned last time not to play with any of the settings. I did try "16 bit" mode just for the hell of it, but that didn't work either.
                        Last edited by Anonymous Coward; April 17, 2010, 08:57 AM.
                        "Will the Highways on the internets become more few?"

                        V'Ger XT


                          Originally posted by Anonymous Coward View Post
                          Now ASPI can load just fine
                          Very good that at least something got better.

                          but the drive connected to the XTIDE is showing "Not ready reading drive D".
                          Where does it show that? When you try to boot from it or when you have booted from SCSI drive and try to access IDE drive from DOS? Does it show properly on boot menu (correct size etc.)?

                          I noticed in the BIOS options that it was set to "32 bit" mode by default, but I also remember you mentioned last time not to play with any of the settings. I did try "16 bit" mode just for the hell of it, but that didn't work either.
                          Old idecfg displays it wrong since i now use different values.


                            The boot menu seems to display both drives properly.

                            With SCSI at D800 and XTIDE at DC00, it doesn't seem to matter which drive I select to boot from, it will boot from the SCSI drive either way, in both cases displaying the "not ready" message for drive D (xtide).
                            With SCSI at D800 and XTIDE at D000, the system boots to the IDE drive regardless of what is selected in the menu, only the SCSI drive is still accessible as drive D.
                            "Will the Highways on the internets become more few?"

                            V'Ger XT


                              I am using whatever came on my revision 1 XT-IDE (Hargle's last '09 BIOS I suspect). It's working ok but could be faster. Should I upgrade/change to the Universal BIOS?

                              I haven't tried it, but is there any way to get the XT-IDE to work with a 750GB HDD? I suspect drive overlays are required?
                              More commonly known as "Yushatak" -
                              Focused on 486 and Pentium Machines
                              I collect All-In-One PCs and Keyboard PCs, especially Compaq.


                                so the XT-IDE bios supports tertiary ide controllers aswell? That give me some ideas. Anyhoo, my XT-IDE's both work flawlessly now, I eagerly await 1.1.0
                                Nothing beats the roar of a 36yr old drive coming to life after a decade in storagg