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 Krille View Post
    This is confusing. "TURBO button unpressed" - To me that means the machine is running at full speed since that button is actually used to slow down the machine. But I'm guessing you meant that the machine hangs when running at full speed?
    Exactly. You are right. It hangs when running at full speed.
    However, with the ISA bus set to 6.25 MHz it should work. Can you use the NICs without the ROMs with the machine set to 12 MHz?
    Yes it's looks strange it can't boot with ISA 6,25 MHz with XUB at NIC.
    The both NICs without boot ROM installed didn't hang the both machines regardless frequency set. Also I can load utility for 3com NIC and set its parameters at frequency 12 MHz. I didn't check the network. I don't know how to check network for NIC "B" because it BNC only.
    Also here are some updates of specs of my machines:
    - "another" 286 actually based on 10 MHz (not 12 MHz) AMD CPU.
    - Schneider VGA AT System 40 actually clocked at 12,5 MHz (not 12).
    This explains the reason that NIC "B" with both EEPROMs boots well in "another" 10 MHz 286 and hangs in Schneider at 12,5 MHz.

    I assume that the ISA frequency of Schneider AT remains unchanged regardless of the selected option in BIOS Setup.
    I think I must check actual frequencies at ISA bus in my machines first. hope that I can bring oscilloscope for the weekend and I'll back here with measurement results.

    May the issue be related to slow timings of EPROM chips used?


      Today I chrcked ISA clock by oscilloscope for my systems.
      P1 - 8,4 MHz
      Schneider: actually there are three options for CPU/ISA in the BIOS Setup: "6,25/6,25" (in this mode BUB boots), "12,5/12,5" and "12,5/6,25". In last mode the frequency of ISA (and CPU too) is 6,25 only for I/O operations to the expansion cards (another kind of operations such as memory read/write, CPU itself etc is perfomed at 12,5 MHz). The chipset is syncroniouse so it can't control different frequencies for CPU and ISA at same time.
      "another" 286: 12 MHz at full speed despite CPU rated 10 MHz installed. ISA clock behavior is the same as in Schneider with oprion CPU/ISA=12,5/6,25
      Also I tried with faster (80ns) PROM - this did not yield positive results.

      So it is clear root cause is incompability of mentioned NICs with high ISA frequency. Krille, thank you for advice! I will try with other NIC cards on my Schneider...


        I've tried a lot of NICs but each time got the same result.
        Also tried SCSI controller with his own ROM BIOS and behavior was the same: it can boots only when system frequency set to 6,25 MHz.



          I'm using r605 (ide_386l version) of XTIDE on a 3C509B-TPO in a 386DX/486DLC machine; it's my first time using it on something newer than a 286 (which I've always had great success with, albeit with smaller drives - up to ~4GB CF cards).

          I'm now trying to use bigger drives (16GB and 64GB Sandisk Ultra CF cards as an example, but also a couple of 60GB 2.5" IBM Travelstar notebook drives). All drives are detected fine (and listed as 'LBA' in the XTIDE boot menu), can be partitioned and formatted okay (using one of either a Windows 98SE boot floppy, or an IBM PC-DOS 7.1 bootable floppy - just in case the FAT32 implementation of one or the other was at fault).

          OS boots from the XTIDE boot menu fine.

          However, it seems that any content on the drives beyond approximately 8GB is inaccessible.

          My recent tests partitioning a 16GB CF card as follows:

          512MB OS, primary partition 1, FAT16, (bootable, LBA flags)
          7.3GB Data 1, primary partition 2, FAT32, (LBA flag)
          7.3GB Data 2, primary partition 3, FAT32, (LBA flag)

          OS, drivers and tools copied on to partition 1 are fine. All content (there's some ~6GB of it) copied on partition 2 is fine. But of the several GB of content I copied to the third partition, almost all of it is reported via 'dir' as empty directories, directory entries with gibberish filenames, or will lock the computer if I try to 'cd' to it.

          I remove the card and put it back in a card reader and everything is there, untouched and absolutely fine.

          The reason I went with that partitioning scheme was to try and identify if there was something consistent with the 'corruption' (not really corruption, but inaccessible content) when I had a single FAT32 partition. It now seems that it's related to accessing the drive beyond a certain point.

          What exactly are the limitations on disk size as imposed by XTIDE, and has anyone seem similar trouble with disk content beyond ~8GB?
          Last edited by Megatron-uk; May 19, 2021, 01:00 PM.


            r606 was released recently which addresses larger sizes in 32-bit OSes, I believe. Try r606.
            Offering a bounty for:
            - A working Sanyo MBC-775 or Logabax 1600
            - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)


              One question I hhave is I have the XT-IDE but haven't updated the bios on them
              if I do will more cf cards work with the device.

              I am using a 486 with the XT-IDE but am unsure which bin file to download.


                Originally posted by Hypr2021 View Post
                One question I hhave is I have the XT-IDE but haven't updated the bios on them
                if I do will more cf cards work with the device.
                Someone else may answer that (because I do not know the answer).

                Originally posted by Hypr2021 View Post
                I am using a 486 with the XT-IDE but am unsure which bin file to download.
                See the 'Different builds' section of [here].

                You have a 486 based computer, so the IDE_386.BIN and IDE_386L.BIN are the best option ("requiring 386 or better"). If the EEPROM on your card is 8 KB sized, then of those two files, you will be restricted to using IDE_386.BIN

                However, if you plan to be moving your XT-IDE card between computers, and those computers include XT's (8088 based) and AT's (286 based), then perhaps it would be a better idea to use the 'lowest common denominator', IDE_XT.BIN or IDE_XTL.BIN. Those will work in 8088/286/386/486 based computers, saving you having to reflash the XT-IDE's BIOS when you move the card about. If the EEPROM on your card is 8 KB sized, then of the two files, you will be restricted to using IDE_XT.BIN

                Be aware of the information at [here].


                  Originally posted by Hypr2021 View Post
                  One question I hhave is I have the XT-IDE but haven't updated the bios on them
                  if I do will more cf cards work with the device.
                  There is a lot of variations of the original XT-IDE controllers around these days available from 3rd parties, The quality of some is poor from what i have seen but i don't own any so have no real experience with them, I own original VCF rev 1 / 2 and 4 controllers and a couple of Lo-Tech controllers.

                  There are CF cards out there that just do not work in 8-bit mode, I have a couple of Transcend CF cards that don't work in 8-bit mode but work fine otherwise, There are also CF cards out there that Violate the ATA spec and recently in XUB r612 Code was added in an attempt to improve compatibility with some CF cards.

                  In answer to your question: I dunno either, All you can do is try the most recent revision of the XUB.


                    Thanks, I did resolve the one issue I had I didn't flash the Glitchworks XT-IDE in question I got 2 CF card booting off it but my Monotech XT-IDE is the next concern, it won't let me flash it to a new BIOS, it says there is a timeout pooling eeprom when I attempt a flash, and it also doesn't detect a CF card unless it has to be formatted / run through FDisk etc.

                    I haven't changed the DIP switches on it


                      Originally posted by Hypr2021 View Post
                      ...but my Monotech XT-IDE is the next concern, it won't let me flash it to a new BIOS, it says there is a timeout pooling eeprom when I attempt a flash, and it also doesn't detect a CF card unless it has to be formatted / run through FDisk etc.

                      I haven't changed the DIP switches on it
                      I assume you are using XTIDECFG.COM and your Monotech controller has an ATMEL 28C64 / 28C256 EEprom, Check your dip switches, Make sure the EEprom is set writeable, It should not matter if the CF card is RAW or properly partitioned / formatted it should be detected either way. Also make sure you are using the XTIDECFG.COM that was included in the same folder where you got the bios file from.



                        This may already be a common practice, but adding the XTIDE BIOS ROM to a machine with an AWARD BIOS by removing the NCR or Symbios SCSI ROM from the main BIOS ROM and adding the XTIDE one in its place is an option that I find really convenient . For this to work, a hardware check for the presence of an actual NCR or Symbios SCSI card must be patched out of the main BIOS as described here . On the Asus P3B-F, at least, doing this seems to work fine with R614 .

                        Big thanks to everyone who help developed/debugged XTIDE and allowed this to become a reality .


                          Hi all,

                          Quick question: does XT-IDE Universal BIOS handle the floppy drive int13 commands? I've tried reading the source but I'm not super experienced in Assembly and I found it too highly structured for me - I couldn't see where it might handle say a Int 13h READ (AH=2) or VERIFY (AH=4) command. Or does the XUB fallthrough to the system BIOS for floppy commands and leave it to that to handle them?

                          I'm looking to tinker with the floppy BIOS code using on my in Xi8088-based machine and I'm using an XUB for the XT-CF interface it uses. I didn't want to start modifying the BIOS code just to find out that it never runs and the XUB handles all Int 13h code!

                          And if XUB does handle floppy seeks/reads/writes, etc..., does anyone know where that code is? I would defo need to lvl-up my assembly to start making my changes in that code base, but hey gotta start somewhere



                            No, there's no support for floppy drives in XUB except for the virtual serial floppy drive functionality but that's a different beast altogether. Commands adressing drives not handled by XUB will be passed to the previous interrupt 13h handler in the chain, and this of course includes floppy drives (unless the handling of those has been relocated to interrupt 40h).
                            Looking for a cache card for the "ICL ErgoPRO C4/66d V"


                              I have a Lo-tech ISA card and am using the IDE_386L.bin from rev 614. The motherboard is a Biostar MB-8433UUD v3.1. The IDE controller is in the southbridge, UM8886BF. I have the motherboard's BIOS set to use PIO-4 on the primary IDE. I have the XTIDE BIOS configured for 32-bit controller. block mode: yes, CHS translation method: LBA, internal write cache: disabled. I'm using a 600x CF card.

                              When I test the speed of my CF card in DOS 7.x WITHOUT xtide, I get around 4,500 KByte/s. When I plug-in the Lo-tech card w/XTIDE BIOS and run the same benchmark, the read speed drops all the way down to 1,200 KByte/s. Once Windows 95 and NT4 loads, they use some driver which puts the speed back to where it should be. Is the XTIDE BIOS reducing my PIO mode or IDE timings? How do I fix it so that the XTIDE BIOS does not reduce my throughput in DOS?

                              I apologise if this has been asked before. I did not skim all 33 pages of this thread to look for a solution.


                                The UM8886BF appears to be a PCI IDE controller and there is no native support for that (or any other PCI controller) in XTIDE Universal BIOS. So it's probably running in PIO mode 0.

                                I guess you need to use XUB to overcome some disk size limitation in the motherboard BIOS? If so, the only recommendation I can give is to use a DDO instead of XTIDE Universal BIOS if you can't live with the lower performance.
                                Looking for a cache card for the "ICL ErgoPRO C4/66d V"