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

Anyone Selling XT-IDE Cards?

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

    giobbi Use a long 32K BIOS version 'IDE_XTL.BIN' and configure it with XTIDECFG.COM as modem7 suggested (and set jumpers for 27256). 'Short' 8K version has no MODULE_BOOT_MENU module.

    I have two negative reports about coexistence with MFM BIOS-es. One controller was a DTC-51xx. The symptom was as you described: both controllers work single well but does not boot together. Jumper setting was correct: 320/C800 for MFM controller and 300/D000 for XT IDE.

    Comment


      I solved flashing with xtidecfg.com and 1.15 rel.; now it's working fine, it appears the menu as shown by modem7, and I can choose to boot from MFM or IDE.

      The other two releases, 2.00 beta 3 and 591 doesn't work for me. So I agree with Glitch's decision to supply programmed eeprom with the stable release.

      What I don't understand is why it was booting with the 2.00 beta 3 release, even with limitations (no menu, etc.) and it stopped suddenly to work, returning ROM ERR. No changes were made to the eeprom content or the MFM config.

      I haven't a spare 27256: I should erase one from another project to do the test alecv suggested, and the 8k version is enough for me, so I will stop here; at least everything is working fine and I have no time for further debug for now!

      BTW Are 27512 pin to pin compatible with 27256? In other words, can I use a 27512 instead of 27256, programming the lower half and use it in the XT-IDE like a 27256?

      Thank you for your help!

      Comment


        Originally posted by alecv View Post
        I have two negative reports about coexistence with MFM BIOS-es. One controller was a DTC-51xx. The symptom was as you described: both controllers work single well but does not boot together. Jumper setting was correct: 320/C800 for MFM controller and 300/D000 for XT IDE.
        I solved that problem using the 1.15 stable release.

        Comment


          Originally posted by modem7 View Post
          Are you aware that this requires two changes:
          1. Change of the two jumpers on the XT-IDE Rev 3 card; and
          2. Reconfigure the XTIDE Universal BIOS

          I knew about the two jumpers, but I didn't know about reconfiguring the BIOS. Maybe it was explained in a previous post? I read the whole thread, but maybe I miss it...

          Can you explain how to do?

          Comment


            Originally posted by giobbi View Post
            BTW Are 27512 pin to pin compatible with 27256 ?
            Edited

            http://www.z80.info/gfx/eprom.gif
            http://www.s100computers.com/My%20Sy...OM%20Board.htm

            28c256: 1=A14, 27=WE (as traced on the AT-IDE v3 PCB)
            27c256: 1=unused, 27=A14
            27c512: 1=A15, 27=A14

            To use 27512 in the 28c256 socket just connect A15 of the 27c512 (pin 1) to GND and A14 (pin27 of chip) to A14 (pin 1 of socket), and write a first half of 27512 with 256 image.

            What MFM controller do you use ? I have positive report with r591 and WD MFM controller (unknown model).
            Last edited by alecv; August 20, 2016, 09:27 AM.

            Comment


              Originally posted by giobbi View Post
              I knew about the two jumpers, but I didn't know about reconfiguring the BIOS. Maybe it was explained in a previous post? I read the whole thread, but maybe I miss it...
              The Compatibility/Hi-Speed jumpers change which register map is used (hardware).
              The XTIDE Universal BIOS (software) needs to know which map is in use.

              More technical information about that is at [here].

              Originally posted by giobbi View Post
              Can you explain how to do?
              You are using version 1.1.5 of the XTIDE Universal BIOS. It does not 'know' about hi-speed mode.

              To use hi-speed mode, you would either have to:
              * Upgrade to a 2.x.x version of the XTIDE Universal BIOS; or
              * Find the hacked 1.x.x version of the XTIDE Universal BIOS (hacked for hi-speed mode).

              Comment


                Apparently people are having trouble finding the XUB 1.1.5 ZIP file, so I've uploaded it here:

                ftp://filedump.glitchwrks.com/xt_ide/bios/xub_1.1.5.zip (FTP)
                http://filedump.glitchwrks.com/xt_id.../xub_1.1.5.zip (HTTP)
                Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

                Comment


                  Originally posted by glitch View Post
                  Apparently people are having trouble finding the XUB 1.1.5 ZIP file, so I've uploaded it here:

                  ftp://filedump.glitchwrks.com/xt_ide/bios/xub_1.1.5.zip (FTP)
                  http://filedump.glitchwrks.com/xt_id.../xub_1.1.5.zip (HTTP)

                  is it the hi-speed hacking?

                  Comment


                    Originally posted by glitch View Post
                    Apparently people are having trouble finding the XUB 1.1.5
                    Why would anyone intentionally run the older version? Doesn't 2.x have all of the features and more?
                    Offering a bounty for:
                    - A working Sanyo MBC-775 or Logabax 1600
                    - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

                    Comment


                      Originally posted by alecv View Post
                      I have two negative reports about coexistence with MFM BIOS-es. One controller was a DTC-51xx. The symptom was as you described: both controllers work single well but does not boot together. Jumper setting was correct: 320/C800 for MFM controller and 300/D000 for XT IDE.
                      A common problem with a lot of old controllers is that they expect to be the only harddrive controller in the system and so they don't play nicely with any other controllers*. I've been trying to come up with a way to fix this and one possibility might be to restore the total harddrive count (at 0:475h) to what they expect before calling the previous handler in the Int13h chain.

                      * If they play nicely at all. I'm currently looking at this MFM controller BIOS in IDA and not only is it using the total harddrive count in 'unusual' ways, it's also playing games with the BIOS timer ticks since midnight counter (at 0:46Ch), overwriting it willy nilly. It's no wonder why people, during the '80s, thought of buying hardware (or software for that matter) as playing the lottery as far as compatibility goes.

                      Originally posted by modem7 View Post
                      More technical information about that is at [here].


                      You are using version 1.1.5 of the XTIDE Universal BIOS. It does not 'know' about hi-speed mode.

                      To use hi-speed mode, you would either have to:
                      * Upgrade to a 2.x.x version of the XTIDE Universal BIOS; or
                      * Find the hacked 1.x.x version of the XTIDE Universal BIOS (hacked for hi-speed mode).
                      The 'hacked' version was actually hargle's BIOS modified by Chuck, not XUB 1.1.5. You might want to revise that image.

                      Originally posted by Trixter View Post
                      Why would anyone intentionally run the older version?
                      I keep asking myself the same question.
                      Last edited by Krille; August 21, 2016, 03:56 PM. Reason: Typo...
                      Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                      Comment


                        Originally posted by Trixter View Post
                        Why would anyone intentionally run the older version? Doesn't 2.x have all of the features and more?
                        The 2.x version apparently hasn't the boot menu and if I press F8 it simply boot from A: instead of C:
                        IMG_20160820_001644.jpg

                        the 1.5 version shows a boot menu with all the options, including "foreign HDD" and your IDE device.
                        I'm not sure if I went wrong or not; I simply tried the xt_ide.bin of both releases.

                        Maybe it's because it's not detecting the DOM at 300H address; but using the 1.5 rel., it's detected without problem.
                        Last edited by giobbi; August 21, 2016, 04:13 PM.

                        Comment


                          giobbi You could recompile xtideuniversal BIOS 2.0.0 as you wish modifying 'makefile' and adding or removing modules. As an example you can add BOOT_MENU module and remove SERIAL_FLOPPY. The resulting binary fits into 8Kb. Otherwise you can add maximum set of modules and use 'long' 32k version and 28c256 chip.

                          Comment


                            Personally, I'm not willing to ship assembled cards with the 2 series BIOS since they're still marked "beta" -- if the author is still calling it beta, that makes it not ready for general use, in my mind. Don't like it? Remove the beta designation

                            Secondly, there's no preconfigured image that fits in 8K with a boot menu. While I and presumably other hobbyists can certainly build our own with the provided source + makefile, I bet there are a lot of people who can't or don't want to try and build their own BIOS image to get it down to 8K. Perhaps make an 8K version with boot menu and no serial disk/floppy support officially available?

                            Third, it's actually kind of hard to figure out what you're supposed to be downloading and/or running w.r.t. the 2.0 XUB. A Google search brings up the Lo-Tech Wiki, then the "official" site (xtideuniversalbios.org) a bit lower down. Of course, the Lo-Tech Wiki still references the Google Code site. The downloads are non-obvious on xtideuniversalbios.org and the source browser seems like an early 2000's CGI for browsing SVN. Considering the Google Code site has handy "Export to GitHub" buttons all over the place, they may be trying to tell you something I'm a programmer and hardware engineer for my day-job and I find it difficult to navigate, so I'm betting other people do too.

                            Just to be clear, I'm not trying to put down anyone's work -- thanks for everyone who works on this project, be it hardware or software! These are just the reasons I'm still shipping XUB 1.1.5 and why I think others might have difficulty in working with the 2.x series.
                            Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

                            Comment


                              glitch I've made r591 with BOOT_MENU for PCem project. This emulator emulates presence of "standart mode" (a.k.a "v1") XT-IDE hardware at 300H and uses _real_ BIOS image.

                              http://pcem-emulator.co.uk/phpBB3/vi....php?f=2&t=523

                              It is possible to reconfigure it for "hi speed" mode using XTIDECFG.COM.
                              Last edited by alecv; August 22, 2016, 07:30 AM.

                              Comment


                                Finally got time to write up a Bill of Materials:

                                https://github.com/glitchwrks/xt_ide...f_materials.md

                                That includes Mouser part numbers. If someone wants to add Digi-Key part numbers and send a pull request (or contact me if you don't use GitHub) I'll add it in.
                                Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

                                Comment

                                Working...
                                X