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

XTIDE Universal BIOS

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

    Hmm... Nope. I can set it to 00h, and that works, but it won't take 18h like R566 did. Something must have changed since that release.
    My vintage systems: Tandy 1000 HX, Tandy 1000 RSX, Tandy 1100FD, Tandy 64K CoCo 2, Commodore VIC-20, Hyundai Super16TE (XT clone), and some random Pentium in a Hewitt Rand chassis...

    Some people keep a classic car in their garage. Some people keep vintage computers. The latter hobby is cheaper, and is less likely to lead to a fatal accident.

    Comment


      It doesn't work for me using my XT 5160, Tried it with XUB R601 - R591 and R566 with HotKey bar, If i set the default boot device to 18h my XT just boots to the C; drive, Though i'm not sure it's supposed to work that way anyway. Never tried it before.

      Comment


        18h is supposed to go to the BASIC ROM... At least, so I thought. I just realized that 0xh and 8xh don't coincide with floppy and hard drive on the interrupt list! *doh!*
        There's only a couple line of documentation regarding the default boot device. Maybe somebody could better explain to me if XT-IDE BIOS takes anything beyond 0xh or 8xh for it's boot order?

        In other news, I made progress regarding the boot from C: issue. Apparently, having a ribbon cable connected to the end of the bus (it's a PLUS to ISA adapter for my I/O card) prevents it from booting from my 128MB CF card, or even seeing it properly, even with no card attached to it. A 6-inch ribbon shouldn't have THAT much reflection. Tried adding a terminator to the data bus at the end of the ribbon, but it didn't make a difference.

        I tried it over a few times. Disconnect the ribbon, and the boot works. Connect the ribbon, and the card at the end of the ribbon works, but the CF can't boot. I don't think this has to do with the BIOS.

        Well, a least that issue is narrowed down.
        My vintage systems: Tandy 1000 HX, Tandy 1000 RSX, Tandy 1100FD, Tandy 64K CoCo 2, Commodore VIC-20, Hyundai Super16TE (XT clone), and some random Pentium in a Hewitt Rand chassis...

        Some people keep a classic car in their garage. Some people keep vintage computers. The latter hobby is cheaper, and is less likely to lead to a fatal accident.

        Comment


          I have a question. Can the XTIDE bios be placed in a 8kx8 ROM in U28? (0xF4000 instead of 0xC8000). The smaller version, of course.

          Comment


            Originally posted by mrmanse View Post
            I have a question. Can the XTIDE bios be placed in a 8kx8 ROM in U28? (0xF4000 instead of 0xC8000). The smaller version, of course.
            Maybe. It fits onto an 8k ROM without the boot menu, but what are you putting it onto?
            My vintage systems: Tandy 1000 HX, Tandy 1000 RSX, Tandy 1100FD, Tandy 64K CoCo 2, Commodore VIC-20, Hyundai Super16TE (XT clone), and some random Pentium in a Hewitt Rand chassis...

            Some people keep a classic car in their garage. Some people keep vintage computers. The latter hobby is cheaper, and is less likely to lead to a fatal accident.

            Comment


              Originally posted by mrmanse View Post
              I have a question. Can the XTIDE bios be placed in a 8kx8 ROM in U28? (0xF4000 instead of 0xC8000). The smaller version, of course.
              As far as i know it should work but i've never tried it in my 5150 before, your 5150 will need to have the latest bios.

              Comment


                Originally posted by blackepyon View Post
                Maybe. It fits onto an 8k ROM without the boot menu, but what are you putting it onto?
                Originally posted by Malc View Post
                As far as i know it should work but i've never tried it in my 5150 before, your 5150 will need to have the latest bios.
                Thanks for the replies! It is indeed a 5150 with the latest bios. I have a couple of (16-bit) IDE controllers that I wanted to try, but without ROM, which none of them have, it would be pointless. With XTIDE installed as a ROM at 0xF4000 at least there is a chance.

                I have just confirmed that the ROM is detected, but I havn't transferred the configuration app to that particular computer yet, so I don't know how well it works.

                Comment


                  Originally posted by mrmanse View Post
                  Thanks for the replies! It is indeed a 5150 with the latest bios. I have a couple of (16-bit) IDE controllers that I wanted to try, but without ROM, which none of them have, it would be pointless. With XTIDE installed as a ROM at 0xF4000 at least there is a chance.

                  I have just confirmed that the ROM is detected, but I havn't transferred the configuration app to that particular computer yet, so I don't know how well it works.
                  16-bit IDE/Floppy controllers won't work in the 5150 due to the reserved IO space in the 5150, I tried them a while back and couldn't get any of them to work, The floppy part works but the IDE part does not, Modem7 came up with the answer as to why, See: http://minuszerodegrees.net/5160/dif...ifferences.htm

                  Comment


                    Originally posted by Malc View Post
                    16-bit IDE/Floppy controllers won't work in the 5150 due to the reserved IO space in the 5150, I tried them a while back and couldn't get any of them to work, The floppy part works but the IDE part does not, Modem7 came up with the answer as to why, See: http://minuszerodegrees.net/5160/dif...ifferences.htm
                    Ah, thanks! That was very clarifying! Well, time to get a xtide v4 then

                    Comment


                      Speaking of 16-bit cards in 8-bit slots, anybody know the rhyme or reason to why 16-bit cards are able to work in 8-bit slots? If it's just the data pins using the high portion of the slot, it's possible to truncate the data bus down to 8-bits, I think, but I'm not positively sure how it does this.

                      For instance, I've got a 16-bit 3Com NIC (3C509-TPO for those playing along at home) with a 28 pin boot ROM socket, and the address/data lines for that socket all go to the low-end, so the ROM itself would work in an 8-bit slot. It doesn't need any of the high address pins for the NIC portion, and the higher IRQ/DMA lines could be set for lower ones. Is it pin C1 (system bus high enable) that tells the card to go to 16-bit mode, where lacking that signal, it just stays in 8-bit?
                      My vintage systems: Tandy 1000 HX, Tandy 1000 RSX, Tandy 1100FD, Tandy 64K CoCo 2, Commodore VIC-20, Hyundai Super16TE (XT clone), and some random Pentium in a Hewitt Rand chassis...

                      Some people keep a classic car in their garage. Some people keep vintage computers. The latter hobby is cheaper, and is less likely to lead to a fatal accident.

                      Comment


                        Originally posted by vk6hgr View Post
                        So thanks to those who have created and worked on this, it makes me happy to be able to give this ancient machine a new lease on life.
                        Thank you! I appreciate the fact that you registered on this forum to give us positive feedback, not many people do that.

                        Originally posted by blackepyon View Post
                        Is there a way to set the XT-IDE BIOS to just default to ROM Boot?
                        No, not currently. I think you're the first to request this. And I'm not sure it's needed in your case - the ROM drive should have a device number like any other harddrive. If you have a CF card installed that means the ROM drive should be 80h or 81h depending on the order of BIOS initialization.

                        Originally posted by blackepyon View Post
                        18h is supposed to go to the BASIC ROM... At least, so I thought. I just realized that 0xh and 8xh don't coincide with floppy and hard drive on the interrupt list! *doh!*
                        There's only a couple line of documentation regarding the default boot device. Maybe somebody could better explain to me if XT-IDE BIOS takes anything beyond 0xh or 8xh for it's boot order?
                        Device number 18h is the 25th floppy drive. And it has nothing to do with interrupts (as you discovered). Devices numbered 0 to 127 (0h to 7Fh) are floppy drives and 128 to 255 (80h to FFh) are harddrives. Anything beyond this (more than 255/FFh) would require more than a single byte and is not possible.
                        Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                        Comment


                          Originally posted by vk6hgr View Post
                          So thanks to those who have created and worked on this, it makes me happy to be able to give this ancient machine a new lease on life.
                          Ditto

                          Originally posted by Krille View Post
                          No, not currently. I think you're the first to request this. And I'm not sure it's needed in your case - the ROM drive should have a device number like any other harddrive. If you have a CF card installed that means the ROM drive should be 80h or 81h depending on the order of BIOS initialization.
                          I have gotten DOS 5.0 to boot properly, so having it boot to ROM isn't a priority, but it would be a nice feature to have it able to automatically boot to more types of devices (maybe even put a menu just for that in XTIDECFG instead of guessing which hex value it might be). Tandy's were a bit unique in that some of them, such as my 1000HX, had DOS installed on ROM, so I was working without the CF as a boot drive for about a year until I tried to upgrade to R601 where it wasn't taking my previous setting.

                          Originally posted by Krille View Post
                          Device number 18h is the 25th floppy drive. And it has nothing to do with interrupts (as you discovered). Devices numbered 0 to 127 (0h to 7Fh) are floppy drives and 128 to 255 (80h to FFh) are harddrives. Anything beyond this (more than 255/FFh) would require more than a single byte and is not possible.
                          Yes, it did show up as trying to boot from drive Y. A Shugart controller can support up 4 floppy drives (1000EX/HX supports 3), so talk about overkill, being able to support 128 floppy drives! But this does give me the information that wasn't in the documentation. Thanks.
                          My vintage systems: Tandy 1000 HX, Tandy 1000 RSX, Tandy 1100FD, Tandy 64K CoCo 2, Commodore VIC-20, Hyundai Super16TE (XT clone), and some random Pentium in a Hewitt Rand chassis...

                          Some people keep a classic car in their garage. Some people keep vintage computers. The latter hobby is cheaper, and is less likely to lead to a fatal accident.

                          Comment


                            [2 years and a reply !]

                            ==> Thanks, WallyB - I definitely must have a try of this, I've let my A1000+BridgeBoard setup away since long as I did not find a solution to use XT-IDE with it.

                            Originally posted by WallyB View Post
                            SUCCESS!! Lo-Tech ISA/IDE-CF Adapter Working in Amiga / Bridgeboard (8086) XT PC. (Initialized X-TIDE)

                            So I finally got the Lo-Tech Adapter working with X-TIDE Universal BIOS. I almost gave up.

                            I had some luck and DOUBLE stumbled upon the solution.

                            I've tested a few times and appears to be consistent Positive.

                            Further testing and understanding of exactly how things work is needed.
                            I'm no expert on Either Amiga or Bridgeboard, but a ton of testing and luck made things work.

                            SUMMARY:

                            1) The Amiga Bridgeboard boots on Powerup, but doesn't Active till the JANUS.library loads via the AMIGA workbench Boot disk.
                            2) However that isn't enough to Initialize the Lo-Tech / X-Tide
                            3) After Amiga Boots up, to active the 8086 XT you launch the PC-Window (Where the 8086 XT PC runs in)
                            4) But that still by itself won't initialized the Lo-Tech / X-Tide (since by design the Amiga Architecture Disables AutoBoot when a Controller/Hard disk in inserted into the ISA SLot)
                            5a) To enable HARD file Autobooting a File (Aboot.CTRL) is normally placed in the AMIGA (SYS:PC/System folder)
                            5b) Normally the Aboot.CTRL file has an entry that Points to a previously created HARD file on the Amiga Side
                            5c) But if that file is there, the PC XT will boot from the File like a normal C: Drive
                            5d) During multiple testing, I by accident removed the HARD file Entry from the Aboot.CTRL file (to supress the error Message, since I removed the HARD FILE)
                            5e) Had I remove the file (not emptied it), things wouldn't work, since AUTOBOOT would be disabled (thus no initialization of LO-Tech/X-Tide)
                            6a) That still would be enough since if the Amiga sensed the Lo-Tech Adapter via INIT it wouldn't turn on AutoBooting
                            6b) So it's IDEAL that Lo-Tech does not get recognized on Power up on the PC XT ISA bus.
                            6c) The 2nd Stumble luck was I didn't reboot the Amiga, and I had the DOS Floppy disk out of the A: Drive
                            6d) Instead of Power Reboot, I did a CTRL-ALT-DEL to reboot the XT PC 8086 a 2nd time, while amiga side was up, and Autoboot enabled with the empty Aboot.CTRL File.
                            6e) That triggered a normal XT PC boot, and since JANUS.library on Amiga Side was already started, the boot was a Standard Phoenix BIOS boot
                            6d) That 2nd XT Boot now does a initialization of the Lo-Tech Adapter with X-Tide BIOS, and the IDE connected device boots

                            The X-TIDE Firmware Image I used in the Lo-Tech is the First one in above post. No the Delayed Init/Tandy version.

                            I tested with the IDE-Seagate Maxtor Drive and it works.
                            I also tested with the Secure Digital SD-Card Adapter and it works. (Picture below)
                            Haven't tested with the Compact Flash Adapter, but I'm pretty sure it will work.

                            Here is proof things worked. Retested a few times and the sequence describe above is working/consistent.

                            [ATTACH=CONFIG]36641[/ATTACH]

                            Comment


                              Originally posted by blackepyon View Post
                              Ditto
                              Thanks!

                              I have gotten DOS 5.0 to boot properly, so having it boot to ROM isn't a priority, but it would be a nice feature to have it able to automatically boot to more types of devices (maybe even put a menu just for that in XTIDECFG instead of guessing which hex value it might be).
                              Booting from more types of devices; It really comes down to the fact that the device has to emulate a floppy drive or a harddrive (on the BIOS Int13h interface level).

                              Regarding a more user friendly boot drive selection; Note that you can use XTIDECFG to configure the BIOS for other machines and in that scenario it's obviously not possible to detect the number (or type) of drives.

                              While XTIDECFG could certainly be made to see the current number of drives in the BIOS Data Area on the machine it is running on, it would still be very hard to reliably map device numbers to drives for future boots as that can change a lot depending on the order of option ROM initialization. It would have to determine factors such as; Is XUB already installed or not? Where in the UMA will the user install XUB? Will the system BIOS initialize option ROMs going from the bottom of the UMA to the top (as is usually the case on old machines) or will it go the other way (which admittedly, AFAIK, is a configuration option available only on more modern machines)? How many drives will the user install in the machine?

                              It would just be guessing and I'm sure the user can do a far better job at that than XTIDECFG.
                              Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                              Comment


                                Originally posted by Krille View Post
                                Thanks!

                                Booting from more types of devices; It really comes down to the fact that the device has to emulate a floppy drive or a harddrive (on the BIOS Int13h interface level).

                                Regarding a more user friendly boot drive selection; Note that you can use XTIDECFG to configure the BIOS for other machines and in that scenario it's obviously not possible to detect the number (or type) of drives.

                                While XTIDECFG could certainly be made to see the current number of drives in the BIOS Data Area on the machine it is running on, it would still be very hard to reliably map device numbers to drives for future boots as that can change a lot depending on the order of option ROM initialization. It would have to determine factors such as; Is XUB already installed or not? Where in the UMA will the user install XUB? Will the system BIOS initialize option ROMs going from the bottom of the UMA to the top (as is usually the case on old machines) or will it go the other way (which admittedly, AFAIK, is a configuration option available only on more modern machines)? How many drives will the user install in the machine?

                                It would just be guessing and I'm sure the user can do a far better job at that than XTIDECFG.
                                Mainly, what I was originally looking for is to have it do is the equivalent of pressing F8 automatically instead of booting A: or C:. I'm assuming that F8 just skips the drive boot and continues through the ROMs like the machine would normally do without the XUB. As I said, the Tandy 1000HX has DOS 2.11 in ROM already, so for the 16MB CF card I was using originally, it could be used for storage and installing a bootable DOS wasn't necessary.
                                My vintage systems: Tandy 1000 HX, Tandy 1000 RSX, Tandy 1100FD, Tandy 64K CoCo 2, Commodore VIC-20, Hyundai Super16TE (XT clone), and some random Pentium in a Hewitt Rand chassis...

                                Some people keep a classic car in their garage. Some people keep vintage computers. The latter hobby is cheaper, and is less likely to lead to a fatal accident.

                                Comment

                                Working...
                                X