Received: from netcomsv.netcom.com (uucp4.netcom.com [163.179.3.4]) by nacm.com (8.6.9/8.6.9) with ESMTP id XAA27059 for <executor@nacm.com>; Mon, 15 Aug 1994 23:30:11 -0700
Received: from kira.UUCP by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1)
id TAA10067; Mon, 15 Aug 1994 19:53:55 -0700
Received: by kira (NX5.67d/NX3.0S)
id AA00360; Mon, 15 Aug 94 17:42:41 -0700
Date: Mon, 15 Aug 94 17:42:41 -0700
From: David John Burrowes <davidjohn@kira.net.netcom.com>
Message-Id: <9408160042.AA00360@kira>
Received: by NeXT.Mailer (1.100)
Received: by NeXT Mailer (1.100)
To: netcom!nacm.com!executor@netcom.com
Subject: Large Mac files: a question
Sender: Executor-Owner@NACM.COM
Precedence: bulk
This is not an executor issue, per se. But, it's closely enough related
that I thought I would ask y'all (sorry for the potentially wasted
bandwidth)
I have a NeXTCube running NS3.2, and an external PLI SuperFloppy (2.8).
I find that if I write large (larger than 100 or 200K, say), I will be
unable to read the file, usually, on a Macintosh.
That is, I write a 600K file to the Mac disk (using either HFS_XFER or
in the NeXTSTEP workspace manager), take it into my Quadra 950 at work,
I'll then get a 'disk error' error message from the Mac when I try to
read about the files (this seems to happen about 80% of the time)
Have any of you seen this before? Is this a standard 'feature' of the
NeXT machines with Mac files?
Thanks for any comments.
david john
p.s. Yes, it does seem to work fine with smaller files.