| From: | Steve Hargreaves |
| Date: | 8 Jul 2001 at 12:49:29 |
| Subject: | Re: SquirrelSCSI |
On 08-Jul-01, Jim Cadwallader said -
>JC It's not because of a missing library IMO. If you are using the '060
>JC squirrelscsi.device it's probably because support for '040 up is installed
>JC by SetPatch, the device thus can't be opened without an error 'til then.
>JC I had the same prob tinkering with the '060 device then went back to the
>JC '020 device I should have been using anyway.
I think I'll just give up on the idea, then. 99% of the time I have no problems,
just the occasional drawer on a CD seems to meet a deadlock, and everything
grinds to a halt until it frees itself. As I said in my orig post, the problems
I have are V rare.
>JC I think it's used for setting SquirrelSCSI options such as POLLEDIO, DEVICE
>JC name,
>JC and may also be used for mounting SCSI HDs.
>JC
>JC Return codes are 0 = success, 5 = warning (e.g. in scripts "If WARN ...")
>JC but
>JC continue script, 10 = error & abort script unless FailAt set higher, 20 =
>JC failure.
Thanks. The wierd thing is, If I include C:SquirrelSCSI is SS before setpatch,
it fails return code 20 and aborts booting & throws me in to a shell. If I then
type C:SquirrelSCSI in the shell window, I get no error :o/
Subsequently executing SS again reproduces the error, so it only seems to fail
in scripts.
Regards
Steve
ICQ 21361336
----------------------------------------------
I have seen what power does, and I have seen what power costs. The one
is never equal to the other.
-- G�Kar
Quote carefully and read all ADMIN:README mails
To unsubscribe mailto:amigactive-unsubscribe@yahoogroups.com
Anyone sending unsubscribe messages to the list will be SHOT!
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/