68kMLA Classic Interface
This is a version of the 68kMLA forums for viewing on your favorite old mac. Visitors on modern platforms may prefer the main site.
| Click here to select a new forum. | | Another Se/30 Quest.... | Posted by: kaleokeanu on 2026-09-25 13:14:48 Hello, I have been talking with Bolle in PM's but realized maybe would be a good idea to share what I am going through with the community:
Hello again,
So I decided to send one of the boards off to CayMac for transfer to a Reloaded build.
I pulled out an old SE/30 that had persistent Bus Errors on Boot and figured I might as well give it a shot
I found 8 Megs of ram per my original quest. And got it to Boot! Kinda.
Part One, The Daystar040:
I got it to boot and see the Turbo040 Happy Mac and actually load into 6.0.7 from a Startup Floppy disk.
In order for it to boot, I did have to flash the original 2434 market firmware to the v4.11. Also noted, I tried to use SST-39SF010A's to replace the original rom and it did NOT work. I was frustrated running through multiple versions of the rom but had purchased some AT27C010 that actually worked when flashed. I will make a forum post about my experience at some point mentioning this. I also had to replace the Aztec Powers Supply that was only providing 4.76v on boot. I swapped an Apple-branded for now (have ordered a BabyFace build) and it was reading at 4.96v upon boot allowing me to make it past "Welcome to Macintosh" once the 040 kicked in. Upon getting into system I noticed weird issues so decided to remove the 040 and make sure the system was stable to begin with.
First weird issue is the random appearance of "Disk initialization failed because the disk was locked"
I read somewhere online about a Color Classic Floppy issue and bridging a 4.7k ohm resistor. This worked initially when I was booting from floppy, but once I tried booting from BlueScsi it seems to appear randomly, with or without an internalfloppy cable with the Read/resistor mod.
I also have to boot off bluescsi into system 7 with Extensions off or it wont boot into desktop.
Sometimes when booting I also get a random bomb with error Type 41.
I have also been able to boot up into Snooper and run tests. Surprisingly nothing seems off. This is also odd, because when interacting with finder, If I try to copy files between "BlueScsi" drives it has a file operation error which led me to initially think to look at the SCSI write-enable lines (which I will probably do). Snooper, however, reported no issues when running Disk Tests on my BlueScsi volume. I will say that once I did start the snooper disk test, after running for 15 minutes no errors, the Disk Initialization error loop immediately began.
Just wondering if u knew of a good place to start looking. I saw a post u commented in about the RTC being the issue. Wondering if there is anyway to know if that is causing these very random issues I am having.
It is frustrating because at one point, I can be fully booted and fine. The next moment I am dealing with errors that wont even make it past boot. The randomness of the failures in what is hard to track down.
Also attached, is my 2434 binary for that version 2.0 I have for the Daystar040? Not sure if it is "production 2.0" but it is different from anything else I saw available on the forums. Further update, since there are so many places to start.
Was able to use Reconnaissance on the SE/30 via the modem port. Passed all tests.
Took off BlueScsi for now and attached internal Superdrive and External Superdrive.
Boots using my Stock Apple 6.0.7 System Startup disk no problem whatsoever. When I put a system 7 boot floppy in I see a happy mac then it goes back to gray screen like at initial startup.
I put a System 7.0.1 Disk Tools floppy into the second drive and try to copy a file and get a disk operation error, when I press continue I get a Bomb and a Bus error. I am thinking the RW signal tracing should be my first place to check?
Seems the ASC is working if Serial works fine, ADB seems to work fine.
SCSI will boot but only 6.0.7 or lower images.
Floppies seem to read just fine, no writing.
Similar writing issues when trying to transfer files between BlueScsi volumes.
I DID find a trace that is concerning, I will map it out when I am back from work.
I have attached my pictures from the board. | Posted by: finkmac on 2026-09-25 13:24:35 fyi I recommend proper mactest pro instead of snooper. | Posted by: lauland1 on 2026-09-25 13:45:26 You didn't mention fully testing the ram, that is simple, if time consuming to do, so I'd do that before anything else.
If you've got an 040 board and bluescsi and/or external floppy, you've got quite a few variables going on.
Eliminate as many as possible, or you may be chasing multiple things.
If you see problems without the 040 and bluescsi, just booting off an internal floppy, you should focus on that first, before even thinking about plugging anything else in. | Posted by: kaleokeanu on 2026-09-25 14:14:09 Yes I stripped it down, the quotes don't capture everything I did. (I haven't been trying to use the 040 since the system isn't stable yet)
I have tried external floppy boot, internal floppy boot. SCSI boot. all with the 8megs of stock ram stock rom and no upgrades.
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 BlueScsi 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.
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 @finkmac 's suggestion, 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.
I am currently using my Performa550 to copy the MacTest Pro files to the 6.0.7 SCSI image that seems to boot fine. I will run all test that do NOT involve file transfers and see what happens.
Will post my results. | Posted by: kaleokeanu on 2026-09-25 15:02:07 Was able to make a MacTest Pro SSW 6.0.8 boot floppy with the Performa 550.
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 the Performa 550.
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?
Any advice on where to start would be greatly appreciated! | Posted by: lauland1 on 2026-09-25 23:50:30 Hmm...my gut is telling me it has something to do with floppy or controller (swim). I'm not positive why, but I have that feel.
It sounds like you covered a lot of bases already.
I will make the observation that System 7 is "more stressful" to hardware than System 6. It will touch and use more memory, and use interrupts heavier, etc etc etc.
Copying files likely allocates large blocks of memory and/or touches some that may not have been, if you just booted to the desktop.
----
The fact that it passed many/most/all tests is puzzling. Either the problem is intermittent, or, it is more of a "stress" one, and doing the test (somehow) is less "stressful" than System 7 copying files.
It sounds a lot like a memory problem.
Since that shouldn't be possible, a tester is a tester, and it passed...the tester should find problems when they exist.
So, that leads back to floppy and/or scsi. If a controller is going bad or marginal, there's not much you can do other than replace it.
Then again there's the analog board, and crumbling connections. On Classics and Classic II's this happens a lot. Much less so with SE/30's.
----
The pictures didn't look too bad. A few traces or solder joints looked marginal, but I've seen far far worse run normally.
The first three were very odd. They look almost like someone was trying to cut the trace, and their tool slipped, hence the "little trail". | Posted by: kaleokeanu on 2026-09-26 03:06:40 So I heard your idea about the memory being an issue.
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 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 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 a write signal? I can believe the Floppy issues could be related to the write signal not functioning correctly as all read operations work flawlessly.
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.... | | 1 |
|