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

  • Twospruces
    replied
    Originally posted by Trixter View Post
    Did you configure them before flashing? They have a slow compatibility mode you likely need to ensure is set before flashing them; they may not work out of the box without configuration.
    thanks for the tip. I am generally now running XTIDECFG on all raw initial images before I run them, but I missed the compatibility mode. I'll try that.

    I'm not using "Full Operating Mode" either. I can give that a try to see if it makes a difference.

    This issue seems to be different though. Where does XUB store the detected drive info? On the first try from cold restart, XUB does not even present any HDD for boot up.

    Leave a comment:


  • Eudimorphodon
    replied
    Originally posted by Twospruces View Post
    Now we see a new entry - Foreign Hard Disk - with some tiny size allocation - at 80h and the proper disk at 81h.
    When I select to boot from the 2nd entry I successfully boot, with the BIOS messages "Booting D>>C".

    The pattern repeats. Every time I reboot, another false entry is created and the proper disk moves down by 1 value.
    I can still boot the machine.
    I'm curious, are you using the "Full Operating Mode" setting? Per the docs:

    Full mode supports up to 5 IDE controllers (10 drives). Full mode reserves a bit of RAM from top of base memory. This makes possible to use ROM Basic and software that requires top of interrupt vectors where XTIDE Universal BIOS parameters would be stored in lite mode. Lite mode supports only one IDE controller (2 drives) and stores parameters to top of interrupt vectors (30:0h) so no base RAM needs to be reserved. Lite mode cannot be used if some software requires top of interrupt vectors. Usually this is not a problem since only IBM ROM Basic uses them. Tandy 1000 models with 640 kiB or less memory need to use lite mode since top of base RAM gets dynamically reserved by video hardware. This happens only with Tandy integrated video controller, not with expansion graphics cards. It is possible to use full mode if reserving RAM for video memory + what is required for XTIDE Universal BIOS. This would mean 129 kiB but most software should work with 65 kiB reserved.
    That it keeps counting up possible "phantom" hard drive numbers past 81h sort of makes it sound like it's going past what would be allocated in "lite" mode?

    Leave a comment:


  • Trixter
    replied
    Originally posted by Twospruces View Post
    * R590 and newer do not work at all.
    Did you configure them before flashing? They have a slow compatibility mode you likely need to ensure is set before flashing them; they may not work out of the box without configuration.

    Leave a comment:


  • Twospruces
    replied
    Originally posted by Twospruces View Post
    Hi, I have an interesting update.
    First, the major change I made was to use R566 IDE_XTL.BIN so that I have the boot menu available. This has proved very valuable.
    mistake; I'm actually using R580 IDE_XTL.BIN.

    * R590 and newer do not work at all.
    * R566 seems to behave the same way but I don't have R566 IDE_XTL.BIN (does anyone have it?)
    * I have a 16MB Hitachi and 1GB Sandisk, and they are both working equivalently.
    * I create the correct MBR on these cards by mounting them (IDE CF adapter) in a Pentium 4 PC running DOS 5. FDISK /MBR
    * in the Z171 clone, I can then (using my procedure in prior post) to get the disk visible, then remove and rebuild partition, format C: /s , copy DOS from A to C

    Something definitely changes in XUB at some point that makes it incompatible with my machine. I have downloaded the SVN repo; if we can figure out how to get a normal disk detection fix, then R580 could be a baseline revision for a fix.

    Leave a comment:


  • Trixter
    replied
    That is bizarre. My off-the-cuff guess is that your clone is not clearing memory on a warm restart, and the XUB is getting confused by seeing previous data at startup. That's just a guess though; hopefully Krille can comment.

    Leave a comment:


  • Twospruces
    replied
    Hi, I have an interesting update.
    First, the major change I made was to use R566 IDE_XTL.BIN so that I have the boot menu available. This has proved very valuable.
    Seems that the issue is now apparent as you will see.

    Upon initial power up (turn off computer, remove CF card, wait 10 sec, install CF card, power up computer), we see this boot menu.

    20190906_231434.jpg

    Here we see the CF card is detected but does NOT show up as a bootable disk option.

    CNTL - ALT - DEL, warm restart

    on this attempt we see

    20190906_231553.jpg

    Now, we see that the CF card is a bootable disk option. In fact I can just select the 80h drive and the machine boots no problem.

    20190906_231600.jpg

    As we see, the BIOS messages "Booting C>>C". Great this is how it should work every time!

    However,
    CNTL - ALT - DEL, warm restart

    Now, something different again.

    20190906_231627.jpg

    Now we see a new entry - Foreign Hard Disk - with some tiny size allocation - at 80h and the proper disk at 81h.
    When I select to boot from the 2nd entry I successfully boot, with the BIOS messages "Booting D>>C".

    The pattern repeats. Every time I reboot, another false entry is created and the proper disk moves down by 1 value.
    I can still boot the machine.

    20190906_231649.jpg

    I can restart the sequence by doing a hard power cycle including removal of the CF card.


    OK so - Does anyone understand what is going on, and how to correct this?

    THANKS!
    (the good news is that it is sort of working..)

    Leave a comment:


  • Chuck(G)
    replied
    FWIW, I've successfully run the XTIDE with 8 and 32 MB ancient CF cards. I think I've got a 2MB one somewhere around here...

    Leave a comment:


  • Twospruces
    replied
    Thanks,
    I do in general see XUB report the Cf card presence.
    I will try the load that includes the boot loader menu and see if I can get better control over boot up. Thanks

    Leave a comment:


  • Trixter
    replied
    Originally posted by Twospruces View Post
    Hi,
    I think what I need is for XUB to be much more verbose during boot up.
    - does it see the CF card?
    This already happens. You should see two lines that look like this (sample, your values may be different):

    Code:
    Master at 300h: TRANSCEND
    Slave  at 300h: Not Found
    If you're not seeing this, you have a fundamental issue that needs to be corrected first. Your boot-up screen should at least contain the first seven lines of something like this: http://wiki.sensi.org/images/pcemhd.jpg

    - does it correctly read the MBR? what is the MBR content?
    If the MBR can't be read, I believe XUB prints a single letter error code. You can look in the source for what the code represents.

    Leave a comment:


  • Twospruces
    replied
    Hi,
    in the XTIDE hardware thread I have been describing a problem I am having getting a custom XT-CF Version 2 lite card working in a Zenith Z-171.

    I think what I need is for XUB to be much more verbose during boot up.
    - does it see the CF card?
    - does it see the partition?
    - does it correctly read the MBR? what is the MBR content?
    - does it read the format of the partition correctly?
    - can I get full manual control over the boot up process?

    Do I need to roll up my sleeves and get ready to compile my own variant of XUB or is there an easy way to see what's going on during XUB boot up?

    thx

    Leave a comment:


  • maxtherabbit
    replied
    Originally posted by pikadroo View Post
    I can't seem to find any mention of a problem I am having with floppy drives, so here it is maybe someone can help.

    With the XTIDE bios installed I am unable to format floppies due to a "Invalid media or Track 0 bad - disk unusable" error. My system is probably an extremely rare Cumulus brand 386SX with a built in phoenix bios that has limited IDE support. All version of the XTIDE bios in v2 will boot a CF card just fine into DOS 6.22 on this computer, it works so great I can't even believe it. The floppy format problem only occurs in v2 beta 2 and v2 beta 3 however, I can format floppies when I use v2 beta 1 just fine. If the XTIDE bios is removed from the computer formatting floppies works just fine.

    Thanks!
    -Drew
    Funny I ran into the same thing, builds of XTIDE BIOS for AT systems have the issue, but those for XT+ systems do not. I'm looking over the SVN now and it looks like these beta 2 and beta 3 builds are now woefully obsolete. This was probably already fixed but the situation with hosting the code for this project is a hot mess. I'm going to try to build the latest revision of the source available on google code and see what that does.

    Leave a comment:


  • pikadroo
    replied
    I can't seem to find any mention of a problem I am having with floppy drives, so here it is maybe someone can help.

    With the XTIDE bios installed I am unable to format floppies due to a "Invalid media or Track 0 bad - disk unusable" error. My system is probably an extremely rare Cumulus brand 386SX with a built in phoenix bios that has limited IDE support. All version of the XTIDE bios in v2 will boot a CF card just fine into DOS 6.22 on this computer, it works so great I can't even believe it. The floppy format problem only occurs in v2 beta 2 and v2 beta 3 however, I can format floppies when I use v2 beta 1 just fine. If the XTIDE bios is removed from the computer formatting floppies works just fine.

    Thanks!
    -Drew

    Leave a comment:


  • Krille
    replied
    Originally posted by Trixter View Post
    Okay, full test results follow. The new M24/6300 code is definitely a small improvement, and running the NEC code on an NEC V30 is an additional improvement.
    Thanks for testing Jim, I hope you get the machine in working order again.
    Originally posted by alecv View Post
    XT IDE Universal BIOS bug?
    Nope. Make sure that the MFM controller is not configured for two drives (check jumper settings).

    BTW, on a slightly related note, have you tried the new MODULE_MFM_COMPATIBILITY?

    Leave a comment:


  • alecv
    replied
    XUB does not boot disk formatted by ADM.
    I've found a bit newer version of ADM (at warez site, sorry)
    http://old-dos.ru/files/file_887.html

    Leave a comment:


  • Malc
    replied
    I've not heard of MITAC ADM v1.0 before, Got a link ?, What version of DOS are you running, What does FDISK say about that partition ?.

    Leave a comment:

Working...
X