Re: Not enough application memory to start Basic

On 14 Jun, Michael Drake wrote in message
<539C509C.8090109@netsurf-browser.org>:

>
>
> On 14/06/14 14:30, Andrew Pinder wrote:
>
> > > We recently decided to make use of "!Cache" as we assumed it would be
> > > suitable and correct. (None of the core developers are actually using
> > > RISC OS at the moment, so we hadn't checked it actually worked.)
>
> > If you give some clues as to how to test it, some of us may be able to
> > give feedback :-)
>
> Thanks, but I think it's already been tested enough to show it doesn't
> work, as it stands. You should be able to put it in !Boot without it
> throwing up errors or having other side-effects.
>
> Our options are to get Cache from http://www.snowstone.org.uk/riscos/
> fixed, and continue using it, or create our own simpler solution.
>
> Steve Fryatt: any thoughts on this?

Well, I can't reproduce the problems that people are seeing. That's on
RISC OS 5, with reasonably recent copies of !Boot, and !Cache placed in
!Boot.Resources then left to be processed from there.

I don't run NetSurf during the boot sequence -- are all the people seeing
issues doing that? What are people's Next slots configured to during the
boot process?

The contents of !Cache don't seem too unreasonable. The !RunImage is just
there to set some system variables in a sensible way and make double-clicks
on the application behave differently once it's been set up (to open the
cache folder). As Chris says, there's Select profile support, and it logs
its setup decisions to SysLog if that's available.

You could probably do the whole lot from within an obey file, but it would
get messy.

I'm not sure what the MimeMan cache stuff is, but wonder if that got left in
by accident. It looks to be cache data for MimeMan.

--
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/