Re: Steamband for RISC OS _ DO NOT USE

In article <3863799c4f.harriet@[EMAIL PROTECTED]
>,
   Harriet Bazley <bazley@[EMAIL PROTECTED]
> wrote:
> On 8 May 2008 as I do recall,
>           Steve Clark  wrote:

[Snip]

Thanks to Harriet & Timo I found the problem.

> I don't see why lib.user, no option that I know of can do that on
> purpose so how could it get triggered consistently by a bug?

That's the clue I'd missed.  <ctrl>dble click does that with bands made
using Musus' Angband builder.

> > 2 no bands have icons

> *Band.!Boot is failing before reaching the line 

> IconSprites <Obey$Dir>.!Sprites

> ?


> > 3 click !RunImage gives "No Writable memory error"
> > 4 Running  !Startdand and clicking Play! gives "Can't use that
> > loc`ation(å)"

> This is caused by the failure of OS_File 6 and/or OS_File 10 in
> !Startband when attempting to create a file at the specified
> location....


> > 
> > I've Tried deletng my BOOT and REplacinh it from scratch (*CD*) with
> > minor improvement.  This extent of damage should be impossible on a
> > RISCOS machine

> That shouldn't be possible.

> You've still got the OS in ROM.   Presumably you've tried a ****ft-Boot?

> Have you got !Re****ter?
Yes, but I don't think it tests for hardware faults.

Timo was right, it may have been a coincidence.  Steamband hanging up when
the keboard buffer is overfull is not uncommon, and usually I can only
escape by quitting the program.

In this case the ctrl key jammed - once I'd stripped down and cleaned
the keyboard it started working again.  My usual editor - StrongEd - was
completely disabled by the jammed key, but typing the alphabet on Edit
had confirmed the problem.

I  don't know why the sprites went wrong but that is likely a feature in
the OS.  The very varied way in which different programs handle the
<ctrl> key was disconcerting and probably caused most of my confusion.

Also until I rebuilt my Boot file the <****ft> key was non-operational,
which prevented me looking at the files inside Steamband to try to find
a cause of the problem.

[Snip]

> Well I've noticed a couple of 'funnies' since upgrading my Steamband
> (first Rhapsody crashed every time I tried to run it then PipeDream kept
> complaining it was out of memory although I had over 4Mb free) but I
> didn't connect either of them with the program.   I don't see how they
> could have been, Steamband doesn't even get seen by the Filer unless I
> manually open the Angband directory.

Until Steamband hangs on someone again we'll not be sure whether it's
just an old keyboard or Steamband overwrites something it shouldn't.
Just in any case - next time I'm using <alt><break> to exit the program. 

-- 
Steve Clark
                                                   
{sjclark@[EMAIL PROTECTED]
 using a 129Mb SA 6.06 RiscPC}