Figure I would ask the community over here for their opinion:
ALSO: I know the Capacitor job is whack before you roast me! This was my first attempt at soldering back in 2012 before I barely knew what I was doing. I have a tan-kit from Console5 that will go in. But this board was working back when I first got it up and running. It has been in a closet for 3-4 years. I sent my main SE/30 board off to CayMac for transfer to a reloaded board because she had severe electrolytic damage that appeared to be progressing with age even after cleaning and repairing.
I have an SE/30 I am working on with some interesting issues. Setup is with Stock Rom and 8megs of ram.
I have tried external floppy boot, internal floppy boot. SCSI boot. Both drives plugged in, all plugged in, no plugged in.
System 6.0.7 floppies boot to desktop no problem. System 7 will not boot. System 7 WILL boot off ZuluScsi with Extensions off.
Ram was tested working in an SE. Ram passed all Reconnaissance Serial App tests as well as Snooper tests inside the current SE/30 Board.
I decided to remove all the ram and attempt booting with a Synchro030 in the PDS slot. This provided the system with 128megs of ram using the PDS slot and can "hopefully" rule out issues with the ram and ram sockets. I know this ram is absolutely flawless and works perfectly in another recapped and working SE/30. Exact same issues using the Synchro030 as with the 8megs of stock ram.
The Issue seems to be when ANY file transfer operations happen. Floppy or SCSI.
When booted off a 6.0.7 startup disk. I can put another disk in the external and it will read it. When I try to move a readme or make changes to either floppy I get a Bomb and Bus Error.
Per a suggestion from @finkmac, I put a MacTest Pro bootable CD on the BlueScsi. Cant boot from CD, but was able to boot into system 6.0.7 off the floppy and load MacTest Pro from its mounted volume on the desktop. When It started the Floppy Format test I got an Error 11 and a freeze.
Next step I made a MTP 6.0.8 Emergency Disk. Se/30 boots off it fine internal floppy drive (I disconnected everything but it for now).
Passed all MTP Logic Board, RAM and VRam tests, including extended.
I put MTP on a 6.0.8 SCSI image and booted with just the BlueSCSI (Which is actually a ZuluSCSI Pico Dynaport wifi) into 6.0.8
Passed tests BUT I skipped the Floppy test (As I had them disconnected). I was then able to actually SAVE the test results to the image SCSI image.
When I tried to reload the file however, it appeared corrupted and MTP couldn't load it.
I popped the Zulu out of the SE/30 and into a Performa 550 I have that works.
It was able to see the 40k saved test results file but failed to open the results in MTP on the Performa. When I try to copy it to another volume I get an error -127.
I am beginning to think there HAS to be an issue with the Read/Write signal somehow. OR I could have a SWIM and SCSI chip that refuse to write but read and pass all MTP random seek tests at the same time?
The D1 trace damage is probably Battery Bomb related. Its mere millimeters from the battery. I am unsure what D1 even does but assume it has to do with the RTC. I thought this may be an issue as I saw that SCSI would not boot system 7 if the RTC was dead, but it will boot Zulu images in system 7 IF I disable extensions. It passes PRAM/RTC tests so not sure about that.
I have also randomly gotten the 'Disk Initialization Failed Disk Locked' error.
I was thinking maybe RP10 issues? That might explain the floppy but not directly the SCSI issues with writing. Then again why did it write that test results file (even though it failed) if it failed to receive the IOW signal? Or is the RW/WRITE line that passes to the floppy drive somehow also triggering the SCSI chip to issue the IOW signal and it isn't getting a good connection (which may explain the random SCSI write fluke). I can believe the Floppy issues could be related to the write signal not functioning correctly as all read operations work flawlessly. Are there known cases of the SWIM being 100% perfect in read operations and fail write operations (Knowing that the drives I am using are good working on other compact macs).
When I put my multimeter to ground and then ran along pins 1-10 I got
(.20 ohms base line)
1 - .23 ohms
2 - .68 kohm
3 - .36 kohm
4 - .18 Mohms
5 - .21 kohms
6 - 2.4 Mohms
7 - 2.3 Mohms
8 - 2.4 Mohms
9 - 2.2 Mohms
10 - .23 ohms
When measuring across pin-pin I get between 49-51 ohms per pin 2-12, etc... 1 and 10 read .23 ohms.
Even if RP10 is dead, would that explain the issues with SCSI writing successfully.... Is there another RP-x or U-x that interfaces the RW signal for both chips? And Does the D1 trace need to be of concern?
Thanks for your insights!
ALSO: I know the Capacitor job is whack before you roast me! This was my first attempt at soldering back in 2012 before I barely knew what I was doing. I have a tan-kit from Console5 that will go in. But this board was working back when I first got it up and running. It has been in a closet for 3-4 years. I sent my main SE/30 board off to CayMac for transfer to a reloaded board because she had severe electrolytic damage that appeared to be progressing with age even after cleaning and repairing.
I have an SE/30 I am working on with some interesting issues. Setup is with Stock Rom and 8megs of ram.
I have tried external floppy boot, internal floppy boot. SCSI boot. Both drives plugged in, all plugged in, no plugged in.
System 6.0.7 floppies boot to desktop no problem. System 7 will not boot. System 7 WILL boot off ZuluScsi with Extensions off.
Ram was tested working in an SE. Ram passed all Reconnaissance Serial App tests as well as Snooper tests inside the current SE/30 Board.
I decided to remove all the ram and attempt booting with a Synchro030 in the PDS slot. This provided the system with 128megs of ram using the PDS slot and can "hopefully" rule out issues with the ram and ram sockets. I know this ram is absolutely flawless and works perfectly in another recapped and working SE/30. Exact same issues using the Synchro030 as with the 8megs of stock ram.
The Issue seems to be when ANY file transfer operations happen. Floppy or SCSI.
When booted off a 6.0.7 startup disk. I can put another disk in the external and it will read it. When I try to move a readme or make changes to either floppy I get a Bomb and Bus Error.
Per a suggestion from @finkmac, I put a MacTest Pro bootable CD on the BlueScsi. Cant boot from CD, but was able to boot into system 6.0.7 off the floppy and load MacTest Pro from its mounted volume on the desktop. When It started the Floppy Format test I got an Error 11 and a freeze.
Next step I made a MTP 6.0.8 Emergency Disk. Se/30 boots off it fine internal floppy drive (I disconnected everything but it for now).
Passed all MTP Logic Board, RAM and VRam tests, including extended.
I put MTP on a 6.0.8 SCSI image and booted with just the BlueSCSI (Which is actually a ZuluSCSI Pico Dynaport wifi) into 6.0.8
Passed tests BUT I skipped the Floppy test (As I had them disconnected). I was then able to actually SAVE the test results to the image SCSI image.
When I tried to reload the file however, it appeared corrupted and MTP couldn't load it.
I popped the Zulu out of the SE/30 and into a Performa 550 I have that works.
It was able to see the 40k saved test results file but failed to open the results in MTP on the Performa. When I try to copy it to another volume I get an error -127.
I am beginning to think there HAS to be an issue with the Read/Write signal somehow. OR I could have a SWIM and SCSI chip that refuse to write but read and pass all MTP random seek tests at the same time?
The D1 trace damage is probably Battery Bomb related. Its mere millimeters from the battery. I am unsure what D1 even does but assume it has to do with the RTC. I thought this may be an issue as I saw that SCSI would not boot system 7 if the RTC was dead, but it will boot Zulu images in system 7 IF I disable extensions. It passes PRAM/RTC tests so not sure about that.
I have also randomly gotten the 'Disk Initialization Failed Disk Locked' error.
I was thinking maybe RP10 issues? That might explain the floppy but not directly the SCSI issues with writing. Then again why did it write that test results file (even though it failed) if it failed to receive the IOW signal? Or is the RW/WRITE line that passes to the floppy drive somehow also triggering the SCSI chip to issue the IOW signal and it isn't getting a good connection (which may explain the random SCSI write fluke). I can believe the Floppy issues could be related to the write signal not functioning correctly as all read operations work flawlessly. Are there known cases of the SWIM being 100% perfect in read operations and fail write operations (Knowing that the drives I am using are good working on other compact macs).
When I put my multimeter to ground and then ran along pins 1-10 I got
(.20 ohms base line)
1 - .23 ohms
2 - .68 kohm
3 - .36 kohm
4 - .18 Mohms
5 - .21 kohms
6 - 2.4 Mohms
7 - 2.3 Mohms
8 - 2.4 Mohms
9 - 2.2 Mohms
10 - .23 ohms
When measuring across pin-pin I get between 49-51 ohms per pin 2-12, etc... 1 and 10 read .23 ohms.
Even if RP10 is dead, would that explain the issues with SCSI writing successfully.... Is there another RP-x or U-x that interfaces the RW signal for both chips? And Does the D1 trace need to be of concern?
Thanks for your insights!
