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

  • PePe-fr
    replied
    Yes, the CF Card is recognized by the adapter (correct name).

    I checked and the correct command to clean all the disk (0 to avery byte of it) is CLEAN ALL, as you wrote.

    After this operation, I was able to start FDISK (without /MBR, as asked), but the XT still freezes when selecting the option 1 (create a primary partition).

    The screen draws as shown, but is incomplete and freezes in that state :

    FDISK-hang2.jpg

    Leave a comment:


  • Malc
    replied
    Don't use the /MBR switch, Do a complete wipe of the CF card, IIRC in diskpart just typing "Clean" doesn't wipe the CF completely, I think the command is "clean all" ?, You will have to confirm that i don't use diskpart. When the XUB initializes does it show the name of the Compact flash card.

    Leave a comment:


  • PePe-fr
    replied
    Following djOS and Malc advices, I made a bootable DOS5 floppy, with FORMAT and DISKPART on it.
    I cleaned my "Industrial CF300" Transcend 256Mb CF card, using diskpart under Windows 10.
    I fired up the XT, booted with the floppy, typed FDISK /MBR and...

    Code:
    Error reading fixed disk. The master code has NOT been updated.
    A>
    A FDISK command without the MBR flag gives a similar result with a different message.

    It darkens !

    Leave a comment:


  • Malc
    replied
    Originally posted by dJOS View Post
    This isn't a problem, I've even done it with Mac's and not had any issues.
    Yup i do it all the time using my XP PC to transfer DOS files to the CF card and then plug the CF card back into my XT or other PC's with no issues

    Leave a comment:


  • dJOS
    replied
    Originally posted by PePe-fr View Post

    A question, even if it's off-topic with the XTIDE question : is it forbidden to plug the CF card you use in your old machine on a new machine, to add stuff on it ? Do you do it or is it a good way to mess everything up ?

    Thanks.
    This isn't a problem, I've even done it with Mac's and not had any issues.

    Leave a comment:


  • PePe-fr
    replied
    I discarded 6.22 (which is however the version of MS-DOS I used the most in my life) because of the minimum RAM required, and the lack of 5.25 300k floppy images out there.
    I'll try with a DOS5 boot floppy.

    A question, even if it's off-topic with the XTIDE question : is it forbidden to plug the CF card you use in your old machine on a new machine, to add stuff on it ? Do you do it or is it a good way to mess everything up ?

    Thanks.

    Leave a comment:


  • Malc
    replied
    Originally posted by PePe-fr View Post
    EDIT : I'm going with DOS 3.3 due to a shortage of all-good floppies. DOS 3.3 takes 2 of them.

    Here is where it hangs (FDISK /MBR, Create Primary partition and said NO to use all the space... so it hangs just when it should be asking for the partition size I want).
    The /MBR switch is not supported in DOS 3.3, It was introduced in DOS 5 >, Normally you shouldn't need to use the /MBR switch, Like djos said use DOS 5, My preference is DOS 6.22 but that's me, I use it on all my old PC's, Or get a smaller CF card.

    Generally it's recommended to partition and format on the computer you intend to use the adapter / CF card in.

    Leave a comment:


  • dJOS
    replied
    Originally posted by PePe-fr View Post
    Thanks !
    I was able to update the BIOS to the latest version.

    Now I have to start over with a fresh install, and hopefully a successful fdisk.
    My previous install (still made with a VM) is still read-only on my XT.

    EDIT : I'm going with DOS 3.3 due to a shortage of all-good floppies. DOS 3.3 takes 2 of them.

    Here is where it hangs (FDISK /MBR, Create Primary partition and said NO to use all the space... so it hangs just when it should be asking for the partition size I want).
    [ATTACH=CONFIG]47252[/ATTACH]

    I will let him alone several hours, to see if it's the low clock speed and the massive card size (256 Mb) which cause such a lag... and to see if it wakes up one day or another !
    DOS 3.3 cant handle such a "large" drive, I recommend you use DOS 5.0 to partition it.

    Leave a comment:


  • PePe-fr
    replied
    Thanks !
    I was able to update the BIOS to the latest version.

    Now I have to start over with a fresh install, and hopefully a successful fdisk.
    My previous install (still made with a VM) is still read-only on my XT.

    EDIT : I'm going with DOS 3.3 due to a shortage of all-good floppies. DOS 3.3 takes 2 of them.

    Here is where it hangs (FDISK /MBR, Create Primary partition and said NO to use all the space... so it hangs just when it should be asking for the partition size I want).
    fdisk-hang.jpg

    I will let him alone several hours, to see if it's the low clock speed and the massive card size (256 Mb) which cause such a lag... and to see if it wakes up one day or another !
    Last edited by PePe-fr; August 11, 2018, 03:43 PM.

    Leave a comment:


  • Malc
    replied
    Originally posted by PePe-fr View Post
    Oups. No autoconfig, just flashed.

    Is it Ok to do an autoconfig with the Xtide tool even if I have a lo-tech card ?
    Yes, You Must configure the XUB first using XTIDECFG.COM before flashing, Configure the bios for your lo-tech card, Hit the "Auto configure" button in xtidecfg.com is easiest unless you want to configure manually and save changes back to the file, And use the lo-tech flash utility to flash the eeprom.

    Leave a comment:


  • PePe-fr
    replied
    Oups. No autoconfig, just flashed.

    Is it Ok to do an autoconfig with the Xtide tool even if I have a lo-tech card ?

    Leave a comment:


  • dJOS
    replied
    Have you actually run the auto config, saved the config to file and written that file to the eeprom?

    Leave a comment:


  • PePe-fr
    replied
    Here are some news :

    Update of XTide : The R598 was flashed correctly, but I got this message on POST, along with a double-beep :

    Code:
    System Error #20, Continue?
    I reverted to R591, it started correctly then.

    I had managed to get a "working" configuration with 3 partitions... C: with DOS (not bootable and probably not writable since I had an error previously, but with DOS files accessible), D: with some games (to test the computer, joystick... worked nicely) and E: with a copy of C: content.
    I used 3 or 4 times, in conjunction with a floppy to start DOS 5.0 and was able to make some tests.

    I fired up FDISK /MBR to try to make the C: partition bootable again and... after reboot had no more C, D or E drives. Plugging the CF Card under Windows confirmed the problem : only one "RAW" volume is now visible in the Windows partition editor.

    I guess that my drives are once more gone. I really don't have any ideas anymore.

    To sum up what I tried :

    * Partition, and install from a RAW drive and a VirtualBox machine : worked, but MBR/FAT blews up after some (short) time in the XT
    * Partition from the XT : FDISK hangs when trying to create a partition
    * Update XTide to R591
    * 2 CF-Cards tested : Transcend 256Mb and Sandisk 32 Gb, same results.

    My configuration :
    * IBM XT Clone (made by a Singapore brand, called Syntax), the BIOS is from 1984.
    * This card and adapter :p.jpg
    * The cards listed above

    Leave a comment:


  • PePe-fr
    replied
    Thanks !

    I'll update to r598 now.
    Anyway, even if deleting the remnants of any partition on the CD Card was straightforward using diskpart, the XT still hangs when I try to create a partition using FDISK (XT clone and DOS 5.0).

    I was never able to partition any CF Card (tried 2) from my XT, as FDISK never let me create anything (I can view partitions and delete them, anyway).

    Leave a comment:


  • retro-pc_user
    replied
    There's a version r598 (the r599 and r600 don't have the XT, AT, or 386 ROM files, just only tiny) on the XTIDE Universal BIOS page: http://www.xtideuniversalbios.org/bi...versions/r598/

    Leave a comment:

Working...
X