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

ADC Super 6

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

    #16
    It looks like from the schematic that POC is not affected by reset but a low delayed by C9 charging at power on. The only other differences I see
    between the jumpers on my board and yours is jumper P top left circled in red on mine is present on the left to pins like the rest. That affects the
    parallel port settings but I wouldn't think matters at reset unless you have a printer attached. However, you are missing jumper E lower left circled
    in yellow. Mine is on the lower two pins 1 and 2. That is an interrupt setting which if floating could matter during reset vs power on.
    norwestrzh on vcf diff.jpg

    Comment


      #17
      No, no printer attached, so if the P jumper has anything to do with the parallel port, then it probably wouldn't do anything. I'm not using the parallel port at the moment.

      I installed a jumper at E (1-2), and it doesn't change anything. If I can believe the schematic, E-2 is pulled high by RM5 in the absence of a jumper at E., so not floating?

      I'm beginning to mistrust my monitor code (how it initializes the ports, maybe?). It is a modification of the old SD Systems Z80 monitor. What do use for a monitor? Anything? Or do you just directly boot up the O.S. from floppy? Do you know if a Super 6 monitor that is "official"? Can you point me to some monitor code that I could try out in place of what I'm using now?

      Thanks for your interest in this problem!!!

      Roger


      Comment


        #18
        My prom has a SuperSix Monitor sticker on it and boots v3.4. I see v3.2 and 3.6 on bitsavers. Looks like there's a disassembly in here too
        http://bitsavers.org/bits/AdvancedDigitalCorp/prom/
        Here's my screenshot. It autoboots the floppy drive on DS0
        s6 monitor.JPG

        Comment


          #19
          Thanks, Larry -- I'll try v 3.4 or v 3.6 (or maybe both?). See if that makes a difference.

          Roger

          Comment


            #20
            Well now, Larry -- this is pretty embarrassing!! I tried ver. 3.4 just now (it took some effort to "jiggle around" (technical term) my boot up code for the IDE/CF card), and it works! The Super 6 will reset properly from the monitor as well as CP/M, without a power cycle. I was surprised that the serial port ran at 19.2k (I expected that it would come up at 9,600). I poked around at some of the monitor commands, and they seem to work OK. I'm using a 27C32B EPROM, so I put my CP/M boot up code at F800h. I didn't want to mess with the monitor code at all before trying it out, so I have to start CP/M with a "GF800". I'm not terribly happy with that monitor because I would lose some functionality by using it. I have to take some time to study it vs. my old one (that wouldn't reset properly). Maybe I can figure out why mine doesn't work?

            I didn't try the 3.6 vers., but near as I can tell, the only difference is the addition of a different boot medium?

            Anyway, sorry for all the fuss. Turns out there wasn't a hardware problem after all -- just my lousy code. Thanks for all your help.

            Roger

            Comment


              #21
              Great !! I'm glad you got it going. My v3.4 boots floppy just fine so I haven't studied it further. My ADC S6 system is using a Monitor Dynamics card for the hard drive. I boot floppy
              but it would be nice to figure out a rom to boot from hard drive but maybe some day ...

              Larry G

              Comment


                #22
                >> I boot floppy but it would be nice to figure out a rom to boot from hard drive but maybe some day ...

                I forgot .... you run MP/M (I believe)? Is that more similar to CP/M 2.2 or 3.0? I'm thinking it is more like v. 3.0. There is a lot of code for that in the R Lee archive. If you can find it on-line, it is in the "A" sub-directory, under "ADVANCED DIGITAL" (of course). There might even be MP/M specific code there? I think I can remember a LOADER used to load up CPM (MPM?).SYS from hard drive or floppy? If you can't find the R Lee archive, I could zip up the content of the ADVANCED DIGITAL sub-directory and email it to you.

                Further investigation of my monitor (that won't reset) is showing me that when I'm running CP/M (2.2) and reset the card, it scans the default directory (as one would normally expect) to warm boot, but there is no serial output. The serial port seems frozen at that point. I wonder why? The CP/M image must still be in memory (intact enough to scan the directory), but it won't give a prompt or respond to input. I compared the code from my monitor and the one that resets OK, and I can't see that either one is doing anything substantially different to initialize the Super 6. Still scratching my head.

                Roger


                Comment


                  #23
                  I'm running TurboDOS on the ADC. I'm running Concurrent DOS on my CompuPro but I can also run MPM86. I gen'd a boot floppy for a 512k system on it. MPM80 takes up too much memory for a 64k system. I have the rlee archive. I'll have to look in it again, it's been awhile. I've always had issues with a serial terminal > 9600 on just about anything.

                  Comment


                    #24
                    >> I've always had issues with a serial terminal > 9600 on just about anything.

                    Interesting!! Initially, I had no trouble at all with the on-board A port running at 19.2k. BUT, I'm finding that it *can* act quite squirrelly with some of my more recent attempts at monitor modifications. I got the bright idea that I could insert the S-100 group's serial card (Z85C30 based) in the backplane, and maybe skip using the on-board serial ports of the Super-6. Although this board has worked quite well for me in an number of other S-100 boxes (at up to 38.4k baud), I cannot get it to work with the Super-6 ... at all. So then I tried a CompuPro Interfacer (just plain "Interfacer" -- I think it is one of the earliest of the CompuPro Interfacer line. Might even pre-date the "Interfacer I"???). It works quite well at 19.2k in some of my preliminary tests. I'm going to try to use it for a console, but that effort will take some time. There will have to be lots of changes. The Interfacer uses TR1863-B UARTs. I had never heard of them prior to this little experiment. The date code on them is 7926!!!

                    Roger

                    Comment


                      #25
                      What's the advantage of a higher speed serial port if it's just driving a terminal? I could see the advantage as far as file transfers. I haven't purchased any modern cards for S100. On my
                      CompuPro I'm running one terminal on the System Support 1 and 3 terminals on the Interfacer 4 but all are running 9600 8N1. When I put in a 286 board and a Quantum Q540 for a hard
                      drive it got really fast, HUGE difference over the 85/88 it initially had. The 3 terminals on the ADC S6 are all the same setting. I can move terminals between these computers which I
                      do all the time since there's no room for more. BTW - I just purchased an AM9511A for the CompuPro SS-1 card and am waiting for it. I never researched what the empty socket was for but someone recently posted about some old benchmark source code in Fortran ? I do have Fortran for my CompuPro. It will give me a reason to fire it up once again. The 286 should rip thru that code in a flash !!

                      PS - hmmm I see it's Fortran 80 so this would hsve to run on my Compupro SPZ slave Z80 which is also installed but will be much slower ?

                      Larry G
                      Last edited by retrogear; August 19, 2021, 01:32 AM.

                      Comment


                        #26
                        >> What's the advantage of a higher speed serial port if it's just driving a terminal?

                        Yes, I see your point. I suppose that if you are just using the serial port for a console/terminal, there isn't a whole lot of difference between 9600 and 19.2k. My situation is a little <ahem> unusual in that regard. I have no floppies on my Super6 and the "drives" (16 of them) are all on compact flash, so the only way to get files and data in, and out, is via the serial port(s), OR using CPMTOOLS to copy things to/from the compact flash card on a PC. The CPMTOOLS approach is pretty nice (and it works well), but is somewhat involved. I've written a little utility that receives a file in .HEX format sent over the console serial line. It loads it into memory (real time), and I use the "save" function of CP/M 2.2. to copy it to "disk". There are distinct limitations, I know. BUT, it is a fast way to transfer things (that fit in memory) *to* the Super6, for now. Going the other way is far easier. I just use the "screen grab" function of minicom (I'm a Linux guy!!). So, the speed of the serial line is quite important to facilitate transfers. I prefer 38.4k, or faster, but the Interfacer appears only to support a maximum of 19.2k. Once I get things going, I plan to get my version of xmodem (via a second serial connection) working. That ought to make things a little more flexible.

                        I've given up on floppies. All of mine are either dead, or dying. Then there's the additional requirement of generating the required +5v and (sometimes) +12v from the +8v, and +16v of the S100 power supply. To tell you the truth, I'm not terribly unhappy to see floppies go by the wayside. Same goes for *real* hard drives! I have often thought of trying to using the Gotek for floppy drives, but that doesn't get around the power issue.

                        Interesting about the AM9511A! I have a COMPU/TIME "Number Cruncher" S100 card, based on the MM57109, but I've never tried to see if it still works. Maybe I ought to?

                        I've run some FORTRAN experiments on my homebrew Z80 SBC, at 20 MHz (with a compact flash interface). It is quite fast, and definitely usable, but it doesn't even come close to HiTech C on that platform.

                        Roger

                        Comment

                        Working...
                        X