Search results

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'm running Tashrouter on an RPi under Debian Bullseye. What is the best approach for making it start automatically at boot?

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?

Ok, I spun up a Bookworm VM and was able to build Netatalk 4. Tomorrow I'll fire it up and take it for a spin. However, it's NAT'ed out to my network from the VMware 10. so may take some work to get clients talking to it.

That's a voltage adjustment, probably for the +5V line. Don't connect it to a motherboard until properly (re)set! The power supply needs to be checked with loads on the outputs. Maybe someone has a link to a tutorial?

I looked at Bookworm, but am seeing that KDE desktop support is "iffy". I'll take it for a test drive in a VM. Anyway, enough off-topic chatter :)

I know nothing about Docker, but can certainly setup a VMware guest OS for the purpose. I really should start thinking about a new distribution, but I cannot and will not use anything that relies on SNAPs. Philosophy aside, SNAP installs don't work from an NFS mounted home directory.

Unfortunately many of the required packages for Ubuntu build are too new for my environment. Due to persistent breakage I do not upgrade unless forced to by cutoff of security patches. Still on Ubuntu 18.04 here. If/when I upgrade my system I'll be glad to to do some testing.

Heh. Ok, thanks for clarifying. So far everything has been working as advertised!

I have been away from Apples for a bit, but just got back to pickup the thread here again. I notice the latest TashRouter has a new interface called MacvtapPort but still retains the older TapPort. My startup program uses the latter. What is the difference between them? Is there a reason I'd...

Nice work, all! I need to get busy and build a patched kernel for my Tashrouter Pi.

I just pulled the latest code and am pleased to report that Apple 2 clients are still 100% happy!