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

    I downloaded the binaries and the Beta 3 works fine. But I wanted to change something, SVNed the sources, compiled them and the result won't recognize the hard disk drive. What can be the problem?

    FYI: the screen says that this is version Beta 3+.

    Kind regards, Ruud Baltissen
    www.Baltissen.org
    With kind regards / met vriendelijke groet, Ruud Baltissen
    www.Baltissen.org

    Comment


      Ppease provide detail about your configuration - controller type, storage device, basically anything relevant.

      Comment


        Originally posted by pearce_jj View Post
        Ppease provide detail about your configuration - controller type, storage device, basically anything relevant.
        I'm using the original XTIDE device, no address lines swapped.
        The error happened with any hard disk I attached 540 MB, 1 Gb, 20 GB, 40 GB
        I SVNed the sources again but that hadn't any effect. AFAIK they were the same as the ones I downloaded two weeks ago.

        But now the big suprise: by accident I burned a BIOS yesterday that I created myself and that one worked fine:

        DEFINES_RUUD = MODULE_HOTKEYS MODULE_BOOT_MENU MODULE_8BIT_IDE MODULE_EBIOS MODULE_VERY_LATE_INITIALIZATION

        To make sure I created IDE_XT.BIN and IDE_RB.BIN just five minutes ago from the same sources: XT fails, RB works fine. But there is a small problem with bigger drives: they are recognized, can format them, but they won't boot. The 1 GB worked fine is more than good enough. Didn't try bigger ones thatvare smaller then 8 GB.

        You are welcome to email me in privat: ruud (-at-) baltissen (-dot-) org

        Kind regards, Ruud Baltissen
        www.Baltissen.org
        With kind regards / met vriendelijke groet, Ruud Baltissen
        www.Baltissen.org

        Comment


          Originally posted by RuudB View Post
          I'm using the original XTIDE device, no address lines swapped.
          The error happened with any hard disk I attached 540 MB, 1 Gb, 20 GB, 40 GB
          I SVNed the sources again but that hadn't any effect. AFAIK they were the same as the ones I downloaded two weeks ago.

          But now the big suprise: by accident I burned a BIOS yesterday that I created myself and that one worked fine:

          DEFINES_RUUD = MODULE_HOTKEYS MODULE_BOOT_MENU MODULE_8BIT_IDE MODULE_EBIOS MODULE_VERY_LATE_INITIALIZATION

          To make sure I created IDE_XT.BIN and IDE_RB.BIN just five minutes ago from the same sources: XT fails, RB works fine. But there is a small problem with bigger drives: they are recognized, can format them, but they won't boot. The 1 GB worked fine is more than good enough. Didn't try bigger ones that are smaller then 8 GB.
          Forgot to mention: I always got "Error 1h!"

          Ruud
          With kind regards / met vriendelijke groet, Ruud Baltissen
          www.Baltissen.org

          Comment


            Originally posted by RuudB View Post
            I'm using the original XTIDE device, no address lines swapped.
            The error happened with any hard disk I attached 540 MB, 1 Gb, 20 GB, 40 GB
            I SVNed the sources again but that hadn't any effect. AFAIK they were the same as the ones I downloaded two weeks ago.

            But now the big suprise: by accident I burned a BIOS yesterday that I created myself and that one worked fine:

            DEFINES_RUUD = MODULE_HOTKEYS MODULE_BOOT_MENU MODULE_8BIT_IDE MODULE_EBIOS MODULE_VERY_LATE_INITIALIZATION

            To make sure I created IDE_XT.BIN and IDE_RB.BIN just five minutes ago from the same sources: XT fails, RB works fine. But there is a small problem with bigger drives: they are recognized, can format them, but they won't boot. The 1 GB worked fine is more than good enough. Didn't try bigger ones that are smaller then 8 GB.
            Forgot to mention: I always got "Error 1h!"

            Ruud
            With kind regards / met vriendelijke groet, Ruud Baltissen
            www.Baltissen.org

            Comment


              I want to help you with this, but it's not at all clear to me what the problem is.

              Generally, any issue you have with the stock build from the current dev tree is very likely related to the late-initialisation module, which is a hack only intended for systems that don't appear to offer option BIOS initialisation in any of the normal ways (like Tandy 1400 laptops, and certain PS/2 systems).

              Re the larger drives boot issue, is it that the system appears to hang after the XTIDE Universal BIOS boot message? It may be that there are 286+ instructions in the boot sector, and in that case wiping out the boot sector (and then re-partitioning and re-formatting) should resolve the issue. I have a utility for this purpose, here.

              Hope that helps!

              Comment


                XT-IDE Rev 1 card i assume, What computer have you got this card in ? the commodore 386 as in post #175 ?


                Originally posted by RuudB View Post
                I'm using the original XTIDE device, no address lines swapped.

                Comment


                  Sorry for the late answers but I must have missed the notifications in one or another way.

                  Originally posted by Malc View Post
                  XT-IDE Rev 1 card i assume, What computer have you got this card in ? the commodore 386 as in post #175 ?
                  No, a XT-clone.

                  But I ran into something else. This minimum configuration I use is:
                  DEFINES_RUUD = MODULE_HOTKEYS MODULE_BOOT_MENU MODULE_8BIT_IDE MODULE_EBIOS MODULE_VERY_LATE_INITIALIZATION
                  Ande this runs fine: it detects my CF card as master at 300h.

                  I wanted to experimant with a CF card so I needed the ADVANCED module. But that would mean I would run out of ROM space. So I added the MODULE_STRINGS_COMPRESSED first. IMHO it should have no effect except a smaller ROM. But when starting up the machine, it found the CF card at 300h as well, but now as slave ???

                  After adding the ADVANCED module it found nothing. That is, it said there was nothing at the master but didn't show the slave anymore.


                  Wanting to post this message, my I fell on James' message regarding the late initialization. I thought to give it a try to remove it. Results:
                  - including the ADVANCED module: same effect
                  - without it: it found the CF card both as master as well as slave.

                  Ill do some more testing today.
                  With kind regards / met vriendelijke groet, Ruud Baltissen
                  www.Baltissen.org

                  Comment


                    Originally posted by RuudB View Post
                    Ill do some more testing today.
                    I did the same tests but with an hard disk drive this time.

                    Minimum configuration: MODULE_HOTKEYS MODULE_BOOT_MENU MODULE_8BIT_IDE MODULE_EBIOS: things work fine.
                    Adding just COMPRESSED: fine as well.
                    Adding just ADVANCED: no HDD is seen. So IMHO here is something wrong. But what?


                    Just some background information:
                    One of the ideas I have is using AT's FDD/IDE cards in a XT. I know, I will only have 8 bits access. While thinking about changing the software, I ran into this 8-bits ISA XT-CF adapter using the Universal BIOS. Now the idea rose to let UB think it is dealing with this XT-CF adapter when in reality it is this FDD/IDE card. The only thing IMHO you have to do is to remove this shifting of the address needed for XT-CF and to tell it to use 01F0h as base address plus adding 200h for the control block. But having a, IMHO, faulty ADVANCED module......
                    With kind regards / met vriendelijke groet, Ruud Baltissen
                    www.Baltissen.org

                    Comment


                      It's already possible to use *some* 16-Bit IDE/Floppy controllers in an 8-bit slot with the XT-IDE Universal Bios and a CF adapter / Card connected. I've had a 16-bit Ide/Floppy controller with CF adapter card working fine in my IBM XT 5160, And append a HD floppy Bios to the XT-IDE Bios and you can use HD Floppy drive.

                      Or am i reading this totally wrong, I've got a stinking cold

                      Originally posted by RuudB View Post
                      Just some background information:
                      One of the ideas I have is using AT's FDD/IDE cards in a XT. I know, I will only have 8 bits access. While thinking about changing the software, I ran into this 8-bits ISA XT-CF adapter using the Universal BIOS. Now the idea rose to let UB think it is dealing with this XT-CF adapter when in reality it is this FDD/IDE card. The only thing IMHO you have to do is to remove this shifting of the address needed for XT-CF and to tell it to use 01F0h as base address plus adding 200h for the control block. But having a, IMHO, faulty ADVANCED module......

                      Comment


                        Hi Ruud!

                        Thanks for the testing and feedback!

                        MODULE_8BIT_IDE_ADVANCED is for the 8 bit IDE controllers capable of using DMA and/or memory mapped I/O; the XT-CF cards, the JR-IDE/ISA card and the Silicon Valley Computer ADP50L card. You don't need it to use Compact Flash media and since you are using the XTIDE v1 card you don't need it at all.

                        When you include *_ADVANCED it is assumed that you are using a XT-CF card (since that is the most common case) so the primary controller is by default set accordingly when building the BIOS (see line 138 in Main.asm). I'm guessing that you forgot to change the controller type to XTIDE v1 with XTIDECFG before flashing? There is also code in the latest revision (r566) that skips detection of slave drives when using a XT-CF controller because before the advent of the Lo-tech ISA CompactFlash board you couldn't use slave drives with the XT-CF class of controllers anyway so trying to detect them was pointless. This will be changed in my next revision btw (whenever that will be).

                        As James said earlier, MODULE_VERY_LATE_INITIALIZATION should not be used unless it is actually needed. There is some kind of problem with it but I don't know what. I will exclude the module from the official builds in the next revision.

                        The problems you had with the 20 GB drive (and other drives) is very likely due to incompatible code in the MBR. If so, the simplest solution is to run fdisk/mbr to fix it.

                        Hope this helps!

                        /Krille
                        Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                        Comment


                          Originally posted by Malc View Post
                          II've had a 16-bit Ide/Floppy controller with CF adapter card working fine in my IBM XT 5160
                          And if I may ask, what changes to UB did you make to make that poassible?

                          And I hope you get well again soon
                          With kind regards / met vriendelijke groet, Ruud Baltissen
                          www.Baltissen.org

                          Comment


                            There is a controller type option, 16-bit controller in 8-bit slot (or similar), that works with many 16-bit ISA controllers when connected to CompactFlash media (or other ATA-2 compatible HDD).

                            Comment


                              Thanks, Just use xtidecfg to configure the Bios and goto " Configure XTIDE Universal Bios / Primary IDE Controller / Device Type and set it to " 16-bit ISA IDE in 8-bit mode "

                              Originally posted by RuudB View Post
                              And if I may ask, what changes to UB did you make to make that poassible?

                              And I hope you get well again soon

                              Comment


                                Originally posted by Malc View Post
                                Thanks, Just use xtidecfg to configure the Bios and goto " Configure XTIDE Universal Bios / Primary IDE Controller / Device Type and set it to " 16-bit ISA IDE in 8-bit mode "
                                I started with the original ide_xt.bin that I extracted from the V3 ZIP file. That one did see my CF card.

                                Next I ran XTIDECFG and changed the device type. The addresses were changed as well. In the file the addresses 51h, 52h, 53h (addresses), 55h (type) and 1FFFh (checksum) were changed.

                                Then I disconnected the HDD cable from my XTIDE rev. 1, connected it to the HDD connector of my FDD/IDE card and the CF was NOT found

                                Am I doing something wrong?
                                With kind regards / met vriendelijke groet, Ruud Baltissen
                                www.Baltissen.org

                                Comment

                                Working...
                                X