| Click here to select a new forum. |
| Replace logic board - Mactest result after recapping mac iici. |
Posted by: crazyben on 2023-09-05 16:22:24 I ran the Mactest after I recapped the Mac iici. I got replace logic board result. Is there another test to see exactly what is not working? Does this mean my recapping was not successful? |
Posted by: joshc on 2023-09-05 17:47:18 What is / isn't working on your IIci now? Were you running the test just to double check or are you concerned something isn't working?
Some photos of your board would be helpful as well. |
Posted by: 3lectr1cPPC on 2023-09-05 17:51:36 Try running Snooper as well, it's another testing suite, and it usually gives pretty specific results. |
Posted by: crazyben on 2023-09-05 18:29:44 No issue with computer everything works as expected. @MrFahrenheit suggested to run a test just to check everything is good after recapping.
I ran the snooper test and it showed RAM and SCSI Bus test failed. Internal SCSI HDD works as Mac boots from it. I will reseat the RAM and run the test again. |
Posted by: 3lectr1cPPC on 2023-09-05 18:30:50 Did you test external SCSI? |
Posted by: crazyben on 2023-09-05 18:32:01 I do not have one to test. I am waiting for external ZuluSCSI to be delivered. |
Posted by: crazyben on 2023-09-05 19:15:46 Reseating the RAM gave same result. It said bank B failed. Does this mean I need new set of RAMs on bank B? |
Posted by: David Cook on 2023-09-05 19:32:40 Try MacTest Pro instead.
Apple MacTest Pro (Mac abandonware from 1996)
www.macintoshrepository.org
I believe the first link on the page (MTP68k_Feb96.ZIP) is the one you want. It should provide more specific information. |
Posted by: Byrd on 2023-09-05 19:36:29 I wouldn’t trust software to diagnose hardware issues in vintage Macs. If your RAM is properly detected, HD booting and it’s not crashing you don’t need to be reliant on anything else. |
Posted by: Phipli on 2023-09-07 00:28:01
I wouldn’t trust software to diagnose hardware issues in vintage Macs. If your RAM is properly detected, HD booting and it’s not crashing you don’t need to be reliant on anything else. Hum.
Not sure I agree. If it is reporting a RAM issue, it means it wasn't able to set and clear some RAM.
That isn't an ignorable situation. Especially if the only reason it boots is because they have a ROMinator and it skips the hardware test.
@crazyben - are you using a ROMinator? |
Posted by: Byrd on 2023-09-07 01:41:25 MacTest is a program rarely used because it's not very good beyond normal hardware troubleshooting - physical checks over software will always win. A error result of "logic board" sounds like a red herring when the OP as noted it appears to be working well post recap, and maybe shuffing some RAM might be the next step if not fully detected, or crashing. |
Posted by: Phipli on 2023-09-07 01:48:58
MacTest is a program rarely used because it's not very good beyond normal hardware troubleshooting - physical checks over software will always win. A error result of "logic board" sounds like a red herring when the OP as noted it appears to be working well post recap, and maybe shuffing some RAM might be the next step if not fully detected, or crashing. The vanilla MacTest program's issue is that it lacks detail in reporting. It does flag real issues though.
If MacTest says there is a RAM issue, there is a RAM issue. That issue might be failed / failing RAM, dirty contacts, bad sockets, broken traces or whatever, but it isn't just making it up. It works by writing patterns to RAM and reading them back, a failure means that it didn't read back what it wrote - that is a real, very real, issue. If you use that RAM, you'll have data corruption. Perhaps it is high up the address space and doesn't get used as often, but it isn't a good thing.
The weird thing is why it isn't caught by the ROM RAM test routine, but that could be because they're using a ROMinator. |
Posted by: joshc on 2023-09-07 02:32:01
physical checks over software will always win. I'm not sure about this.
How can OP verify bank B physically, beyond cleaning the contacts? And without a SIMM tester that takes 30 pin SIMMs, which are impossible to find? |
Posted by: crazyben on 2023-09-10 14:58:14 i did contacts cleaning it gave same result. I will test the scsi bus once u get the bluescsi external. |
Posted by: Phipli on 2023-09-10 15:03:50
i did contacts cleaning it gave same result. I will test the scsi bus once u get the bluescsi external. What simms do you have in it? What size, and how are they arranged? Do you have any spares?
Do you have a ROMinator (3rd party ROM) installed, or a stock ROM?
Concentrate on the RAM first because the SCSI issue could be caused by either not having an internal terminator, or the RAM issue, so we'll come back to that later, once RAM tests pass. |
Posted by: crazyben on 2023-09-10 15:26:19 4 of the right (bigger) ones on Bank A. 4 if left(smaller) ones on Bank B. System is showing 8,192K but i am not sure how much they are. How can I check that? Stock ROM. |
Posted by: Phipli on 2023-09-10 15:27:45
4 of the right (bigger) ones on Bank A. 4 if left(smaller) ones on Bank B. System is showing 8,192K but i am not sure how much they are. How can I check that? Stock ROM. If you switch them over between bank A and B, does the reported problem follow the RAM, or stay in the same bank? |
Posted by: Phipli on 2023-09-10 15:28:39
How can I check that They're probably 1MB SIMMs. I wouldn't worry about that specifically ATM. |
Posted by: crazyben on 2023-09-10 15:38:26 Now as soon as run the test I get this error.
|
Posted by: Phipli on 2023-09-10 15:42:36
Now as soon as run the test I get this error.
View attachment 61848 OK, so remove the 4 SIMMs that are possibly the bad ones (now in Bank A??) And put them to one side.
Put the good SIMMs back in bank A.
Boot while holding the shift key to disable extensions, and run the test again.
Do you have any spare SIMMs at all? |
| 1 > |