Search results

The device name is "mswinpr2", which your build has support for. https://ghostscript.readthedocs.io/en/latest/Devices.html#ms-windows-printers

Ghostscript has a GDI output option on Windows, so it can print to literally any Windows printer.

PCMacLan's print spooler has rudimentary support for passing Postscript jobs to Ghostscipt automatically. Of course the manual doesn't document it at all.

You can "create" a Postscript printer under Windows using Ghostscript and a tool called RedMon. This works similar to how Linux and CUPS along with CUPS Filters converts Postscript jobs into native printer formats. The latest version of PCMacLAN (9.1) supports Windows XP and still works with...

Only Linux and NetBSD have actively maintained support for AppleTalk /DDP.

macOS hosts don't support AppleTalk/DDP.

Hopefully this results in the terribly broken firmware in these devices getting fixed. There were rumors that a later revision existed to fix the problems, but it hasn't shown up.

To clarify, Netatalk 4.1.0 can store/retrieve the resource fork of files natively on macOS hosts without the need of "._" AppleDouble files. Additionally, Netatalk will now natively read and sync any FinderInfo data (File Type/Creator data, labels, etc.) it finds on the host file system.

I'd solder on a PCB directly on top of the footprint of the removed HDI-45, just push the pins directly into the holes on the board and use any lugs to stabilize it. It'll likely be a double sided board depending on the pin routing. There may be enough room to direct mount a right angle VGA...

Back in the late 90's, people didn't know where the market for ATX backplates was going. Most of the early ATX cases I had worked with included a set of "standard" back plates. Most of these were port configurations (ex: "Micronics", "Intel", etc.) that were already released onto the market...

The issue with System 3.3/Finder 5.4 was likely due to the AFPGetSrvrInfo packet being too large. That has been fixed with Netatalk 4.0.3. Something isn't working right here because PCMacLan shouldn't have any trouble connecting as an AFP3.1 compatible client.

Try directly connecting to the server via TCP/IP under "Miramar AppleTalk Network->AppleShare IP Network->Add a new IP Server". That completely bypasses AppleTalk from the handshake. Note that currently trying to connect via AppleTalk will limit the connection to AFP2.2. Either way, I'm not...

Sharing a sub-directory of another folder that is already being shared is nesting. share1=/home/userfolder share2=/home/userfolder/anotherfolder I have PCMacLan 9.1.1 running in a XP VM. It seems to work fine over both AppleTalk and TCP/IP and Netatalk 4.0.4 with user home directory shares...

Don't nest shares in afp.conf. This will cause problems down the road, particularly with permissions. I can setup PCMacLan 9.0 to test for problems if needed. FTP is not NAT friendly and will fail in many cases behind one. Make sure "PASSIVE" mode is enabled. Some clients may detect a problem...

A quick search indicates that Linux Mint might not use nftables for firewall usage. If so, this stuff isn't going to work without additional setup. Try typing nft flush ruleset from the command prompt and see if an error is generated.

chmod +x the script file and run it directly. Also could be weird newline characters on the file screwing things up. Cutting and pasting the text into a nano session usually avoids this.

The missing nft and single quotes will do that.

If macipgw is already running, that script might not run as it should. Type sudo systemctl stop macipgw before trying to run the script. The script itself requires root privileges, so add an sudo in front of it. It may also not be picking up your default network interface. Replace $atalkd_if...

One significant block of scripting in A2SERVER's setup is recompiling the AppleTalk kernel module if IPDDP is found. Debian has always compiled IPDDP support in, while in my experience, Ubuntu has not. Don't know if that holds for forked distros. The newer kernels aren't bug free either. I'm...

If you have a NAS device from a major vendor (Synology, etc.), chances are you've used Netatalk without even realizing it.