[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Trouble creating an AppleShare ProDOS volume
Frank Townsend <ftownsen@iamdigex.net> wrote:
> I have two additional issues:
>
> 1) While I can copy a ProDOS application (ShrinkIt e.g.) from a local drive
> to the server and can see it in the ProDOS directory tree, when I select it,
> it fails to run and just reloads the view of the same tree. Is that
> expected behavior, that I can copy but not run ProDOS apps copied to the
> AppleShare Mac volume? I thought it might be normal behavior, so . . . .
> (on to question (2))
Make sure the volume presented by the server and all the relevant
folders on it are obeying ProDOS naming conventions (no more than
fifteen characters, starts with a letter, only use letters, digits and
periods).
(The server volume might be an entire hard drive partition, or just a
shared folder, depending on how you have your server configured.)
> 2) I have a second drive on the Mac which I partitioned as a ProDOS volume
> and a HFS volume. When I start up the server, I get a message as follows:
>
> "The volume "PRODOS' could not be prepared for use with AppleShare"
This is correct. You cannot share a ProDOS-formatted volume using
AppleShare, because the file system is too limited in functionality.
You shouldn't need to use a ProDOS-formatted volume (even if it were
possible) because the file system used on the server is completely
transparent to the client - the AppleShare server and client exchange
data using a virtual file system, and it is the responsibility of the
server and client to map this into each operating system in a meaningful
way.
You might have an AppleShare server running on a Mac (serving files from
an HFS or HFS+ volume), a Windows NT Server (serving files from a FAT or
NTFS volume), or a Linux machine (serving files from a ext2 volume).
The client doesn't care, as long as the server is able to support the
feature set required by the client, and the files and folders involved
don't violate the naming conventions supported by the client (ProDOS in
this case).
--
David Empson
dempson@actrix.gen.nz