Announcement

Collapse

Forum 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.


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.


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.



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.


"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.

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

    Originally posted by UPI View Post
    Having an error pop up may be disconcerting to my customer.
    This is an open-source project licensed under GPL2 license, and not a commercial product. While the GPL2 license allows almost any use of the software, including commercial use, resale, etc. (as long as you make sure the source code is available), it specifically declines any warranty or responsibility for any problems. If something fails and your customer's data gets corrupted you're on your own

    Other than that specific error codes simplify troubleshooting. So I personally prefer 'Error 80' instead of generic 'Floppy Disk Failure' message.

    Originally posted by UPI View Post
    I have "Shadow System BIOS" and "Shadow Video BIOS" enabled. Is this the same?
    It is not. Check your CMOS Setup for "Shadowing" options. Usually there is a list of options like "Shadow 16KB ROM at XXXX", where XXXX is the address. Enable the option(s) with address matching your XT-IDE card. For example if you have your card configured with 8 KiB ROM at address 0CE00h you need to enable shadowing for address 'CC00' (since it is 16KB block in this example, the shadowing will be enabled for the 0CC00h-0CFFFh block). If you have a 32 KiB ROM, you'll need to enable shadowing for two consecutive blocks covering that ROM.

    Comment


      Originally posted by sergey View Post
      Other than that specific error codes simplify troubleshooting. So I personally prefer 'Error 80' instead of generic 'Floppy Disk Failure' message.
      I don't believe I have ever seen a computer that gives an error on every boot when no floppy is inserted. I would agree if a floppy were present and unreadable, but that is not the case here.
      As far as shadowing goes, the two I listed are the only ones shown in the CMOS. I will scour it again tomorrow to make sure.

      Thanks for the feedback.

      Comment


        Originally posted by UPI View Post
        I don't believe I have ever seen a computer that gives an error on every boot when no floppy is inserted. I would agree if a floppy were present and unreadable, but that is not the case here.
        You are right about that. Maybe I should just hide the timeout error (and only display other "real" errors) or try something else. The default setting tries to boot from hard disk first. I think most people prefer it since it is always possible to boot from floppy using hotkey.

        Originally posted by UPI View Post
        As far as shadowing goes, the two I listed are the only ones shown in the CMOS.
        It is very much possible that your BIOS does not support shadow ram for other than main and video bios. AMI BIOS on my 286 is like that. Since you have 386, you can use emm386 and probably other similar memory managers to set shadow ram.

        Comment


          Originally posted by aitotat View Post
          Since you have 386, you can use emm386 and probably other similar memory managers to set shadow ram.
          Please excuse my ignorance as I am not a programmer nor do I have much understanding of the ISA bus or boot ROMs:

          The application that runs the machine was built using Phar Lap's DOS Extender. In other words, it is compiled into the EXE so I don't think another memory manager is possible.

          Is it possible to tack XTIDE onto the MB BIOS? I have attached the binary of the BIOS.
          Attached Files

          Comment


            Originally posted by UPI View Post
            I am also having lockups with the application. It doesn't always initialize when running on XTIDE.
            It is a resource hog running Pharlap Memory Manager and a custom High Speed ISA 8 Channel Serial board.
            Can you tell us more about this application? Can you determine what causes it to not initialize? What settings did you change with XTIDECFG? What make/model is the serial board? Advantech or Moxa or something else (since you say "custom")?
            Looking for a cache card for the "ICL ErgoPRO C4/66d V"

            Comment


              Originally posted by Krille View Post
              Can you tell us more about this application? Can you determine what causes it to not initialize? What settings did you change with XTIDECFG? What make/model is the serial board? Advantech or Moxa or something else (since you say "custom")?
              Sometimes it just locks up during loading of the program when it is still displaying standard DOS text and sometimes it crashes. Sometimes it reaches the graphical display (Real Mode???). Again, the executable was compiled with the Phar Lap TNT DOS Extender builtin to the EXE.

              I have no clue how to determine the cause of the crashes because I know almost nothing about DOS extenders, memory addresses, DEBUG, memory dumps, memory maps etc. It sometimes just locks up and sometimes it crashes with all kinds of TNT errors and sometimes it starts fine.

              I am currently using the 8kb AT version of XTIDE beta 3. I tried it completely stock and then with only 1 controller enabled and then with the floppy as the first boot device. I had also tried the bone stock 16kb version. I seemed to have more success with it set to D8000 than anything else. I have tried it with a Kingston NIC and a 3C509B NIC with no difference seen. I am running it on a 27C256 PROM.

              The serial board is a custom built unit (by Electroglas) running an 80186 processor on board. It is addressed using the 12-16MB memory addresses. The motherboard can only have 12MB installed or it will conflict with the serial board. I do not know much more than that.

              I am afraid that Phar Lap TNT is bumping into XTIDE or that slower hard drive operation is causing timing issues but I have no clue how to determine either.

              Comment


                Can you please test the RAM with memtest86 to make sure it's not a hardware problem?
                Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                Comment


                  Originally posted by Krille View Post
                  Can you please test the RAM with memtest86 to make sure it's not a hardware problem?
                  The PC/machine runs fine w/o XTIDE installed but I will test the RAM to be absolutely sure.
                  I normally run on an 80GB drive with a Western Digital 9.06 overlay. I would like to get away from the overlays and even away from hard drives to get to XTIDE with CF.

                  Comment


                    Originally posted by UPI View Post
                    I normally run on an 80GB drive with a Western Digital 9.06 overlay.
                    Did you format the drive after you installed XTIDE Universal BIOS or did you just uninstall the overlay (if that was even possible)?

                    Comment


                      I found two bugs in beta 3. The first one is quite bad: slaves drives are not initialized properly during reset. They are detected fine but do not work after that. Another bug I found is related to minimum time to display hotkeys. Delay did not work because initialization cleared the counter. Fix for both bugs is in SVN. I'll do some more testing before releasing new version.

                      Comment


                        Originally posted by aitotat View Post
                        Did you format the drive after you installed XTIDE Universal BIOS or did you just uninstall the overlay (if that was even possible)?
                        I am using a completely separate drive (no overlay but the exact same model of Seagate ST380215A) with XTIDE that I FDISK'ed and formatted while booted on XTIDE.

                        One interesting note: XTIDE will recognize the 80GB w/overlay but it just hangs at "Booting C>>C". I don't really plan to use XTIDE with drives using an overlay, but I would think it would still work.


                        Originally posted by krille View Post
                        Can you please test the RAM with memtest86 to make sure it's not a hardware problem?
                        memtest86 passes fine.

                        Comment


                          I don't know if this will be useful, but I was able to set a switch to print out a memory report from the application.
                          Attached Files

                          Comment


                            Just updated my 486 box to r520 and i now get " Non-System disk or disk error, Replace and press any key when ready " when trying to boot from C: drive, So I grabbed another Hard drive / caddy ( i use removable caddy's on this box ) and swapped the hard drive, Ran fdisk / partitoned and formatted the drive and installed Dos 6.22 but still get the same error. I reverted back to r519 and all is fine again.

                            Originally posted by aitotat View Post
                            I found two bugs in beta 3.

                            Comment


                              Originally posted by Malc View Post
                              Just updated my 486 box to r520 and i now get " Non-System disk or disk error, Replace and press any key when ready " when trying to boot from C: drive
                              I'm not sure what caused this. I didn't have any problems with Master and Slave Drive combination but I did not try with only one drive. I tweaked the reset a bit more and tested on two different systems without problems. I hope it now works.

                              Comment


                                Originally posted by UPI View Post
                                One interesting note: XTIDE will recognize the 80GB w/overlay but it just hangs at "Booting C>>C". I don't really plan to use XTIDE with drives using an overlay, but I would think it would still work.
                                It is the overlay software that hangs since at that point execution has moved to the boot sector code. I'm not sure but I suspect that the overlay software expects the same parameters that it detected when it was installed (main BIOS probably had 504 MiB limit). Now it gets different parameters from XTIDE Universal BIOS and does not work with them.

                                Comment

                                Working...
                                X