This isn't about file sharing with AppleTalk. It's about file sharing with AppleShare over IP. AppleTalk hasn't been used for file sharing since 10.3, and even then it was only for discovery purposes. The AppleTalk that was dropped from 10.6 was only used for printing to an AppleTalk printer.Leo Laporte, The Tech Guy, stated on this past weekend's episode that OSX code named "Snow Leopard" is the watershed for PowerPC-based Macs. It is the only version that you'll need an Intel Mac to run. This also includes dropping AppleTalk, as it is old and outdated.
73s de Phreakout.
-
Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.
Snow Leopard and Classic Mac OS
- Thread starter napabar
- Start date
I'm presently connecting to a 10.5-running PPC server from my 10.6-running Intel laptop via FTP. (Go -> Connect to Server -> Typed in "ftp://MacServer.local") It mounted the root of the server as a new network share "/" on my desktop. I can browse it exactly the same as an AFP-connected share. (Although it is much slower.)
And I just launched AppleWorks 6 over the FTP connection. (Yup, AppleWorks 6, a PPC-only app.) When I double-clicked the icon, I got a warning "The application "AppleWorks 6" is on an FTP server. Are you sure you want to open "AppleWorks 6"? Applications may not run or may run very slowly when opened from an FTP server."
Update: AppleWorks refused to load. I did successfully load TextEdit, RealPlayer, and Sound Studio though. (TextEdit the 10.5-shipped Universal binary, RealPlayer 10, a Universal binary, and Sound Studio, a PPC-only app.)
Which reminds me. I need to check Sheepshaver's compatibility before I upgrade to Snow Leopard to ensure I can stilltransfer directly from OS X to my 128K.
Using MacTerminal, while slow is actually pretty easy. What surprises me is that Apple never updated MacTerminal to represent the files graphically. For all practical purposes it works like any terminal software, or FTP – files are represented by a directory list. Odd considering that Apple could have really set themselves apart from the crowd. Auto connection would have been helpful too, so one doesn't have to manually choose send and receive (though I understand why that was the case with a 400K disk-based system.
FTP was never designed to do that. It is "file transfer protocol", it is not a file sharing protocol. Most file sharing protocols are designed for LANs, not WANs. Also, Classic OS has it's own share of pain through use of resource forks which make no sense to the rest of the planet.I was referring to Classic Macs not being able to run apps off an FTP share.
Mounting a FTP share as a disk is something that came along in 10.4 or 10.5 (can't remember). A Mac Plus can't do that! It has to use a client, and pull the files down to it's on drive first.
Isn't FTP broken? Most contemporary sites require that the client uses SFTP or FTP over SSL. Not easy on a classic or vintage Mac.
MacTerminal 1.1 was the GUI Mac-Like plug-n-play interface. It correctly handles the resource forks on the file so that it does not need to be compressed to be transferred (a bit of a hassle on anything less than System 6). So, you basically find the file you want to send and send it. It shows up on the other Mac exactly the way it appeared under the Classic Finder using ClarisWorks, which uses the MacTerminal 1.1 protocol. I could never get Zterm to work as smoothly and the files never made the transition intact. With MacTerminal, you just double click them and they work. I even wrote to the ZTerm people at one point asking them to add the MacTerminal 1.1 protocol, but it never happened, AFAIK. ClarisWorks was the last communications package I'm aware of which supports the MacTerminal 1.1 protocol.
Mac128,
This article from Apple states that MacTerminal supports xmodem. So does ZTerm. Did you try send a file xmodem to xmodem?
http://docs.info.apple.com/article.html?artnum=1166&coll=ap
Yup. In fact to use MacTerminal 1.1, the protocol is set to XModem. The same is set under ClarisWorks. For whatever reason this did not work in ZTerm. While it may be XModem protocol, it is not MacTerminal 1.1 compatible, meaning it doesn't keep the resource forks intact in a way MacTerminal Xmodem understands them. This doesn't really surprise me as MacTerminal 2.2 is the highest version which can be used on a 128K, so the vintage version of XModem protocol it uses could be different than the a more modern and standardized version used in ZTerm. Also, MacTerminal 1.1 was a Mac-only legacy transfer protocol which was eliminated with ClarisWorks. I have to imagine that Apple modified the XTerm implementation to allow for encoding and decoding of the resource fork, and likely packet size, none of which would have been necessary on the original CP/M format, or PC driven variants which ZTerm claims to largely support. I just don't see anybody continuing a MacTerminal 1.1 legacy standard which was likely mostly usurped by more efficient ones in the late 80s.
On the other hand, I may not have had the settings adjusted exactly right on ZTerm, so it is worth obtaining the latest version and checking it out.
However, one thing Sheepshaver provides for that I do not believe Leopard does is the ability to use MFSLives to read from MFS disk images under the Finder (as Tiger allows). There is a certain amount of corruption that can occur when an HFS only FInder manipulates an originally MFS written file. Of course anything less than OS 8 on Sheepshaver will read an MFS file allowing that file to be loaded by SheepShaver. This also means all original disk images and Classic SEAs, and other archives, etc. can be kept and run in a "native" environment.
Last edited by a moderator:
Hmmm. I've just been messing around with ZTerm. I ran it on my LC and PowerMac 6500, and used a printer cable to connect. I was able to send files and apps over, and they retained their resource fork. It would be my expectation that a Mac specific app like this would cover those bases. I have MacTerminal 1.1, but it won't run on my LC, even under System 6. I still think there is a way to make this work. You mind emailing me MacTerminal 2.2 to give it a whirl?
I'm also going to send Dave Alverson an email. His last entry on his ZTerm page was a year ago, where he mentioned he was working on a UB for ZTerm. That would be cool, as I didn't install Rosetta with 10.6, and don't plan to.
There are also some other Terminal programs out there, like MacWise I might give a whirl.
Some here have mentioned that many companies still use FTP, and that you can still use FTP to "access" old Macs from new. Terminal programs have also been mentioned for "access." I myself am well aware of that, but "limited access" is not the same as the robust file transfers one can perform via AppleTalk. I challenge you to drag and drop your SE/30's hard disk partitions (in my case, some being more than 1GB in size) to your OS 10.6 Intel Mac and do a full backup over Ethernet via FTP or Terminal programs! I've done a complete backup of my SE/30 this way, including System 6.x and 7.x and OS 8.1 system folders, with all files, filenames, custom icons, etc. intact after the transfer, with no special compression or encoding required. That is the big difference. Yes, FTP and terminal apps still provide access. But such "limited access" does not excite me.
Similar threads
