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

    You will have to use software to configure the card, Enable the boot rom etc. Download 3c509x2.exe from [ Here ] and extract the contents, Put 3C5X9CFG on a DOS boot floppy and run it on your 5170 and hopefully it will find your card and you can configure it.

    Comment


      Does anyone have ant information on this YouTube video?
      https://www.youtube.com/watch?v=8qpP...ature=youtu.be

      I have the same XT-CF card by Lo-tech and the video gives the impression that Kiselev's FDC 2.2 was combined with the XT-IDE to now give 1.44 mb access to the old 8080 bios.

      I have tried attaching them together and loading to the card in a few ways. I get the FDC config menu, but it won't write it to the EEPROM. After that it will boot normally to the XT-IDE but with no floppy access at all.

      Comment


        Originally posted by Theoisle View Post
        ...I have tried attaching them together and loading to the card in a few ways. I get the FDC config menu, but it won't write it to the EEPROM. After that it will boot normally to the XT-IDE but with no floppy access at all.
        It won't write to the EEPROM because the FDC config utility does not support the EEPROM used in the Lo-Tech card, Configure the bios first and then flash the EEPROM or use a different FDC Bios.

        Comment


          Using the FDC 2.2 documentation I found the configuration settings at the end of the file. I was able to edit the file and figure the checksum, but was only able to get it to work for 720 kb floppy disks. 1.44 MB will ot work at all on this Compaq Portable model 101709 8080. I suppose that the floppy controller is the limitation there. The next project is to build a new FDC. So far the lo-tech XT-CF and this fdC patch allows access to a A: 360 kb, B: 720 kb and C: 30 MB CF card, which is mounted by the expansion slots so I can easily pop in whatever OS, that I want o experiment with.

          Comment


            Ok, I have the XT-IDE Universal BIOS on an Atmel 28C256 ROM chip. It works in a generic nic that I have, but I am trying to swap that card out with a 3Com 3C509B card. But I cannot get the XT-IDE bios to load. I have the card set to use D000 - D3FFF, which is matches the other card. But even with the chip installed the 3Com config utility complains about no PROM installed or a conflict (neither is true). And when the system starts it does not load the XT-IDE at all.

            So any ideas on what I am doing wrong here? I did try setting the PROM chip size to 32K, and then 16K, neither worked.

            IBM 5160 - 360k, 1.44Mb Floppies, NEC V20, 8087-3, 45MB MFM Hard Drive, Vega 7 Graphics, IBM 5154 Monitor running MS-DOS 5.00
            IBM PCJr Model 48360 640kb RAM, NEC V20,, jrIDE Side Cart, 360kb Floppy drives running MS-DOS 5.00
            Evergreen Am5x86-133 64Mb Ram, 8gb HDD, SB16 in a modified ATX case running IBM PC-DOS 7.10

            Comment


              Is the I/O base address for the 3C509B the same as the other nic ?, If you change the I/O base address you must reconfigure the XUB and re-flash, It might be though that the 3C509B is not compatible with the Atmel 28C256 EEPROM, Can you burn a 27x EPROM and try that, Have you used that 3C509B before and know it's working corectly.

              Comment


                Originally posted by Malc View Post
                Is the I/O base address for the 3C509B the same as the other nic ?, If you change the I/O base address you must reconfigure the XUB and re-flash, It might be though that the 3C509B is not compatible with the Atmel 28C256 EEPROM, Can you burn a 27x EPROM and try that, Have you used that 3C509B before and know it's working corectly.
                I did set the I/O address to be the same (D0000) as the other nic. And the 3c509b does work just fine. I was using it last night to connect to our IRC channel. What is a 27x EPROM?

                Is it possible to use the XUB in one of the optional ROM sockets on the 5170 motherboard?

                IBM 5160 - 360k, 1.44Mb Floppies, NEC V20, 8087-3, 45MB MFM Hard Drive, Vega 7 Graphics, IBM 5154 Monitor running MS-DOS 5.00
                IBM PCJr Model 48360 640kb RAM, NEC V20,, jrIDE Side Cart, 360kb Floppy drives running MS-DOS 5.00
                Evergreen Am5x86-133 64Mb Ram, 8gb HDD, SB16 in a modified ATX case running IBM PC-DOS 7.10

                Comment


                  Not the ROM address, The base I/O address for the 3C509B ie: 300h etc. 27x = 2764 - 27C64 / 27128 - 27C128 / 27256 - 27C256 EPROMs, I've never tried anything in those optional ROM sockets myself.

                  Comment


                    Originally posted by Malc View Post
                    Not the ROM address, The base I/O address for the 3C509B ie: 300h etc. 27x = 2764 - 27C64 / 27128 - 27C128 / 27256 - 27C256 EPROMs, I've never tried anything in those optional ROM sockets myself.
                    It was the same. But I also tried a few different I/O addresses on the other NIC without re-flashing and it did not affect the XUB functions at all, and I did try a few different I/O address on the 3com. It seem to ignore the ROM all together. Right now the 3com is set to 280h and the other is 300h, originally the first nic was set to 280h.


                    I don't think I have any 27x Roms to try, what is the difference between a 28x and a 27x PROM?


                    EDIT: Found this in the technical reference for the EhterlinkIII cards. Any info here that might explain the issue?

                    CMOS EEPROM Support
                    The 3C509B supports the use of CMOS EEPROM for the boot ROM. Such boor ROMS work exactly the same as the previous version of the boor ROMs, but can be updated if desired. This allows updatable boot ROMs to be built for the 3C509B at a much lower production cost than for the 3C509.

                    Changed ROM Support
                    The 3C509B changes the ROM support in a variety of ways; full decode of the ROM address allows the use of real 8 K or 16 K parts if desired (rather than 32 K parts with multiple copies of the 8 K or 16 K images), support for 64 K parts, and support for switching 16 K windows into any part larger than 16 K. It is no longer possible to use a 32 K part without window switching.
                    Last edited by lutiana; June 18, 2017, 02:42 PM.

                    IBM 5160 - 360k, 1.44Mb Floppies, NEC V20, 8087-3, 45MB MFM Hard Drive, Vega 7 Graphics, IBM 5154 Monitor running MS-DOS 5.00
                    IBM PCJr Model 48360 640kb RAM, NEC V20,, jrIDE Side Cart, 360kb Floppy drives running MS-DOS 5.00
                    Evergreen Am5x86-133 64Mb Ram, 8gb HDD, SB16 in a modified ATX case running IBM PC-DOS 7.10

                    Comment


                      28x are EEPROMS which can be erased / flashed in the XT-IDE cards using XTIDECFG.COM, 27x are Eproms which are programmed in a Prom Programmer. I suspect that the 3C509B is not compatible with the Atmel EEPROM 28C256, I don't have any i could try though.

                      Comment


                        Originally posted by Malc View Post
                        28x are EEPROMS which can be erased / flashed in the XT-IDE cards using XTIDECFG.COM, 27x are Eproms which are programmed in a Prom Programmer. I suspect that the 3C509B is not compatible with the Atmel EEPROM 28C256, I don't have any i could try though.
                        See my edit from the last post, but the technical reference specifically calls out the chips as CMOS EEPROMs, so I am really not sure if that makes a difference or not.

                        IBM 5160 - 360k, 1.44Mb Floppies, NEC V20, 8087-3, 45MB MFM Hard Drive, Vega 7 Graphics, IBM 5154 Monitor running MS-DOS 5.00
                        IBM PCJr Model 48360 640kb RAM, NEC V20,, jrIDE Side Cart, 360kb Floppy drives running MS-DOS 5.00
                        Evergreen Am5x86-133 64Mb Ram, 8gb HDD, SB16 in a modified ATX case running IBM PC-DOS 7.10

                        Comment


                          Originally posted by Malc View Post
                          Is the I/O base address for the 3C509B the same as the other nic ?, If you change the I/O base address you must reconfigure the XUB and re-flash
                          Sorry Malc but this is incorrect. XUB doesn't need to know the I/O address of the NIC it's on, only the I/O address of the IDE interface(s), otherwise it wouldn't be able to communicate with the harddrive(s).

                          Originally posted by lutiana View Post
                          Is it possible to use the XUB in one of the optional ROM sockets on the 5170 motherboard?
                          It depends on what address range the XUB will end up in and if the system BIOS will scan for option ROMs in that area. You might have to mod the system BIOS slightly if it doesn't scan high enough in the UMA.

                          BTW, are you aware of the incompatibility between the IBM system BIOS (all three versions) and the XUB? You will need to use some other system BIOS than the original IBM BIOS.

                          Originally posted by lutiana View Post
                          EDIT: Found this in the technical reference for the EhterlinkIII cards. Any info here that might explain the issue?
                          Try filling the ROM with copies of XUB. For example, if the ROM window (and the XUB) is 8 KB, then try writing 4 copies of the BIOS to one file and flash that to the ROM;
                          Code:
                          copy/b xub.bin+xub.bin+xub.bin+xub.bin result.bin
                          Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                          Comment


                            Originally posted by Krille View Post
                            Sorry Malc but this is incorrect. XUB doesn't need to know the I/O address of the NIC it's on, only the I/O address of the IDE interface(s), otherwise it wouldn't be able to communicate with the harddrive(s).
                            Yeah i realized that a while after i posted that it didn't matter on the nic.

                            Comment


                              [QUOTE=Krille;465125]Sorry Malc but this is incorrect. XUB doesn't need to know the I/O address of the NIC it's on, only the I/O address of the IDE interface(s), otherwise it wouldn't be able to communicate with the harddrive(s).
                              [QUOTE=Krille;465125]

                              Yeah, I figured this was the case as I've been shifting the address around a fair bit with my testing.


                              Originally posted by Krille View Post
                              It depends on what address range the XUB will end up in and if the system BIOS will scan for option ROMs in that area. You might have to mod the system BIOS slightly if it doesn't scan high enough in the UMA.

                              BTW, are you aware of the incompatibility between the IBM system BIOS (all three versions) and the XUB? You will need to use some other system BIOS than the original IBM BIOS.
                              Yes. I am running the AMI BIOS in the system. What is the best way to determine if the BIOS can do this? Just plug the EERPOM into the socket and see what happens?

                              Originally posted by Krille View Post
                              Try filling the ROM with copies of XUB. For example, if the ROM window (and the XUB) is 8 KB, then try writing 4 copies of the BIOS to one file and flash that to the ROM;
                              Code:
                              copy/b xub.bin+xub.bin+xub.bin+xub.bin result.bin

                              After some chatting in the IRC channel someone pointed out the pin differences between the 28C256 and the 27C256 and suggested I run pin 1 on the chip to pin 27 on the socket, then run pin 27 on the chip over to pin 28 on the chip (to disable WE). I jerry rigged this to test it and it worked perfectly. So now I just need work out how to make this change temporary enough that I can undo it in the event I need to update or change XUB.

                              IBM 5160 - 360k, 1.44Mb Floppies, NEC V20, 8087-3, 45MB MFM Hard Drive, Vega 7 Graphics, IBM 5154 Monitor running MS-DOS 5.00
                              IBM PCJr Model 48360 640kb RAM, NEC V20,, jrIDE Side Cart, 360kb Floppy drives running MS-DOS 5.00
                              Evergreen Am5x86-133 64Mb Ram, 8gb HDD, SB16 in a modified ATX case running IBM PC-DOS 7.10

                              Comment


                                The schematic I saw has a switch line for the write enable.
                                Just turn off the signal to the WE\. It should have a pullup resistor.
                                It will disable writes.
                                Dwight

                                Comment

                                Working...
                                X