Intel to Classic file sharing

For several years I have updated my server on OS 9.2.2 using file sharing from OSX 10.5.8. Today I tried to update a file from another Mac with OSX 10.6.8. It mounts the OS 9 volume as usual and I can copy files from it but all files and folders appear to be read only and hence I cannot write to it.


What are my options for writing to OS 9.2.2 from OSX 10.6.8?

Posted on Nov 9, 2018 12:35 PM

Reply
22 replies

Nov 11, 2018 8:32 AM in response to Neville Hillyer

I wonder if Apploetalk has anything to do with it?


OSX.4.x lost the file transfer ability of Appletalk... 10.1.5 thru 10.3.9 had it!


http://docs.info.apple.com/article.html?artnum=301183


With OS9 set with Appletalk to using TCP/IP, and or Chooser>AppleShare+IP, you can connect to the 10.4.8 machine.


Another solution is OpenDoor's $39 Shareway IP, (some OS7, 8, 9 releases had a limited version included)...

http://www.opendoor.com/shareway/


Which makes OS9 Tiger compatable.


"Mac OS X 10.4 and later don't support Personal File Sharing (or other AFP) over Appletalk, though by initiating the connection from the opposite direction you could still achieve an IP connection from a Mac OS 8 computer to a sharing Mac OS X computer. The Network preference pane in Mac OS X 10.4 and later still offers the AppleTalk checkbox, but it is for browsing AppleTalk-advertised resources and zones. The subsequent connection must be over TCP/IP."


http://docs.info.apple.com/article.html?artnum=106461

For 10.7 & up, likely this applies...

Connecting to legacy AFP services - Apple Support

And lately Apple has dropped AFP totally, SMB is used... & perhaps a solution here?

Dec 3, 2018 9:14 AM in response to BDAqua

I now have Leopard and various versions of Snow Leopard installed on my Mac Pro and I get the following results:


All versions can mount a remote OS 9 volume or folder. Leopard can write files to the mounted volume without any difficulty. Some versions of Snow Leopard can write some files at a first attempt but some of these appear empty or corrupted.


I eventually found I could get consistent satisfactory results by using a bash script to write about 40kB to a dummy file twice. After this further files can be written without any difficulty until the connection is terminated. Whist this is slightly tedious I can live it.


Further insights or fixes would be of interest to me.


Here is my bash script:


open 'afp://user-name:password@###.###.###.###/volume/web-pages'; sleep 1; f(){ echo {a..z}{A..Z}{z..n} > /Volumes/volume/web-pages/dummy-file; }; f; f


You are welcome put this on your other site.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Intel to Classic file sharing

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.