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

    I have XT-IDE ATL 2.0.0B3 up and running in my 486 machine, using the motherboard IDE, and it's currently installing FreeDOS 1.1 from CD to a Western Digital 40GB I managed to scrounge up. So far, no big problems aside from the FreeDOS installer being slow on a 486SX-25. I'm using a 27C128 I borrowed out of another card, and it's currently living in my Etherlink III's boot PROM socket assigned to C800h.

    I've been wanting to get this going for a while now, since the system BIOS is CHS-only and none of the DDOs I've been able to find easily support FAT32.

    Comment


      R580 binary is now available here.

      Comment


        I see that R580 (and other older releases) has also "ide_tiny.bin", ~4k only used space... that's what I need for an integration on an existing BIOS

        I have already searched info on it by Google and repository but no luck.

        The file is 8k for some reason? Can I cut it down to 4k or I loose some info (checksum is not a problem)? What module are excluded? what instruction code is used (8086/80188/286)? anyone know?
        Thank you for the info!

        Comment


          Originally posted by Simone2013 View Post
          Can I cut it down to 4k or I loose some info (checksum is not a problem)? What module are excluded? what instruction code is used (8086/80188/286)? anyone know?
          The Tiny build uses 8086/8088 instructions only. Yes, you can truncate the file but I would recommend building with 'make xt_tiny' instead if possible (to avoid the risk of botching it while editing). This will create a 3987 byte file without the option ROM checksum if building from the latest revision (r58. Note that you will need to add MODULE_8BIT_IDE_ADVANCED to get support for the XT-CF cards. See the makefile for more info regarding modules.
          Looking for a cache card for the "ICL ErgoPRO C4/66d V"

          Comment


            I am trying to build the latest R588 binary but I can't compile the new Serial_Server binary... I get an error related to win32.obj . I followed the guide on the wiki and successfully compiled the other parts. Any idea how to fix things so serial server compiles too?



            TIA for any info/help!

            edit:
            please keep in mind that this is the first time I am compiling anything , I tried to figure out if a win32.obj file exists or is a part of something I am missing but I failed. I have installed the full version (300+ mb) of tdm-gcc.
            Last edited by keropi; October 6, 2015, 12:07 PM.

            Comment


              See the makefile in the serial_server folder, You need either Microsoft Visual C++ 2010 or Windows SDK v7.1 installed or Also works with Open Watcom C/C++ Version 1.9

              I have Open Watcom C/C++ Version 1.9 installed and it builds fine, You can grab Open Watcom from http://www.openwatcom.org/

              Comment


                Originally posted by Malc View Post
                See the makefile in the serial_server folder, You need either Microsoft Visual C++ 2010 or Windows SDK v7.1 installed or Also works with Open Watcom C/C++ Version 1.9

                I have Open Watcom C/C++ Version 1.9 installed and it builds fine, You can grab Open Watcom from http://www.openwatcom.org/
                Thanks so much for this, openwatcom worked and I get a binary

                I have another question regarding the checksums calculation with Strawberry Perl , is it correct to think that I need it for the checksums whether I make source changes or not? It is only marked as "optional" because you can calculate the checksums with XTIDECFG.COM, correct?

                edit:
                here is R588 , it seems all is OK unless I did something really really wrong https://www.mediafire.com/?ibcixfypudgjm2s
                Last edited by keropi; October 6, 2015, 03:06 PM.

                Comment


                  You don't need to install strawberry perl, ie: build the binary's with no checksum calculation "mingw32-make all" and when you configure the bios with XTIDECFG.com it can calculate the checksum for you. If you want to do checksum calculation when building the binary's "mingw32-make checksum" or modify sources then strawberry perl must be installed.

                  Comment


                    where is latest version?

                    and how can i compile it?

                    ^^;

                    Comment


                      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.
                      Last edited by SpidersWeb; March 19, 2016, 04:23 PM. Reason: Added proper version numbers
                      Twitter / YouTube

                      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.
                        This is absolutely the correct place to report issues.

                        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.
                        The first thing to try is a newer version of the BIOS. Beta 3 is old and known to have problems. Though I must admit that I don't recognize this particular bug. It might be a problem with you forcing the "Normal" translation instead of using "Autodetect". Although with this drive the result should be the same.

                        Generally speaking, it seems very few people use old CHS drives so there's very little testing done and consequently not that much feedback.
                        Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                        Comment


                          Originally posted by SpidersWeb View Post
                          AT version of XTIDE, 2.0 beta 3, Toshiba T5200/100
                          You might want to try the version I posted in this thread:
                          http://www.vcfed.org/forum/showthrea...dows-95-issues
                          which is built from the latest post beta 3 source code and was running on my Toshiba T5200.
                          It contains a mod to stop Windows 95 running in MSDOS compatibility mode which is irrelevant to your problem but at least it's the latest code.
                          I have made further changes since then to work around a few more compatibility issues with Windows/386 and some problems specific to the T5200 including getting 2 drives to work as master and slave (using compact flash) but I'll make a separate post about those once I've finished testing.

                          Comment


                            I'll try and push forward with the new SVN Site, then perhaps you can merge in your changes?

                            Comment


                              So where exactly is the newest bios? Here? https://www.lo-tech.co.uk/wiki/XTIDE...nary_Downloads

                              Google code has not been used for years. I'm using v2 beta 3, but I don't see any option for booting drive B: instead of A or C. My older XT-IDE card does this fine.
                              I have a Major in Post-Apocalyptic Economics.
                              Wanted: Any PC-Compatible Reciprocation Dingle Arm

                              Comment


                                Originally posted by offensive_Jerk View Post
                                So where exactly is the newest bios? Here? https://www.lo-tech.co.uk/wiki/XTIDE...nary_Downloads
                                The last available revision of the XUB was 588 on the svn June 3 2015, i've uploaded r588 which includes the modules as standard. Here

                                Google code has not been used for years. I'm using v2 beta 3, but I don't see any option for booting drive B: instead of A or C. My older XT-IDE card does this fine.
                                I'm guessing that with your R1 XT-IDE card you see the 'Boot Menu' as with XUB v1.1.5, The boot menu is optional with more recent releases. When you boot your machine, directly after the beep just press the B Key to boot from the B drive. If you'd rather have the Boot Menu instead of the Hotkey bar you'd have to do a custom build or let me know what bios file you are using and i'll change it for you.

                                Comment

                                Working...
                                X