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

EISA configuration .CFG file collection

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

    EISA configuration .CFG file collection

    Hi, I've been working on this list for a while now. Adapter description files for the MCA bus already have a home over at mcamafia.de. Well now there is a counterpart for EISA configuration files available here:

    http://108.59.254.117/~mR_Slug/EISA/

    There are 1,682 unique configuration files, however there are multiple versions of some files. For example Compaq made many updates to their config files. All of the different files are unique in some way. They are ordered by the file date. So if the latest version doesn't work you can try an earlier one. Some .CFG files may look identical, however the include files differ.

    Hope someone finds it useful.
    EISA .cfg Archive | Chip set Encyclopedia

    #2
    Wonderful collection. Is it available in a single zip file? :}

    Comment


      #3
      I can also give you CFG files. My CFG file collection contains also more than 1000 files incl. some necessary OVL files. Additionally I have different EISA configuration utilities: AMI_ECU, two versions of ASUS EISA utility and for Olivetti LSX 50xx series plus M486, CP486 plus many Olivetti special add on cards.

      Drop in a PN if you are interested. And I also would be interessted in a full ZIP of your collection. Thanks.
      Last edited by 1ST1; June 16, 2017, 02:27 AM.
      <album>

      Comment


        #4
        Originally posted by 1ST1 View Post
        Drop in a PN if you are interested
        PM sent.

        I can produce a tarball. Many of the Compaq include file are reused over and over. So they are in a hidden subdir "lib" and symbolic links are made to the relevant sections. I will have to regenerate it, as there have been some mods since I uploaded the tarball. I think it was about 250MB. Downside is you need to do it on a nix box.

        I have kept log file with the sources of each .cfg as well. However this wont make a huge amount of sense, without the sources archive. At the very least, all of: lin.fsid.cvut.cz, was included, Every Softpaq I could find. I also looked through ftp.bluefeathertech.com, and the website/ftp ?metropoli?. (sorry never can remember the name, its been around for ages), also ftp.isu.edu.tw.

        I have worked on the basis that, if I find a .cfg file that's bit-identical (also taking into account the include files), I always use the date of the older file(s), and discard the later dated version. For example some .cfg's included on the softpaq's never changed, so they only have one entry, with the file(s) date set to the oldest date.

        Some such as http://108.59.254.117/~mR_Slug/EISA/!CPQF140.CFG/, have multiple versions. Again, keep the the oldest, discard the newer. However in this case there have been many updates (changes) to the config files, so multiple versions are presented.

        There are some HP adapters, that as far as I can tell had .cfg's supplied only with a version of HP-UX. I dont know much about these. I am guessing they are adapters that only work with HP UNIX workstations with an EISA bus. Be good if someone could shed some light on this.

        Update:
        New files added from 1ST1.
        You can now download the whole thing as a tarball.
        Last edited by mR_Slug; June 17, 2017, 08:54 AM. Reason: new info
        EISA .cfg Archive | Chip set Encyclopedia

        Comment


          #5
          This is a very nice repository! Thanks for putting it together. A couple of questions/observatiosn:

          1. Was there a particular set of files/system/accessories you were going for? For example my Everex Step Megacube is not in your list.
          2. Some of the "CFG" files are just descriptor files for standard ISA cards - which is cool in its own way but will not obviously allow for automatic config of the board.

          I also have a few hundred CFG files laying around (Everex and G2K stuff plus misc. adapters) but unfortunately they are not sorted in any shape or manner. However, if you are interested I am happy to send them your way.

          p.s. Any chance of producing an archive for the DOS/Windows world? I am guessing most people using these would probably have a DOS (or early windows NT) machine to begin with.
          Current Wish List: 1. IBM 7531 Industrial Series PC 2. NEC MultiSync XL (JC-2001) Monitor 3. MicroSolutions UniDOS card 4. Compaq 14" VGA CRT Monitor (the one that came with the SystemPro). 5. Stacker HW CoProcessor Board MCA BUS. If you have any of the above for sale please PM me. Thank you!

          Comment


            #6
            This is truly amazing - I love this kind of project / labour of love. If you are taking donations, is there a particular way you would like people to submit contributions?
            Blog: http://brassicgamer.blogspot.co.uk/
            YouTube: https://www.youtube.com/channel/UCcG...mQsRIdX0Osb31Q

            Comment


              #7
              Originally posted by Shadow Lord View Post
              1. Was there a particular set of files/system/accessories you were going for? For example my Everex Step Megacube is not in your list.
              Not really any plan. I was originally looking for just one .cfg for a Proteon token ring card. I found it on driverguide. Since this is filled with malware, i started collecting them. Well it kinda morphed into looking for all of them. I found your thread on the Megacube, fascinating system. If you have the Step's .cfg PM me with a link. Please if possible include the original .zips/disk images.

              Originally posted by Shadow Lord View Post
              2. Some of the "CFG" files are just descriptor files for standard ISA cards - which is cool in its own way but will not obviously allow for automatic config of the board.

              I also have a few hundred CFG files laying around (Everex and G2K stuff plus misc. adapters) but unfortunately they are not sorted in any shape or manner. However, if you are interested I am happy to send them your way.
              It seems almost every ECU comes with nearly a hundred .cfg's for ISA. They are useful for EISA configuration (if they match the ISA card's jumper config) as they tell the ECU what resources are in use. Yes please, PM me with a link. (or just post to this thread)
              Originally posted by Shadow Lord View Post
              p.s. Any chance of producing an archive for the DOS/Windows world? I am guessing most people using these would probably have a DOS (or early windows NT) machine to begin with.
              Dont have any plans to, do you mean software or drivers?

              Originally posted by brassicGamer View Post
              This is truly amazing - I love this kind of project / labour of love. If you are taking donations, is there a particular way you would like people to submit contributions?
              Do you mean $'s or .cfg's? If you PM me with a link to any .cfg's i will try to
              add them.
              EISA .cfg Archive | Chip set Encyclopedia

              Comment


                #8
                Originally posted by Shadow Lord View Post
                2. Some of the "CFG" files are just descriptor files for standard ISA cards - which is cool in its own way but will not obviously allow for automatic config of the board.
                Yes, there are many for ISA cards. This is very important because the EISA config utility needs to know which ressources are used by manually configured cards. Otherwise it can not automatically setup the EISA cards without conflicts. There are CFGs for specific ISA cards like soundblaster or serial/parallel port cards which makes it quite easy to reserve these resources, I think some even show which jumpers/dip switches to set on the real card to get this config, and there is at least one generic ISA CFG which can be used for any other ISA card to reserve any adress range, IRQ, DMA, etc.

                @mR_Slug please also add all known EISA configuration utilities you have or got from me. Not every EISA PC will run with every setup utlity, for example the Olivetti LSX series can't be setup properly using the AMI-ECU. This is because Olivetti uses their utility to do also things other EISA PCs are doing with their BIOS setup, like configure harddisk type, floppy types, date/time, etc. I have forwarded you a version of AMI ECU, two customized versios from ASUS and the Olivetti EISA configuration utility. For example also Compaq used to have it's own tool.
                <album>

                Comment


                  #9
                  Compaq tended to use their "F10" Windows-like setup program on a hidden OEM partition to configure EISA cards..... at least on their later EISA machines.

                  Comment


                    #10
                    Originally posted by mR_Slug View Post
                    Not really any plan. I was originally looking for just one .cfg for a Proteon token ring card. I found it on driverguide. Since this is filled with malware, i started collecting them. Well it kinda morphed into looking for all of them. I found your thread on the Megacube, fascinating system. If you have the Step's .cfg PM me with a link. Please if possible include the original .zips/disk images.


                    It seems almost every ECU comes with nearly a hundred .cfg's for ISA. They are useful for EISA configuration (if they match the ISA card's jumper config) as they tell the ECU what resources are in use. Yes please, PM me with a link. (or just post to this thread)
                    I will contact you via PM and we can set something up. My CFG files came from FTP sites all over when I was originally looking for the Everex files. I also have a file that explains the format of the EISA cfg file and cfg file generator program.

                    Tarballs are hard to use/modify in the DOS world. A ZIP archive would be much easier to work with and to setup a mirror for most of us not running a *nix system.
                    Current Wish List: 1. IBM 7531 Industrial Series PC 2. NEC MultiSync XL (JC-2001) Monitor 3. MicroSolutions UniDOS card 4. Compaq 14" VGA CRT Monitor (the one that came with the SystemPro). 5. Stacker HW CoProcessor Board MCA BUS. If you have any of the above for sale please PM me. Thank you!

                    Comment


                      #11
                      Originally posted by 1ST1 View Post
                      @mR_Slug please also add all known EISA configuration utilities you have or got from me. Not every EISA PC will run with every setup utlity...
                      Yes, will get to it. I'll try and sort out all those files. Give me a few days.


                      Originally posted by Shadow Lord View Post
                      I also have a file that explains the format of the EISA cfg file and cfg file generator program.
                      That's great. Sorry I didn't hit refresh in the browser, before I replied to your PM. so I missed your post.
                      Originally posted by Shadow Lord View Post
                      Tarballs are hard to use/modify in the DOS world. A ZIP archive would be much easier to work with and to setup a mirror for most of us not running a *nix system.
                      The biggest problem on win/dos is the symbolic links. They save an inordinate amount of space. There is a text file in the root, called "log" or something, indicating all the sym-links.

                      Once I have added your files, and got all those ECU's sorted and up I'll do a zip, but even with compression it's going to be huge. I don't want to create a huge file for people to download, only for a week later, to say there is a new version.
                      Last edited by mR_Slug; June 22, 2017, 07:53 PM. Reason: missed post
                      EISA .cfg Archive | Chip set Encyclopedia

                      Comment


                        #12
                        Update:
                        (Double post, as i can't edit last post)

                        The source files with the various ECU's etc are now online. Link is on the main EISA page:
                        http://108.59.254.117/~mR_Slug/EISA/
                        EISA .cfg Archive | Chip set Encyclopedia

                        Comment


                          #13
                          Originally posted by mR_Slug View Post
                          Once I have added your files, and got all those ECU's sorted and up I'll do a zip, but even with compression it's going to be huge. I don't want to create a huge file for people to download, only for a week later, to say there is a new version.
                          Yeah, I can totally see that. I am not sure how much work this would be but maybe you have a base massive file and then monthly (quarterly updates)? I am guessing after the first few growth spurts you won't be adding huge number of cfg files to the collection. Just one or two here and there that could easily be handled as a small update archive...
                          Current Wish List: 1. IBM 7531 Industrial Series PC 2. NEC MultiSync XL (JC-2001) Monitor 3. MicroSolutions UniDOS card 4. Compaq 14" VGA CRT Monitor (the one that came with the SystemPro). 5. Stacker HW CoProcessor Board MCA BUS. If you have any of the above for sale please PM me. Thank you!

                          Comment


                            #14
                            Perhaps put it on Github?
                            Torfinn

                            Comment


                              #15
                              I like the tarballs with the symbolic links because it reduces a huge amount of data down to about 30MB. If anyone really needs a dir structure without symbolic links, you can just:

                              wget -m -np http://108.59.254.117/~mR_Slug/EISA/

                              I think if you do this, then when it's updated, run the same command again, it should skip files it has already downloaded.

                              If anyone really needs a .zip as it stands, before I add Shadow Lord's files let me know, and I can make one. And then when its updated I will make an update zip and a new full version.

                              I don't think it's really necessary to put it on Github. There are only about 5 people interested in this. Most .cfg's that are known to exist are there. As Shadow Lord points out I won't be adding updates often. Github is great for code, particularly open-source projects, but so far it looks like there will be one more update after Shadow Lord sends me his files.

                              <side note>
                              I really don't know how some of you cope without having access to at least one *nix box Take any little computer install Slackware, Debian or whatever, run it headless, and use PuTTY in windows to access the command line. So many useful utilities like tar, grep, Perl, etc. Or install cygwin on windows.
                              </side note>

                              BTW, one minor update, now when you go to a dir like this:
                              http://108.59.254.117/~mR_Slug/EISA/...FG/1992-05-22/

                              At the bottom there is a link to tar the whole directory, so downloading a .cfg with lots of include files is easier. It was originally there, but I accidentally deleted the functionality when trying to remove cruft from the directory before making the 30MB tarballs.
                              EISA .cfg Archive | Chip set Encyclopedia

                              Comment

                              Working...
                              X