[Prev][Next][Index][Thread]
Re: Executor 1.99p & HyperCard 2.2 Installer
>>>>> "Frank" == Phylax <phylax@pyramid.mhv.net> writes:
Frank> Hi, I'm running Executor 1.99p under DOS and Linux and need
Frank> to use HyperCard 2.2. I copied all installation disks from
Frank> 800 kB disks to 1.44 MB disks and Executor recognizes those
Frank> without problems. When I try to run the Installer Script of
Frank> HyperCard 2.2, Executor crashes with a Segmentation fault
Frank> or Protection fault, respectively. Does anybody know a
Frank> solution for this problem? Any help would be appreciated.
There probably isn't a short term solution, but there is a workaround.
The workaround would be to install HyperCard on a Mac first, then
bring it over to Executor. There are a number of ways you can do
that.
The easiest is to use an external hard drive, but this requires you to
have an external hard drive and also requires your PC to have a SCSI
adapter.
The next easiest would be to use Stuffit or Compact Pro to create a
big file that contains the HyperCard directory and then use a network
to copy things across. Of course this requires you to have a Mac with
an ethernet card near your PC and of course your PC will need an
ethernet card, too. If you have those, you can use NCSA Telnet to
push the file across in MacBinary mode, then use Stuffit Expander to
expand it.
Beyond that, you can use Compact Pro to make a bunch of installation
floppies, which you can then copy to your hard drive under Executor
and then run Compact Pro to expand the pieces. NOTE: you can't do
this directly off the floppies yet; there are aspects of the Mac
filesystem that aren't implemented that prevent this from working.
All three of the above require you to use a Mac in some capacity to
get HyperCard loaded. We regret this inconvenience and it is
something we'll be spending a lot of time working on after 2.0 ships.
The problem is that installation programs often use aspects of the Mac
filesystem that most other programs don't use, so it takes more work
for us to get installers to go than to get applications themselves to
go. We don't like to be in this position, but we also don't yet have
enough engineers to fix everything simultaneously.
Frank> Thanks, Frank
Frank> =============================================================================
Frank> Frank Stolze Frank.Stolze@marist.edu
Frank> http://pyramid.fac.marist.edu/~phylax/
Frank> =============================================================================
--Cliff
ctm@ardi.com
References: