Networking is back (afpd daemon crashed on server). Referencing aliases of the remote volumes still isn't working. Each one prompts me for my credentials, then gives up with a complaint that the volume is not found. I tried recording an Applescript to open the Chooser and run through the...
Unfortunately, something that I did in the course of troubleshooting has broken the DaynaPORT SCSI networking completely. Need to backtrack or possibly reinstall System 7.5.5. Ugh.
The .ENET0 driver does appear in the DRVR resource. I tried several times to get a screen shot, but all attempts yield a blank page when I load the .pict file into Preview on a modern Mac. There's a driver called .ATP that precedes .ENET0. If the ethernet device is loading after .ATP that...
There are two zones. From what I see in the log file, the wifi connection is made before any emulation starts. And, even if it was slow to init after power on, a reboot would see a connection that's already up (simply restarting the Mac does not reset the SCSI emulation). What I'd really like...
Yes, they work as they should and stay connected as long as the system is up. With localtalk or ethernet there is distinct network activity that appears early in the boot process (flickering arrows in the upper left). I assume that's where the Appletalk client does network discovery. With the...
Unfortunately that does not work. On the next restart I am prompted to enter my credentials for each share, after which it fails with an error message about the volume not being available. There's something off about the system configuration, but I'm at a loss to understand what it might be...
Very interesting write-up, thanks! Would this perhaps explain why I'm unable to make Appletalk volumes appear automatically on reboot of my SE/30? I have the Daynaport driver installed to use a ZuluSCSI Pico Slim for wifi networking. Despite checking the boxes in Chooser to make remote...
FWIW, neither driver appears in the Apple menu. I'll do some studying on ResEdit, a tool I'm unfortunately not at all familiar with.
There's also one important difference between wired ethernet or localtalk connections and one made over Wifi. In the latter case the Appletalk session is...
Ah.. As opposed to simply checking those items in the chooser? I will try it.
Good suggestion, but it doesn't work. On restart I get prompted to authenticate for each remote volume, but that fails with a complaint that the remote volume cannot be found.
The problem may be down in the system...
I had originally posted in the compact mac forum, but I think this is a more appropriate place. Since switching to Daynaport SCSI networking for my SE/30 (via Zuluscsi Pico Slim) persistent volume connections are no longer working. I suspect this is because Appletalk init during boot takes...
After some minor grief I was able to network my SE/30 through the Pico Slim Daynaport device and connect to my netatalk server. The only glitch is that volumes I've checked as "connect on restart" do not actually show up after a reboot. When the desktop comes up I'm able to open the Chooser...
In the large I guess this points to the wisdom of "if it ain't broke, don't fix it". While I had my properly functioning Mac Plus apart I decided to recap the analog board. I've been through similar exercises a half-dozen times with no issues. I have many years of bench experience and...
Thanks! After a LOT of poking around I'm convinced it's a Novy Mac20MX. I found a Quik30 manual and there are some differences between the units. Consensus seems to be that software for TSI accelerators will work fine.
This 68030 accelerator board was in a Mac Plus I picked up several years ago. Looked through dozens of posts and cannot identify it. There is no model number or vendor marking on the device, but they use the letters 'CX' all over the place, so maybe that's the model?
Ack - nevermind. I found a suggested systemd unit file in an earlier post. That seems to have done the trick..
Heh - we crossed in the wires. That is working - thanks.
I have a handful of ISA LocalTalk boards along with a COPS LT-1. At one time there was a Linux driver for the COPS and one could run netatalk on that interface (although not very well).
I'll have to dig through my archives to refresh Ye Olde brain cells.
From an FAQ in the late 90s (predating my work):
* I can't get PhoneNet PC, MacLan Connect, or Apple ][ AppleTalk to
connect to the netatalk fileserver.
Netatalk doesn't implement the entire AFP...
Ok, so something different from the capability I added. I can assure you that ProDOS would not interoperate with netatalk before I coded in what I thought was called "short name" support.
That's very strange. I added "short name" support to netatalk in the late 90s in order to get it cooperating with the //e Workstation card. Has that been removed?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.