Thread View: comp.sys.next.misc
2 messages
2 total messages
Started by Henry McGilton
Mon, 16 Nov 1992 05:46
Speaking of Mac Disks
Author: Henry McGilton
Date: Mon, 16 Nov 1992 05:46
Date: Mon, 16 Nov 1992 05:46
35 lines
1998 bytes
1998 bytes
As a previous poster (George Kamis) noted, Next Step 3.0, can
format, read, and write Macintosh formatted floppy disks.
Two points to mention about it:
1. data transfers to and from Mac disks are incredibly
slow -- it beats tyromancy, but only by a slim margin.
2. Writing files is flakey. There is some (unspecified)
limit on the number of files you can write, and when you
hit the limit, the file system on the disk appears to be
hosed. Let's hope NeXT can figure this one out soon
and at least let us know what the limits are.
I have a hierarchy with fifteen directories and around 430
files. The total size of the hierarchy is around 700K --
only about half of the capacity of a Mac 1.4 MB disk. The
limit seems to come somewhere between 100 and 200 files.
I couldn't see a pattern. I eventually transferred all
the files to the Mac, and put all the files onto one disk
using the Mac. The NeXT appears to be able to handle
reading the disk all right -- just writes are flakey.
3. (since I promised to mention two points). Transferring
files from the NeXT to the Mac does only that -- there's
no translation services (NL to CR for instance) a la
FloppyWorks. In fact, I ended up using FloppyWorks in the
end to do the translation, as well as to set file type and
creator.
So be aware that the universe of discourse in NeXT to Mac disks
may not cover all the things required to move files around correctly.
........ Henry
Re: Speaking of Mac Disks
Author: Gordon Van Huizen
Date: Mon, 16 Nov 1992 21:46
Date: Mon, 16 Nov 1992 21:46
28 lines
1597 bytes
1597 bytes
In article <1992Nov16.054635.521@trilithon.mpk.ca.us> henry@trilithon.mpk.ca.us (Henry McGilton) writes: > > As a previous poster (George Kamis) noted, Next Step 3.0, can > format, read, and write Macintosh formatted floppy disks. > > Two points to mention about it: > A few other things: 1. The Mac file handling has a problem with file names that are too long. If you have Mac files nested a few folders deep you may find that you can't access the files. 2. When you copy a Mac file to a NeXT filesystem using the file viewer, you are only copying the data fork. The resource fork will be ignored. 3. If you want to copy or access the Mac resource fork, you must do it from the command-line. It appears as a second file and isn't displayed by doing a wildcard ls. For a give file named "bob", "bob" is the data fork and "bob.#rsrc#" is the resource fork. -- ---------------------------------------------------------------- Gordon Van Huizen vox: 619.488.9411 fax: 619.488.3045 Metrosoft gvh@metrosoft.com [NeXTmail welcome] ----------------------------------------------------------------
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads