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
    Originally posted by Holmes View Post
    I do have another CF adapter coming, but it's not here yet. I find it unlikely that something broke physically in my setup, as all these components were working a few days ago under 1.1.5. I guess I might have zapped something since then.

    Seems to me that something in R591 definitely works differently than 1.1.5. I do have other ide cables I can try.
    Many years ago one of my XT's with a R1 XT-IDE card developed a problem, At the time i think i changed the CF card for a bigger one 2Gb, I ran FDISK and partitioned the CF card, Rebooted and tried to format the card but failed, I ran FDISK again and there were no partitions defined, I went through the process again, Rebooted and again there were no partitions defined, The problem actually turned out to be one of the IC's on the card had gone faulty, I replaced the IC and have had no problems since.

    A few years ago on another XT of mine i upgraded the XUB to a newer revision and was getting all kinds of weird things happening, One minute it worked, Reboot and the CF card wasn't recognized properly, Reboot and the CF card was corrupted, That turned out to be the CF adapter decided to turn it's toes up, I've seen similar problems through bad connections.

    Leave a comment:


  • Holmes
    replied
    Originally posted by Malc View Post
    Sounds more like a hardware problem to me, Have you got another CF adapter you can try, Like Stone said try another CF card a smaller one, You could also try another cable.
    I do have another CF adapter coming, but it's not here yet. I find it unlikely that something broke physically in my setup, as all these components were working a few days ago under 1.1.5. I guess I might have zapped something since then.

    Seems to me that something in R591 definitely works differently than 1.1.5. I do have other ide cables I can try.


    Originally posted by Stone View Post
    Yes, it would help proportionately with the size of the drive.

    I was thinking a smaller CF... but it wouldn't hurt to try a smaller partition as that might be the root of all evil, here. Try something like 500 MB -- you'll never fill that up on a 5150 anyway. Or even smaller might be worthwhile. You know multiple partitions is not fatal!

    BTW, what DOS version are you using?
    I'm using MSDOS 5.0. I'll try a smaller partition. No I don't have any unused cf cards.

    Leave a comment:


  • Stone
    replied
    Originally posted by Holmes View Post
    That's true, I probably won't notice the speed difference, except for that horrendously long time DOS takes to measure the free space on the hard drive. But I guess reducing the size of the HD would help that, too!
    Yes, it would help proportionately with the size of the drive.

    Originally posted by Holmes View Post
    I didn't think reducing the size of the HD would make a difference with the problems I'm having. Are you saying get a smaller CF, or just make the partition smaller? Would that potentially fix my problem? I really don't want to buy another CF card.
    I was thinking a smaller CF... but it wouldn't hurt to try a smaller partition as that might be the root of all evil, here. Try something like 500 MB -- you'll never fill that up on a 5150 anyway. Or even smaller might be worthwhile. You know multiple partitions is not fatal!

    BTW, what DOS version are you using?

    Leave a comment:


  • Malc
    replied
    Originally posted by Holmes View Post
    Ok, I gave this a try. I ran wipedisk, then ran fdisk, partitioned for max which was 2gb, rebooted and checked partition and it was okay. Then I formatted and transferred system. Rebooted. Each time I rebooted, it detected cf okay and drive size was correct in the xtide menu.

    When I tried rebooting off c:, it froze after the "Booting C>>C" message. I rebooted off floppy and ran fdisk, and the partition is gone!

    Maybe I'll just go back to 1.1.5 and deal with it not being the fastest possible.
    Sounds more like a hardware problem to me, Have you got another CF adapter you can try, Like Stone said try another CF card a smaller one, You could also try another cable.

    Leave a comment:


  • Holmes
    replied
    Originally posted by Stone View Post
    I wouldn't think of that as your bottleneck when you're working with a 5150!

    BTW, why would you want 2 GB on a 5150? Don't you think that in 50 years it will still be 75% EMPTY? You might even have success with a smaller CF e.g., 1 GB or even much less.
    That's true, I probably won't notice the speed difference, except for that horrendously long time DOS takes to measure the free space on the hard drive. But I guess reducing the size of the HD would help that, too!

    I didn't think reducing the size of the HD would make a difference with the problems I'm having. Are you saying get a smaller CF, or just make the partition smaller? Would that potentially fix my problem? I really don't want to buy another CF card.

    Leave a comment:


  • Stone
    replied
    Originally posted by Holmes View Post
    Maybe I'll just go back to 1.1.5 and deal with it not being the fastest possible.
    I wouldn't think of that as your bottleneck when you're working with a 5150!

    BTW, why would you want 2 GB on a 5150? Don't you think that in 50 years it will still be 75% EMPTY? You might even have success with a smaller CF e.g., 1 GB or even much less.

    Leave a comment:


  • Holmes
    replied
    Originally posted by Malc View Post
    Try this, download WipeDisk and run it from a DOS boot floppy, reboot and run FDISK and partition the drive, Reboot and run FDISK again check that the drive was partitioned 2Gb or less.
    Ok, I gave this a try. I ran wipedisk, then ran fdisk, partitioned for max which was 2gb, rebooted and checked partition and it was okay. Then I formatted and transferred system. Rebooted. Each time I rebooted, it detected cf okay and drive size was correct in the xtide menu.

    When I tried rebooting off c:, it froze after the "Booting C>>C" message. I rebooted off floppy and ran fdisk, and the partition is gone!

    Maybe I'll just go back to 1.1.5 and deal with it not being the fastest possible.

    Leave a comment:


  • paperinik77pk
    replied
    Hi all, I'd like to tell you about a strange problem on my XT-CF rev2...it seems it does not write to CF master boot record.

    It starts, it detects drives and compactflash. I boot from floppy, then I try to fdisk the cf.
    Everything seems ok, but the led light stays on.

    I reboot as requested. When the floppy ends to boot, I try to format the drive. No disk present. Then I enter fdisk again and...no partition.

    This happens with an empty cf card. With an already formatted one the xt-cf boots and then i can do everything on it but writing.
    I create a folder,the led light is very bright, the folder is there but I cannot access it.

    I reboot the machine and the directory is not there anymore.

    FDISK /MBR gives the same result - led light and nothing happens.

    I have XTIDE BIOS R591 with boot menu, while previously the car had R567. Going back to 567 does not solve the problem.

    What do you think?
    Thank you in advance!
    Davide

    Leave a comment:


  • Malc
    replied
    Originally posted by Stone View Post
    Your XT has USB? Can you be more specific as to how? I use USB via DOS but even that requires a PCI card.
    I built one of the Lo-Tech experimental ISA - USB cards that uses the CH375B chip and WCH drivers, Works but a tad slow in the XT, Better in a 286 / 486.

    Leave a comment:


  • Stone
    replied
    Originally posted by Malc View Post
    That's what i've been doing for some time, Transferring from my XP box to my XT via CF, Though more recently it's been via USB
    Your XT has USB? Can you be more specific as to how? I use USB via DOS but even that requires a PCI card.

    Leave a comment:


  • Malc
    replied
    Originally posted by Holmes View Post
    .......I'll be using the CF as a transfer card to get stuff over to this PC.
    That's what i've been doing for some time, Transferring from my XP box to my XT via CF, Though more recently it's been via USB

    Leave a comment:


  • Holmes
    replied
    Originally posted by Stone View Post
    Everything was working fine before you tried this BIOS upgrade, wasn't it?
    Yes. If this whole upgrade thing doesn't work out, I'm thinking I'll have to go back to 1.1.5. One of the reasons I wanted to upgrade the BIOS is I wanted to do the Chuck speed update to my Rev1 card. Also, I wanted to make sure the CF drive layout was the most "compatible" with modern equipment, as I'll be using the CF as a transfer card to get stuff over to this PC.

    Leave a comment:


  • Stone
    replied
    Originally posted by Holmes View Post
    I actually want the CF on this machine, because it's a convenient way for me to transfer files back and forth.
    Everything was working fine before you tried this BIOS upgrade, wasn't it?

    Leave a comment:


  • Holmes
    replied
    Originally posted by Malc View Post
    Why did you run FDISK /MBR and then FDISK and partiton the drive. Try this, download WipeDisk and run it from a DOS boot floppy, reboot and run FDISK and partition the drive, Reboot and run FDISK again check that the drive was partitioned 2Gb or less.
    I wasn't sure if the physical disk layout changes with the new BIOS would cause a problem with the MBR, so I just recreated it, as it was a critical component of making the CF work in the first place. I presumed it wouldn't do any harm.

    OK, thanks for the link. I'll give it a try. So you think something got corrupted with the partition table?

    Originally posted by Stone View Post
    Another reason why I prefer DOMs over CFs.
    I actually want the CF on this machine, because it's a convenient way for me to transfer files back and forth.

    --------------------------------------------

    Is there anything on the actual configuration of the BIOS that could be messed up? I left it as default, and checked things over from a high level, and things looked okay, but I really don't know what I'm looking at with all the detailed settings.

    Leave a comment:


  • Malc
    replied
    Originally posted by Stone View Post
    Another reason why I prefer DOMs over CFs.
    I don't own any DOM's, Never had one, I've always used CF with no real problems.

    Leave a comment:

Working...
X