Search results

PCMacLAN supports native AppleTalk (it includes the transport layer). Microsoft included a native AppleTalk stack in Windows 2000 and Server 2003, but dropped it from XP, hence the need for 3rd party software.

One thing I haven't extensively tested is the conversion of Apple Double data from the old .AppleDouble folder format to native extended attributes and "dot" files (ex: ._MyFile). So..... back up your shares before trying this! The code should work fine as it wasn't really touched, but always...

That is the factory configuration in my beige G3. If you have the latest ROM, it should work fine. That limitation was mostly an OS X thing anyway.

AFP reply from localhost:548 via IPv6 Flags: 1 Cmd: 3 ID: 57005 Reply: DSIGetStatus Request ID: 57005 Machine type: Netatalk4.0.0dev AFP versions: AFPVersion 1.1,AFPVersion 2.0,AFPVersion 2.1,AFP2.2,AFPX03,AFP3.1,AFP3.2,AFP3.3,AFP3.4 UAMs: DHX2,DHCAST128,2-Way Randnum exchange,Randnum exchange...

Apple did release a "hybrid" IWM that could do MFM floppies, but only supported double density disks. As far as I know, the chip only shipped on the Applied Engineering PC Transporter card.

Heh, all this CommSlot II talk just reminds me what a waste of a PCI slot it was on the 4400. I like the idea of integrating a 3rd PCI device directly into the riser. Something like SATA and/or USB doesn't take up too much board space.

Google is completely removing the "less secure" apps and app-specific password options in the near future. Any solution now needs to use OAuth2 based authentication.

You might want to create a new thread for this. Something is blocking the traffic or atalkd is misconfigured. As a side note, you don't actually need the RPi to be an access point. Appletalk communications between two WiFi machines on the same access point works fine, its only when the packets...

The RPi's hardware is not the issue here. You'd have to sniff the network and see if AARP multicast packets are making it over WiFi to the Pi. The Airport should have no problem doing this.

@Maku, the Linux kernel should have no problem routing AARP frames, the translation from Wifi to Ethernet happens there, not in the device driver. Those are the wireless routers that always seem to work too. I have no problem running a RPi400 with netatalk as an AppleTalk WiFi client as long as...

Just follow the tests in the service manual for the fuser. If it passes the continuity tests and resistance readings, it should be fine.

Other than afpfs-ng, which is TCP/IP only, there isn't any other AFP client for Linux that I know of.

I've swapped the board off the Portable's CP3045A with one off of a standard SCSI CP3040A (I bought this as a mechanical donor if the original portable drive died). It actually seems to work for reading data off the drive, but I didn't trust it enough to do any long term testing.

True Story: A bunch of big name motherboard makers decided to skimp on ESD protection on their USB ports when building Intel i865 based boards. Enough of them blew up that a recall had to be issued.

Another thing to consider is alternate platforms. I think both the 8-bit Apple II and GS/OS AppleTalk stacks assume MacRoman encoding. I don't know about PC clients, but anything on DOS and Windows has to support converting from their native encodings to Apple's. I don't know if these assume...

Netatalk 4.0 might take awhile. The current 2.x branch is stable and can directly upgrade an older install.

We are one pending PR from being able to enable AppleTalk on the main branch. Most of the low hanging fruit is done. The hard part will be taming the beast that is the afpd service. Quite a lot of code was shuffled around after AppleTalk support was removed.

This came up during my work on Netatalk. Officially, Netatalk 2.x allows one to display and create NBP entities and zone names in any supported character encoding (ex: MacHebrew, MacGreek, MacJapanese, etc.) The "official" documentation, Inside AppleTalk, is pretty quiet on this. It only...

A good chunk of the work getting the other AppleTalk daemons running has been done as of today. Right now the main branch is a weird hybrid of all AppleTalk only services, except for AFP file sharing, which is still DSI/TCP only.

I've been going through the 3.x afpd code base seeing what needs to be restored. Eventually I'll get my notes up, but there are two parts of this so far: 1. Adding back pre-AFP 2.2 compatibility: Thankfully most of this is still in place in the code base. The biggest change is restoring the...