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

    Originally posted by hwarin View Post
    Hi friends

    I've finally got good results with "VeryEarlyInit" and "Steal_Ram" options.

    Here is the code that I've successfully tested, should work for 8088 SideCar and BridgeBoard.
    I have a rainy-day project to setup the xtide with an 8088 bridgeboard. I have all of the parts, but haven't worked up the nerve yet... does your work imply that the standard xtide won't work in an a2000 without your modifications?

    Comment


      Originally posted by Krille View Post
      This has been discussed before and everyone agreed on having the BIOS print the revision number just like you described. The problem is that it requires changes on the server side, and no one knows how to do it/has bothered to look into it.
      Ah well. There's always Hex Editor. That's what I've been using... For the few lines that I can actually read, anyways.
      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 Towmater View Post
        I have a rainy-day project to setup the xtide with an 8088 bridgeboard. I have all of the parts, but haven't worked up the nerve yet... does your work imply that the standard xtide won't work in an a2000 without your modifications?
        I'm not intimately familiar with the A2000, but it does have 8 and 16-bit ISA slots, so I assume you should be able to just plug and play if it's as PC compatible as it's advertised. If you've got the parts, I say just put it together and see how it works. Electrically at least, you shouldn't have any issues.
        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 built a Tex-Elec kit a few months back and have been fighting with this stupid thing ever since. One BIOS (the publicly posted 2.0.0 b3)will run a drive, but somehow screws up the computer's ability to use floppies. Another one (r580) fixes that issue, but doesn't acknowledge any hard drive plugged into it. Others (Like the R602 and 1.1.5) simply make the card act as if there is no ROM there. (The PC itself is an XI8088 with the XT-IDE card set to 300 and c8000, but it behaves the same way in an XT)

          I have finally found the page where the recent builds are stored (Is there a particular reason that page is hidden?) Am I supposed to do something special when writing these files? I used the IDE_XT.BIN, wrote it to the ROM (it's an 8K flash rom), and the XTIDE (REV 4) just acted like there was no ROM there. I noticed the bin file is 6.3K instead of 8.2K, so is there supposed to be some sort of filling/offest procedure I am supposed to do? (I use a Gq-4x4. Erase, blank check, slowest write, verify)

          Comment


            I was not aware that Tex-Elec was selling the XT-IDE rev.4. I've had good experience with R601, but that's on the XT-CF rev.2b, which Tex-Elec sells.

            I'm not aware of anything special to do when writing these files, but if it's acting like there's no ROM there, the flash might have failed or you've somehow flipped the "ROM Enable" switch to the off position, because if it was successful, you should at least see the ROM's POST screen whether it can detect the card/hdd or not.

            That's just off the top of my head. I don't think those address should have any conflicts, but if it's acting the same way in two different machines, then the fault is probably on the card or the ROM. If the chips are socketed, you could use your EEPROM programmer to do a logic check on the chips to make sure there aren't any lemons among them.

            If Sergey or Glitch are lurking about, they may have other ideas to run through.
            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


              My bad, It's the blue Glitch Works kit (rev 4), that I bought from him/them on Ebay. (labled 'Seller you bought from)

              I've never had the ROM error out when writing it, but I suppose I could try buying another one.

              Comment


                Originally posted by Moogle! View Post
                My bad, It's the blue Glitch Works kit (rev 4), that I bought from him/them on Ebay. (labled 'Seller you bought from)

                I've never had the ROM error out when writing it, but I suppose I could try buying another one.
                Well, I was going by what was on his site. No idea what's on eBay.

                Check the ROM Enable switch, and try testing the ROM in the programmer. I haven't tried the 2.0.0B3 R602, but 1.1.5 r566 does have problems recognizing some CF cards, I've noticed (or maybe that was just where I had the '245 buffer located on my protoboard). R601 solved the problems I was having.

                Also, what mode are you using to program the BIOS? If you're using PIO-8 mode, it probably won't like it.
                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 no idea what mode the GQ-4x4 uses. It's been pretty successful in the past with other EPROMS, Flashchips, and OTPs.

                  I pulled the 8K EPROM from my Hedaka 919 to test with. Erasing it in the UV box now.

                  Comment


                    Make sure you have a backup of that BIOS before you wipe it. Once you have a clean EEPROM chip use the XTIDECFG.COM utility to flash it. Make sure you're programming it as "XT-IDE" or "XT-IDE rev.2 (or modded rev.1)," whichever matches the Chuck-mod settings.
                    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


                      Well, EPROM idea was a dud, but I tried flashing it using XTIDECFG with the original 8K flash chip in it*, and it actually worked. I used r602. It still will not acknowledge any drive though, but I can at least boot from a floppy properly. (However that fails the first time, every time, after it looks for the hard disks and then tries the floppy.)

                      I am still playing with it. Thanks for the advice.

                      *ironically this sort of thing was the reason I bought that programmer, to avoid in-PC flashing

                      Comment


                        As you now know you *Must* configure the XUB for your particular system using XTIDECFG.COM first and then flash / burn to E/Eprom, Glitch Pre-flashes the EEproms in the kits with XUB v1.1.5 so if you originally setup a CF / hard drive using XUB v1.1.5 and upgrade to a recent newer revision of the XUB you will likely have to wipe / clean the CF / hard drive and re-partition / format the drive. It's probably a good idea to wipe / clean the hard drive in any case.You shouldn't really need a programmer to flash the EEprom in the XTIDE cards, XTIDECFG.com has gotten a lot better over the years.
                        Modem7 has some info on the XTIDE on his site http://minuszerodegrees.net/xtide/re...%20general.htm

                        Comment


                          I ultimately think you and blackeypon were correct about using XTIDECFG.

                          In the meantime, I just sat down and with my iron and re-flowed every single joint on that board. It looks a lot better now. I also moved the jumpers from compatibility to hi speed, and now it's ID-ing and booting from the drives again, and even seeing that 64MB compact flashcard.

                          Thanks for all the help guys.

                          Comment


                            Originally posted by Moogle! View Post
                            Well, EPROM idea was a dud, but I tried flashing it using XTIDECFG with the original 8K flash chip in it*, and it actually worked. I used r602. It still will not acknowledge any drive though, but I can at least boot from a floppy properly. (However that fails the first time, every time, after it looks for the hard disks and then tries the floppy.)

                            I am still playing with it. Thanks for the advice.

                            *ironically this sort of thing was the reason I bought that programmer, to avoid in-PC flashing
                            Well, that's progress, at least. That other chip you tried might have a different pinout than the Atmel the kit came with.

                            It's not necessary to use the FLASH utility; XTIDECFG can flash within the program itself. At least, it works for me. There's a data-protection flag you gotta set properly when flashing it, otherwise you can't re-flash in the utility without using a programmer to wipe it, and I'm still trying to figure out which way it's supposed to be set. But these programmers have other uses, so worth keeping around regardless.

                            You can hold down the [A] key at POST to make it boot straight to A:, and in the in XTIDECFG, once you have the BIOS loaded, before you flash it, under "Configure XTIDE Universal BIOS" > "Boot Settings," you can set the default boot device to 00h if you want first floppy, or 80h for the first hard drive.

                            What are J1 and J2 set to on the card? If it's configured for "high-speed mode" then under "Configure XTIDE Universal BIOS" > "Primary IDE Controller" > "Device Type" you'll need to have it set as "XT-IDE rev.2 or modded rev.1" when you flash the ROM, but if set for compatiblilty mode, then set for "XT-IDE rev.1". And of course, make sure the "Base (cmd block) address" is set for "300h," if that's what your card is set for. The ROM address switches can be changed at any time, but whatever the I/O switches are set for must be programmed into the BIOS when you flash it.
                            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


                              Using XTIDECFG to do the flashing is what I meant. Sorry, I wasn't clear.
                              Attached Files

                              Comment


                                Originally posted by Moogle! View Post
                                I ultimately think you and blackeypon were correct about using XTIDECFG.

                                In the meantime, I just sat down and with my iron and re-flowed every single joint on that board. It looks a lot better now. I also moved the jumpers from compatibility to hi speed, and now it's ID-ing and booting from the drives again, and even seeing that 64MB compact flashcard.

                                Thanks for all the help guys.
                                Sweet! Glad we could help!
                                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