robin-fo
Well-known member
Sadly you won‘t get native LocalTalk using a serial adapter.. But exchanging files might still work using a modem protocol
-
Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.
Best bridge machine?
- Thread starter jdlanza
- Start date
Sadly you won‘t get native LocalTalk using a serial adapter.. But exchanging files might still work using a modem protocol
Skate323k137
Well-known member
I'm really close to getting this working. I have a good working lp command that works from the shell on the RaSCSI (i.e. if i run `head doc.txt | lp -h my.cups.server it will spit out 10 lines from my printer as expected). I have configured the RaSCSI web interface with the right CLI command and such. But that's where I get stuck.
How do I get the SCSI printer to show up in Chooser? Or what driver should I be using on my Mac to make that happen? I am using Mac OS 7.5.3 right now on an accelerated SE. If I can get this last bit sorted (selecting the printer on the mac itself) I think I'm golden; I see the printer device on ID 6 in SCSI Probe.
Skate323k137
Well-known member
Still pulling my hair out on this SCSI printer idea, perhaps I should split it to it's own thread if I can't figure it out soon.
On my RaSCSI, I upgraded it from an older version, but did so per the docs. Like I said above, the lp command and cups seem to be fine.
Netatalk had to be set up, and I have the printer showing up with nbplkup:
I'm supposed to be able to use LaserWriter Chooser extensions, right? And out of curiosity and for sanity sake, how does the RaSCSI Printer show up in Chooser when it's on the SCSI bus?
Thanks for any help. I might just do a fresh install of the RaSCSI just in case something strange happened during upgrades.
On my RaSCSI, I upgraded it from an older version, but did so per the docs. Like I said above, the lp command and cups seem to be fine.
Netatalk had to be set up, and I have the printer showing up with nbplkup:
I'm supposed to be able to use LaserWriter Chooser extensions, right? And out of curiosity and for sanity sake, how does the RaSCSI Printer show up in Chooser when it's on the SCSI bus?
Thanks for any help. I might just do a fresh install of the RaSCSI just in case something strange happened during upgrades.
Byte Knight
Well-known member
As I recall, you need LaserWriter 8.0 and use the generic driver. The printer is not actually on the SCSI bus - CUPS is a "print server" on your network.
Skate323k137
Well-known member
Don't take this wrong; I know very well how CUPS works. For better or worse I've got a good decade of Linux adminning under the belt. CUPS is functioning fine, both on the Pi and on the iMac physically hooked to the printer. I can pipe text to the lp command on the Pi and have paper come out. That's all set up.
I tried the LaserWriter 8 extension I already have. I suspect its the same but I'll try that link. I hope that sorts it.
Also, the physical connection from the classic mac to the RaSCSI is, well, SCSI. So the classic mac is somehow interacting over SCSI, right? Otherwise, why reserve it (the printer) an ID?
Last edited:
robin-fo
Well-known member
Netatalk won‘t offer your Mac a ‘SCSI‘ LaserWriter as it is a networking stack and knows nothing about the RaSCSI software on your Raspberry Pi. Your Mac and the Pi need to be in the same AppleTalk network for this to work. So you either connect the Mac to the same wired Ethernet connection as the Pi, or you add a DaynaPort SCSI-to-Ethernet bridge to your virtual SCSI devices and configure your Mac to use it as AppleTalk connection. You need to install the DaynaPort drivers on the Mac for this and use the RaSCSI setup script or web interface to setup a network bridge between the Pi‘s Ethernet port (or WiFi) and the virtual DaynaPort.
Skate323k137
Well-known member
Thank you for clearing up the missing link here! A network connection makes more sense, and at least there I see data making it somewhere useful. I still was confused because I'm binding the printer to a SCSI ID. If I had ethernet access from the SE to the Pi, it seems like binding the printer to a SCSI ID wouldn't be necessary? Perhaps that's just the easy way to set it up in the RaSCSI Config and web frontend, I don't know.
Sadly my accelerated SE has no ethernet and the DaynaPort setup did not fully work last time I tried it (could have been my home WLAN, some packets made it out but none made it back, despite tcpdump showing responses being sent). Airtalks didn't like my main network either (netgear nighthawk mesh network) but I have them happily on their own router now.
I wish the printer stuff was better documented, I wasted a lot of time today. I know it is rather new, so I'm glad for any help, don't get me wrong.
Edit: this begs the question, if the RaSCSI and Mac are on the same Appletalk network, does the RaSCSI even need to be hooked to a SCSI bus at all if I theoretically only wanted to use it for this feature?
Last edited:
robin-fo
Well-known member
Nope
You can use any device that runs Netatalk.You don‘t bind a printer to a SCSI id.
What do you actually see there?
I recommend using wired Ethernet as a start. You need to change your RaSCSI configuration for this. Easyinstall.sh is your friend
Skate323k137
Well-known member
So this info and the SCLP Driver are irrelevant for Mac users? At this point I've not just used the easyinstall.sh but I've browsed the repo and source code, recursively looking through the code for the SCLP specific lines.
Implement SCSI printer device (SCLP) · Issue #664 · PiSCSI/piscsi
See https://www.staff.uni-mainz.de/tacke/scsi/SCSI2-11.html) for information on the SCSI-2 printer device. Steps a client has to take: The client sends RESERVE UNIT in order to get exclusive access...
github.com
In the web interface you provide the appropriate lp shell command and it binds to a SCSI ID. Back on a classic Mac, In SCSI Probe, it shows a vendor of RaSCSI and device ID of Printer.
I can use an LC II or many other machines I have that have ethernet, but that's a bit less exciting than what I hoped (perhaps foolishly?). I know my hopes don't change reality
Last edited:
robin-fo
Well-known member
I‘m sorry to have confused you. I thought you were following this guide: https://github.com/akuker/RASCSI/wiki/AFP-File-Sharing#Print_Server
I didn‘t know there was already some SCSI printing code in RaSCSI. However, it appears that SCSI printing is still experimental, so using networking instead of ‘raw‘ SCSI is probably still the way to go.
I didn‘t know there was already some SCSI printing code in RaSCSI. However, it appears that SCSI printing is still experimental, so using networking instead of ‘raw‘ SCSI is probably still the way to go.
Skate323k137
Well-known member
No apology necessary, I appreciate the helpful stuff regardless.
That github issue was closed with a link to this which would indicate that this might only work [well] on Atari systems at the moment:
Added support for SCSI printer device (SCLP) by uweseimet · Pull Request #670 · PiSCSI/piscsi
Printing files via RaSCSI, including optional device reservation, successfully tested with an Atari. Tested with and without reservation, with and without initiator ID. [2022-02-15 11:30:02.437] [t...
github.com
As a last ditch I could try the LaserWriter IISC driver but I don't think support for that is there yet. It would be amazing if it happened but AFAIK that isn't a postscript printer so that may be some part of the difficulties.
Back to the bridge machine topic though, this does make me consider doing a good AFP share from the RaSCSI regardless. It would be useful for many reasons.
Skate323k137
Well-known member
I fired up my Pismo, connected via ethernet to my home LAN, and I was able to use my Printer via the RaSCSI with an ethernet appletalk connection. It was very quick and easy at this point, since the RaSCSI already had the default printer etc configured. I printed out a hassle free full color page of text, and it is pretty satisfying. The RaSCSI will have to stay on the home network after all.
Now I'm on to reading the configs and readme's for Netatalk, it seems way too useful to not learn.
Now I'm on to reading the configs and readme's for Netatalk, it seems way too useful to not learn.
robin-fo
Well-known member
Great! Did you already try networking over SCSI (DaynaPort emulation)?
Skate323k137
Well-known member
I have not (re)tried that yet, but I am almost certain it was my mesh network messing it up last time. I had tcpdump running on the Pi after setting it all up, and it would show incoming packets from the SE and respond to pings, but the SE would report 100% packet loss if memory serves.
When I set up my Airtalks, they didn't like the mesh Wifi either. I configured them their own AP on an old spare linksys wireless router, with no WAN connection, and they are quite happy there. Next time I get the urge to try getting the DaynaPort working, I'll probably try this router with the Pi and SE.
I also got afp sharing working on the Pi which changes everything.
Edit: I see directions to get Netatalk 3 set up with a Time Machine destination available. Is this an option in 2.x? I can't find it on first look. It would be a bonus, not a necessity by any means.
Last edited:
adespoton
Well-known member
Hey everyone; I'm back for another round. I seem to look into all this every 5 years or so.
https://www.macip.net/macipgg-vm-3-0/ has an old reference for a "software-based localtalk bridge" For software solution see: http://68kmla.org/fo…&t=22036#p21405 - but of course, the old link was never archived and points to nowhere now.
I'm looking for the nuts and bolts because, in the current dearth of Pi boards, I decided to go for an x86-based Mini PC, so I'm going to have to set up everything from scratch, and want to bridge LocalTalk without an AsanteTalk bridge.
Does anyone remember what's needed for this step in the whole process? Once it's done, I'll likely spin up a MacIPGW VM, upgrade A2Server on it, then upgrade to the latest Netatalk 2.x or the recently released Netatalk 2.2.8, and finally add in Avahi for forward-compatibility with Bonjour-capable devices.
What could go wrong? Please tell me so I'm more prepared And if anyone knows what the software bridge solution was that way-back made me bookmark it and go "well, of course!" please let me know.
I'd love to get all my networking-capable hardware on the same network yet-again, for the third time.
https://www.macip.net/macipgg-vm-3-0/ has an old reference for a "software-based localtalk bridge" For software solution see: http://68kmla.org/fo…&t=22036#p21405 - but of course, the old link was never archived and points to nowhere now.
I'm looking for the nuts and bolts because, in the current dearth of Pi boards, I decided to go for an x86-based Mini PC, so I'm going to have to set up everything from scratch, and want to bridge LocalTalk without an AsanteTalk bridge.
Does anyone remember what's needed for this step in the whole process? Once it's done, I'll likely spin up a MacIPGW VM, upgrade A2Server on it, then upgrade to the latest Netatalk 2.x or the recently released Netatalk 2.2.8, and finally add in Avahi for forward-compatibility with Bonjour-capable devices.
What could go wrong? Please tell me so I'm more prepared
And if anyone knows what the software bridge solution was that way-back made me bookmark it and go "well, of course!" please let me know.I'd love to get all my networking-capable hardware on the same network yet-again, for the third time.
Phipli
Well-known member
Are you asking after this?
LocalTalk Bridge 2.1 - Macintosh Garden
The Apple LocalTalk Bridge is an unsupported control panel that bridges a LocalTalk network to another network selected from the Network or AppleTalk control panels.
Phipli
Well-known member
Or something Linux based (I forget what the Linux ethertalk bridge is called, @cheesestraws will know)
cheesestraws
Well-known member
I'd use either LocalTalk Bridge or Apple Internet Router, depending on how complicated you like your network to be.
This would be a good application for TashTalk to add LocalTalk to a PC, but nobody has actually done it yet.
This would be a good application for TashTalk to add LocalTalk to a PC, but nobody has actually done it yet.
@adespoton Netatalk 2.2.8 should have avahi/zeroconf/bonjour working already. Also A2SERVER has been updated for newer Linux distros and testing is being done using the new netatalk and systemd setup. It should work with zero issue on x86 machines.
As for bridging LocalTalk, right now there are no new solutions as noted. Stick with a hardware bridge or LocalTalk Bridge on an old Mac.
As for bridging LocalTalk, right now there are no new solutions as noted. Stick with a hardware bridge or LocalTalk Bridge on an old Mac.
kkritsilas
Well-known member
I have an iBook G4, a Pismo, and a non-funtional C650 and a non-functional PM 7300/200. The iBook and Pismo are USB and Firewire, and the desktop Macs are SCSI. I am currently in the processof completing a Zip drive setup that will allow for movement if files between the iBook/Pismo and the C650/7300. I have a USB Zip 250 and a Firewire Zip 750MB drive, and I am in the process of getting a SCSI Zip 100 drive. I can write 100MB Zip disks on the iBook/Pismo using the USB 250MB Zip drive, then sneakernet them to the older desktop machines with the SCSI Zip 100MB Drive. While 100MB isn’t a high capacity storage solution by today’s standards, for older machines like these desktops, it should be fine.
