Search results

Jumper to fast mode (basically this sets the card to appear as a SmartPort device) and place it in Slot 5 if you want to use more then 2 ProDOS partitions on a drive. These early cards are very weird about partitions as they tend to be written "raw" without any partition table on the drive. The...

Technically yes if you can find an old copy of PCMacLan that works on Windows 95. COPSTalk was also available as well. Also, if running Windows 95, PC Setup 2.1.7 may be of interest as it has native storage drivers for Windows 95: https://web.archive.org/web/20030127064829/http://www.pcsetup2x.com/

"Obtain IP Address Automatically" is DHCP and should work. One thing to try is changing the TCP/IP connection in Open Transport to something else, like MacIP, just as long as it isn't the network adapter you are using with the DOS card. If that works, it lines up with what I vaguely remember...

Windows 95 can use a real mode ODI driver with its native network stack. The "Existing ODI Driver" is the stub driver you need to load. You shouldn't need the Netware client at all. The built-in TCP/IP stack and Microsoft SMB client should work as-is.

That's Apple's stock PC Setup software that shipped with their cards. Its likely the 3rd party PC Setup 2.0.1 will work with this card. It adds native Windows 95 drivers for storage and CD-ROM.

As stated on several sites, the wire pairs need to be flipped similar to this example. https://mirrors.apple2.org.za/Apple%20II%20Documentation%20Project/Interface%20Cards/Accelerators/AE%20TransWarp%20GS/Photos/TransWarp%20GS%20-%20CPU%20Cable.jpg

That website has the pinout for the top connector, not the main CPU socket.

The pinout of that cable is weird. The Bill Shuff cable I have has all pairs twisted (reversed) at the TWGS end of the cable. The pinout is not 1:1 between the card and CPU socket if you directly crimp on the IDC-40 plug.

Apple needs to fix longstanding issues with their SMB client before folks finally give up using AFP. Granted, most all of the commercial NAS solutions have dropped AFP (using Netatalk), but there are still plenty of Netatalk servers out there running side-by-side with Samba or some other...

The character sets and values are here: https://en.wikipedia.org/wiki/Apple_II_character_set "Normal" text requires the 8th bit to be set. There are no extended characters on the II/II+ (IIe/c have lowercase here), so setting the 7th bit just duplicates the set. To use the "alternative" set...

FWIW, at least AppleShare isn't going to have a problem with this. Unlike with the Mac, the designers of Apple Filing Protocol set the epoch to midnight on 1-1-2000. File sharing was using negative values (the value is a 32bit signed integer) back in the 90s! Note this would need to be taken...

You need to turn on one of the older UAMs in order to login. See: https://netatalk.io/manual/en/Configuration#which-uams-to-activate ASC 3.7.2 only supports clear text, guest, or RandNum authentication. Out of the box, netatalk may have come configured to support DHX and/or DHX2.

If possible, can you create a new folder and try sharing it? Netatalk versions prior to 4.1 didn't use native macOS resource forks and FinderInfo. Just trying to rule that out as a conflict. Also to advise you that your old shares are going to lose that information if mounted with the newer...

They should all be rebranded C-Itoh 8510 printers.

When the container is in this weird state, can you attempt to startup python's built in web server in the container and see if it binds to a listening port? Also check that you can connect to it from a machine on your network.

afpd forks child processes to service a client, that's why you are able to maintain a connection. The child process continues to work fine, but if you try to reconnect or connect new clients, the main process won't respond because it is unable to open up TCP port 541 to listen for new...

The sockets thing would be how many sockets Netatalk, specifically afpd, has open (both listening and active clients). The "resource not available" message points to the DDP listening socket (128) somehow becoming unavailable, which is triggering afpd to restart. Somehow after the restart, it...

Is there anything else AppleTalk/DDP running on that machine/interface? I'm not too familiar with Docker, does it's NIC passthru use the host's MAC? This behavior is certainly odd. The other possibility is that you are running out of listening sockets. How many connections are being made to...

I'm seeing references to a host called "saturn" in your past nbplkup queries sharing the same AppleTalk address as Pluto. Is there more then one docker container running netatalk or is the host itself running netatalk? That would case binding errors as the container can't open up listening ports...

Disable AppleTalk and see if the problem still occurs. The "asp_getsession" error is from afpd not initializing AppleTalk sockets correctly. The best I can tell is something is clobbering the NIC in the container so that it appears "busy/unavailable" whenever a device tries to bind and open a...