Action Retro's latest video shows a SuperMac SCSI video adapter that can run in 15.75khz mode. Its mostly for the composite video port, but it clearly outputs RGB at the same timings.
Pin 5 is green video, which also carries sync. When running at NTSC rates = black and white composite video. The Apple IIgs monitor uses the same pinout as the Macintosh DB-15 and only accepts composite sync on pin 3. If you can force the Toby and other machines to 15.75khz RGB with composite...
Composite color would require the card have a NTSC encoder on it. RGB would be doable though. If the card can output 15.75khz video, those sense pins would be used with a monitor like the IIgs AppleColor RGB or the Commodore 1084.
If running classic networking, open up the Network control panel and verify the correct zone is listed. If Open Transport, open up the AppleTalk control panel. The Mac should be auto-updating this, but isn't for some reason. Also try selecting the LaserWriter in Chooser, closing it, then...
..and if we are wishing for other things, there is always the 67 page "Print Spooling in an AppleTalk Network" APDA product # A7Z0013. Although I really don't need it since Adobe documented most everything the LaserWriter driver does.
Thats... promising news.
I have a general idea of how the bootstrap should work, mostly be monitoring what my Fastpath and netatalk do when starting up. Maybe top secret information like what off-the-shelf transformer to use for LocalTalk will be found.
Unfortunately this was a document you had to pay $20 for. Apple didn't seem to release it digitally later on. Quite a bit of APDA documentation is likely lost because of this. Maybe @al kossow knows of someone who might have this in their "stacks" somewhere?
The bit of information I'm looking...
See title. This was available thru APDA as part number C0144LL/A, but doesn't seem to have been archived. It covers nitty gritty AppleTalk networking details that aren't covered in "Inside AppleTalk" and is considered an addendum to that book. Apple's APDA listing says that IA 2nd Edition...
To all TashRouter users, particularly ones using another router to seed their Ethernet networks. Update to the latest code on github. It fixes a nasty issue with the ZIP service. A packet was being sent out as unicast instead of broadcast causing an AARP storm, plus it was preventing TashRouter...
Namer is limited to only seeing and renaming devices in the current zone. That is intentional on Apple's part. Zones are strictly organizational in nature. You can name all the segments the same, or something different. Its your choice. The only limitation I've found involves netbooting Apple...
Farallon's docs do state that PhoneNet is lower resistance and has a floating ground compared to Apple's connector system. Despite that, you can connect the two together, but distance become limited to what Apple's cabling supports.
OK, a possible solution already was found in this thread. After reading @RolandJuno's numerous logs, this is "what works" per tashrouter-rickards5-debugout.txt.
-Ditch the caching of NBP Lkups. Its not needed and clearly causing issues. Revert to the name_information.py on github.
-Use long...
Hopefully I'm reading this right.
TashRouter picks up the Broadcast request from the printer (why is the printer outputting NBP broadcast lookup requests?), and relays it to all zones, including the TashTalk network. Somehow a LookupReply from TashRouter makes its way back to the printer, which...
The "yielding" debug line happens when a lookup reply is intercepted and re-transmitted. Seems that information sometimes has the printer's net/node/socket in it instead of the requesting machine's information..... from a BroadcastReq that the printer sent. That packet gets sent back to the...