Announcement

Collapse

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

XTIDE Universal BIOS

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

    #31
    All XTIDE cards will have this version of the BIOS pre-flashed onto the atmel parts when you receive the card.

    Something I just thought about though: since I will be using my eeprom burner to program them all; I doubt that software write protect will be enabled on your chip after the burner is done. You may have to go in and flash it again and enable WP on the eeprom to get it locked down... (or just don't put the write enable jumper on the card)

    Comment


      #32
      Originally posted by hargle View Post
      since I will be using my eeprom burner to program them all
      Remember to generate the checksum byte. None of the files have checksum byte at the end since configuration program generates it automatically.
      Are you going to flash XT build with default settings?

      Comment


        #33
        so using the config program and then exiting (and saving the file) doesn't generate the checksum? Shouldn't be a problem though, since I burned it onto a couple atmel parts to test it. I'll just read that chip before programming the rest of them.

        The only option I changed from defaults was to *not* use the 1k base memory, since that caused all the Tandy owners to have issues with certain video modes.

        Comment


          #34
          Checksum byte is generated when saving changes to a file and when flashing. There are no checksum bytes on the unmodified files but that doesn't matter since you made changes to default settings.

          XT build should work for everyone. Those XT users with 188, 186, V20, V30 or 286 processor should upgrade to XT+ build for a little faster transfer rates. AT users should upgrade to AT build for 16-bit transfers and OS hooks.

          Comment


            #35
            I've burned approximately 1/2 of the ROMs over the past couple nights, and they work just fine. It even turns out that my burner has support for enabling the software write protect, so all the roms I am doing are protected when they come off the burner. I have not tested that they are actually protected, only that the code burned in worked.

            As soon as I'm finished burning these, I'm ready to ship all the parts to lutiana for kitting, but he's disappeared for the time being...

            Comment


              #36
              The wheels of progress!

              Glorious to behold!

              *rubs hands together in anxious anticipation*

              Thanks for the time and effort Hargle!
              __
              Trevor

              Comment


                #37
                Harddisk recognitation with Multi/IO/RTC-Card not possible

                Hi, Folks!

                My Configuration: XT 8088 Board, 8-bit VGA Graphics Adapter, XTIDE installed BIOS v1.0.0_RC1.

                When I use a original IBM Floppy Controller with 5 1/4" 360k drive, it works fine.

                If I remove the floppy controller and I try to boot without any floppy controller, my HDD couldn't be detected by XTIDE Bios.
                Thats no problem, because I normally use a floppy controller.

                My problem is, I have a Multi-IO Card (COM1, LPT1, Game Port, Floppy Disk and Real Time Clock). I use this card several years now and it works fine. When I replace the old IBM Controller with my "Multi"-Card which I use normally, then the XTIDE Bios don't work correctly any more.

                First boot, BIOS 0x80 detect a drive but the drive name "nec ...." is not displayed or only the last part of the string will be shown. If I make a warm reboot, XTIDE shows the name of die drive correctly, and It says "boot sector found" (or similar) but boot is still not possible.

                I tried to change IO Range and Memory Adress, but the situation is always the same.

                Do you have any idea what I can do in order to use my Multi-RTC card with the XTIDE together?

                Thank you very much for the gread developement!
                quark

                Comment


                  #38
                  Originally posted by quark View Post
                  Hi, Folks!
                  My Configuration: XT 8088 Board, 8-bit VGA Graphics Adapter, XTIDE installed BIOS v1.0.0_RC1.
                  Is it an original IBM or some clone?

                  If I remove the floppy controller and I try to boot without any floppy controller, my HDD couldn't be detected by XTIDE Bios.
                  Are hard disk detection strings and boot menu displayed? If not, then this might be related to late initialization. If no floppy or hard disks are found during POST, main BIOS probably won't ever call boot strap loader to start XTIDE late initialization.


                  First boot, BIOS 0x80 detect a drive but the drive name "nec ...." is not displayed or only the last part of the string will be shown. If I make a warm reboot, XTIDE shows the name of die drive correctly, and It says "boot sector found" (or similar) but boot is still not possible.
                  I tried to change IO Range and Memory Adress, but the situation is always the same.
                  Sounds like a hardware or BIOS conflict.
                  Does the Multi I/O card has BIOS of its own?
                  Can you boot from floppy drive using boot menu?
                  Did you remember to update BIOS configuration when you tried other I/O port? Try port 340h and make sure that both XTIDE card and BIOS are configured properly.

                  Comment


                    #39
                    detailed test results

                    Is it an original IBM or some clone?
                    It is a clone (with 640kb memory onboard, speed 4,77 Mhz or 8,00 MHz).
                    I also own a original IBM mainboard ( 256kb system board without ram extensions) and I make the same tests in this moment.

                    Both mainboards have the same behavior. There is nearly no difference (see detailed test results).

                    Are hard disk detection strings and boot menu displayed? If not, then this might be related to late initialization. If no floppy or hard disks are found during POST, main BIOS probably won't ever call boot strap loader to start XTIDE late initialization.
                    XTIDE boot menu will be displayed all time.

                    My test results:

                    Harddisk: D3755 (NEC 100MB capacity)
                    Operating System: MS-DOS V6.22
                    8-bit VGA-Graphic Adapter

                    Original IBM Floppy Controller (Clone + IBM Board identically
                    floppy boot -> OK
                    hard disk boot -> OK

                    Without any Floppy Controller (Clone + IBM Board identcially)
                    floppy boot -> not possible, no controller installed
                    hard disk boot
                    boot menu displays "D3755" string correctly, message "80h ... boot sector found", next message not in english, translation: "Please insert a system disk". It's seems to be a message from MBR, because its in the language of the operating system.

                    Multi I/O Card with Floppy Controller and RTC
                    floppy boot -> OK
                    hard disk boot
                    ----> Clone-Board: boot menu displays at cold boot a wrong string, missing first characters. displays "5" or "755" it varied. Next message "no valid boot sector". After a warm boot, the string "D3755" is shown correctly, but still "no valid boot sector".
                    ----> IBM-Board: boot menu displays string "D3755" correctly, next "boot sector found" and then the system hang up. (No message from operating system)

                    Does the Multi I/O card has BIOS of its own?
                    No, there is no EEPROM. Just UM8272A, MM58167 (RTC), NS8250N and some logic chips.

                    Can you boot from floppy drive using boot menu?
                    Yes, see test results above.

                    Did you remember to update BIOS configuration when you tried other I/O port? Try port 340h and make sure that both XTIDE card and BIOS are configured properly.
                    Yes I updated BIOS configuration and change dip switches. I verifiy this with booting from HDD with the IBM Controller. I tried 0x300, 0x380 and now 0x340 but the above test results are the same.
                    Last edited by quark; February 12, 2010, 06:02 AM.

                    Comment


                      #40
                      Really strange. Missing characters might indicate that something corrupts data somewhere in 0:800h and above. Not only drive names but POST stack address is also stored there so that might explain why system hangs. It does not explain why clone board doesn't find valid boot sector. Is the drive information correct when the name is only partially displayed?

                      I have a clone XT (8088@8 MHz, 640kB and similar multi I/O card) waiting for new XTIDE card. I'll take the XTIDE from 286 and try it on the XT on sunday. I hope i can reproduce the problem and find a solution.

                      Does anyone know what ports the MM58167 (i have MM58167AN) RTC chip uses?

                      Comment


                        #41
                        I'd think that all RTCs use standard CMOS ports, 70, and 71h.

                        Comment


                          #42
                          Is the drive information correct when the name is only partially displayed?
                          The drive information will be recognized correctly in any case, "only" the device name string (D3755) is corrupt. (And of course, the boot functionallity is missing)

                          Capacity: 99.9 MiB / 100.0 MiB
                          Addr Bus IRQ PIO SpB
                          L-CHS 8 - 0 1

                          Comment


                            #43
                            jeeze. something that old and crusty might be at fault itself. It could easily be a signaling/timing issue.
                            Please try:
                            1) 80 pin cable
                            2) a drive made this century.

                            If the same results, then we can start looking for other things to blame.

                            Comment


                              #44
                              Originally posted by aitotat View Post
                              Does anyone know what ports the MM58167 (i have MM58167AN) RTC chip uses?
                              Because IBM had no RTC card for the PC, designers of cards containing an RTC chip had nothing to follow. So the card designers themselves chose where the ports on the RTC chip mapped to in I/O address space.
                              AST for example, have published details of the I/O space that they chose for their cards. The information is in TB-0052A at http://www.textfiles.com/computers/ASTRESEARCH/.

                              Comment


                                #45
                                jeeze. something that old and crusty might be at fault itself. It could easily be a signaling/timing issue.
                                I use my Multi-IO/Floppy/RTC Controller always in my XT (just removed for testing with XTIDE), so I am beleave that this card itself works without any problems.

                                Please try:
                                1) 80 pin cable
                                2) a drive made this century

                                If the same results, then we can start looking for other things to blame.
                                I will check it.

                                Thanks to all for you advice and help to find the problem.
                                Last edited by quark; February 13, 2010, 04:52 AM.

                                Comment

                                Working...
                                X