RISC OS of the future...
Pages: 1 2
James Wheeler (3283) 344 posts |
RPi nightly build doesn’t seem to have a splash screen. |
Jeffrey Lee (213) 6046 posts |
Yeah – the BootFX module (which is responsible for the JPEG splashes and progress bar) claims Service_DesktopWelcome to suppress the standard desktop splash.
|
Andrew McCarthy (460) 126 posts |
Not necessarily impatient users per se, just users that want to get to the desktop quickly and start-using it.
Not quite, traditional behavior as RISC OS didn’t block on waiting for an IP address, but that point has been partly discussed here and else where in the Boot time thread where perhaps this digression probably should go ;-) EDIT: BTW thank you for the *Unplug BootFX tip, I did try it and I now understand why it was necessary to add the new start-up screen :( |
Jeffrey Lee (213) 6046 posts |
Be careful what you wish for, or I might revert the OS_ChangeDynamicArea optimisations that shaved over 10s off the boot time of modern machines, or the USB mass storage driver optimisations that fixed abysmal USB 2 performance, or the FileCore disc mount optimisation (which combined with the slow USB performance could cause large USB drives to take tens of seconds to mount) ;-) |
Rick Murray (539) 13401 posts |
FFS! So all those times in my life I started my A3000, A5000, RiscPC and thought that the Wimp was doing “housekeeping” as it starts, it was really just wasting my time? Who’s smart idea was that then? |
Steve Pampling (1551) 7931 posts |
If I’m reading things right it pops up the splash and then runs in little circles for 4 seconds and then clears the splash and then carries on. |
Jeffrey Lee (213) 6046 posts |
You are not reading things right. It initialises the splash screen (StartAsTask), clears the screen (ClearScreen), renders the splash screen + calculates the end time (NoBootError), then falls into PollLoop. PollLoop uses the NextPump variable to track its progress as it starts all of the other Wimp tasks (builtin stuff like the icon bar & pinboard, ROM apps like Edit which could be set to auto-boot via CMOS bits in the RISC OS 3 era, and whatever’s in your Choices:Boot.Desktop file). Only once all of those are done does it start checking to see if the 4s timeout has been reached (KeepItUpLoop). Of course on something like an A3000 you probably would have had a very minimal boot sequence (if any), so most of the time would have been spent doing nothing. |
Steve Pampling (1551) 7931 posts |
Thank god for that. |
Rick Murray (539) 13401 posts |
IconBarHack in the aforementioned code. That’s quite a bodge! ;-) Dunno why the footnote isn’t working. Textile being objectionable… fn1. “Recent” as in RiscPC era. Sadly, I don’t have a copy of the MEMC era Wimp code. |
Jeffrey Lee (213) 6046 posts |
Yes – digging through the history in CVS, it looks like the 4s timer first appeared in RISC OS 3.7, while older versions would have just exited as soon as all the tasks had started. |
Chris Mahoney (1684) 2100 posts |
Well, without further ado, Nosplash. Goes in !Boot.Choices.Boot.PreDesk. Note that the module name is not allocated and it has no documentation other than what’s in this post :) Edit: 22 downloads on the first day. Not too bad. Now we just need something to get rid of the 4-second delay in the first place! |
Pages: 1 2