Search results

Stuff-It Expander 5.1.4 on MacOS 9 and The Unarchiver on macOS.

Guess AE took a page from Commodore (or was it the other way around?) with slowing down the rotation speed to meet the data rate requirements with an older controller. The same method was used with the FDHD drive in the Amiga 4000 to work with the Paula controller. Looks like the original AEHD...

The AppleShare 3 printer and file servers appear in folders after extraction. The archive is working fine and I have installed on System 7.1 without issue.

Before I even got this far, I knew that Apple chip would be the same as the PC Transporter disk interface. Applied Engineering also had the "AE HD" drive that allowed Apple IIgs machines (with driver) to read and write GCR 1.6MB floppies. AE had an "AE HD+" drive for the Macintosh that allowed...

Its common to handle tasks on clock ticks with emulators. Its not surprising that most emulators the int main() is just one big loop :). Somehow the GSport SCC emulation was able to handle this without a problem along with bridging to EtherTalk (with Ethernet speeds).

minivmac's LToUDP implementation has some bugs. Through testing with tashtalkd and TashRouter indicates its a problem with minivmac itself. The emulator's ability to transmit data onto the network seems to be speed limited, roughly to the speed of a modem. This is very noticeable if you ever try...

Cheap generic PICkit clones have no problem programming a TashTalk. I managed to get one for under $20 on ebay.

The PowerBook still isn't seeing all zones, but a complete shutdown of both TashRouter and atalkd and then restart should clear that up. Its completely normal for routers to develop stale zone tables when you are starting up and shutting down routers one at a time.

Most Mac emulators patch the ROM to an extent. Its one reason why the machine is fairly easy to emulate! It wasn't until efforts like MAME or QEMU that there was any attempt to emulate the machine with actual hardware.

Motorola had a different approach to Intel in that the newer generation CPUs weren't 100% compatible with software written for the earlier generation. Apple got away with this by not supporting older OS versions on newer hardware. The Amiga worked around it by having loadable CPU libraries in...

I think I know what might be going on. Change the MAC address used by TashRouter for the tap interface, it should not match the one NetBSD assigned the interface on creation. For A2SERVER, I just use a completely bogus address (AA:BB:CC: DD:11:22) since its a virtual interface anyway. ie...

This is an invalid configuration. Both atalkd and TashRouter both need the same zone list configured on tap0. The atalkd line should be as follows in this case: tap0 -seed -phase 2 -net 3 -addr 3.33 -zone "Danger Zone" -zone "EtherTalk Network" Anyway, one more thing to try. TashRouter had a...

Keep in mind that the Zorro bus was being developed by pretty much ONE person, Dave Haynie. No surprise it took a few revisions of the Buster chip to get stuff working. Reading the war stories can be funny at times. Things like "EISA got this nice feature, might as well add it to Zorro while...

OK, seems that atalkd is working now... just have to get TashRouter running at the same time!

There should be RTMP traffic on vioif0, at a minimum it should be broadcasting two tuples for networks 2 and 3 that atalkd is setup for. TashRouter appears to be working correctly, its routing table has all three networks. One last test, shut down TashRouter and restart atalkd. See if you are...

Things seem to be communicating. Don't know what is causing the zone error, unless TashRouter isn't replying to the requests from atalkd for a zone list. On your Ethernet network, run Wireshark with the "atalk" filter. You should see the RTMP packets every 10 seconds, and expanding them should...

Odd, but it may be a regression from fixes on Linux to prevent NBPReplies coming from the loopback. Can you setup atalkd as follows: See if Macs on your main network trigger NBPReplys.

TashRouter is now working over AppleTalk, the AARP lookup/reply shows that. LToUDP traffic shouldn't be going over the tap interface at all. On Linux, TashRouter's LToUDP always seems to correctly select the main NIC and send out packets in my setup. I do have the problem with Minivmac on...

Here is a sample output from one of my test VMs with A2SERVER. I manually started TashRouter (6502.183) and then atalkd (6502.16). 21:20:22.418742 aarp probe 6502.183 tell 6502.183 <-- TashRouter AARP Probe 21:20:22.622576 aarp probe 6502.183 tell 6502.183 21:20:22.823363 aarp probe 6502.183...

atalkd is emitting the right packets. When you fire up TashRouter, does anything pop up? You should see a burst of AARP probes from TashRouter at a minimum, then eventually periodic RTMP packets roughly every 10 seconds. You will see them from both atalkd's address (3.17) and TashRouter's address.