HULL@UNLVAX1.BITNET (01/17/90)
Previously on a AppleShare network, I was able to allow more than
one user access to a HyperCard stack by giving Read-Only access to the
stack folder. While attempting to duplicate the exact environment on
MacVap v1.1 (Advanced Network v2.15 rev "C"), I receive the message
"Can't Open Stack "stack name". File is lock or in use."
The Netware for Macintosh Supervisor supplement says that not
Macintosh access rights correspond completely with Netware access rights.
Trustee assignments to the stack folder are [RO S]. File flags are
Read-Only [Locked] and Sharable (multi-user). These are set via Netware desk
accessory and Netware Control Center.
I've tried various access rights but still receive the same message.
Is there a file attribute being overlooked or does MACVAP not capable of
supporting Multi-user HyperCard Stacks?
Any assistance is appreciated. Thanks in advanced
Allan Hull
HULL@CRCVMS.UNL.EDU
(402) 472-5225ANDREW@BROWNVM.BITNET (Andrew Gilmartin) (01/18/90)
The following was written to support HyperCard users under NetWare.
It has not been updated since HyperCard 1.2.5. I hope this helps
-- Andrew Gilmartin
Computing & Information Services
Brown University
Box 1885
Providence, Rhode Island 02912
andrew@brownvm.brown.edu (internet)
HyperCard for Macintosh installation and sharing
Installation
Server requirements
Total disk spaced need to a minimum HyperCard environment is 1019K.
Required files are;
* HyperCard 1.2.2 (392K)
* Home (30K)
* Help (597K)
For more information on workstation requirements see "Getting Ready" in
HyperCard User's Guide.
Workstation requirements
* Macintosh Plus (or later)
* Minimun of 1Mb of RAM
* System 4.1 and Finder 5.5. CIS recommends that you use at least
System 6.0.4 and Finder 6.1.4 where possible.
For more information on workstation requirements see "Getting Ready" in
HyperCard User's Guide.
Installing the application
HyperCard can be concurrently used. The HyperCard application does not,
however, come with the shared attribute set. To set the shared attribute
use the Macintosh application ResEdit. For information on using ResEdit
to set the shared bit see "Using ResEdit" in this guide. The group
Everyone should have Search, Open, and Read rights to the HyperCard
folder. Use the Novell's DOS command grant to set these attributes. For
example,
grants s o r for <hypercard folder> to everyone
where <hypercard folder> is the name of the HyperCard folder.
The Home stack acts much like a configuration file, maintaining
information about the user, the level of expertise, and where HyperCard
should look for other stacks. As this information can change HyperCard
tries to write to this stack oblivious of access privileges. The file
server will not allow the write returning error code -5000 to HyperCard.
HyperCard does not know how to handle this error so presents the user
with an error dialog box with a Cancel button. Clicking the Cancel
button will either quit HyperCard or again present the same dialog box.
If the latter happens the only way back to the Finder is either to
restart the Macintosh or to enter the monitor and execute the command,
G FINDER
Once returned to the Finder restart the Macintosh. Not restarting will
likely cause problems later on.
Preventing problems with the Home stack is simply a matter of checking
the Can't modify stack option in the Protect Stack... dialog box.
HyperCard will abide by internal protections but not always external
ones. As a general rule for all stacks that should not be modified by a
user check the Can't modify stack option.
Most users with not attempt to modify the Home stack's protection.
Should an attempt be made the user will be presented with the same error
dialog mentioned before. The Departmental Network Administrator can take
further precautions but this does require some familiarity with
HyperCard's scripting language HyperTalk.
Placing the HyperTalk message handler in the Home stack's script will
prevent the majority of users from causing themselves problems.
on doMenu which
if which is "Protect Stack..." and ^
the sort name of this stack is "Home" then
answer "Can't change the Home stack's protection."
else
pass doMenu
end if
end doMenuROGERDAL@LAVALVM1.BITNET (Roger-Daniel Laberge) (01/18/90)
>The following was written to support HyperCard users under NetWare. >It has not been updated since HyperCard 1.2.5. I hope this helps > >-- Andrew Gilmartin > >Server requirements > >Total disk spaced need to a minimum HyperCard environment is 1019K. >Required files are; > When printing bitmap with HyperCard under NetWare, does the server colapse? That's what's happening under 3 Com +. We are thinking of NetWare but we want to play safe... Roger-Daniel Laberge Centre de traitement de l'information Universite' Laval Quebec, Qc ROGERDAL@LAVALVM1.BITNET
ANDREW@BROWNVM.BITNET (Andrew Gilmartin) (01/18/90)
> > The following was written to support HyperCard users under > > NetWare. It has not been updated since HyperCard 1.2.5. I hope > > this helps > > -- Andrew Gilmartin > > Server requirements > > Total disk spaced need to a minimum HyperCard environment is > > 1019K. Required files are; > When printing bitmap with HyperCard under NetWare, does the server > colapse? That's what's happening under 3 Com +. We are thinking of > NetWare but we want to play safe... > Roger-Daniel Laberge At present I don't have clear idea of how much disk space a spooler needs to print a HyperCard stack. As a rule of thumb you can expect HyperCard to send at least half a megabyte even for a stack of a dozen cards. -- Andrew Gilmartin Computing & Information Services Brown University Box 1885 Providence, Rhode Island 02912 andrew@brownvm.brown.edu (internet)