Replies: 4 comments 4 replies
-
|
By the way, why is this removed from issues to discussions? As in my humble opinion this is an issue! |
Beta Was this translation helpful? Give feedback.
-
|
A few thoughts. First I'd start with our pre-made 6.0.8 image and a freshly formatted SD card. I usually do not have to edit anything in the Network control panel, just open Chooser and enable Appletalk. Second note that Appletalk over Wi-Fi can have issues described here https://github.com/BlueSCSI/BlueSCSI-v2/wiki/WiFi-DaynaPORT#ethertalk Also make sure you are very close to your Wi-Fi access point. The Pico's Wi-Fi antenna range is limited. I would also run a RAM test just to be sure - these are 30 year old computers, you never know. Hope that gives you a few ideas to try. What system is running the Apple Talk share and what version of the OS? I could give it a try with my SE as well. Sorry for the late reply, I though I had replied when I moved it initially. |
Beta Was this translation helpful? Give feedback.
-
|
I'm seeing the same behavior. I have the BlueSCSI on the latest firmware (2026-03-01). I essentially do the following:
At this point, everything works. If I reboot, I get a crash. Sometimes, if I keep rebooting, the OS decides to disable EtherTalk and switch back to LocalTalk. At this point, the system will boot fine. |
Beta Was this translation helpful? Give feedback.
-
|
To add this: If I'm in the crash state, I can boot from floppy and move the EtherTalk Phase 2 extension out of the System folder. I can now properly reboot, but if I put the extension back and reboot, it will crash. If instead, I put the extension back, change the Network from LocalTalk to EtherTalk and then back to LocalTalk, and then reboot, the system is find. The OS seems to cache the EtherTalk option, so even just removing it and putting it back isn't enough. You have to physically change back to LocalTalk before a reboot. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When activating AppleShare over Ethernet in the Network control panel the system crash on reboot, With a memory violation error. Only option is to remove the EtherTalk Phase 2 extension from the system folder.
The system works fine to ping using MacTCP.
This works fine on System 7.5.3 on the same Mac SE.
In both case the installation method described in the wiki are used.
Some additional information:
Updated the BlueSCSI V2 to the latest version (2024-12-08).
Still issues when rebooting when EtherTalk Phase 2 "EtherTalk Alternative" is activated during (re)boot, in the Network Control Panel. The system will crash with an "address error".
When "LocalTalk Built In" is selected, in the Network Control Panel, before shutdown or reboot, the system will (re)boot without any issues.
The AppleShare connectivity works, when "EtherTalk Alternative" is activated after an reboot, in the Network Control Panel. Connections can be made to other Mac's on the same segment. Files can be copied between systems without issues.
Beta Was this translation helpful? Give feedback.
All reactions