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

  • Filter
  • Time
  • Show
Clear All
new posts

    Beta-3 is very old. Please use this pre-configured BIOS image, or build from source yourself from R566.


      Is there a checksum for the pre-configured image? Would help to insure the image isn't corrupted.


        Are you having problems with it?


          Nope. Just want to make sure the file loads into my programmer correctly. Back in the day when I programmed EPROMs with a commercial programmer, we always put the checksum on the sticker that went on the window. It came in handy when we weren't sure if an EPROM was corrupted or a file loaded into the programmer correctly.


            I built up an XT-CF-Lite v4 and flashed in the preconfigured Bios and it seems to work just fine with a Kingston 32MB card. Next project is an XT-IDE.
            Last edited by cbolvin; September 13, 2014, 06:28 PM.


              Originally posted by cbolvin View Post
              Next project is an XT-IDE.
              Are you going for the Vintage-Computer Rev 2 board? If you do, and you don't already have a high speed serial port, I would suggest adding the UART components. They don't cost very much and I've found it very useful.

              Good luck,



                Originally posted by SkydivinGirl View Post
                Are you going for the Vintage-Computer Rev 2 board? If you do, and you don't already have a high speed serial port, I would suggest adding the UART components. They don't cost very much and I've found it very useful.

                Good luck,


                Yep, Will add the extra parts. I bought two XT-CF-Lite V4 boards with enough parts to build both along with 2 bare XT-IDE-v2 boards. I still need to order the parts for those but I like fully populated boards.

                I just finished restoring my Compaq Portal Plus (General clean up, LL format the ST225 HD and rebuild keyboard) and tested the XT-CF-Lite in it. Ultimately it'll go into the other portable (dual floppy) but the system board is giving me fits at the moment. It was working up until a week or so ago then decided to throw ROM errors. Still trying to diagnose the problem.



                  I didn't see it in the manual, but does this new BIOS support 2.4MB floppy drives?


                    Originally posted by olePigeon View Post
                    I didn't see it in the manual, but does this new BIOS support 2.4MB floppy drives?
                    You probably want to ask that in a thread about the XT-FDC:


                    I think you mean 2.88mb drives, and depending on the controller you choose to build with, the answer is yes. But, I'm not an expert.
                    -----[ Al ]-----

                    3 - TRS-80 Model I, TRS-80 Model 4D, LNW-80 Model I, Coco, 3 - Coco 2, Coco 3, 2 - Tano Dragon 64, C64, C64c, C128, 2 - Atari 800XL,
                    Atari 520-ST, Atari Mega-2 ST, Amiga 1000, TS-1000, TS-2068, ZX-Spectrum, IBM 5150, 2 - Apple ][gs, Laser 128, and a butt load of Macs and Intel PCs.


                      sorry i kinda disappeared on you any new releases?

                      that last release in may fixed some bugs


                        Not sure if this is an XT-IDE Bios issue but here goes:

                        I've been experimenting using my P4 XP Home PC and Using a 128 Mb Compact Flash card and a cheap chinese USB card reader i can partition / Format and load Dos 6.22 on the CF card and make the partition active, I can boot from the card via USB into Dos no problems.

                        I take the CF Card and plug it into a CF card adapter in my 486 box which is running the latest R567 bios and the machine boots up into Dos no problems.

                        Now here's the problem, I take the same CF card from my 486 box and plug it into my IBM XT 5160 which is also running the latest bios R567, I turn on the machine and i get " Missing operating System " ?

                        Now if i partition / Format and load Dos using the 5160 i can take the card and put it in my 486 and the USB card reader on my P4 and it boots into Dos no problems.

                        As i said i'm not sure if this is a bios issue but any idea's ?



                          Try FDISK/MBR. Many times that will take care of the 'Missing operating System' message.
                          PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step


                            Thanks but didn't work, just hangs at " Booting C: " now, Tried " sys c: " also but no difference, I'll try building a new bios for the XT, Can't think what else to try at the mo.


                              You need to do "fdisk /mbr" on the XT, so that XT-compatible boot code is written to the MBR. The hang you're experiencing is boot code that doesn't run on on an XT (ie. uses 286 or later CPU instructions).
                              Offering a bounty for:
                              - A working Sanyo MBC-775 or Logabax 1600
                              - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)


                                Yup that's what i did, " fdisk /mbr " and no joy.