[Oberon] Re (2): Re (2): Starting V4.
joerg.straube at iaeth.ch
Thu Feb 4 07:57:10 CET 2021
Sorry, it seems to depend on what version of V4 you look at.
I just checked with the V4 on Windows, there the boot sequence seems to be different.
There is no code to run commands from System.InitCommands.
During initialization of System.Mod
- Init is called
- then OpenViewers is called
In OpenViewers the module "Configuration" is loaded, if available.
If not available, OpenViewers opens the file System.Tool (hardcoded).
In the Init procedure of Configuration.Mod you can put all your desired commands you want to run during boot. Eg.
- set your preferred color scheme
- set the working directory
- open System.Tool
Am 04.02.21, 07:17 schrieb "Joerg" <joerg.straube at iaeth.ch>:
I‘m not quite sure but the text file „System.InitCommands“ is only there if you created one, with your commands you want to add during boot.
> Am 04.02.2021 um 03:49 schrieb peter at easthope.ca:
> From: =?utf-8?Q?J=C3=B6rg?= <joerg.straube at iaeth.ch>
> Date: Wed, 3 Feb 2021 22:14:40 +0100
>> In PO, the file „System.Tool“ is opened in System.OpenViewers (this is hard coded)
>> In V4, the file „System.Tool“ is opened in System.Init. If valid
>> commands exist in the file „System.InitCommands“, then these
>> command are executed instead.
> Here I have V4 1.7.02 in Debian Linux.
> Neither System.Init nor System.InitCommands is present. Also no
> Oberon.Ini, although a copy from the Windows release was sent to me.
> Appears that some bolts were omitted when 1.7.02 was assembled for
> I'll aim to find, install and execute an earlier version. Might find
> more there.
> Ideally, I should make a complete release and put it on Sourceforge.
> The opportunity might be some time in the future. =8~/
> Thanks for the help, ... P. L.
> Tel: +1 604 670 0140 Bcc: peter at easthope. ca
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
More information about the Oberon