On 03/08/2018 12:33 PM, Dean Notarnicola via vcf-midatlantic wrote:
When I worked at Simon and Schuster in the early 90s, we were 50/50 split PCs and Macs. No issues with file exchange, as the application document formats were common across both, so no issues with resource forks. We instructed vendors to use only FAT formatted media, and we had Appletalk to Ethernet bridges installed for older Macs that needed it. I cannot recall one time not being able to transfer a file across platforms, as long as there was an appropriate application.
On Thu, Mar 8, 2018 at 12:20 PM Herb Johnson via vcf-midatlantic < vcf-midatlantic@lists.vintagecomputerfederation.org> wrote:
On 3/8/2018 11:58 AM, Ethan O'Toole wrote:
Oh and on the crusty macs the whole file fork thing.
We used Macs in our engineering documents for network design. Other than MS Word having bugs transfer across networks worked decently. I recall a few issues that a set of rules fixed. But we were engineers and part of a larger company. I also had a customer who had everything! XNS, PUP, Vinse, Novel, SMB, DECNet, AppleTalk, EtherTalk, SNA, BiSync, HP printing (weird bridge protocl) and IP. I'm sure I forgot a few. They had specific rules but most of there data was headed to the Mainframe of the DEC networks. Large companies tend to work out rules to follow. -- Linux Home Automation Neil Cherry ncherry@linuxha.com http://www.linuxha.com/ Main site http://linuxha.blogspot.com/ My HA Blog Author of: Linux Smart Homes For Dummies