🚀 go-pugleaf

In article <SPENCER.89Apr13140204@spline.eecs.umich.edu>
spencer@eecs.umich.edu (Spencer W. Thomas) writes:
>I am having trouble opening a HyperCard stack I placed on an AUFS
>volume.  I copied the stack there from my Mac, but Hypercard won't
>open it.  When I copy the stack back to my hard disk, it opens fine.
>I can open stacks on (regular) AppleShare volumes.  What is going on
>here?  The only clue I have is that when I tried a different stack
>(copying it to my AUFS directory, then trying to run Hypercard on it),
>I got an error -50 (indicating, I think, that a volume parameter
>wasn't supplied, or that it was supplied wrongly).


This is due to a BiZaRrE bit of code in HyperCard. It's not even a bug,
since it was apparently put there on purpose. For some reason I can't
remember, HyperCard opens stacks by a NaMe lIkE ThIs. In other words, it
capitalizes every other letter in the file name. Since Unix file systems
are case sensitive, of course AUFS isn't finding the file. I don't remember
for sure, but I think it capitalizes the first letter and every second
letter thereafter, but it might be the other way around, so your stack
might be looked for as "My sTaCk", but it might also be "mY StAcK". Don't
forget that spaces count...

Thus, the quick solution is to name your file so that this weird conversion
has no effect.

I thought that HyperCard 1.2.2 fixed this anamoly. If you're using 1.2.1
or earlier, get 1.2.2, it will probably fix all of your problems.

---
Alexis Rosen
alexis@ccnysci.{uucp,bitnet}
alexis@rascal.ics.utexas.edu  (last resort)