Peter

andrew> BASIC VI, aka BASIC64 is present as System:Modules.BASIC64 on all RO4 systems (and back through to... well, I don't know when, but that's what the modules database should tell you :-) )

As for the divide between OS and ROM; I'd suggest that if the module is part of the products default installation, then it's part of the OS. Take, for example, the PatchApp module (Boot:Utils.PatchApp on Select - I don't have a RO4 boot sequence to check the location but I would imagine it would be the same), aka AppPatcher. This lives on disc, but is should be considered part of the OS because it provides a vital function for the running of the system.

Should VProtect fall into that category too ? Pass; it's not vital to the running of the machine, but is supplied alongside PatchApp and it's actually a product of external entity that's just being supplied with the OS - you might consider ABClibrary similarly external from the OS itself. It really depends on what the maintainer of the datebase wishes to declare as what exactly the components are that comprise at 'Product' (in its parlance).

Modules, remember, are only one part of the whole OS - the boot sequence includes many different components whose versions can be identified readily (and some which cannot be so readily identified). Consider, if you have Select, the content of the Boot:Manifest file which describes the versions of components of the Boot sequence. Consider, as a subset of those, the output from *Help Library which describes library command versions.

What am I saying ? Oh, I don't know... Probably just that there is a degree of difference between OS, ROM and Product, and where you draw the line is really a matter of opinion - and in the case of this site, a matter for the maintainer of the site to decide.