Is remote booting still possible?

I wonder what’s different about your setup

*show Boot*
Boot$ChoicesRW : Share::PiBoot.$.!shareboot.MchConfig.XXXXXXXXXX
Boot$Dir : Share::PiBoot.$.!ShareBoot
Boot$OSVersion : 520
Boot$Path : Share::PiBoot.$.!ShareBoot.
Boot$ReadOnly(Number) : 0
Boot$State : desktop
Boot$ToBeLoaded : Boot:MchConfig.XXXXXXXXXX.Boot.PreDesk
Boot$ToBeTasks : Boot:MchConfig.XXXXXXXXXX.Boot.Tasks
Boot$Unique : XXXXXXXXXX
BootFX$Path : Resources:$.Resources.BootFX.
BootNet$File : Freeway
BootResources$Dir : Share::PiBoot.$.!shareboot.Resources
BootResources$Path : Boot:RO520Hook.Res.,Boot:RO510Hook.Res.,Boot:RO500Hook.Res.,Share::PiBoot.$.!shareboot.Resources.
*show Choices*
Choices$Dir : Boot:MchConfig.XXXXXXXXXX
Choices$Path : Boot:MchConfig.XXXXXXXXXX.,Share::PiBoot.$.!shareboot.RO520Hook.
Choices$Write : Boot:MchConfig.XXXXXXXXXX
*

While working with the RPi3 this bug intervened so the RPi3 was replaced by a RPi2 which automatically created it own Boot$Unique directory.

Thanks; I’ll compare those later (it’s bedtime in this part of the world).

ShareBoot, no networking other than ShareFS, so no NetTime.

I wondered whether it could be permissions, but the fact that I was able to create the directory manually – from the client – would presumably disprove that.

Well it disproved it until proven otherwise! I removed “-protected” from the *Share command and it auto-created the directory successfully. I’m still not sure why, since MchConfig has WR/wr.

That’s completely workable in a home environment although it’ll be good in the long run to figure out the necessary permissions and document them somewhere.

ShareBoot, no networking other than ShareFS, so no NetTime.

Some success :-

Set Inet$Resolvers AA.BB.CC.DD WW.XX.YY.ZZ
Route -e add default 192.168.1.1
|
| Set ntp server by IP
Set NetTime$Server aa.bb.cc.dd
SetEval NetTime$Loaded 1
RMEnsure NetTime 0.39 X RMLoad System:Modules.Network.NetTime
RMEnsure NetTime 0.39 SetEval NetTime$Loaded 0
If <NetTime$Loaded> Then NetTime_PollInterval 1800

PlusNet IPs.

Posted from RPi2 booted over ShareFS.

Some success

A bit more success, the RPi3 is now also booting from ShareFS.

However the RPi3B+ won’t play. The PiBoot Share is never seen and *FWShow errors.

No valid Internet interfaces found.

It looks as if Freeway is not finding the RPi3B+’s new network interface.