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

    Regardless, it should still be hosted on github.
    Offering a bounty for:
    - A working Sanyo MBC-775 or Logabax 1600
    - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

    Comment


      Originally posted by Trixter View Post
      Regardless, it should still be hosted on github.
      Hosting on github was discussed a long while back and the developers didn't want it there, I can't remember why though.

      Comment


        Originally posted by keenerb View Post
        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?
        That's recent, I just checked and get the same, It was working a few days ago.

        Comment


          Originally posted by Malc View Post
          Hosting on github was discussed a long while back and the developers didn't want it there, I can't remember why though.
          It ought to be publicly available.

          The software is GPLv2 licensed anyway, if it's not on github it has to be available SOMEWHERE for people who download the binaries.

          Comment


            Originally posted by keenerb View Post
            It ought to be publicly available.
            Hopefully it will be again, be it on github or somewhere else, but that's up to the project owner / developers.

            The software is GPLv2 licensed anyway, if it's not on github it has to be available SOMEWHERE for people who download the binaries.
            It's Free software, All good things come to an end eventually, hopefully not in this case though.

            Comment


              Private hosting as in not on another public code site. It doesn't mean it will be inaccessible!

              Comment


                OK so maybe I'm missing this bit:

                Strawberry Perl is required to execute optional scripts when building XTIDE Universal BIOS. Scripts include string compression (not needed unless you modify the sources) and checksum calculation. Just run the Strawberry Perl installer with default settings.
                I notice there's a byte at the end of the bios that's always different between builds. I think that must be my problem.

                The wiki says you can use the xtidecfg utility to generate this checksum, but the xtidecfg program only lets you append the checksum AS part of flashing the rom.

                HOWEVER, xtidecfg doesn't support the flash chip the xt-cf board uses, which is http://www.mouser.com/Search/Product...-39SF010A7CPHE

                I'll see if installing strawberry perl and getting that checksum generated works...

                Comment


                  Code:
                  All done!
                  checksum: Build/ide_tiny.bin: 3991 bytes before, 8192 bytes after
                  checksum: Build/ide_xt.bin: 6499 bytes before, 8192 bytes after
                  checksum: Build/ide_xtp.bin: 6268 bytes before, 8192 bytes after
                  checksum: Build/ide_at.bin: 6950 bytes before, 8192 bytes after
                  checksum: Build/ide_xtl.bin: 9168 bytes before, 12288 bytes after
                  checksum: Build/ide_xtpl.bin: 8919 bytes before, 12288 bytes after
                  checksum: Build/ide_atl.bin: 9788 bytes before, 12288 bytes after
                  checksum: Build/ide_386.bin: 7025 bytes before, 8192 bytes after
                  OK that looks a lot better. Off to flash.

                  *edit*

                  Looks like it worked this time. Yay. Added a few lines to disable the my Tandy 1000TL's floppy drive, recompiled, and it works like a charm. Had to recompile the xtidecfg tool as well, an older version wouldn't work with the new rom.
                  */edit*
                  Last edited by keenerb; May 13, 2016, 03:17 PM.

                  Comment


                    How would I append a second bios image to the XT-IDE image? Just as simple as cat newbios.bin >> xtide.bin?

                    Comment


                      Yes, copy /b

                      Comment


                        Originally posted by keenerb View Post
                        I don't believe you can anymore.

                        TortoiseSVN reports "/svn path not found" when I try to check out https://xtideuniversalbios.googlecode.com/svn
                        Yep, it looks like they finally pulled the plug.

                        Originally posted by keenerb View Post
                        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...
                        Looks fine to me except there shouldn't be a .svn directory in the Build directory. I'm guessing the Build directory doesn't exist? The file sizes, as you know by now, will be correct if you run 'make checksum' or open the files with XTIDECFG and then save them back to disk.

                        Originally posted by keenerb View Post
                        I notice there's a byte at the end of the bios that's always different between builds. I think that must be my problem.
                        Yes, that's the checksum byte.

                        The wiki says you can use the xtidecfg utility to generate this checksum, but the xtidecfg program only lets you append the checksum AS part of flashing the rom.
                        It will also generate the checksum when you save the file back to disk.

                        HOWEVER, xtidecfg doesn't support the flash chip the xt-cf board uses, which is http://www.mouser.com/Search/Product...-39SF010A7CPHE
                        Flash programming support is on my wishlist of features to be added to XTIDECFG. It irks me that people can't use a single tool to program all the supported hardware.
                        Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                        Comment


                          Originally posted by SpidersWeb View Post
                          Don't like bumping old threads, but this looks like the place I should report a minor issue I had.

                          AT version of XTIDE, 2.0 beta 3, Toshiba T5200/100, Conner CP30174E. IRQ 14, Block Mode enabled, LBA set to "NORMAL" manually.
                          Drive detected, but would not boot. Booting from floppy gave me complete/perfect access to the drive, I could copy software on to it and run it - but no boot. I repartitioned, checked it was active, formatted /S - no matter what I did I always got the "Non System Disk or Disk Error" you get from a blank floppy etc On one occasion the computer was non-responsive and required a power off afterwards.

                          Went back to XTIDE 1.1.5, and the drive booted straight in to MS DOS.

                          Same hardware was used in both scenarios. ROM address was D200 and I'd disabled EMS/Shadow in the BIOS.
                          Was this ever resolved?
                          Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                          Comment


                            Thanks Krille.

                            I figured out I needed to run the make checksum option eventually. It didn't seem to be all that clear that it was an absolutely REQUIRED part of the process when following the build instructions.

                            I also was using an older version of xtidecfg which didn't seem to recognize the bios as valid at all, and wouldn't create the checksum when I saved back to disk.

                            It's working quite well now, though.

                            Comment


                              Originally posted by Krille View Post
                              Was this ever resolved?
                              Sorry I've had a lot of repairs/hauls/building going on so haven't tested out the latest 2.x revision (which I assume would be required before anyone looks in to it).
                              Since it was working with 1.15 I'd already screwed the machine back up at the time. I just wanted to report it in case it was useful to someone.

                              Happy to do more testing later on when I've got more time.

                              Any one else running C/H/S ?
                              Twitter / YouTube

                              Comment


                                Bah, ignore this message.

                                I managed to overwrite my copy of sergery's high-density floppy BIOS with the xt-ide bios, so I was writing two copies of the ide bios to flash instead of fdc + ide.
                                Last edited by keenerb; May 17, 2016, 05:57 PM.

                                Comment

                                Working...
                                X