Search results

As mentioned before, this is common with Apple II files stored on HFS volumes as they usually don't have resource forks (only GS/OS supported them), but still needed to store ProDOS filetype/auxtype information. Also many cross platform document formats are data fork only, so rely on FinderInfo...

Eck, I meant to say 2 bytes (16 bits).... whoops.

The "Finder Flags" are the 4 bytes after the 8 bytes of File Type/Creator. Its stores things like the color/label, "has custom icon", "is on desktop", "is alias", "invisible", etc.

Not every file has a resource fork (this is certainly the case for Apple II files stored on Macintosh volumes) and the resource fork doesn't store the Finder Flags (labels, etc.).

I'll get around to adding full native macOS FinderInfo metadata support.

The ZipGSX requires a utility to turn the accelerator on or off. Unlike the TranswarpGS which has that fancy built-in CDA. The cables and CPU socket used on these cards are very fussy. You need to try and carefully re-seat the cable. Also the pins on the cable aren't the same profile as a CPU's...

AppleDouble has the advantage of incorporating the Finder Flags (archive bit, label/colors, etc.) into the archive as well since it has the full FinderInfo of a file. I'll take a look at the source later and maybe add in support for native FinderInfo on macOS hosts using extended attributes.

I'm guessing the .info files are the raw 32 byte FinderInfo data? If so, you can grab this natively from macOS file systems by dumping the extended attribute called com.apple.FinderInfo. Easy enough to do in C. You can technically dump the resource fork this way, but its a pain in the neck.

Both cards were BTO options on the beige G3, so no surprises there. The server configurations generally came with AppleShare IP installed along with other "serious bizness" packages. Otherwise they are the same as the plain G3s.

The UnArchiver can extract MacBinary and Stuff-It files on a modern system. In terms with disk imaging tools, there is CiderPress II. The command line versions should run fine on macOS. The GUI versions require Wine. While more Apple II oriented, it does work with HFS disk images and MacBinary...

I heard the Mac chime, its back.

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...