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

Tandy 1000 RLX and XT-IDE V3

  • Filter
  • Time
  • Show
Clear All
new posts

    Tandy 1000 RLX and XT-IDE V3

    Just got a brand spanking new XT IDE V3 in the mail today (wow, that's a nicely done card!) and am trying to get it working with my Tandy 1000 RLX. The RLX has the XT-IDE 40MB drive currently installed.

    To get the card to show up in the BIOS screen, I had to set it to CE000 (per It shows up, and I see four choices; floppy, 80h, 81h (which I'm assuming are the Tandy's hard disk and ROM drive), the CompactFlash 4GB card I put in, and the ROM BIOS boot option.

    I was able to boot from the Tandy's normal drive (running Tandy MSDOS 5) and fdisk the CompactFlash into two 2GB partitions (E:\ and F:\), and then XCopy the C:\ drive over to E:\ just fine.

    Now, here's the fun part. When I disconnect the built in Tandy 40MB drive, the XT IDE BIOS screen no longer shows up, and so it doesn't even scan the BIOS for the option ROM for the card. I've tried running SetupRLX and making sure boot is set to disk, that's fine. However, this stinking RLX still boots to an A> prompt with the XT IDE connected and the Tandy HDD disconnected.

    I reconnect the Tandy 40MB disk and it shows the XT IDE BIOS again. Obviously, it's not gonna let me boot off the CF with another active disk in the system.

    How do I get around this?

    There's an interesting thing. We had problems getting the XUB initialising with the Tandy 1400 laptop, perhaps the two issues are related.

    You could try the special 'very late initialisation' code from here, though it will need to be configured for the particular card that you're using as you write it to the ROM.


      Originally posted by acadiel View Post
      How do I get around this?
      Don't know if this helps, but I have one of James' ISA CompactFlash boards working fine in a TL/2. It's set up at CC00h and I don't have anything connected to the built-in IDE adapter.


        As bjt mentioned, you might try a lower ROM address with nothing connected to the Tandy's disk controller.
        Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More


          Originally posted by glitch View Post
          As bjt mentioned, you might try a lower ROM address with nothing connected to the Tandy's disk controller.
          Without anything hooked to the internal connector (the 40MB drive):

          C8000 0100 - get ROM A>, no XTIDE BIOS popup
          CA000 0101 - get ROM A>, same
          CC000 0110 - get ROM A>, same
          CE000 0111 - get ROM A>, same
          D0000 1000 - get ROM A>, same
          D2000 1001 - get ROM A>, same
          D4000 1010 - get ROM A>, same
          D6000 1011 - get ROM A>, same
          D8000 1100 - get ROM A>, same
          DA000 1101 - get ROM A>, same
          DC000 1110 - get ROM A>, same
          DE000 1111 - get ROM A>, same

          With the 40MB HDD enabled:

          C8000 0100 - no BIOS hook
          CA000 0101 - no BIOS hook
          CC000 0110 - get the XTIDE BIOS hook
          CE000 0111 - get the XTIDE BIOS hook
          D0000 1000 - get the XTIDE BIOS Hook
          D2000 1001 - get the XTIDE BIOS Hook
          D4000 1010 - get the XTIDE BIOS Hook
          D6000 1011 - get the XTIDE BIOS Hook
          D8000 1100 - get the XTIDE BIOS Hook
          DA000 1101 - get the XTIDE BIOS Hook
          DC000 1110 - get the XTIDE BIOS Hook
          DE000 1111 - get the XTIDE BIOS Hook


            Did you try the special bios?


              Originally posted by bjt View Post
              Don't know if this helps, but I have one of James' ISA CompactFlash boards working fine in a TL/2. It's set up at CC00h and I don't have anything connected to the built-in IDE adapter.
              The RL series have weird issues with the xt-ide devices. I had a similar problem with my non-X RL Hard Drive box.

              The bios James listed with "very late initialisation code" was necessary to get the xt-ide working on my RL.


                I'll flash the BIOS that was earlier mentioned in the thread that does late initialization.

                Any caveats or quick 'how to' on how to do it? The read me in the file isn't very forthcoming.


                  Run XTIDECFG, load the .bin, select controller type and IO base address, then write to flash.


                    Just some updates.

                    Got the late start BIOS installed.

                    Glitch's XT IDE card is set to 300h (default) for address. Right now, set to CC00h for the base address of the ROM. Booted Tandy from internal 40MB hard drive (or from floppy) and it puts up the A>>FDD [A], C>>HDD [C], F6 ComDtct, and F8 RomBoot prompt up.

                    Scan shows my Sandisk 4GB drive. Drive shows up as two partitions, D and E. Files are there.

                    So far so good. Ran the XTIDECXFG program, loaded the BIOS from the EEPROM to make sure everything is up to snuff. Autoconfigure finds one controller, so I know we're good there.

                    Problems worked around after the flash:

                    1) FDISK under MS DOS 5 does not show the partitions on the Sandisk device, which I previously created, even though the drives showed up in DOS. Solution, repartitioned disk and copied everything over again with XCopy. I now have a 2GB D:\ and a ~2GB E:\.

                    Problems can't work around:

                    1) ROM Disk is missing. Can't run Deskmate. Tried F:\ and beyond. No dice. When the XT IDE is in the picture as active, no ROM drive. (Tested by turning the enable ROM jumper off and rebooting.)
                    2) When I remove the Tandy 40MB drive from the picture, the XT IDE BIOS does not show up and does not boot the system still. Tried a whole bunch of different base ROM addresses.


                      If drive letters D: and E: points to your Sandisk device, what device is C

                      I'd like to take a look at the system BIOS in this machine. Can you please post a dump of it?
                      Looking for a cache card for the "ICL ErgoPRO C4/66d V"


                        Originally posted by Krille View Post
                        If drive letters D: and E: points to your Sandisk device, what device is C

                        I'd like to take a look at the system BIOS in this machine. Can you please post a dump of it?
                        c:\ is the 40MB XT IDE drive that came with the system. If you remove it, the XTIDE doesn't initialize. Very strange.

                        How can I properly dump the BIOS? Any utils you recommend?



                          Originally posted by acadiel View Post
                          How can I properly dump the BIOS? Any utils you recommend?
                          Try PCJRCART with "-dumpROM -noheaders" as command line options.
                          Looking for a cache card for the "ICL ErgoPRO C4/66d V"


                            Here you go



                              I just picked up a RLX; once it's delivered I'll see what my xt-ide does...