Announcement

Collapse

Forum 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.


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.


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.



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.


"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.

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

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

    Hi aitotat,
    I built the r485 binanries.
    I saw that the XTP version should work with NEC V20/V30. Since I have installed a V20 im my Commodore PC, I first tried the XTPL version, but it didn't work. The machine hung up during boot at the moment the IDE_XT BIOS should have been initialized.
    So I then tried the plain XT version, which semms to work at first.
    The XTIDE BIOS shows up with:
    Code:
    Master at 1F0h:
    Slave  at 1F0h: not found
    Booting C>C
    Boot sector not found
    Booting A>A
    Booting MS-DOS 6.22 from disk A: works. Next thing I tried was creating a DOS partiton using fdisk.
    Looked good ... until reboot. The XTIDE BIOS again found no boot sector.
    I took a look with fdisk ... no partitions defined.
    Tried fdisk /mbr ... no boot sector found.
    I also tried booting MS-DOS 3.20 and creating a partition with fdisk ... same result.


    biosdrvs shows no name for the drive and after listing CHS data it ends up with:
    EBIOS information from AH=48h...
    BIOS returned error code 1h

    any hints ?

    Comment


      Drive name is missing so drive was detected but drive ID was not properly read. Did you change device type to 16-bit ISA IDE in 8-bit mode? I don't know why XTPL version did not work. I'll need to test that.

      Comment


        You're right, I missed that.
        I now changed to 16bit in 8bit mode, but now the CF card isn't detected anymore. (not found)
        Seem's my controler card isn't compatible ?
        It uses a goldstar GM82C765B PL chip.
        Does it make sense to try other controller types ?

        Comment


          Originally posted by Toast_r View Post
          Seem's my controler card isn't compatible ?
          Yes, it seems that way. I don't know why 8-bit mode only works on some controllers.

          Comment


            Yes, there was a bug in XTIDECFG.COM. 8k builds were saved with correct size but large builds always became 32k. The bug is now fixed.

            v2.0.0 beta 2 does not support 16-bit IDE controllers in 8-bit mode. It is now supported (in SVN r485) but you need to make your own build of XTIDE Universal BIOS and the Configurator.
            """I'm looking for the newer svn repositories, but http://xtideuniversalbios.googlecode.com/svn/branches has nothing underneath it."""

            Nevermind, I saw that the version number on the xtidecfg was 2.0.0 so I thought it was a old version...

            All's good.

            Later,
            dabone
            Last edited by dabone; November 29, 2012, 10:01 AM.

            Comment


              Originally posted by aitotat View Post
              Yes, it seems that way. I don't know why 8-bit mode only works on some controllers.
              Appears to be electrical (some multi-functions prevent POST running).

              Comment


                Is the XTIDE board still available? I would like to purchase one.

                Comment


                  Originally posted by hargle View Post
                  That's a perfectly fine solution, in fact, it's a great solution for IDE controllers that are on the motherboard (on the AT based machines-very few XT machines have onboard IDE)
                  You would need to disable the BIOS on the ADP50L and put the XTIDE BIOS on a chip and put it in the network card. I've done this on a 386 machine of mine with a 3com NIC and an old promise IDE controller.
                  I know this is 2 years old, however is there a simple way to disable an IDE BIOS on an AT style (386DX) motherboard so that I can use a ROM on a NIC or SB etc? Could it be as simple as telling the BIOS that no HDD are installed?

                  I was going to use an old Unicore LBA Pro ISA card, however I can't really spare an ISA slot.
                  My Wish List: Vintage Mac SCSI->ETHERNET DaynaPORT LINK T DP0801 Manual, Hallock Systems gear / disk images, Copy II PC 'Enhanced' Option Board, Earth Computers ISA Z80 cards & TurboDOS disk, TRS-80 Model IV TurboDOS, Pulsar Little Big Board gear, Model 16/6000 Tandy Videotext Information System (VIS) Operator's Manual, S100 Expansion Interface (Original version which utilised an S100 32K memory card) for EACA PMC/TMZ/Dick Smith System 80

                  Comment


                    yep, just set the drives to NONE in the onboard setup, it should be that easy. [insert murphy's law here of course]
                    If you have a setting to disable the IDE controller in setup, leave it to enabled.

                    Then, during power up, the mainboard BIOS should skip all communication to any attached drives.
                    When the ROM that contains the universal BIOS then loads, it will talk to the onboard IDE controller, interrogate the drives, and add them to the system just as the mainboard BIOS would if you had them set to one of the drive types available, minus whatever drive size limitations your 386 BIOS has. It's a beautiful fix.

                    Comment


                      Can you burn a new version of the XTIDE Universal BIOS or make PROM settings changes to a PROM installed in a Kingston KNE20T NIC?
                      I was able to burn the latest version onto a 27C256 PROM using a programmer and everything works great, but when I run XTIDECFG, it does not want to write to the PROM.
                      Is this the way it is supposed to work? If you can't make changes while installed in the NIC, how do you change settings before programming the PROM?

                      Thanks for such a great project!

                      Comment


                        I found the answer here:
                        http://vogons.zetafleet.com/viewtopi...285957a3370f95

                        I didn't think about using the XTIDECFG program to edit the .BIN file and then burning the result to the PROM.

                        Comment


                          Today I have been testing the XTIDE Universal BIOS in a IBM PS/1 2011 but it doesn't work. This is a special machine, as it has a DOS in ROM feature. I suspect that the booting procedure is not standard.

                          -With v2.0 builds, the computer boots as if the XTIDE Universal BIOS was not present. I have downloaded the trunk source code and inserted some OUT instructions to show debug in a ISA POST debug card, and I can confirm that the ROM is being loaded, but it never shows or detects any hard drive.
                          -With 1.1.5 release and Late Initialization DISABLED, the BIOS detects the hard drives but the boot menu is never shown. It always boots from the foreign hard drive if it is installed. If the foreign hard disk is missing then it boots from the first hard disk connected to the IDE port managed by the XTIDE Universal BIOS. Also if the computer is configured to boot from DOS in ROM, then the system doesn't boot, it stops after the XTIDE Universal BIOS hard drive detection.
                          My videos:
                          IBM PS/1 model 2011 restored and enhanced
                          IBM PC Advanced Diagnostics Cassette load

                          Comment


                            DOS in ROM what a marvel that was. r505 works well for me on the TeraDrive.
                            However I've found what appear to be other issues with beta 3 and r550.
                            Neither auto detect any hard drives attached.
                            I've put some more information over here.

                            To think, I came here looking on how to get a 32K image working for the sake of nice flashy menus.
                            Then I get caught up in all this, I love weekends!
                            Flashing to an XTIDE v2 card set for 8K ROMs (with 32K ones just will not flash, fails reporting the bytes read do not match bytes written).

                            For the TeraDrive it shows the six screen menu, drop to DOS and then the XTIDE Universal BIOS fires up.
                            Does the PS/1 do anything like that?
                            McRetro.net | YouTube Channel | McRetro Gaming | Photo Gallery | File Server

                            Comment


                              Originally posted by nestor View Post
                              -With v2.0 builds, the computer boots as if the XTIDE Universal BIOS was not present.
                              -With 1.1.5 release and Late Initialization DISABLED, the BIOS detects the hard drives but the boot menu is never shown. It always boots from the foreign hard drive if it is installed. If the foreign hard disk is missing then it boots from the first hard disk connected to the IDE port managed by the XTIDE Universal BIOS.
                              Sound like the main bios installs INT 19h (boot loader) handler after ROM initialization so it replaces XTIDE Universal BIOS boot loader. v2.0.0 uses it to detect drives. v1.1.5 can detect drives during ROM initialization (late initialization disabled) but INT 19h handler is required to display boot menu.

                              Also if the computer is configured to boot from DOS in ROM, then the system doesn't boot, it stops after the XTIDE Universal BIOS hard drive detection.
                              If I remember correctly the v1.1.5 has INT 18h handler that is used to jump back to boot menu for certain boot failures. It wasn't very useful feature so it was removed. I think this is why you cannot boot to ROM DOS with v1.1.5. But that means the main bios does not replace INT 18h handler (ROM boot). I think XTIDE Universal BIOS can then be made to work by using INT 18h handler to detect drives.

                              Comment


                                Originally posted by nestor View Post
                                With v2.0 builds, the computer boots as if the XTIDE Universal BIOS was not present. I have downloaded the trunk source code and inserted some OUT instructions to show debug in a ISA POST debug card, and I can confirm that the ROM is being loaded, but it never shows or detects any hard drive.
                                I'm very interested in this as I'm stuck on getting the BIOS to initialise on a Tandy 1400FD laptop. Maybe the problem could be the same. Would you be willing to make your modified BIOS available?

                                Comment

                                Working...
                                X