HardDisc image

The 20th July ‘standard’ hard disc image is not complete. It gives the following errors:
‘Directory Boot:RO510Hook.Res not found’
‘Directory Boot:RO400Hook.Res not found’
‘Directory Boot:RO370Hook.Res not found’
‘Directory Boot:RO360Hook.Res not found’
‘Directory Boot:RO310Hook.Res not found’

I was trying to put together an up to date disc image starting afresh from the standard disc contents (in case anything had changed) and applying the successive updates to generate a new Distro. Incidentally, the directory RO510Hook.Res was never present and didn’t give an error before.

Incidentally, the directory RO510Hook.Res

Whoever added the RO510Hook forgot to update the corresponding (pre)desktop file(s) to point to them, so they’ve incorrectly been omitting that from boot resources and just pointing at RO500Hook. I fixed that.

As to the missing directories, they are there when the build completes so I think it is ‘tar’ throwing away empty directories. You can manually create them – there should be “Apps” “Boot” and “Res” in each of the hooks. Is the self extracting HardDisc4 different? That would confirm my ‘tar’ theory.

That will be a side-effect of Sprow’s work-in-progress to make the boot sequence more ‘universal’ again. I’ll have to wait for a comment from him on when he thinks this stuff will be stable again.

Damn, he beat me to it!

Is the self extracting HardDisc4 different?

Don’t know, but they are missing in the HardDisc4/util self extracting version.

I have tried to create a fresh disc image with the 21 July ROM and hard disc image HardDisc4/util.

During start up I have had to do the following work arounds:
create the following empty directories:
!Boot.RO510Hook.Res
!Boot.RO400Hook.Res
!Boot.RO370Hook.Res
!Boot.RO360Hook.Res and
!Boot.RO310Hook.Res
to avoid errors during booting saying ‘Directory … not found’.
In the 8 July HardDisc4 image the empty 510Hook.Res directory was not present but no error was generated. Is there an ’IfThere’ missing somewhere?

After configuring the DHCP networking and time setting from internet I have to manually
set the filetype of !Boot.Choices.Internet.Startup from Text to Obey.

However the good news is that RISC OS Now boots up on to the desktop, with no ethernet cable connected, in 55 seconds. (With the cable connected it is 18 seconds so there seems to be about 40 seconds added with no networking.)

create the following empty directories

I remain puzzled as to why that’s happening – when built on ADFS they all copy over fine here, so now I’m pointing my finger at HostFS (which is what the autobuilder uses). My previous theory about ‘tar’ not storing empty directories was shot to bits when I noticed that the (empty) Choices directory is correctly preserved. I’ve tweaked the makefile to try something else for tomorrow.

In the 8 July HardDisc4 image the empty 510Hook.Res directory was not present but no error was generated. Is there an ’IfThere’ missing somewhere

No, per my earlier comment, this is a longstanding fault that the boot sequence didn’t add 510Hook to its path variables. In fixing that, it has exposed this empty directory problem.

On the “Internet.Startup”, seems to create obey files for me, though !InetSetup has been having some work done on it I note.

I have tried to create a fresh disc image with the 21 July ROM and hard disc image HardDisc4/util.

During start up I have had to do the following work arounds:
create the following empty directories:
!Boot.RO510Hook.Res
!Boot.RO400Hook.Res
!Boot.RO370Hook.Res
!Boot.RO360Hook.Res and
!Boot.RO310Hook.Res
to avoid errors during booting saying ‘Directory … not found’.

These errors now fixed, thanks.

After configuring the DHCP networking and time setting from internet I have to manually set the filetype of !Boot.Choices.Internet.Startup from Text to Obey.

This error still (24 Jul 2012) persists: if you start with the vanilla boot sequence [with ‘Boot:Choices’ empty], then the file ‘StartUp’ has to be created (and is created with filetype ‘text’ and so just prints to the screen on start up rather than doing anything). If you modify an existing boot structure there will already be a file of the correct filetype present and the file is therefore created with the correct filetype.

if you start with the vanilla boot sequence [with ‘Boot:Choices’ empty], then the file ‘StartUp’ has to be created (and is created with filetype ‘text’ and so just prints to the screen on start up rather than doing anything).

I’ve still not been able to recreate this, nor can I see why it would happen from looking at InetSetup. What I tried: an IOMD ROM with harddisc4 containing Boot 0.95, boot to desktop, check !Boot.Choices.Boot got copied in and !Boot.Choices.Internet doesn’t exist. Ran InetSetup, configured some stuff, saved. !Boot.Choices.Internet now exists and includes a Startup file of type obey.
This was on ADFS, and I also checked on an emulator on HostFS.

You’re not write protecting “SetUpNet” are you? That’s the only route I can see where you’d get an unfiletyped “StartUp”. What is Boot$ToBeLoaded set to?

You’re not write protecting “SetUpNet” are you? That’s the only route I can see where you’d get an unfiletyped “StartUp”. What is Boot$ToBeLoaded set to?

No. I did not run InetSetUp, what I did was to double click on !Boot and click on Network, Internet, Interfaces, Configure, via DHCP, Set, CLose, Close, Save, Reset later. If you open the directory viewer on !Boot.Choices.Boot.Internet and delete the file ‘StartUp’ then go through this process you will see a file ‘StartUp’ of type Text is created. This is repeatable. QED.

I did not run InetSetUp, what I did was to double click on !Boot and click on Network

The network icon in !Configure runs InetSetup, which is what I did too. I’ve also tried on a Beagleboard both via a USB memory stick and SDFS (just set Choices$Write manually, then click save in InetSetup). However in both cases the Startup file was created as an obey file.

Stumped.

Chris, if you set Reporter to run at boot, logging commands etc, you may get some clues as to when the problems are happening.

After configuring the DHCP networking and time setting from internet I have to manually set the filetype of !Boot.Choices.Internet.Startup from Text to Obey.

This error was still there on 24 Jul 2012 but has now been corrected.