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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    From the latest on SVN, revision 561.
    Building a BIOS for a 5160 XT, I removed options MODULE_SERIAL, MODULE_SERIAL_FLOPPY,
    and ELIMINATE_CGA_SNOW, and added MODULE_BOOT_MENU.

    When it boots up the menu flashes up for an instant and disappears.
    The Timeout doesn't show up in the configure pgm.

    Any idea why?

    Thanks,
    Bill

    Comment


      Are you using the latest build xtidecfg, The "Selection Timeout" for the Boot Menu is under "Boot Settings"

      I use the Hotkey bar but i just rebuilt the bios on my XT 5160 to use the Boot Menu and it worked fine, I don't use MODULE_SERIAL, MODULE_SERIAL_FLOPPY in my builds as i have no use for them but i leave ELIMINATE_CGA_SNOW in, I removed MODULE_HOTKEYS and added MODULE_BOOT_MENU back in and rebuilt the bios r561.

      Originally posted by wrljet View Post
      From the latest on SVN, revision 561.
      Building a BIOS for a 5160 XT, I removed options MODULE_SERIAL, MODULE_SERIAL_FLOPPY,
      and ELIMINATE_CGA_SNOW, and added MODULE_BOOT_MENU.

      When it boots up the menu flashes up for an instant and disappears.
      The Timeout doesn't show up in the configure pgm.

      Any idea why?

      Thanks,
      Bill

      Comment


        Yes, I had rebuilt the xtidecfg pgm. I wasn't sure if it shared settings with the other makefile.

        I changed my build options to remove the MODULE_HOTKEYS and now it works.

        One other possible issue, in the previous attempt, I had read the exiting config fro the old
        Flash before reconfiguring. Not sure if that affects the options it saw from the
        ROM vs. the newly read-from-disk ROM image.

        Thanks for your post -- it got me going.

        Originally posted by Malc View Post
        Are you using the latest build xtidecfg, The "Selection Timeout" for the Boot Menu is under "Boot Settings"

        I use the Hotkey bar but i just rebuilt the bios on my XT 5160 to use the Boot Menu and it worked fine, I don't use MODULE_SERIAL, MODULE_SERIAL_FLOPPY in my builds as i have no use for them but i leave ELIMINATE_CGA_SNOW in, I removed MODULE_HOTKEYS and added MODULE_BOOT_MENU back in and rebuilt the bios r561.

        Comment


          Originally posted by Malc View Post
          I removed MODULE_HOTKEYS and added MODULE_BOOT_MENU back in and rebuilt the bios r561.
          Originally posted by wrljet View Post
          I changed my build options to remove the MODULE_HOTKEYS and now it works.
          MODULE_HOTKEYS and MODULE_BOOT_MENU are supposed to work together but you guys are saying they don't? Am I reading this correctly?
          Looking for a cache card for the "ICL ErgoPRO C4/66d V"

          Comment


            I don't include both as i mainly just use the Hotkey bar now, But i just rebuilt and included both and it does seem to be working, The only thing i did notice is: Press F2 and the boot menu pops up as normal and the " A " drive is highlighted, If i leave it as is and press Enter the machine boots to the " C: " drive as configured in xtidecfg, But if i move it down to the " B " drive and back up to " A " press enter and the machine boots from the A: drive fine, Apart from that it seem's to be working fine.

            Originally posted by Krille View Post
            MODULE_HOTKEYS and MODULE_BOOT_MENU are supposed to work together but you guys are saying they don't? Am I reading this correctly?

            Comment


              Didn't work for me, but perhaps as I mentioned above, when it didn't work I had read the existing config
              off the EEPROM that was built with another set of options. I haven't retried that build yet with a fresh config.
              Last edited by wrljet; July 15, 2013, 05:19 AM.

              Comment


                Originally posted by Malc View Post
                The only thing i did notice is: Press F2 and the boot menu pops up as normal and the " A " drive is highlighted, If i leave it as is and press Enter the machine boots to the " C: " drive as configured in xtidecfg, But if i move it down to the " B " drive and back up to " A " press enter and the machine boots from the A: drive fine
                This should now be fixed in r562.

                Comment


                  Originally posted by wrljet View Post
                  when it didn't work I had read the existing config
                  off the EEPROM that was built with another set of options.
                  XTIDECFG does not allow to read old settings if they are no longer compatible but it is determined by comparing version information. It is very much possible that I have changed something and forgot to change version information. So it is most likely that reading old settings caused the problems.

                  Comment


                    Originally posted by aitotat View Post
                    XTIDECFG does not allow to read old settings if they are no longer compatible but it is determined by comparing version information. It is very much possible that I have changed something and forgot to change version information. So it is most likely that reading old settings caused the problems.
                    Yeah, I figured that was probably a dumb mistake on my part, but it didn't occur to me until I had already blown the second new build into the EEPROM and configured it from scratch (which worked).

                    Comment


                      Hello,

                      I have an old Commodore 386SX-25 with a 40 MB hard disk. I replaced it with a Quantum 20 GB, installed the Universal BIOS of course, and was able to fdisk and format the drive. But the computer won't boot from it. Once booted from a floppy I'm able to see and use the C drive. Then I found a 4 GB and things worked as it should.

                      The obvious questions:
                      - does anybody know why the 20 GB doesn't boot?
                      - does anybody how to get it to work?

                      Thank you very much for any help!

                      Kind regards, Ruud Baltissen
                      www.Baltissen.org
                      With kind regards / met vriendelijke groet, Ruud Baltissen
                      www.Baltissen.org

                      Comment


                        Hi,
                        Maybe a silly question but did you set the primary partition as active if yes do you have all the system files on your drive. I suppose you installed DOS, are you?

                        Cheers,
                        diskers

                        Originally posted by RuudB View Post
                        Hello,
                        I have an old Commodore 386SX-25 with a 40 MB hard disk. I replaced it with a Quantum 20 GB, installed the Universal BIOS of course, and was able to fdisk and format the drive. But the computer won't boot from it. Once booted from a floppy I'm able to see and use the C drive. Then I found a 4 GB and things worked as it should.

                        The obvious questions:
                        - does anybody know why the 20 GB doesn't boot?
                        - does anybody how to get it to work?

                        Thank you very much for any help!

                        Kind regards, Ruud Baltissen
                        www.Baltissen.org

                        Comment


                          PS. You won't be able to get a single partition above 4GB when using FAT16. For bigger partitions you should use FAT32.

                          Comment


                            Originally posted by diskers View Post
                            PS. You won't be able to get a single partition above 4GB when using FAT16. For bigger partitions you should use FAT32.
                            I'm already happy with a system disk of 50 MB and a data disk of 500 MB.
                            The reason I use these big hard disks is quite simple: I have more than enough of them. I wished I had more of the smaller ones.

                            Kind regards, Ruud Baltissen
                            www.Baltissen.org
                            With kind regards / met vriendelijke groet, Ruud Baltissen
                            www.Baltissen.org

                            Comment


                              Originally posted by diskers View Post
                              Maybe a silly question but did you set the primary partition as active if yes do you have all the system files on your drive.
                              Weird, it seems my first answer is missing.
                              Anyway, I did. But I just took a 40 GB disk and gave that one a try as well. And... that one worked W/O any problem. So one would expect the 20 GB drive to be faulty. But that one now works flawlessly in a Pentium-III system.
                              Whatever it was, the original problem is solved and that matters. I can only thank you (and all who read this thread) for your time!

                              Kind regards, Ruud Baltissen
                              www.Baltissen.org
                              With kind regards / met vriendelijke groet, Ruud Baltissen
                              www.Baltissen.org

                              Comment


                                I ran into another problem. I wanted to install Netware 3.12 and the install program says there is no hard disk present. I told the setup of the computer there isn't a hard disk present. If that is where the install programs looks for the HD, it has a point. So I just picked the biggest one and restarted the computer. Now the Universal BIOS was acting a bit strange: it said there was a foreign HD at 80 and the real one was found at 81. Booting from 81 worked fine except I got a D drive that was the same one as C. And E was what first used to be D. But Netware was stil complaining there was no HD.
                                In the end I picked a 4 GB one and told the Commodore it was a 233 MB HD. I partioned and formatted it and the install program found no trouble for the rest.

                                Is this a known issue, or maybe new? Is there something I can do to get around this problem?

                                I hope to hear from you. Any advise, info or request to test something is welcome!

                                Kind regards, Ruud Baltissen
                                www.Baltissen.org
                                With kind regards / met vriendelijke groet, Ruud Baltissen
                                www.Baltissen.org

                                Comment

                                Working...
                                X