Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!swrinde!kent
From: kent@swrinde.nde.swri.edu (Kent D. Polk)
Newsgroups: comp.sys.amiga.misc
Subject: Re: SKsh and A3000
Message-ID: <1126@swrinde.nde.swri.edu>
Date: 5 Feb 91 21:56:31 GMT
References: <1991Jan31.232429.25396@max.physics.sunysb.edu> <37090001@hpfcdc.HP.COM> <26690@uflorida.cis.ufl.EDU>
Sender: news@swrinde.nde.swri.edu
Organization: Southwest Research Institute, San Antonio, Texas
Lines: 22

In article <26690@uflorida.cis.ufl.EDU> pm0@springs.cis.ufl.edu (Patrick Martin) writes:
>What you have to do to get it to run is:  1) Set it up like the directions
>say then 2) Place a lock on the file s:.skshinit (You can do this by
>loading .skshinit into an editor and putting the window into the background.
>
>I would like to know how to put a lock on the file without going to this
>extreme.  (Still an Amiga novice)  Anyways, now run skshinit like you
>normally would and it should run fine.  It does on my A3000 anyways.

The nofastmem method doesn't work on any of the A3000's I tried it on.

I was the one who discovered the method of placing a lock on
s:.skshinit to startup up Sksh on an A3000. I have tried various
methods of putting a lock on s:.skshinit, and not all of them work.
Unfortunately, I don't know about the inner workings of this stuff & so
don't have too many easy suggestions. If anyone can shed some light on
this matter, I sure would appreciate it.


Kent Polk: Southwest Research Institute (512) 522-2882
Internet : kent@swrinde.nde.swri.edu
UUCP     : $ {cs.utexas.edu, gatech!petro, sun!texsun}!swrinde!kent