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

ISA All-Memory board

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

    ISA All-Memory board

    I was considering a relatively simple project in which 100% of the memory (both RAM and ROM) was on a single ISA card with a micro controller responding to these address ranges. This way, a non-functional motherboard could possibly be brought back to life if the fault was either with the RAM, ROM, or one of the associated control or data path ICs. The micro has more than enough memory and speed to support tho whole 640KB plus ROM images... It would be similar to my EPROM emulator project, except ISA-slot based and supporting more memory.

    The only complication would be how to disable the on-board data buffers for the RAM/ROM... One thought could be to socket the associated motherboard ICs and not populate them when using this card. Another could be to simply cut the buffer direction pin(s)... Something would need to be done to keep the motherboard buffers from conflicting with the All-Memory ISA card... Maybe someone has a better solution...

    Could possibly add a few ICs to implement XT-IDE as well.. or connectors for serial/parallel to match the AST six-pack functionality...

    Just brainstorming... There are a number of non-functional motherboards out there whose users are unable to debug which may end up scrapped. If there was a board which replaced the functionality of all off the motherboard's memory components, it could bring these systems back to life.

    #2
    Not to sound too negative, but are “hard-to-diagnose” memory component errors really that common of a failure mode for XT motherboards? Wholesale memory replacement shims have been pretty useful for machines like the Commodore PET where the correct 1970’s era chips are both really failure prone and hard to find, but the memory used in PC/XT class computers is still reasonably plentiful and the BIOS self test code usually is pretty good at at least hinting where the problem is.

    Also it might get really nontrivial to try to disable the onboard memory on any arbitrary clone machine. Some machines are going to have a single buffer with both memory and I/O devices behind it, which means you can’t just cut a direction pin, you’ll have to attack upstream of that. And newer machines might not have discreet circuitry that’s easily modified, you’ll have buffer enable signals emerging from an implementation using PALs or even a full-blown ASIC.
    My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

    Comment


      #3
      Putting aside the issue of catering for the applicable motherboard transceivers/drivers, I see that cards for ROM and RAM are at [here] and [here].

      As for catering for the applicable motherboard transceivers/drivers. Even for the IBM 5155 and 5160, where a jumper pad (E1) exists to do that catering for the ROM sockets, soldering is still required (to bridge E1). For the IBM PC family, circuit diagrams exist, and so users can be instructed on how to cater for the applicable motherboard transceivers/drivers via cutting/soldering. Problematic will be clone motherboards for which a circuit diagram has yet to be located.

      Comment


        #4
        I seem to remember somebody used a lo-tech ram board in a, i think it was a 5150, They disabled the onboard memory / circuitry and the 5150 worked fine using the lo-tech ram board, It was some time back, there should be a post on it somwhere on this forum. But as already mentioned clones / non-obtanium circuit diagrams would be a problem.
        Last edited by Malc; May 2, 2021, 11:07 PM.

        Comment


          #5
          Originally posted by Malc View Post
          I seem to remember somebody used a lo-tech ram board in a, i think it was a 5150, They disabled the onboard memory / circuitry and the 5150 worked fine using the lo-tech ram board, It was some time back, there should be a post on it somwhere on this forum.
          I found two threads about this here and here. The long and short of it is it does seem to be "possible" on the IBM hardware but there's actually more to it than just isolating the memory sockets, you also need to lobotomize the parity checking circuitry.

          Obviously the problem is going to get further complicated if you're looking at a "Turbo XT" clone, especially if it's one that uses an 8086 and/or has circuitry to run the expansion bus at a different speed from the CPU. The machine I specifically had in mind when I mentioned the possibility of there being a single buffer pinch point through which both I/O and memory drives the bus was a Tandy 1000-family machine; I actually figured out a way to override built-in ROM on that computer with memory on a card through a combination of a jumper wire to a pin on a (thankfully documented) PAL and abusing a proprietary DMA control line on the bus, so it's definitely a thing you can do if you have the documentation, but in the case of a machine that just has some bad RAM chips I'm not sure it's the optimal way to go.
          My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

          Comment


            #6
            Very interesting. It sounds like the LoTech board and a few motherboard mods can already cover what I was proposing. Well, at least for the 5156/5160... and uncertain if not impossible for clones with consolidated and/or undocumented data paths.

            I would suggest making a card which sat between the 8088 and its socket, but I don't think DMA would work at all in this case.

            Anyway, always fun to brainstorm and bounce ideas off form members!

            Comment


              #7
              Originally posted by Malc View Post
              I seem to remember somebody used a lo-tech ram board in a, i think it was a 5150
              The board was tested with a minimum RAM configuration in a 5150, I think 64KB but it should also work with 16KB on the board. As said, getting rid of all the system board RAM will need some modifications.

              Comment

              Working...
              X