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

  • Malc
    replied
    128Mb is plenty, 32Gb is a waste, You could always have an internal 128Mb drive and an 128Mb accessible from the rear, That's how i have mine setup, With the XUB you can boot from either if you wanted to or just use the rear one for file transfer, What revision of the XUB have you got on it now.

    Leave a comment:


  • PePe-fr
    replied
    Well, there seems to be no problem anywhere.

    The strange thing is that 1 card works out of 3. I managed to make a 128Mb Sandisk work perfectly, and still have the same FAT corruption for every write attempt I do on the two other ones (Sandisk 32Gb and Transcend 256Mb).

    At this point, I will consider that there is some kind of incompatibility between my particular machine (it's a clone... a very undocumented one) and larger than 128Mb storages. The seller of the IDE board was able to test it with large cards, and I managed to partition, format and copy files on my biggest card using a Pentium 1.

    I'll consider the case as solved for now, sell my 2 big cards and buy a second Sandisk 128Mb just in case !

    Thanks for your help, this allowed me to conduct good tests and understand how all this works as I'm a newbie with retro-computing even if I used this particular XT for years before phasing it out !

    Leave a comment:


  • PePe-fr
    replied
    Using Check-It v3 with the IDE card in the computer (no other choice due to the size of the program), I observed nothing abnormal using the "base memory map" tool :

    In reserved memory, I have :

    B800h to BC00h : CGA Video RAM
    BC00h to C000h : Hi RAM (don't have a clue on what it is really)
    C000 to C800h : nothing
    C800h to CA00h : Disk RAM (the IDE card, the 84 first bytes confirm it)
    CA00h to F400h : nothing
    F400h to 0000h(!) : System ROM (BIOS dated 12/23/83)

    I also have data on the conventional memory if needed, and on the block and character devices (DOS stuff ?).

    Leave a comment:


  • PePe-fr
    replied
    Argh.

    The EXE itself weights 343Kb... will never fit on a floppy to make a test without the IDE card installed.

    Leave a comment:


  • dJOS
    replied
    Try CheckIt 3.0, it's got this handy feature.

    Leave a comment:


  • PePe-fr
    replied
    Thanks.

    So all I need to find is a "tool" which maps the memory, at least to tell me which areas have data in them.
    In that way I could make a mapping after unmounting the XTIDE card, and watch if somebody did write in the area(s) of interest ?

    And then remove parts until the memory area is free again ?

    Here are the card's adress requirements :

    Code:
        Resource requirements:
            IO ports 300-31Fh
            ROM: 32KB at C800h or D800h

    Leave a comment:


  • modem7
    replied
    Originally posted by PePe-fr View Post
    If I sum up, there is NO IRQ for the XTIDE board, and thus no risk of IRQ conflict.
    But, there may be (or not) a conflict with the memory address used by the board.
    The XT-IDE uses both a range of memory addresses (for the ROM/EEPROM) and a range of I/O addresses.
    Either, or both, could potentially conflict with something else.
    Diagram at [here].

    Leave a comment:


  • PePe-fr
    replied
    Yup.

    I found an old floppy with DOS 2.11, using TIMER v1.2 to set and use this RTC chip.

    Here is data about the memory where the soft searches for the data from the RTC :

    Code:
    --------------------------- 
    PC Timer - version 1.2
    --------------------------- 
    
    Changes:
    Hundredths and Tenth of seconds usage supported
    Day of Week supported
    Base port list changed
    Base Ports: 0x240, 0x0C0 (auto scanned)
    Chip port addressing: direct, 16 ports
    Chip: NS MM58167 (UMC UM82C8167)
    
    Ports map (offset from base port):
    +0x01 Counter - Hundredths and Tenth of seconds. (bcd, 0x00..0x99)
    +0x02 Counter - Seconds (bcd, 0x00..0x59)
    +0x03 Counter - Minutes (bcd, 0x00..0x59)
    +0x04 Counter - Hours (bcd, 0x00..0x23)
    +0x05 Counter - Day of week (bcd, 0x01..0x07) (0x01 - Sun, 0x02 - Mon … 0x07 - Sat)
    +0x06 Counter - Day of month (bcd, 0x01..0x31)
    +0x07 Counter - Month (bcd, 0x01..0x12)
    +0x08 RAM - used as following - (0x90-JAN, 0xA0-FEB,0xB0-MAR,0xC0-APR,0xD0-MAY,0xE0-JUN,0xF0- all other months). 
    +0x09 RAM - used as year storage (bcd, 0x00..0x99)
    No conflict here, apparently.

    If I sum up, there is NO IRQ for the XTIDE board, and thus no risk of IRQ conflict.
    But, there may be (or not) a conflict with the memory address used by the board.
    Last edited by PePe-fr; August 15, 2018, 06:29 AM.

    Leave a comment:


  • modem7
    replied
    Originally posted by PePe-fr View Post
    ...(there is "system timer" at IRQ0 but it must be another timer as it appears even with the controller off).
    The system timer referred to, is on the motherboard, and is not a clock.

    You should refer to the clock on your card as a clock, or RTC.

    Leave a comment:


  • modem7
    replied
    Originally posted by PePe-fr View Post
    Anyway, I still have too much questions about Xtide and the way it works (for example, I read everywhere that there is no DMA and thus no need for an IRQ, however I see that IRQ 5 in CheckIt is taken by "Fixed Disk"... what's this ?)...
    The diagram at [here] represents in the normal (but there are variations, such as the XT-IDE). In an XT-class computer, IRQ 5 is normally used by an XT-class hard disk controller.

    But that is not concrete. For example, I could create my own custom card (e.g. part of an alarm system), designing it to use IRQ 5, and creating matching software that gets called when the card generates IRQ 5. I would be asking for trouble though if I put that card into a computer that already had a card using IRQ 5.

    In an XT-class computer, all CheckIt can do is detect that there is software (in RAM or ROM) that will be executed if a card generates IRQ 5. But it cannot work out which card it is. I am sure that Checkit is simply making an assumption: "I am running on an XT-class computer, and IRQ 5 is in use. Therefore, IRQ 5 must be in use by a hard disk controller."

    Leave a comment:


  • PePe-fr
    replied
    Yes, J22 and 23 are serial ports. Only J22 is connected (as COM2 is disabled) on my machine.

    I had my motivation torn into pieces yesterday night... After my first tests, it really looked like if this timer part of the card was creating the problems.
    I reactivated it and put one of my larger cards and the FAT blew up as always (after some time, that was curious because at once I could write on the larger CF cards for the first time).

    Then I deactivated this time once more and... well the cards (256Mb one) continued to blow up when writing on it.

    Anyway, I still have too much questions about Xtide and the way it works (for example, I read everywhere that there is no DMA and thus no need for an IRQ, however I see that IRQ 5 in CheckIt is taken by "Fixed Disk"... what's this ?)...

    Leave a comment:


  • Malc
    replied
    I wouldn't go adding to much into the system until i was completely happy with it, Can you boot from the CF cards that work, Have you got any other floppy controllers you could try, I have used 1Gb and 2Gb cf cards in my 5160 before with no problems.
    Originally posted by PePe-fr View Post
    Well. It’s not perfect as I’m still having trouble with 2 of my 3 cf cards.

    I have a SanDisk with 128 mb which gives good results and allowed me to copy multiple programs to my modern PC for backup.

    I’ll be happy with it for now ! Perhaps that larger cf cards are just too big for this XT.

    Thanks again, I’ll open a new thread about the possible optimisations later (I already have a math coprocessor underway).

    Leave a comment:


  • hornbetw
    replied
    J22 & J23 are probably for 25 pin serial ports.

    Tom

    Leave a comment:


  • PePe-fr
    replied
    Well. It’s not perfect as I’m still having trouble with 2 of my 3 cf cards.

    I have a SanDisk with 128 mb which gives good results and allowed me to copy multiple programs to my modern PC for backup.

    I’ll be happy with it for now ! Perhaps that larger cf cards are just too big for this XT.

    Thanks again, I’ll open a new thread about the possible optimisations later (I already have a math coprocessor underway).

    Leave a comment:


  • PePe-fr
    replied
    I did conduct various tests :

    Test 1 :

    Disabled :
    LPT+Gameport
    Serial
    Timer

    => SUCCESS

    Test 2 :

    Enabled :
    LPT+Gameport
    Serial

    => SUCCESS

    Will now work on the timer : enable to check that the problem is still there, and try to work on the IRQ setting if it can be of interest ?



    Your help was invaluable in this work.

    Leave a comment:

Working...
X