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

How to read parallel-port POST diagnostic codes?

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

    How to read parallel-port POST diagnostic codes?

    There are many cheap diagnostic cards available on ebay that read the codes output to port 80h during POST and display them on a standard 7-seg LED. But what if you have a board that outputs to 378h (ie. LPT)?

    I was trying to help someone with a dead AT&T 6300 (it boots up to a "0" on the monitor before dying) by disassembling the 1.43 ROM BIOS (using the 6300 Plus BIOS as a guide, as I'm not aware of the 1.43 BIOS source published anywhere). I was surprised to see that there are clear "Check Points" output at various points in the POST code:

    Code:
    seg000:DB8F i_powerup:                              ; CODE XREF: seg000:E05Bj
    seg000:DB8F                                         ; seg000:EA73j
    seg000:DB8F                 cli
    seg000:DB90                 mov     al, 40h ; '@'   ; checkpoint #0
    seg000:DB92                 mov     dx, 378h
    seg000:DB95                 out     dx, al          ; Printer Data Latch:
    seg000:DB95                                         ; send byte to printer
    (The codes range from 40h to 4Fh, which I'm assuming are common printer control codes that don't print anything, as I don't remember my 6300 printing characters every time it booted.)

    How would someone read these codes? Is there are relatively straightforward way to, for example, wire up a cable from the 6300 to something else, or is there an easier method I'm missing?
    Offering a bounty for:
    - A working Sanyo MBC-775 or Logabax 1600
    - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

    #2
    On one of my systems, the parallel port is connected (on board) to an 8-LED DIP display. You just read the code right off the board. You could do the same thing with a bunch of LEDs soldered onto a DB25M plug.
    Reach me: vcfblackhole _at_ protonmail dot com.

    Comment


      #3
      Originally posted by Trixter View Post
      (The codes range from 40h to 4Fh, which I'm assuming are common printer control codes that don't print anything, as I don't remember my 6300 printing characters every time it booted.)
      40h to 4Fh are just common ASCII codes from '@' (as depicted in your code) followed by 'A' up to 'O' (check any ASCII table)

      If there is no strobe puls generated the printer will ignore those bytes but you can check them on the data pins of the LPT port.

      Comment


        #4
        Assuming you don't mind spending a bit of cash and waiting a month for delivery from China why not just get a POST reader for a LPT? They are commonly available on eBay.
        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


          #5
          Originally posted by gertk View Post
          40h to 4Fh are just common ASCII codes from '@' (as depicted in your code) followed by 'A' up to 'O' (check any ASCII table)

          If there is no strobe puls generated the printer will ignore those bytes but you can check them on the data pins of the LPT port.
          In which case installing a switch to pull the strobe line will cause the printer to print the status characters.
          Be polite and I may let you live.

          https://www.youtube.com/playlist?lis...5NBVfKX5471R9U

          Comment


            #6
            Originally posted by Shadow Lord View Post
            Assuming you don't mind spending a bit of cash and waiting a month for delivery from China why not just get a POST reader for a LPT? They are commonly available on eBay.
            I did not know these existed! I only knew about the PCI/ISA interface ones. Thanks, this will do the trick nicely.
            Offering a bounty for:
            - A working Sanyo MBC-775 or Logabax 1600
            - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

            Comment


              #7
              Many of the Olivetti PCs are using parallel port to output POST diagnostics. We can say, all of them which are using Olivetti own BIOS. That also includes AT&T 6300, Xerox 6060 and many PCs from Triumph Adler while that company was owned by Olivetti. It should be all Olivetti PCs and laptops up to about 1992. Then they started to use AMI BIOS on their own boards or buying boards from elsewhere, there a classic ISA/PCI POST diag card works fine.

              Unfortunatelly I could not find anywhere a POST code list for such Olivetti PCs until yet. But it is still usefull, you can see this way if the processor does something sensefull or not before display comes up.

              But you can buy ready made test modules from ebay which are working just fine on Olivetti PCs for just a few bucks.

              Example, it's also available from vendors in US, Europe or China: http://www.ebay.com/itm/Motherboard-...wAAOxyiOxR1PY6

              It has USB port, just for power supply. But on Olivetti PC not needed, the PC powers this module, I have tested it already and it works fine.
              <album>

              Comment


                #8
                I wonder if you can't peruse the AT&T 6300 Plus BIOS listing and dig the codes and their meanings out of there.

                I do know that the Plus was an 80286 system, but I suspect that the basic POST codes are either very similar or the same.
                Reach me: vcfblackhole _at_ protonmail dot com.

                Comment


                  #9
                  6300 Plus is the same as Olivetti M240: 8086-10 XT on size shrinked mainboard and nicely restyled M24 chassis.
                  <album>

                  Comment


                    #10
                    It's really odd to see the parallel port POST analyzer being sold on eBay. How many current desktops and laptops even have a traditional printer port on them?
                    Reach me: vcfblackhole _at_ protonmail dot com.

                    Comment


                      #11
                      Originally posted by Chuck(G) View Post
                      It's really odd to see the parallel port POST analyzer being sold on eBay. How many current desktops and laptops even have a traditional printer port on them?
                      How many current desktops and laptops even have a traditional ISA bus on them? I suspect there is a niche market for them. I personally have a couple of ISA, PCI, PCI-E, and LPT ones squirreled away for just in case. At <$5 delivered it seems like cheap insurance.
                      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


                        #12
                        The POST cards are usually ISA/PCI, depending on which way they're inserted. But the gizmo here is a parallel-port diagnostic card.
                        Reach me: vcfblackhole _at_ protonmail dot com.

                        Comment


                          #13
                          Originally posted by 1ST1 View Post
                          Many of the Olivetti PCs are using parallel port to output POST diagnostics. We can say, all of them which are using Olivetti own BIOS. That also includes AT&T 6300, Xerox 6060 and many PCs from Triumph Adler while that company was owned by Olivetti.
                          Do you know if any of them released BIOS source?

                          But you can buy ready made test modules from ebay which are working just fine on Olivetti PCs for just a few bucks.
                          I received mine Saturday and will be giving it a shot soon and will report back.

                          Originally posted by Chuck(G) View Post
                          I wonder if you can't peruse the AT&T 6300 Plus BIOS listing and dig the codes and their meanings out of there.
                          That's what I did for a few hours a week ago; I disassembled the 6300 1.43 BIOS, and then annotated some of it using the 6300 Plus BIOS source as a reference. They are about 80-90% similar. I already have all of the parallel-port POST codes identified in the 6300 1.43 BIOS:

                          Code:
                          seg000:DB90                 mov     al, 40h ; '@'   ; Checkpoint #0
                          seg000:DBDE                 mov     al, 41h ; 'A'   ; Checkpoint #1
                          seg000:DBF9                 mov     al, 42h ; 'B'   ; Checkpoint #2
                          seg000:DC16                 mov     al, 43h ; 'C'   ; Checkpoint #3
                          seg000:DCA9                 mov     al, 44h ; 'D'   ; Checkpoint #4
                          seg000:DD55                 mov     al, 45h ; 'E'   ; Checkpoint #5
                          seg000:DE1C                 mov     al, 4Bh ; 'K'   ; Checkpoint #B
                          seg000:DF40                 mov     al, 48h ; 'H'   ; Checkpoint #8
                          These output as 40h, 41h, etc. although the 6300 Plus source refers to them as "#0", "#1", etc. In the 6300 1.43 ROM BIOS disassembly, they translate to:
                          • Checkpoint #40h: POST has started
                          • Checkpoint #41h: CPU test OK
                          • Checkpoint #42h: ROM checksum OK
                          • Checkpoint #43h: DMA timer test OK
                          • Checkpoint #44h: DMA channel test OK
                          • Checkpoint #45h: PIC (programming interrupt controller) test OK
                          • Checkpoint #4Bh: RAM size and test OK
                          • Checkpoint #48h: Realtime Clock OK
                          Offering a bounty for:
                          - A working Sanyo MBC-775 or Logabax 1600
                          - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

                          Comment


                            #14
                            I wonder if this would work with a Toshiba T-1000. I have one that won't POST, and the service manual shows troubleshooting codes for the parallel port.

                            Comment


                              #15
                              Hey Trixter. If you are the same as me right now and considering using this to figure out what the battery leak killed on the machine I'll grab the adapter above on ebay and report back what's happening from my machine.
                              [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
                              --------------------------------------------------------------------------------------------
                              [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

                              = Excellent space heater

                              Comment

                              Working...
                              X