On 20 May 2013, george greenfield <george.greenfield@tiscali.co.uk>
wrote:
[snip]
> - 0810/519 /never/ connects the first time of booting; the second
> attempt (not using the 'restart' button, but a complete relaunch)
> almost always connects, and if not, a third attempt invariably works.
Here 0810/519 usually connects, first time, provided that the host
machine is not diverted by its housekeeping, or whatever. I've learned
to wait for a few minutes, after Win7 boots, before running RPCEmu.
I suspect that the 'restart' button doesn't reset _everything_, so I too
normally quit, and re-launch.
[snip]
> - Running a fairly recent version of NetSurf (3.1 Dev#1122) with JS
> enabled, the app takes about a minute to load for the first time after
> startup - it's as if it was parsing fonts (but there's no indication
> that it is doing this). During this time, MIPS remain at 'idle'
> levels: +/- 4-5 MIPS. When it has been run once, it can be quit and
> relaunched at normal speed, and in use it behaves normally and seems
> just as quick (but not noticeably quicker) than a parallel
> installation on 089/402. The usual !Boot and !System NetSurf modules,
> and IConv, have been installed. I can't explain this behaviour - has
> anyone else encountered it?
Slow loading could be caused by large Hotlist, Cookies or URL files in
Choices, or a large Log file, or Cache directory, in in Scrap. However,
this would not explain the subsequent normal loading times.
Do other applications behave the same way?
Here using Win7 32bit 1.7GHz dual-core processor / RPCEmu0810 / RO519
(19-May-13), running NetSurf #1178 json, from HostFS, for the first time
takes 9 secs. However, an obey file in 519 Boot deletes Hotlist,
Cookies, URL, Log and Cache, so that NetSurf starts with a clean slate.
Tony
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
No comments:
Post a Comment