🚀 go-pugleaf

In article <1992Sep6.230737.4585@cs.nott.ac.uk> smb@cs.nott.ac.uk (Simon Burrows) writes:
>The RISC OS 3.10 desktop messages file contains an entry labelled "Pre",
>which contains no text (it is used to display messages about pre-release
>versions of RISC OS 3). This is quite useful if you put your own name
>in here, and register the file with ResourceFS, since it is displayed
>in large letters as part of the RISC OS 3 Title Screen.
>
>SimonB.

Nice! Personally I am so sick of that screen (having seen it daily since last
November) that long ago I stuck a short hack module by Brian Brunswick in my 
boot sequence which stops the screen appearing. It might even speed up the 
desktop entry by a second or so ... I thought Brian had posted the module to 
Newcastle - but I may be wrong.

(For some techie content to this post - the module works by claiming a
RO3 service call, so that you can have your own complete replacement screen -
perhaps there will be a flood of modules that give us title music, and star
bursts, and ... )

Nick.
--
Nick Smith, Churchill College, Cambridge, UK.  %$%  Email: nas20@uk.ac.cam.phx
sig quote wanted - must be under guarantee.   $%$  --- Usual disclaimer. ---

In article <1992Sep6.230737.4585@cs.nott.ac.uk> smb@cs.nott.ac.uk (Simon Burrows) writes:

>versions of RISC OS 3). This is quite useful if you put your own name
>in here, and register the file with ResourceFS, since it is displayed

This sounds very nice, but just how does one register a file with
ResourceFS?

Steve
|  Steve Loft                                  steve@klaatu.demon.co.uk   |
|  Doncaster,                                                             |
|  South Yorks.                                                           |

In article <1992Sep7.114632.17745@infodev.cam.ac.uk> nas20@cl.cam.ac.uk (Nick Smith) writes:
>
>Nice! Personally I am so sick of that screen (having seen it daily since last
>November) that long ago I stuck a short hack module by Brian Brunswick in my 
>boot sequence which stops the screen appearing. It might even speed up the 
>desktop entry by a second or so ... I thought Brian had posted the module to 
>Newcastle - but I may be wrong.

That module sounds useful, particularly for hard disc ARM2 users - the
start up is the most painful bit with RISC OS 3 and ARM2.

One way to speed up display of the RISC OS 3 Title Screen, if you have
a hard disc, is as follows:

Once the title screen has been displayed, and you are in the desktop,
type *SAVEFONTCACHE <filename>.

Now, in your system !Boot file, include the line *LOADFONTCACHE <filename>
BEFORE the desktop starts up. I don't think this is possible if you have
a single file !Boot (rather than application directory) created by the
automatic 'Desktop Boot' facility.

This makes the start up much quicker. I'm currently looking into another
way of drastically speeding up the ARM250 machines (where the title page
display is still rather slow). Details at a later date if successful.

Hope this is useful!

Simon.
--------------------------------------------------------------------------
Simon Burrows smb@cs.nott.ac.uk psyhsmb@unicorn.nott.ac.uk +44 533 712030
--------------------------------------------------------------------------

In article <715900053snx@klaatu.demon.co.uk> Steve@klaatu.demon.co.uk (Steve Loft) writes:
[...]
>This sounds very nice, but just how does one register a file with
>ResourceFS?

You register files by using the Resoure_Register SWI, providing the call with
a pointer to a structure containing a set of files to put on ResourceFS. This
is best done from a module.

If people can wait a month or so (for me to get back to Cambridge - this is
being posted from a BBC Master via modem!), then I can send people copies of
my !MakeRes application - you just drag in the files you want, and it will save
a relocatable module that puts them on ResourceFS for you.

If I get several requests for the module before I return to Cambridge, I'll put
it on the Newcastle Infoserver instead.

A version that instead produces an object file containing functions to register
and deregister the files is coming soon - this will allow files to be easily
embedded in a module generated with cmhg.

--Clive.