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

    #91
    Yes, just keep typing the in the hex values and they will be placed in successive locations in RAM starting with the address specified in the "P" command. Press ESC after you've entered all data.

    You can do the "D"ump command after entering the data to make sure it looks right. Here's the manual for your ROM monitor: https://deramp.com/downloads/vector_...itor%204-0.pdf


    Mike

    Comment


      #92
      20200406_115249.jpg

      So I hit 'P 0000' then continued to enter the entire program (even though as I typed each character remained an F).. Did a Hex Dump 0000-0010 and as you can see it's all still F's..?

      EDIT: I'm guessing it would help if I actually had my RAM expansion board installed?

      Now it seems on a Dump the memory is filled with FF 00 FF 00.. But at least as I type now it saves it..
      Last edited by nullvalue; April 6, 2020, 09:04 AM.

      Comment


        #93
        Would you happen to know if the DB25 serial port on this computer should be pinout compatible with a PC? Basically can the two easily talk or do I have to build a custom cable? Which terminal app/protocol would I use to transmit the PC2FLOP.COM program?

        Comment


          #94
          It appears the serial port is connected to the bitstreamer with a ribbon cable and that makes the DB-25 look like DCE unless other modifications have been done on the board. That means you’ll need a DB-25 to DB-9 “straight through” cable (not a null modem cable).
          I like using Teraterm for a terminal emulator https://altairclone.com/downloads/teraterm477.zip. The .com should be sent with a simple file transfer (no protocol, make sure 8-bit is enabled).

          Mike

          Comment


            #95
            Originally posted by deramp5113 View Post
            It appears the serial port is connected to the bitstreamer with a ribbon cable and that makes the DB-25 look like DCE unless other modifications have been done on the board. That means you’ll need a DB-25 to DB-9 “straight through” cable (not a null modem cable).
            I like using Teraterm for a terminal emulator https://altairclone.com/downloads/teraterm477.zip. The .com should be sent with a simple file transfer (no protocol, make sure 8-bit is enabled).

            Mike
            So I'm trying to get this to work, I get the program in memory and execute it (G0000) - I send it the file, but it's not filling the memory at 0100 from what I can tell. I have tried using the 'E' (External Communications) command in the Monitor and can't get anything sent from serial to display on the screen. This should work, right? Using a scope, I don't see any activity on the TX pin when I type a key. I found this manual to the Bitstreamer 1 card. https://usermanual.wiki/Document/Vec...3752909379.pdf The Bitstreamer is configured for 300 baud and the 24-pin ribbon cable is plugged into J3. Is there anything else you can think of that I should be looking at?

            Comment


              #96
              Here is a closeup of J3 on the Bitstreamer, does it look right?
              20200424_222112.jpg

              Comment


                #97
                Do you know if the machine expecting RTS/CTS handshaking? If that's not working, it'll refuse to send/receive.

                Comment


                  #98
                  When dealing with RS-232 issues one of these helps figure out what pins are active and need to talk to each other: https://www.amazon.com/Kentek-Molded...7821659&sr=8-7
                  Crazy old guy with a basement full of Pentium 1 laptops and parts

                  Comment


                    #99
                    Originally posted by DeltaDon View Post
                    When dealing with RS-232 issues one of these helps figure out what pins are active and need to talk to each other: https://www.amazon.com/Kentek-Molded...7821659&sr=8-7
                    While that does look handy, I kind of already tested the lines using a scope. I am receiving data from the PC, however the S100 is not seeing it. At least CPU isn't seeing anything from the Bit Streamer...

                    Comment


                      Originally posted by hjalfi View Post
                      Do you know if the machine expecting RTS/CTS handshaking? If that's not working, it'll refuse to send/receive.
                      I am not positive - I don't think so but the documentation doesn't really say.

                      Comment


                        At what address is the board strapped? We have to know that to get started. The “External Com” command uses I/O address 4. PC2FLOP uses I/O address 2 or 4.

                        The 8251 requires no handshake lines to receive and requires its CTS pin asserted in order to transmit. Based on the picture you sent, your computer is wired as DCE and would connect to a terminal with a straight through DB25 cable. DTR pin 20 from the terminal is connected to the 8251 CTS input. Normally, a 4.7K pull-up on the Bitstreamer pulls up CTS if nothing is driving it.

                        The 8251 requires a multi-byte init sequence before it will work. This is done by the monitor PROM for you if the board is at a standard address.

                        Mike

                        Comment


                          Originally posted by deramp5113 View Post
                          At what address is the board strapped? We have to know that to get started. The “External Com” command uses I/O address 4. PC2FLOP uses I/O address 2 or 4.
                          There is a section in the manual that talks about changing the address:

                          changeaddress.png

                          It says "For example, to change the board address from PORT 0 to PORT 4, cut the trace from A2 to A2SEL and add a jumper from A2 to A2SEL."

                          Uhh.. what? is that a misprint? either way, here is my U7:

                          20200427_083743(1).jpg

                          So it looks like its configured for address 2?
                          Last edited by nullvalue; April 27, 2020, 05:46 AM. Reason: found more info in the manual

                          Comment


                            Looks like it is jumpered per the example given in the diagram. So it's configured for Port 4.

                            Comment


                              Your board is jumpered at I/O address 4. That puts the serial port at I/O address 6/7 which is not supported by the monitor PROM or PC2FLOP. Move the A2 jumper back to pin 8 (A2 not) and that will put the serial port at I/O address 2/3 which is supported by PC2FLOP. Note this is still not the port address supported by the External Comm command which is typically I/O address 4/5.

                              Mike

                              Comment


                                Thanks guys! I must not be reading the diagram correctly. How would I jumper to set to address 4/5 to test External Comm?

                                Also, before I continue with the serial stuff, I have to solve something else. I think I may have some bad RAM chips in my 8k board. It wouldn't allow me program anything into memory while that board was installed. I'm working on building an 2102 SRAM chip tester using an Arduino.

                                Comment

                                Working...
                                X