Image Map Image Map
Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 37

Thread: Ibm pc at parity check

  1. #21
    Join Date
    May 2006
    Location
    Melbourne, Australia
    Posts
    5,720

    Default

    Quote Originally Posted by jacobtohahn View Post
    I am sure that I got the IBM BIOS, from http://minuszerodegrees.net/bios/BIO...ARIATION_1.zip.
    So, a type 1 motherboard, and you have upgraded the motherboard BIOS to the final revision.
    Do you recall experiencing the symptom before that upgrade ?

  2. #22

    Default

    Quote Originally Posted by modem7 View Post
    The hard drive appears to be the infamous CMI 6426 - see [here].
    Still works now . Any software that I can use to occasionally backup the drive to a folder on the 100MB HardCard (D drive) just in case?

    Quote Originally Posted by modem7 View Post
    And if a chip, it isn't necessarily a RAM chip. For example, it could be chip/s that are involved in parity calculation/comparison.
    Hoping that’s not what it is!! These cards are pretty rare and expensive. If that is the issue I’d have to change to a RAMpage AT.

    Quote Originally Posted by modem7 View Post
    Prior to going down that (expensive) route, I suggest:
    * Re-seat all socketed chips in case of a poor electrical connection.
    * Per what mikey99 wrote, run a RAM diagnostic (such as CheckIt). AST may have supplied something specifically for the card.
    I’ll reseat the chips after running CheckIt.

  3. #23

    Default

    Quote Originally Posted by modem7 View Post
    So, a type 1 motherboard, and you have upgraded the motherboard BIOS to the final revision.
    Do you recall experiencing the symptom before that upgrade ?
    Not sure. I still have the old ROMs so I could try the old bios again. If that’s the issue then I don’t know how I’d use the 2.5” drive I installed afterwards. Probably using a 3rd party bios.

  4. #24
    Join Date
    May 2006
    Location
    Melbourne, Australia
    Posts
    5,720

    Default

    Quote Originally Posted by modem7 View Post
    And if a chip, it isn't necessarily a RAM chip. For example, it could be chip/s that are involved in parity calculation/comparison.
    Quote Originally Posted by jacobtohahn View Post
    Hoping thatís not what it is!! These cards are pretty rare and expensive. If that is the issue Iíd have to change to a RAMpage AT.
    If so, you have the option of running the card with its parity checking turned off. Not nice, but still an option.

    Quote Originally Posted by jacobtohahn View Post
    Not sure. I still have the old ROMs so I could try the old bios again.
    It would be good to rule the BIOS upgrade out of the 'possible cause' list.

  5. #25
    Join Date
    May 2006
    Location
    Melbourne, Australia
    Posts
    5,720

    Default

    Quote Originally Posted by modem7
    The hard drive appears to be the infamous CMI 6426 - see [here].
    Quote Originally Posted by jacobtohahn View Post
    Still works now .
    If that changes, a burial at sea will be very appropriate.

  6. #26

    Default

    Quote Originally Posted by modem7 View Post
    If that changes, a burial at sea will be very appropriate.
    Haha, I actually have 2 of those hard drives and both work fine.

  7. #27

    Default

    SOLVED! It was the BIOS. I replaced it with the AMI BIOS and it works like a charm.

  8. #28

    Default

    Quote Originally Posted by jacobtohahn View Post
    SOLVED! It was the BIOS. I replaced it with the AMI BIOS and it works like a charm.
    And no, nevermind then. After a few hours of operation it did the exact same thing. I think that I should turn off parity checking.

  9. #29
    Join Date
    May 2006
    Location
    Melbourne, Australia
    Posts
    5,720

    Default

    Quote Originally Posted by jacobtohahn View Post
    I think that I should turn off parity checking.
    If the parity generation/checking circuitry is working properly, then there is a RAM related problem. If so, the symptom may simply change to 'DOS just locked up' or 'My running program just locked up'.

    The RAM test done by the power-on self test is rudimentary - just a confidence thing. How did the running of the RAM test in CheckIt go ?

  10. #30

    Default

    Quote Originally Posted by modem7 View Post
    If the parity generation/checking circuitry is working properly, then there is a RAM related problem. If so, the symptom may simply change to 'DOS just locked up' or 'My running program just locked up'.

    The RAM test done by the power-on self test is rudimentary - just a confidence thing. How did the running of the RAM test in CheckIt go ?
    The CheckIt test passed completely fine. I’ll test without parity checking and see if DOS locks up.
    EDIT: Still happening even without Parity checking enabled.
    EDIT 2: I’m almost sure it’s the card. I’m going to buy a RAMPage AT and use it instead.
    EDIT 3: After even more testing, I’ve found that it is actually the onboard RAM itself. I have a spare 5170 board that I swapped the RAM from. Testing now.
    EDIT 4: Still getting it even with new RAM. That narrows it down to the motherboard parity circuitry. I will swap out the entire board tomorrow. The board is untested but seemingly working.

    Also, here’s a picture of the screen with the error:
    4E69E655-7BE0-497C-BFE3-34B967A9EF01.jpg
    Last edited by jacobtohahn; May 22nd, 2018 at 08:08 PM.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •