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

    Hardware failure, should be back by the end of the week.

    Comment


      Originally posted by pearce_jj View Post
      Hardware failure, should be back by the end of the week.
      Excellent! Thank you

      Comment


        Originally posted by pearce_jj View Post
        Hardware failure, should be back by the end of the week.
        I see it's back up did you get the problems sorted, Can it be updated with new revisions now ?

        Comment


          Yes but only if they don't have additional files for reasons that remain unknown

          Comment


            I was able to update my XTIDE BIOS, but then hosed it with a bad configuration. I was trying to set the BIOS display to monochrome, and now all I get is crazy snow on boot. Since it won't boot from disk, I don't know what to do. Any thoughts?

            Comment


              Replied on the other thread.

              Comment


                Does anyone happen to have a copy of the XTIDE bios already split into even / odd (in BIN format?) for U17 & U37 on an IBM 5170 motherboard? I have a couple different ISA cards, and it works great in those - but I thought I would give this a try next. I'm still researching the best way to properly split the file.

                Comment


                  Turbo Pascal

                  Comment


                    Originally posted by jasmi View Post
                    Does anyone happen to have a copy of the XTIDE bios already split into even / odd (in BIN format?) for U17 & U37 on an IBM 5170 motherboard? I have a couple different ISA cards, and it works great in those - but I thought I would give this a try next. I'm still researching the best way to properly split the file.
                    I posted a copy of r591 with boot menu a while back for the U17 and U37 sockets, It's configured for a 16-bit IDE controller, Give that a try if you want, See post #120, http://www.vcfed.org/forum/showthrea...estions/page12
                    Are you aware of the incompatibility of the XUB and the IBM 5170 BIOS, See Modem7's site, http://minuszerodegrees.net/xtide/XT...20Problems.htm

                    Comment


                      Originally posted by jasmi View Post
                      ... for U17 & U37 on an IBM 5170 motherboard?
                      Welcome to these forums.

                      As was recently discovered ('rediscovered' is probably more accurate), any BIOS expansion ROM code (such as the XUB) for the IBM 5170's sockets U17/U37 needs to be 64 KB sized.

                      Originally posted by jasmi View Post
                      I'm still researching the best way to properly split the file.
                      A simple Windows utility to create the odd and even components (and go the other way, a merge) is at [here].

                      Comment


                        Originally posted by modem7 View Post
                        As was recently discovered ('rediscovered' is probably more accurate), any BIOS expansion ROM code (such as the XUB) for the IBM 5170's sockets U17/U37 needs to be 64 KB sized.
                        I have added a 'ROM sockets U17 and U37' page to the IBM 5170 section of my web site - see [here].

                        Comment


                          Hi folks.

                          I set about re-building a Cyrix 486DX2-66 machine that's been sitting in my shed for ~20 years, and it was a lot of hit-and-miss as I have almost no parts left over from this era (Why, why did I throw them all out?! Stupid!)

                          The machine basically worked but the smallest working IDE HDD I could find was 8GB - too large for the BIOS on this machine which has the classic 2GB disk limit (Wouldn't even boot if the disk was enabled in BIOS). While researching the problem, I found this project and burnt the EPROM onto a Genius GE2000 (NE2000 clone) network card. It actually worked and I was able to install FreeDOS successfully.

                          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.

                          Comment


                            Anybody unable to change the default boot device from 80h in R601? I can't disassemble the binary beyond what shows up in Hex editor (unless somebody knows an opensource assembly editor they'd recommend), so I don't know why it didn't take the setting properly. My Tandy 1000HX doesn't seem to like anything trying to boot from C (it just hangs there). Might have something to do with the fact that it has DOS 2.11 in ROM, and THAT usually shows up as C: when there's no CF card installed.

                            I was trying to get it go to 18h, like I had in my last flashing. In the absence of a BASIC ROM, just returns an error then boots to the HX menu like the machine normally would. Since the HX has DOS 2.11 in ROM, I don't really need the CF to be bootable anyways. My last flash was with R566, which reads my 16MB Canon card just fine, but doesn't read any of the others I've got, which is why I wanted to upgrade to another build.

                            Also, pressing F8 (ROM Boot) at POST boots to the HX's ROM, getting to the HX menu that I'd prefer to go to anyways. Is there a way to set the XT-IDE BIOS to just default to ROM Boot?
                            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 don't own any Tandy's but changing the default boot device in r601 works fine for me using my IBM XT, I can change to A: or C:. With regards to it "Just hanging when trying to boot from C:" usually means the CF card has not been setup properly. There has been several threads about the HX and XT-IDE in the past, One such thread is here http://www.vcfed.org/forum/showthrea...-Compact-flash it may help.

                              Comment


                                Hmm... I should check to see if I've got the latest version of XTIDECFG.COM. Not sure if it's changed or not since I last downloaded it.

                                I don't THINK that it should make a difference which card I'm using, but it's a PLUS version of the Lotech ISA-CF rev.2 (had to build my own, there wasn't enough space for a PLUS-ISA adapter), but so far as I can tell, the hardware is working fine.

                                I CAN actually read the CF from DOS, and read/write to it without issues. It's just booting from C: that doesn't seem to want to work. I've done DISKPART CLEAN (can't even see the fixed disk otherwise). I'm pretty sure I've done FDISK /MBR and I have done FORMAT /S. I'm not sure if I did it with DOS 3.3 or DOS 6.3 though. Might that make a difference?

                                I'll post on the other thread if I have further issues with booting, they seem to have gotten it working.
                                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