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

    UPDATE:
    I found the problem: the CF card. I used a white label before and now a Sandisk Ultra II and it now works (after FDISK /MBR)

    ----


    Hi there,

    I'm new here and I have the XT-CF-V4 from Sergey Malinov.

    Everything seems to work fine:
    I've flashed the EEPROM with the latest bios using the latest XTIDECFG application.

    When it boots, it hangs at the booting from C>>C.
    The led doesn't blink, nothing happens.

    What I've tried:
    - installing several versions of the IDE_XT.BIN file
    - Fdisk /MBR
    - Format /Q/U/S (there are files like command.com on the CF card) and seems to be ok
    - Fdisk normally (there's an active partition FAT)

    So I'm out of ideas. Maybe you guys have some more suggesions to try.
    When I boot from Floppy, there's a C drive which is the CF card.

    The computer is an IBM 5150 (8086 processor) I used the IDE_XT.BIN file to flash the EEPROM.

    Thanks,
    Angelo
    Last edited by xp2002; March 31, 2016, 11:51 PM.

    Comment


      Originally posted by xp2002 View Post
      UPDATE:
      I found the problem: the CF card. I used a white label before and now a Sandisk Ultra II and it now works (after FDISK /MBR)

      ----


      Hi there,

      I'm new here and I have the XT-CF-V4 from Sergey Malinov.

      Everything seems to work fine:
      I've flashed the EEPROM with the latest bios using the latest XTIDECFG application.

      When it boots, it hangs at the booting from C>>C.
      The led doesn't blink, nothing happens.

      What I've tried:
      - installing several versions of the IDE_XT.BIN file
      - Fdisk /MBR
      - Format /Q/U/S (there are files like command.com on the CF card) and seems to be ok
      - Fdisk normally (there's an active partition FAT)

      So I'm out of ideas. Maybe you guys have some more suggesions to try.
      When I boot from Floppy, there's a C drive which is the CF card.

      The computer is an IBM 5150 (8086 processor) I used the IDE_XT.BIN file to flash the EEPROM.

      Thanks,
      Angelo
      Ah i see yeah i have the same issues with booting up c alone so i am forced to use a floppy to boot those machines ^^;

      Comment


        Originally posted by sparky4 View Post
        Ah i see yeah i have the same issues with booting up c alone so i am forced to use a floppy to boot those machines ^^;
        Yes, the solution will be to use another cf card. Like Kingston or sandisk. I used 512mb Sandisk and 1GB Kingston cards with success.

        Comment


          Hi all,

          I have a strange problem I am using one of lo-tech's CF lite 2.x cards with the default xt-ide bios downloaded from the lo-tech site (which I believe is R580).
          The card is jumpered at rom at c8000h / io at 300h

          The machine I have this in is one of the pc-retro 5150 clone boards, I'm also using a 16bit multi-io card with the IDE section disabled to get me hd floppies, com and lpt ports.
          I also have one of the lo-tech maxmem XT cards in to bump the memory up to 640K.

          The card works fine with just a 1.44 MB drive connected, I can boot from either the floppy or the CF card. However as soon as I connect a 5.25" drive (either a 360K or a 1.2M, configured correctly in the controller bios of course) the XT-IDE refuses to boot from the CF card giving up with an error 1h. I've just checked with two 1.44MB drives configured and connected and am getting the same problem

          The odd things is if I boot from floppy I can access both the floppy drives a: and b: and my CF partitions c: and d:.

          Since I have a flashrom adapter in the motherboard with a 29x010, programmed with both the Super BIOS v2.5 and the latest IBM PC bios, I have tried with both and got the same results.

          Anyone have any idea what the problem may be?

          Also does anyone know where I can get the latest copy of the source?

          Cheers.

          Phill.
          Last edited by prime; April 16, 2016, 01:23 PM.

          Comment


            Originally posted by prime View Post
            Also does anyone know where I can get the latest copy of the source?
            It's still possible to do a checkout from Google Code. Just enter https://xtideuniversalbios.googlecode.com/svn as the URL in your favourite SVN client to checkout the entire project including wikis and everything (https://xtideuniversalbios.googlecode.com/svn/trunk if you're only interested in the source).

            Example command line that will checkout only the source to the folder XUB: svn co https://xtideuniversalbios.googlecode.com/svn/trunk XUB

            I hope this helps. I'm sorry I can't help with the actual problem you're having.
            Looking for a cache card for the "ICL ErgoPRO C4/66d V"

            Comment


              Right I think I've made some progress..

              With the Addon floppy BIOS not in the system, the CF card boots, though obviously you can only access DD floppies.

              Since the ROM on the lo-tech card is mapped into C800-CFFF and the actual XTIDE ROM is only 8K I decided to try putting my floppy bios on there and found that it works IF the floppy BIOS is at a lower address than the XTIDE BIOS.

              So what I have now works :

              xtfdc at C800:0
              xtide at CA00:0

              Originally I had the floppy bios at F000 and the IDE at C800, and that didn't work with two drives connected, with only 1 it worked fine which is odd.

              Cheers.

              Phill.

              Comment


                xtfdc?? where is the software?

                Comment


                  Originally posted by sparky4 View Post
                  xtfdc?? where is the software?
                  I located the last BIOS version that I recorded, and placed a copy at [here].

                  Comment


                    Originally posted by Krille View Post
                    It's still possible to do a checkout from Google Code. Just enter https://xtideuniversalbios.googlecode.com/svn as the URL in your favourite SVN client to checkout the entire project including wikis and everything (https://xtideuniversalbios.googlecode.com/svn/trunk if you're only interested in the source).

                    Example command line that will checkout only the source to the folder XUB: svn co https://xtideuniversalbios.googlecode.com/svn/trunk XUB

                    I hope this helps. I'm sorry I can't help with the actual problem you're having.
                    I don't believe you can anymore.

                    TortoiseSVN reports "/svn path not found" when I try to check out https://xtideuniversalbios.googlecode.com/svn

                    Did anyone re-host this on Git or another service?

                    Comment


                      Building from source; file sizes wrong.

                      Code:
                      C:\xt-ide\xt-ide build\source-archive_original\xtideuniversalbios\trunk\XTIDE_Universal_BIOS>mingw32-make all
                      Deleted "(*.*)" from "Build/"
                      * Tiny XT version "Build/ide_tiny.bin" built.
                      * Small XT version "Build/ide_xt.bin" built.
                      * Small XT Plus version "Build/ide_xtp.bin" built.
                      * Small AT version "Build/ide_at.bin" built.
                      * Small 386 version "Build/ide_386.bin" built.
                      All small binaries built!
                      * Large XT version "Build/ide_xtl.bin" built.
                      * Large XT Plus version "Build/ide_xtpl.bin" built.
                      * Large AT version "Build/ide_atl.bin" built.
                      All large binaries built!
                      All done!
                      
                      05/13/2016  11:53 AM    <DIR>          .
                      05/13/2016  11:53 AM    <DIR>          ..
                      03/17/2016  01:03 PM    <DIR>          .svn
                      05/13/2016  11:55 AM             7,025 ide_386.bin
                      05/13/2016  11:55 AM         1,606,661 ide_386.lst
                      05/13/2016  11:55 AM             6,950 ide_at.bin
                      05/13/2016  11:55 AM         1,620,279 ide_at.lst
                      05/13/2016  11:53 AM             9,788 ide_atl.bin
                      05/13/2016  11:53 AM         2,017,966 ide_atl.lst
                      05/13/2016  11:55 AM             3,987 ide_tiny.bin
                      05/13/2016  11:55 AM         1,311,821 ide_tiny.lst
                      05/13/2016  11:55 AM             6,495 ide_xt.bin
                      05/13/2016  11:55 AM         1,590,468 ide_xt.lst
                      05/13/2016  11:53 AM             9,164 ide_xtl.bin
                      05/13/2016  11:53 AM         1,935,491 ide_xtl.lst
                      05/13/2016  11:55 AM             6,264 ide_xtp.bin
                      05/13/2016  11:55 AM         1,584,074 ide_xtp.lst
                      05/13/2016  11:53 AM             8,915 ide_xtpl.bin
                      05/13/2016  11:53 AM         1,929,097 ide_xtpl.lst
                      I haven't altered the source at all. I've installed mingw and nasm.

                      It's not building an 8kb/12kb file, and the files it is building aren't working on my CF adapter.

                      Any idea what's up?

                      I think the only source I have available (since I can't use SVN to check out a specific version) is simply broken...
                      Last edited by keenerb; May 13, 2016, 09:01 AM.

                      Comment


                        Originally posted by keenerb View Post
                        Did anyone re-host this on Git or another service?
                        I can put it on GitHub and manage the repo, if that's desired. The XT-IDE board KiCad files will be on GitHub.
                        Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

                        Comment


                          Keenerb - you need to run XTIDECFG against one of the bin files to set up the options etc before writing out to flash.

                          Re hosting; this has taken a back seat because the Google code site was available read-only for ages so it wasn't such an issue. The plan is to move it private hosting, which is in progress though, I'll see this gets running shortly.

                          Comment


                            Originally posted by pearce_jj View Post
                            Keenerb - you need to run XTIDECFG against one of the bin files to set up the options etc before writing out to flash.

                            Re hosting; this has taken a back seat because the Google code site was available read-only for ages so it wasn't such an issue. The plan is to move it private hosting, which is in progress though, I'll see this gets running shortly.
                            xtidecfg doesn't prompt me with an option to config the rom when I load one of these compiled bin files. I just get flash/write file out to original location.

                            Here's the file that was compiled:

                            https://www.dropbox.com/s/1y467nkq8x..._xt_o.bin?dl=0

                            In a hex editor it looks good.

                            Does the ROM have an internal checksum or anything that needs to be updated?
                            Last edited by keenerb; May 13, 2016, 09:37 AM.

                            Comment


                              Originally posted by pearce_jj View Post
                              The plan is to move it private hosting, which is in progress though, I'll see this gets running shortly.
                              Keep in mind that private hosting often follows the maintainer, putting it somewhere like GitHub means it will at least still be fork-able as long as GitHub continues to exist. I had some measure of difficulty in finding the XT-IDE rev 2 schematics/board layouts when I started working on rev 3.
                              Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

                              Comment


                                To be clear, the private hosting relates to the BIOS code, not the PCB of similar name.

                                Comment

                                Working...
                                X