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

    request for real-mode binary

    Can someone please make a real-mode binary of IDE_XT.BIN that can be launched from a bootloader such as grub or syslinux (just like memtest86+ can)? I believe this would require only minor changes before compilation.

    This would allow more machines to launch the XUB from a floppy drive, which would be useful for testing and also for PCs where a physical (E)EPROM solution might be impractical. It would work in a similar way to the 'rescue floppy' created by Ontrack Disk Manager (DDLOADER.BIN) or similar DDOs.

    It would be good if it could be configurable via a tweaked version of XTIDECFG.COM. If not, defaulting to a single 16bit-in-8bit-slot controller at 1F0/3F0 would allow widespread testing on XT-class PCs.

    I do have a method for loading the XUB from a floppy, but currently it only works on some machines. See my thread here for details: http://www.vcfed.org/forum/showthrea...stead-of-EPROM

    Comment


      I've been trying to follow instructions here to build my own XTIDE UNIVERSAL BIOS. Unfortunately, I didn't get very far. When using Tortoise to download source, it appears the link for the repository (http://xtideuniversalbios.googlecode.com/svn/trunk/) is dead. Is there another link or an alternate way to acquire sources. I am not experienced with this stuff, but I learn quickly if someone is willing to teach.

      Comment


        Yes the old google code link is dead, The new repository url is, http://www.xtideuniversalbios.org/sv...universalbios/

        That is, xtideuniversalbios.org/svn/xtideuniversalbios/ ( with http://www in front)

        Comment


          Thanks Malc. That worked. Maybe someone could update the wiki to include that link?

          Comment


            Yes the wiki and docs are on the list to be updated on the new XTIDE Universal Bios website, The Pre-Built binaries can be downloaded from the Pre-built binaries download center.

            Comment


              Thanks Malc for posting the pointers on this. If you (or anyone else) have some time that could be put in to updating the wiki, please PM me for access.

              Comment


                The following are some comments and responses from another thread that I've been hijacking. I think this is a more appropriate place for this conversation.

                Originally posted by ibmapc View Post
                ...mine (XTIDE rev 3) works perfectly with XUB up to r588 with "Chuck MOD" (They're up to r591) but anything newer than r588 and it fails to id the DOM or any drive connected including spinning hdd. I wonder if the later revs are leaving the older designs behind, focusing on James' designs. I have hi-jacked this tread far enough now. Prolly should start a new one or tack on to another more appropriate thread?!
                Originally posted by Malc View Post
                Nope, FWIW I've had no problems with r591 and my XT-IDE R 1 card using CF and / or spinning disk. I don't own any DOM's.
                Originally posted by ibmapc View Post
                I have only tried the newer revs with the "high speed" jumpers installed with IDE Controller Type set in XTIDECONFIG to match, "Rev 2 or modded rev 1". The bios comes up during boot but does not find any drives unless I downgrade to r588 or earlier. I have not tried it in "compatibility mode". Is your Rev 1 card stock? Or has it been "Chuck Modded"? This should probably be discussed in another thread. Any sugestions which one? There are several threads regarding XTIDE.
                Originally posted by Malc View Post
                My Rev 1 card is stock, I never did the 'Chuck mod', I'd use the XTIDE Universal BIOS v2.0.0 beta testing thread.
                Originally posted by Krille View Post
                Load a suitable BIOS file from r591 in XTIDECFG and then do an autodetect (a drive must be connected when doing this). If that doesn't work then you likely have a hardware problem.
                Thank you Malc and Krille for your responses.

                Malc, I will have to do some re-configuring and see if I can get my rev 3 card to work in compatibility mode with r591.

                Krille, please note that it works perfectly with r588 and older. If it's a hardware problem, it doesn't show up until r589 and newer Bios.

                This would be a good time to tell you about my machine. It is far from "Stock";

                -IBM 5155
                -later XT Motherboard 64 - 256k version with 1megXT MOD (256k chips in all ram banks, 640k base memory, D000h to EFFFh used as UMA)
                -Bios updated to 5-9-86 version.
                -AST Hot Shot 286 Accelerator at 10mhz
                -ATI EGA Wonder
                -Sound Blaster 2.0 with CMS "Upgrade"
                -XTIDE rev 3 with 1gig DOM

                I'll try to find time this weekend to put it in my stock 5155 to rule out (or rule IN) compatibility issues.

                Is anyone using a rev 2 or 3 card in "High Speed" mode with r589 or newer?

                Comment


                  Originally posted by pearce_jj View Post
                  Thanks Malc for posting the pointers on this. If you (or anyone else) have some time that could be put in to updating the wiki, please PM me for access.
                  Would it be possible to have the Wiki in several languages? I don't know how much need there is for the manuals in languages other than english but I'm thinking it would be nice to have if there is a need (and if someone is prepared to maintain the pages for each language of course).

                  Originally posted by ibmapc View Post
                  Krille, please note that it works perfectly with r588 and older. If it's a hardware problem, it doesn't show up until r589 and newer Bios.
                  Your posts earlier in this thread indicates that you might be using a build you made yourself. If so, did you make sure to include;
                  • MODULE_8BIT_IDE? If not, there is no support for the XT-IDE cards in the build.
                  • NO_ATAID_VALIDATION? If not, some drives might not be detected.

                  If you're using the official builds from http://xtideuniversalbios.org/binaries then both of these defines are included so it should work unless you somehow made a mistake when configuring the BIOS (which is why I wanted you to try the autodetection).

                  -AST Hot Shot 286 Accelerator at 10mhz
                  If there really is a compatibility problem then this would be my primary suspect but I doubt that's the problem.
                  Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                  Comment


                    Originally posted by Krille View Post
                    Your posts earlier in this thread indicates that you might be using a build you made yourself. If so, did you make sure to include;
                    • MODULE_8BIT_IDE? If not, there is no support for the XT-IDE cards in the build.
                    • NO_ATAID_VALIDATION? If not, some drives might not be detected.

                    If you're using the official builds from http://xtideuniversalbios.org/binaries then both of these defines are included so it should work unless you somehow made a mistake when configuring the BIOS
                    I've tried it both with "Official" builds and my own configured builds with the two modules you mentioned as a minimum. I've tried several combos with boot menu or hot keys. None worked.

                    Originally posted by Krille View Post
                    (which is why I wanted you to try the autodetection).
                    I did try the "auto configure". It say's "found 0 controllers" unless I use r588 or older. I always use the configurator that's the same version as the bios that I'm loading. With r588 it finds my controller and configures it correctly.

                    Originally posted by Krille View Post
                    If there really is a compatibility problem then this (AST Hot Shot 286 Accelerator) would be my primary suspect but I doubt that's the problem.
                    I agree. Right now, it's jumpered to startup in 286 mode. I can change it to start in 8088 mode next time I remove the cover and see if that makes any difference.

                    Comment


                      Originally posted by ibmapc View Post
                      I did try the "auto configure". It say's "found 0 controllers"
                      OK, I did some more testing tonight. It seems I was remembering it wrong when I made that statement. The "found 0 controllers" message only comes up after a failed boot. Meaning that if I flash the EEPROM with r589 or newer and then re-boot, it fails to id the drive connected to the XTIDE and then boots to drive A. Then, I run XTIDECFG, load bios from file, or from EEPROM and select "auto configure" and the message "found 0 controllers" is displayed. So it seems during the failed boot, the XTIDE locks up and XTIDECFG can not auto configure it, no matter what bios I attempt to load. If I power cycle the unit and boot with XTIDE bios disabled, (booting to floppy),then enable bios and run XTIDECFG and load r588 everything works fine, including "auto configure". This was all done with the AST HotShot set to start in 286 mode during power on. So then I switched the HotShot to 8088 mode(ALT+8 switches between processors) and did a "three finger re-boot" (during soft boot, the HotShot stays in the same mode). I then flashed the EEPROM with r591. It re-booted and it successfully identified the DOM and booted dos. All seemed to work fine until I switched to 286 mode. It then started having trouble finding files on the DOM and directory listing became gibberish. So I again downgraded to r588 and ran several tests in both 286 and 8088 mode and found no failures. So, it seems like there is a timing issue when using the r589 and newer when in accelerated 286 mode. Maybe r588 is a little slower than the newer versions thereby keeping the timing from being a problem? I still need to remove the cover so that I can move the jumpers on the XTIDE to "Compatibility mode" and re-load r591 configured for same. If that works in 286 mode, I would then run some benchmarks to see which is faster, r591 in "compatibility mode" or r588 in "high speed mode"

                      Comment


                        Did anyone try to run XTIDEUNIVERSALBIOS on the 16-bit MFM (WDxxxx) controllers ? As it is known MFM controllers perform IDE commands subset (uses the same TaskList register set) but does not respond for IDE ATA Identification commands. I tried to setup C/H/S manually with XTIDECFG w/o success. Is it possible to run XUB and MFM?

                        Comment


                          I know this is a very old thread, but I have a question about updating my XTIDE BIOS to post-version 1.1.5.

                          So my system is an IBM PC 5150, running the original XTIDE version 1 hardware, built from the kit. I have not done the Chuck speed mod to it. The XTIDE has a 1GB IDE hard drive attached to it, and it is working well. It currently has the 1.1.5 BIOS.

                          I am interested in upgrading it to the 2.0.x BIOS, but am worried about the warnings about corruption of data when upgrading, and something about L-CHS parameters changing in the BIOS revision. I tried looking into this technically, and it seems like messing that info up would seriously mess the data integrity up.

                          How would you go about upgrading this, while keeping my hard drive contents. My understanding is that a new hard drive would need to be repartitioned and reformatted with the new BIOS to be safe.

                          Any ideas on how I would migrate my hard drive after updating the XTIDE BIOS to version 2?

                          I guess I could get a USB-to-IDE adapter cord. Then I could transfer the hard-drive contents to a modern computer. What would I do then? Update the XTIDE BIOS to v2, repartition/reformat the IDE hard drive with the new BIOS v2, connect the IDE hard drive back to my modern PC and then transfer the backup contents back to the IDE hard drive? Would that work?

                          Any suggestions would be great, thanks.
                          Last edited by Holmes; March 10, 2017, 07:02 AM.

                          Comment


                            Originally posted by Holmes View Post
                            ....So my system is an IBM PC 5150, running the original XTIDE version 1 hardware, built from the kit. I have not done the Chuck speed mod to it. The XTIDE has a 1GB IDE hard drive attached to it, and it is working well. It currently has the 1.1.5 BIOS.
                            I have the same R1 cards, didn't do the 'Chuck mod' either, One of my 5160's is still running the 1.1.5 BIOS, Never felt the need to upgrade that one.

                            I am interested in upgrading it to the 2.0.x BIOS, but am worried about the warnings about corruption of data when upgrading, and something about L-CHS parameters changing in the BIOS revision. I tried looking into this technically, and it seems like messing that info up would seriously mess the data integrity up.
                            Yes, I can't remember exactly when it changed without looking back, It was a long time ago now, Basically i found an FDISK / Partition / Format and Re-install was best.

                            How would you go about upgrading this, while keeping my hard drive contents. My understanding is that a new hard drive would need to be repartitioned and reformatted with the new BIOS to be safe.

                            Any ideas on how I would migrate my hard drive after updating the XTIDE BIOS to version 2?

                            I guess I could get a USB-to-IDE adapter cord. Then I could transfer the hard-drive contents to a modern computer. What would I do then? Update the XTIDE BIOS to v2, repartition/reformat the IDE hard drive with the new BIOS v2, connect the IDE hard drive back to my modern PC and then transfer the backup contents back to the IDE hard drive? Would that work?

                            Any suggestions would be great, thanks.
                            What exactly do you want to transfer over to the new drive ?, This is what i would do and have done successfully in the past.

                            I would recommend you upgrade to the latest available revision of the XUB which is R591
                            Remove your current hard drive and put it somewhere safe.
                            Fit your new drive as master and using a DOS boot disk with the XUB and XTIDECFG.COM on the floppy, Boot the machine / Configure the BIOS using XTIDECFG.COM and flash the EEPROM. Reboot / FDISK / Partition and format the new drive and install the operating system.

                            Fit your old drive as a Slave ( I'm assuming your PSU will cope with 2 drives ) and boot the machine, You will not be able to boot from your old hard drive but should be able to read and copy any data over to the new drive.

                            Comment


                              Originally posted by Malc View Post
                              I have the same R1 cards, didn't do the 'Chuck mod' either, One of my 5160's is still running the 1.1.5 BIOS, Never felt the need to upgrade that one.



                              Yes, I can't remember exactly when it changed without looking back, It was a long time ago now, Basically i found an FDISK / Partition / Format and Re-install was best.



                              What exactly do you want to transfer over to the new drive ?, This is what i would do and have done successfully in the past.

                              I would recommend you upgrade to the latest available revision of the XUB which is R591
                              Remove your current hard drive and put it somewhere safe.
                              Fit your new drive as master and using a DOS boot disk with the XUB and XTIDECFG.COM on the floppy, Boot the machine / Configure the BIOS using XTIDECFG.COM and flash the EEPROM. Reboot / FDISK / Partition and format the new drive and install the operating system.

                              Fit your old drive as a Slave ( I'm assuming your PSU will cope with 2 drives ) and boot the machine, You will not be able to boot from your old hard drive but should be able to read and copy any data over to the new drive.

                              Thanks for the reply!

                              I need to transfer a whole bunch of junk on the old hard drive. I have lots of applications (Word, Windows, Lotus 123, etc.), games, documents. It's not mission critical, though. I'd hate to have to reinstall everything all over again. I think originally I transferred the install files over using a serial connection and Fastlynx.

                              So you feel I should be able to read the old drive as a slave under the new XUB bios? That was my chief concern, as I wasn't sure if the XUB would still read the old drive okay, or if it would garble that with the new drive "layout".

                              Comment


                                Yes should be fine, ( Famous last words ) Seriously though i never had any problems reading the old hard drive as a slave and copying data to the new drive. As i said you won't be able to boot from the old (slave) hard drive but once you have all the data off you could wipe the drive / fdisk / partion and format and use the drive as a slave if you wanted to.

                                Comment

                                Working...
                                X