Not likely. If its using something similar to libpcap to inject packets into the host's interface (like VirtualBox's "bridge" interface option), other VMs on the machine can't "see" those packets. Many VMs have provisions to allow this to work properly with TCP/IP, but it doesn't extend to other...
Sorry, meant afp.conf, not netatalk.conf. Note that atalkd will not "make up" a zone name. If no router is found, it will pick an address in the startup range (network in the 65000 area). Running jrouter on the same machine in another container is likely an issue. The two containers likely can't...
If you have a seed router on the network (in this case, jrouter), just enter a network interface in ATALKD_INTERFACE and leave ATALKD_OPTIONS blank. This will force atalkd to issue a ZIPGetNetInfo packet to request network information and automatically configure the interface for use.
By...
A GatorBox is still useful as a LocalTalk-to-Ethernet bridge. AIR 3.0 implements a somewhat more complex tunneling protocol to cut down on bandwidth use by RTMP packets and such over the bridge. The GatorBox tunnels were fairly simple, just forwarding any AppleTalk traffic over the tunnel. Bad...
The 74A cartridge in my LJ4MP has the opposite problem. For some reason it doesn't deposit toner at all onto statically charged portions of the drum. Printer itself is working, I can see a light ghost of the test page on the paper.
Apple later expanded this concept in HFS and AppleShare with the Catalog Node ID, giving every file a unique identifier alongside of the file names. Its a key part of how alias work.
Looks like its an external clock to speed up SCC transfers. The SCC allows for external devices to provide their own clock (pin 2 of the mini-DIN 8 serial port).
NOS toner can degrade, particularly the wiper for the drum that scraps waste toner off. Look at the drum after printing and see if it is completely clear of toner. If it has streaks/residue, the wiper is failing. It could also be a bad drum as well. With the Canon PX engine printers, it takes...
Just use a MicroSD card at that point. The Pi4 doesn't have an actual M.2 slot on it making this difficult. Weirdly enough, the one PCIe riser/splitter I have uses a cable with USB 3.0 type-A plugs (wire protocol is still PCIe) between the x1 piece that goes into the board and the riser itself.
NVMe will be faster then USB. Also helps that that NVMe storage devices are actually designed to boot and run computers.
I am disappointed in the I/O selection. No onboard LocalTalk? :p
It should. How well, I don't know as I haven't attempted to use QEMU to emulate a PPC machine on a Pi4. QEMU emulating a Quadra 800 running System 7.1 works fine however.
There shouldn't be any need to define the local hostname in /etc/hosts, it gets it from /etc/hostname. Also, Netatalk 4 bases the server's name off of the system host name by default. ;)
With regards to AFP and AppleShare, those "file flags" are defined as file attributes in the AFP protocol and can be retrieved and changed with the FPGetFileParams/FPSetFileParams calls. One of the changes made between AFP1.1 and AFP2.0 are these flags. From Inside AppleTalk page 13-20:
AFP2.0...
I can't believe Apple shipped that printer with only 2MB stock. The LaserJet 4P (PCL only) came with 2MB, while the 4MP (Postscript and PCL) came with 6MB standard. Even with the full 22MB in my 4MP, its a dog when printing with PostScript as PCL5e is MUCH faster. Printing via CUPS is worse...
The dbd utility can convert the old AppleDouble v2 format to the new extended attributes format in one shot.
The way forward to print to an ancient printer is to write a printer application, or just manually push the jobs using the command line pap utility.... which is what the backend script...
CUPS 3.0 has been delayed quite a bit. The first distro to switch will likely be Ubuntu. Thankfully Debian tends to be very conservative and likely won't switch any time soon. This won't mean the end of printing from your classic Mac though as papd will eventually be updated to support CUPS 3.0...
I can confirm it works, but you have to manually add the printer's URL under "Add Printer" in the CUPS web interface. The "Find New Printers" option no longer works for 3rd party back ends. To get the URL, you have to manually run the pap back end script, which will list URLs of all found...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.