Announcement

Collapse

Forum 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.


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.


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.



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.


"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.

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

386 motherboard with chipset OPTI 82C495XLC BIOS needed

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

    386 motherboard with chipset OPTI 82C495XLC BIOS needed

    Hello,

    Today i found old 386 board based on OPTI 82C495XLC chipset without EEPROM chip. But i found sticker around EEPROM panel:
    386 BIOS HI
    COPYRIGHT 1984- 90
    AWARD SOFTWARE INC


    BIG photo

    So, at internet i found two bioses for this chipset:
    1) http://chukaev.ru54.com/bios/3opm002.zip - AMI BIOS for 82C495XLC. I born into 27C512 and when MB starting i listen 9 long beeps.
    2) http://sannata.ru/bios/386DX/ROM3DX05.RAR - MR.BIOS(AMI?) for 82C495XLC. Starting only with ISA8 video card. If any ISA-16 (trident, realtek) inserted - no signal at monitor.

    I am searching for original BIOS for this motherboard...


    Thank you.

    #2
    The battery has leaked and corroded a large portion of that board. It's not likely to work no matter what BIOS is in it.
    PM me if you're looking for 3½" or 5¼" floppy disks. EMail “ ” For everything else, Take Another Step

    Comment


      #3
      Originally posted by Stone View Post
      The battery has leaked and corroded a large portion of that board.
      You right! I desolder battery, clean all around with C2H5OH then wather, then again C2H5OH and finaly blowdry. ~Five tracks were destroyed by corrosion. I desolder power connector, capacitors, one cache panel and other components for visualy control this tracks. Then I restore this tracks with small wires and solder all components to board. Power on and this motherboard start up with Trident ISA-16 video-card very well. Booted to DOS, start checkit memtest. All tests passed. This board work now with http://sannata.ru/bios/386DX/ROM3DX05.RAR BIOS.

      Thank you for answer!
      Attached Files

      Comment


        #4
        What kind of BIOS staff are these? Some sort of generic BIOS that works with many boards? I'm kind of interested in BIOS for a 386 board myself and wonder if any of those will do

        Comment


          #5
          Thank you for adding pictures of the repairs you made.

          Comment


            #6
            Originally posted by orion24 View Post
            What kind of BIOS staff are these? Some sort of generic BIOS that works with many boards? I'm kind of interested in BIOS for a 386 board myself and wonder if any of those will do
            Some 286/386/486 BIOS collections with chipset names:
            http://chukaev.ru54.com/bios_cs_en.htm
            386 BIOSes:
            http://sannata.ru/bios/386DX/
            http://sannata.ru/bios/386SX/

            Comment


              #7
              Originally posted by Tronix View Post
              Some 286/386/486 BIOS collections with chipset names:
              http://chukaev.ru54.com/bios_cs_en.htm
              386 BIOSes:
              http://sannata.ru/bios/386DX/
              http://sannata.ru/bios/386SX/
              I'll look into these when I've got time. The board is this one: http://museum.ttrk.ee/th99/m/S-T/31375.htm

              Comment


                #8
                Originally posted by Stone View Post
                The battery has leaked and corroded a large portion of that board. It's not likely to work no matter what BIOS is in it.
                Seems the OP got around the problem. Quite encouraging really for other restorations/repairs folk might like to undertake.
                Last edited by Caluser2000; September 22, 2014, 09:57 AM.
                Thomas Byers (DRI)- "You'll have a million people using the A> [MS-DOS prompt] forever. You'll have five million using [nongraphic] menu systems such as Topview, Concurrent PC-DOS, Desq, and those types. But there'll be 50 to 100 million using the iconic-based interfaces."

                Comment


                  #9
                  I'd like to have the award bios for opti 495 too. By the way, AMI and MR-BIOS should have a decent chance at working in your board as long as they are written for the opti 495 chipset.
                  "Will the Highways on the internets become more few?"

                  V'Ger XT

                  Comment


                    #10
                    Has anybody bothered to dump all the different BIOS for older 286-486 motherboards?
                    What I collect: 68K/Early PPC Mac, DOS/Win 3.1 era machines, Amiga/ST, C64/128
                    Nubus/ISA/VLB/MCA/EISA cards of all types
                    Boxed apps and games for the above systems
                    Analog video capture cards/software and complete systems

                    Comment


                      #11
                      Originally posted by Unknown_K View Post
                      Has anybody bothered to dump all the different BIOS for older 286-486 motherboards?
                      "Bothered" makes it sound like such a trivial task ... How much effort do you think it would be?

                      Start with the number of different motherboards for that time period. (1984 to maybe 1995) ? The number of chipsets is less than the number of different motherboards, but you have the additional challenge that these boards have to be in a good running state. And it's not enough to just dump the BIOS - you need a detailed description of each board, pictures, etc.

                      Comment


                        #12
                        Why do the boards need to be running, figured an eprom programmer could read them (are they copy protected)? TH99 would have the majority of board information and pictures. Sure it is work, but if a few people pitched in for the boards they have it might be manageable.
                        What I collect: 68K/Early PPC Mac, DOS/Win 3.1 era machines, Amiga/ST, C64/128
                        Nubus/ISA/VLB/MCA/EISA cards of all types
                        Boxed apps and games for the above systems
                        Analog video capture cards/software and complete systems

                        Comment


                          #13
                          Originally posted by Unknown_K View Post
                          Why do the boards need to be running, figured an eprom programmer could read them (are they copy protected)? TH99 would have the majority of board information and pictures. Sure it is work, but if a few people pitched in for the boards they have it might be manageable.
                          The BIOS could be read from a dead board but what if the BIOS is what killed the board? Flawed update or otherwise corrupted. Then everyone who installs that BIOS will have their boards stop working as well.

                          Comment


                            #14
                            Originally posted by krebizfan View Post
                            The BIOS could be read from a dead board but what if the BIOS is what killed the board? Flawed update or otherwise corrupted. Then everyone who installs that BIOS will have their boards stop working as well.
                            I don't know of any BIOS in that era that has a flashable chip. You would need to replace the chip you have with another, leaving the original intact. Sure the copy might be bad, but that is a chance you take doing any swapping.
                            What I collect: 68K/Early PPC Mac, DOS/Win 3.1 era machines, Amiga/ST, C64/128
                            Nubus/ISA/VLB/MCA/EISA cards of all types
                            Boxed apps and games for the above systems
                            Analog video capture cards/software and complete systems

                            Comment


                              #15
                              Originally posted by Unknown_K View Post
                              Why do the boards need to be running, figured an eprom programmer could read them (are they copy protected)? TH99 would have the majority of board information and pictures. Sure it is work, but if a few people pitched in for the boards they have it might be manageable.
                              I was not expecting an EPROM programmer would be required; the BIOS can generally be dumped by using DEBUG commands. And that requires a running system.

                              If you want to make an EPROM programmer required, then yes, the boards do not need to be running. But that's a higher hurdle.


                              Mike

                              Comment

                              Working...
                              X