New Boot sequence , Iyonix and RISC OS 5.18 network issues

re: Toolbox modules

I had a lot of support issues with Basalt, because of the version numbers. I gave up bothering to check these anymore and just assume the lowest common denominator, circa 1995 perhaps. That is a shame. I think AppBasic does the same.

re: Toolbox modules

Essentially, for support stability the ROOL branch needs a Toolbox set that delivers all that functionality and any extras people create on the way.
Then people can use one, supported, OS on all machines made in the last 18+ years and developers have one single OS to target.

This part of Sprow’s post is, possibly, the most relevant and I have heard others say the same:

I’ll repeat (again) that the Harddisc4 image is self consistent and contains all the modules and resources needed for the apps on it that ROOL are licenced to distribute.

The last phrase of this is the problem?
Yes, you are confused about the version number of EtherUSB. I didn’t give the version number of EtherUSB, but it’s v0.13. v5.19, 15th September is the ROM version I am using.

Anyway, I still have the problem of my BeagelBoard powering up to *Supervisor. If I then reboot BB I get the desktop without problem.
I know I can test all sorts of combinations of SD card, ROM, USB hub, USB stick etc.; but to save time does anyone have an idea of where the fault is most likely to be?

I’ll repeat (again) that the Harddisc4 image is self consistent and contains all the modules and resources needed for the apps on it that ROOL are licensed to distribute.

Perhaps it would be nice to include also those modules and resources that do not happen to be called for by the apps in the standard image where ROOL are licensed to distribute the modules/resources themselves?

To answer part of my own post, I think I can see why Sprow was confused by my BB’s EtherUSB version number. Verma reveals that v0.21 of 9/9/12 is in ROM, that is, version 5.19 of my 15th September download (actaully dated 13/9/12). So I can remove EtherUSB from the !Boot directory.

If I change the ROM, it is often that the first start after launch the ROM ends in *supervisor. With type !Boot it continues normally. For me it has always helped bring up the network settings and re-save (unchanged). The next restart was then fine.
Should leave the older version in EtherUSB in !Boot should not be a problem because the newer should be preferred. If you are go back to a ROM without EtherUSB, the system reverts to the saved.

Thanks for that help, I will try it next time BB gives me *Supervisor.