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

Unique S-100 computer (Z-80/Vector Graphic/Micropolis)

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

    #16
    Originally posted by deramp5113 View Post
    check the output voltage of each regulator on the CPU card and PROM/RAM card and let me know what you measure.
    Ok, I have booted a number of times with just those 3 cards in and it hasn't got me a prompt. Most of the time I get the static screen I previously posted. Sometimes I get an instance where screen has characters "dancing" around, mostly 9's inverting with = signs and other odd stuff. Nothing very promising looking..

    The voltage regulators all seem the check out..

    Z80
    7805: 4.88v

    PROM/RAM
    7905: -5.13v
    7905: -5.04v
    7812: 12.04v
    7812: 12.07v

    Comment


      #17
      What about the 5v regulator on the PROM/RAM (upper right corner)?

      Mike

      Comment


        #18
        Oh I measured that one, forgot to write it down - looks good. 7805: 5.02v

        Comment


          #19
          Originally posted by nullvalue View Post
          ...does it matter in which physical order the cards are installed? I seemed to get different garbled screens depending on the order of installation.
          It shouldn't; it might be worth while to clean up the card edge connectors with a soft eraser, spray the sockets with Deoxit or an equivalent contact cleaner and work the cards in and out a few times.

          An interesting system to be sure; I have the opposite: a set of Cromemco cards in a VG MZ chassis

          Comment


            #20
            Originally posted by MikeS View Post
            it might be worth while to clean up the card edge connectors..
            Thanks I'll give that a shot.

            Its evident there was a floppy controller in this machine at one point but was removed. Is it possible its somehow hard jumpered to boot from floppy? Or are these systems supposed to boot to the monitor every time/or boot failure?

            Comment


              #21
              From what I can see looking at the jumpers on your PROM/RAM card and the CPU board, the system is configured as a very standard VG system. During the first three bus cycles after power on or reset, the PROM/RAM board responds with the first three bytes starting at E000h (in the monitor PROM). These first three bytes are a jump to the initialization routine in the monitor PROM. The init routine initializes the video display and then puts up the command prompt. The monitor only requires the 1K RAM that is on the PROM/RAM board for operation.

              The PROM/RAM board can’t force a jump to the boot PROM on the Micropolis FDC (at F800h)

              Now that you’ve checked the power supplies on each board, let’s look at other simple possibilities.

              1) The CPU is not reset/running properly. An ECO in the manual for the CPU board suggests putting the axial 22uf cap back in the reset circuit (just to the left of the CPU - you can see it has been removed on your board).

              2) I assume you’ve tried pushing the reset button on the back as well as simply cycling power?

              3) The PROM/RAM board or the EPROMs or RAM chips on the board have a problem. Carefully remove and re-insert the EPROMs and the two RAM chips a few times to freshen up the contact between the pins and sockets.

              If none of these tests reveal anything, do you have an oscilloscope?

              Mike
              Last edited by deramp5113; October 26, 2019, 09:00 AM.

              Comment


                #22
                I have completed the following:
                • Cleaned all board edge connectors and sockets
                • Found a radial 22uf cap and put it back in the CPU board at the spot you mentioned
                • Reset button on the back does nothing at all.
                • Re-seated every IC on all 3 boards. The Z80 was really stuck in there good, tried to be extremely careful but when I worked it out, one of the legs was broken and stuck in the socket. I managed to run a wire from that CPU pin to the socket pin on the backside of the board. Continuity test passed.

                None of this seemed to help. Recycling the power presents the same garbled text screen. The text is basically the same every time I boot.

                Unfortunately, I do not have an oscilloscope. I can borrow one from a friend, its an analog scope. What should I check? I may need his help.
                Last edited by nullvalue; October 26, 2019, 11:11 AM.

                Comment


                  #23
                  Hey, I was just talking to someone on Reddit with one of these! (/jk)

                  I can't offer any additional advice but I can strongly recommend the cheap Chinese logic analysers like these: https://www.banggood.com/USB-Logic-A...r_warehouse=CN

                  They're only eight channels, which means you have to choose between watching the data bus or watching the low eight bits of the address bus, but they work out of the box with PulseView and take so much guesswork out of debugging this stuff. Plus, you can't really go wrong with $8 delivered. They're fantastically useful for all sorts of other jobs, like logging and analysing serial connections, too.

                  A logic probe, too, is amazingly useful for showing you whether a line is low, high, or has traffic: https://www.banggood.com/Digital-Log...r_warehouse=CN

                  Comment


                    #24
                    Thanks again for your help over there! I may need to invest (very little) Iin these. Though my friend did offer me to keep the scope hes bringing over. Do these things do anything that a scope doesn't?

                    Comment


                      #25
                      They record digital signals on multiple channels. The one I linked to streams data to a PC via USB, so it'll record an unlimited amount of data. Connect it to the data bus and you get a complete record of every single instruction and value passing across the bus during the execution of a program. You can then examine the trace, attach decoders for various protocols like UARTs, SPI, I2C, etc after the fact. It makes debugging, e.g., boot sequences very easy.

                      Ideally you want to record every signal on the bus, but with 16 address lines and 8 data lines plus a handful of signalling lines you end up needing a lot of channels. I've seen 16-channel ones for about $100 and that's still low end. Those little 8 channel ones are very cheap, very easy, and really useful and I wish I'd gotten one years ago.

                      Comment


                        #26
                        Originally posted by deramp5113 View Post
                        If none of these tests reveal anything, do you have an oscilloscope?
                        I have the oscilloscope now, could you give me a few pointers on what I should try checking first?

                        Comment


                          #27
                          First, make sure the Z80 reset line (pin 26) goes low and then high when you press and then release the reset button. It looks like your board has been strapped to use the standard PRESET line from the bus (pin 75) instead of the "special" short reset from the DRAM card (pin 55). This means you should be able to see the RESET pin on the Z80 go low when you press the reset button on the back.

                          Second, verify the Z80 is getting the 4mhz clock on pin 6.

                          Mike

                          Comment


                            #28
                            Get a quality logic probe before you bother with a logic analyzer. I've never personally owned one of the cheap Chinese analyzers, but I've helped people troubleshoot systems that were using them, and in two different cases, the cheap Chinese logic analyzer was causing additional problems with the system. 90% of old computer problems can be solved with a logic probe and multimeter anyway. I've got a big 80-channel HP logic analyzer, and it's one of those things that sometimes you absolutely have to have, but mostly it doesn't live on the bench.
                            Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

                            Comment


                              #29
                              Since this is a C-M industrial computer the ROM's might be custom programmed and not for booting to a prompt. Try finding a download of the Vector Graphic standard boot ROM's. If you find the download, I'm sure one of us would help with doing the burning or pick up a TL866 programmer to program the ROM's using a PC. A copy of the CPU manual can be found at: http://s100computers.com/Hardware%20...Vector-Z80.pdf
                              Crazy old guy with a basement full of Pentium 1 laptops and parts

                              Comment


                                #30
                                Is there a decent S100 emulator, allowing virtual cards to be installed, configured, etc?

                                Comment

                                Working...
                                X