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 v2.0.0 beta testing thread

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

    #61
    Originally posted by dabone View Post
    The sector issue that you noticed seem to be a error from the bios I was using, the original oprom from the chuckg thread about modifing the xtide.
    That BIOS is a mod based on Hargle's BIOS which doesn't support CHS addressing so that's probably why.

    Block mode : Set to 0 from max 1 sectors
    PIO mode : Max 1, Min cycle times: 383 ns, with IORDY -1 ns
    More odd looking stuff right there.

    Hope this helps in some way, and thank you very very much for your hard work.
    It does, and thank you for the kind words!
    Looking for a cache card for the "ICL ErgoPRO C4/66d V"

    Comment


      #62
      Originally posted by dabone View Post
      but 441 and on do not.
      This helps very much. r441 has ATA ID validation. The idea is to ignore drives that cannot identify without transfer errors. ATA-5 and later have checksum at the end of ID sector that makes the validation easy. Simpler method is used for ATA-4 and older: P-CHS-parameters must be in valid range (1...16383 Cylinders, 1...16 Heads and 1...63 Sectors Per Track).

      It seems P-CHS parameters are correct so it must be the checksum that is causing problem. I suspect that your drive is detected as ATA-5 or later but it does not have checksum byte at the end of ID sector. Can you dump the ID sector (you can use IDentify Device utility from XTIDE Debugging Utilities) so I can see if that is the case?

      Comment


        #63
        I used the IDentify Device utility on the 64mb, 512mb and 2gb cards.
        The 64 and 512 don't work with the 441 and up, but the 2 gb does.
        But all of the cards just returned 8080 over and over again. Like this.

        The card I'm currently using to test is a XTIDE Rev 1 with the chuck mod.

        0000:8080 8080 8080 8080 8080 8080 8080 8080
        0008:8080 8080 8080 8080 8080 8080 8080 8080
        0016:8080 8080 8080 8080 8080 8080 8080 8080
        0024:8080 8080 8080 8080 8080 8080 8080 8080
        0032:8080 8080 8080 8080 8080 8080 8080 8080
        0040:8080 8080 8080 8080 8080 8080 8080 8080
        0048:8080 8080 8080 8080 8080 8080 8080 8080
        0056:8080 8080 8080 8080 8080 8080 8080 8080
        0064:8080 8080 8080 8080 8080 8080 8080 8080
        0072:8080 8080 8080 8080 8080 8080 8080 8080
        0080:8080 8080 8080 8080 8080 8080 8080 8080
        0088:8080 8080 8080 8080 8080 8080 8080 8080
        0096:8080 8080 8080 8080 8080 8080 8080 8080
        0104:8080 8080 8080 8080 8080 8080 8080 8080
        0112:8080 8080 8080 8080 8080 8080 8080 8080
        0120:8080 8080 8080 8080 8080 8080 8080 8080
        0128:8080 8080 8080 8080 8080 8080 8080 8080
        0136:8080 8080 8080 8080 8080 8080 8080 8080
        0144:8080 8080 8080 8080 8080 8080 8080 8080
        0152:8080 8080 8080 8080 8080 8080 8080 8080
        0160:8080 8080 8080 8080 8080 8080 8080 8080
        0168:8080 8080 8080 8080 8080 8080 8080 8080
        0176:8080 8080 8080 8080 8080 8080 8080 8080
        0184:8080 8080 8080 8080 8080 8080 8080 8080
        0192:8080 8080 8080 8080 8080 8080 8080 8080
        0200:8080 8080 8080 8080 8080 8080 8080 8080
        0208:8080 8080 8080 8080 8080 8080 8080 8080
        0216:8080 8080 8080 8080 8080 8080 8080 8080
        0224:8080 8080 8080 8080 8080 8080 8080 8080
        0232:8080 8080 8080 8080 8080 8080 8080 8080
        0240:8080 8080 8080 8080 8080 8080 8080 8080
        0248:8080 8080 8080 8080 8080 8080 8080 8080
        It's the same for all the cards.

        Later,
        dabone
        Last edited by dabone; December 4, 2012, 05:03 PM.

        Comment


          #64
          I took a quick peek at that util in a disassembler and it looks like the I/O base address is assumed to be at 300h. Also, it probably doesn't support the "chuck mod" (which is likely the reason it fails).
          Looking for a cache card for the "ICL ErgoPRO C4/66d V"

          Comment


            #65
            Ok, Mod's undone and here are the results.

            64MB

            0000:848A 01EA 0000 0008 0000 0240 0020 0001
            0008:EA00 0000 2020 2020 2020 2020 2030 3832
            0016:3230 3132 3039 3830 0002 0002 0004 5664
            0024:6720 312E 3138 5361 6E44 6973 6B20 5344
            0032:4346 422D 3634 2020 2020 2020 2020 2020
            0040:2020 2020 2020 2020 2020 2020 2020 0001
            0048:0000 0200 0000 0100 0000 0001 01EA 0008
            0056:0020 EA00 0001 0100 EA00 0001 0000 0000
            0064:0000 0000 0000 0000 0000 0000 0000 0000
            0072:0000 0000 0000 0000 0000 0000 0000 0000
            0080:0000 0000 0000 0000 0000 0000 0000 0000
            0088:0000 0000 0000 0000 0000 0000 0000 0000
            0096:0000 0000 0000 0000 0000 0000 0000 0000
            0104:0000 0000 0000 0000 0000 0000 0000 0000
            0112:0000 0000 0000 0000 0000 0000 0000 0000
            0120:0000 0000 0000 0000 0000 0000 0000 0000
            0128:0000 0000 0000 0000 0000 0000 0000 2020
            0136:2020 2020 2020 2020 2020 2030 3832 3230
            0144:3132 3039 3830 0000 0000 0000 0000 0000
            0152:0000 0000 0000 0000 0000 0000 0000 0000
            0160:0000 0000 0000 0000 0000 0000 0000 0000
            0168:0000 0000 0000 0000 0000 0000 0000 0000
            0176:0000 0000 0000 0000 0000 0000 0000 0000
            0184:0000 0000 0000 0000 0000 0000 0000 0000
            0192:0000 0000 0000 0000 0000 0000 0000 0000
            0200:0000 0000 0000 0000 0000 0000 0000 0000
            0208:0000 0000 0000 0000 0000 0000 0000 0000
            0216:0000 0000 0000 0000 0000 0000 0000 0000
            0224:0000 0000 0000 0000 0000 0000 0000 0000
            0232:0000 0000 0000 0000 0000 0000 0000 0000
            0240:0000 0000 0000 0000 0000 0000 0000 0000
            0248:0000 0000 0000 0000 0000 0000 0000 0000
            512MB

            0000:848A 03E1 0000 0010 0000 0240 003F 000F
            0008:45F0 0000 2020 2020 3031 3230 3031 4231
            0016:3530 3257 3039 3432 0002 0002 0004 4844
            0024:5820 322E 3231 5361 6E44 6973 6B20 5344
            0032:4346 422D 3531 3220 2020 2020 2020 2020
            0040:2020 2020 2020 2020 2020 2020 2020 0001
            0048:0000 0300 0000 0200 0000 0003 03E1 0010
            0056:003F 45F0 000F 0101 45F0 000F 0000 0407
            0064:0003 0078 0078 0078 0078 0000 0000 0000
            0072:0000 0000 0000 0000 0000 0000 0000 0000
            0080:0400 0000 0000 0000 0000 0000 0000 0000
            0088:0000 0000 0000 0000 0000 0000 0000 0000
            0096:0000 0000 0000 0000 0000 0000 0000 0000
            0104:0000 0000 0000 0000 0000 0000 0000 0000
            0112:0000 0000 0000 0000 0000 0000 0000 0000
            0120:0000 0000 0000 0000 0000 0000 0000 0000
            0128:0000 0000 0000 0000 0000 0000 0000 0000
            0136:0000 0000 0000 0000 0000 0000 0000 0000
            0144:0000 0000 0000 0000 0000 0000 0000 0000
            0152:0000 0000 0000 0000 0000 0000 0000 0000
            0160:0000 0000 0000 0000 0000 0000 0000 0000
            0168:0000 0000 0000 0000 0000 0000 0000 0000
            0176:0000 0000 0000 0000 0000 0000 0000 0000
            0184:0000 0000 0000 0000 0000 0000 0000 0000
            0192:0000 0000 0000 0000 0000 0000 0000 0000
            0200:0000 0000 0000 0000 0000 0000 0000 0000
            0208:0000 0000 0000 0000 0000 0000 0000 0000
            0216:0000 0000 0000 0000 0000 0000 0000 0000
            0224:0000 0000 0000 0000 0000 0000 0000 0000
            0232:0000 0000 0000 0000 0000 0000 0000 0000
            0240:0000 0000 0000 0000 0000 0000 0000 0000
            0248:0000 0000 0000 0000 0000 0000 0000 0000
            2GB

            0000:848A 0F82 0000 0010 0000 0240 003F 003D
            0008:0FE0 0000 2020 2020 3031 3136 3036 4132
            0016:3330 3742 3032 3335 0002 0002 0004 4844
            0024:5820 342E 3034 5361 6E44 6973 6B20 5344
            0032:4346 482D 3230 3438 2020 2020 2020 2020
            0040:2020 2020 2020 2020 2020 2020 2020 0004
            0048:0000 0300 0000 0200 0000 0003 0F82 0010
            0056:003F 0FE0 003D 0104 0FE0 003D 0000 0007
            0064:0003 0078 0078 0078 0078 0000 0000 0000
            0072:0000 0000 0000 0000 0000 0000 0000 0000
            0080:0010 0000 0000 4004 4000 0000 0004 4000
            0088:0000 0000 0000 0000 0000 0000 0000 0000
            0096:0000 0000 0000 0000 0000 0000 0000 0000
            0104:0000 0000 0000 0000 0000 0000 0000 0000
            0112:0000 0000 0000 0000 0000 0000 0000 0000
            0120:0000 0000 0000 0000 0000 0000 0000 0000
            0128:0000 0000 0000 0000 0000 0000 0000 0000
            0136:0000 0000 0000 0000 0000 0000 0000 0000
            0144:0000 0000 0000 0000 0000 0000 0000 0000
            0152:0000 0000 0000 0000 0000 0000 0000 0000
            0160:0000 0000 0000 0000 0000 0000 0000 0000
            0168:0000 0000 0000 0000 0000 0000 0000 0000
            0176:0000 0000 0000 0000 0000 0000 0000 0000
            0184:0000 0000 0000 0000 0000 0000 0000 0000
            0192:0000 0000 0000 0000 0000 0000 0000 0000
            0200:0000 0000 0000 0000 0000 0000 0000 0000
            0208:0000 0000 0000 0000 0000 0000 0000 0000
            0216:0000 0000 0000 0000 0000 0000 0000 0000
            0224:0000 0000 0000 0000 0000 0000 0000 0000
            0232:0000 0000 0000 0000 0000 0000 0000 0000
            0240:0000 0000 0000 0000 0000 0000 0000 0000
            0248:0000 0000 0000 0000 0000 0000 0000 0000
            Later,
            dabone

            Comment


              #66
              I thought the Identify Device Utility used BIOS to get the ATA ID but I was wrong. Sorry about that.

              Good that you managed to get the ATA ID. WORD 80 tells the ATA version. If bit 2 is set, then drive is ATA-2 drive. If bit 3, then drive is ATA-3 and so on. Zero and FFFFh means no version info is available. The 2 GB card reports being ATA-4 and 64 MB card does not specify ATA version at all. The 512 MB card seems to have some drive specific data since 0400h would mean ATA-10 and there is no such thing.

              Then I took a look at CF specification (v4) and it says WORD 80 is reserved (should be set to zero) for CF cards since they do not report ATA version. The 64MB card seems to set it to 0 as CF cards should and 2GB card seems to report the version like hard drives do. I don't know what the 512MB card reports but now I need to modify ATA ID validation code since WORD 80 cannot be assumed to hold version info or no info at all.

              Comment


                #67
                Glad I could help, let me know when you finish the update, and I'll give it a try.

                Later,
                dabone

                Comment


                  #68
                  It should now be fixed. ATA version is no longer checked.

                  Comment


                    #69
                    Ok, tested version 487, and the 512mb works now, but the 64mb is still not seen.


                    (2 and 4gb are still working fine.)


                    I finally got the 64mb booting, fdisk, create partition, mark active, reboot, then fdisk /mbr then format c: /s.

                    Later,
                    dabone
                    Last edited by dabone; December 5, 2012, 07:20 PM.

                    Comment


                      #70
                      I built the svn this weekend and have been having trouble getting it to work. The build went well after modifying the makefile for linux, and moving Romvars.inc into the correct location. I flashed the bios successfully with an XT-IDE V1, and moved it over to my ethernet card a 3c509 and enabled the boot rom in its configuration. My goal with this setup is to have the universal BIOS break the 504 mb barrier on my 486. The drive in question is a 6.7gb seagate plugged into a promise dc-4030vl. Is this a reasonable configuration and goal?

                      On booting, the XT-IDE bios showed up, detected the drive and tried to boot C which has a preexisting dos partition. It failed and tried to boot A, which was also plugged into the dc-4030vl. This succeeded, and it booted to an MS-DOS installation disk, but the installer could not detect the hard disk. It was also really really slow. I tried removing my drive from the system bios to let the universal bios handle everything, but the problem remained.

                      Now when I remove the dc-4030vl and use my goldstar prime 2C multi-function card it exhibits different symptoms. The copyright message shows up, but it doesn't detect any drives. It zips right past the disk search like it's not looking at all. Instead I'm able to put the disk back in the system bios and it works as normal, at full speed. The only indication that it's there is the copyright message/disk search on boot.

                      Any idea what I'm seeing here? Should I expect this to work or am I missing something important? Should I try this on a stable version before moving to the beta?

                      Comment


                        #71
                        I don't have any experience about promise dc-4030vl but I do have Prime 2C -based Multi I/O cards and those definitely work. The promise is VLB controller, right? They require native support (or drivers) to get full speed. Few VLB controllers have jumpers to set PIO mode. Those do not require native support or drivers.

                        Slow speed might be explained by 8-bit access to ROM so enable Shadow RAM from system BIOS. But first it might be best to concentrate getting the Prime 2C to work and then try the Promise. Are you sure you have AT build? (likely since the Promise detected something). The default settings should be fine.

                        It might be a good idea to try release version first in case something went wrong when building the BIOS.

                        Comment


                          #72
                          I'm not quite sure what you mean by "native support". Do you mean whether the controller supports DOS natively? Or whether the XTIDE BIOS supports the controller natively? The DC-4030VL supports DOS at full speed without any drivers. It has drivers and a setup utility on ROM. Is that native support?

                          I will get things working with the Prime 2C and then play more with the 4030VL. I'm using the 386 BIOS if it matters. I just realized I probably have to reflash the chip to configure it for a 16-bit card.

                          Comment


                            #73
                            If the DC-4030VL has ROM, then it has its own BIOS to control the drives connected to it. Just like you are trying to use XTIDE Universal BIOS to take control of the drives. You need to disable DC-4030VL ROM BIOS if you want to use XTIDE Universal BIOS to handle drives connected to DC-4030VL. Without native support, XTIDE Universal BIOS handles VLB and PCI controllers just like they would be standard 16-bit ISA IDE controllers. At the moment XTIDE Universal BIOS has native support for Vision QD6500 and QD6580 based VLB IDE controllers.

                            Most VLB IDE controllers require software support that motherboard BIOSes don't have. I believe most people never used DOS drivers for VLB Multi I/O cards (I never did). Without the drivers and BIOS support they gained nothing from using VLB instead of 16-bit ISA (unless the VLB controller had jumpers to set PIO mode).

                            Comment


                              #74
                              Ah, I wasn't sure whether the XTIDE BIOS would replace the controller's BIOS or just the system BIOS. I was hoping it just replaced the hard disk detection part of the system bios, leaving the controller to function as if it was placed in a system with a more capable bios. If it completely takes over the card, I guess I'm not going to be getting caching while the XTIDE bios is on there. There is a driver required for accessing drives 3 & 4, I wonder if it would also enable caching in the presence of the XTIDE bios. Something for me to try.

                              Would you be interested in an extended loan of the DC-4030VL, for as long as it takes to add support to the universal bios? You're probably busy fixing bugs for the 2.0 release, but if you're interested in including support in v2.1 or whatever let me know.

                              Comment


                                #75
                                Don't know if this was posted yet, but I can't get the ide_xtpl.bin to work on beta 2. The regular one works fine, ide_xtp.bin.

                                I have a 256kbit EEPROM and it's definitely setup correctly. It flashes without error, and can even be read without error.

                                Any ideas? Not that there's much that I need from it anyway.

                                When I try to use the large one, my POST shows "ROM ERROR E000"

                                EDIT: Also, holding down Control on the ide_xtp.bin BIOS, isnt skipping the routine. I have literally no way to boot to floppy, as there's not even an option in the configuration utility to set a delay unless I use the xtpl BIOS I can't even use.
                                Last edited by evildragon; February 14, 2013, 05:40 AM.
                                IBM PS/2 Model 25, NEC V30 8MHz, 640KB RAM, ATI VGA Wonder XL, 2GB SSD, Ethernet, DR DOS 6/GeOS, Xircom PE3 Ethernet

                                Comment

                                Working...
                                X