Hi, My first post here and I hope someone can help. I’ve been using NCID on a GetChip for the past 9-12 months and it has been great, until the CHIP stopped connecting to WiFI. I decided to install instead on a brand new Pi Zero.
The Pi is setup as a headless unit with Raspbian Stretch Lite release date 2017-11-29 kernel version 4.9
However when I install the client package I get the error below:
Unpacking ncid-client (1.7-1) ...
dpkg: error processing archive ncid-client_1.7-1_all.deb (--install):
trying to overwrite directory '/usr/share/ncid/images' in package ncid 1.7-1 with nondirectory
Processing triggers for systemd (232-25+deb9u1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
ncid-client_1.7-1_all.deb
I’ve tried setting the ncid and images directories to 777 and this doesn’t make any difference. I’ve also tried installing the client first and again the server then fails to install with the same message.
I'm now going to try installing 1.6.1 to see if I can get that to install.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've now installed 1.6.1 both server and client and they installed OK with no problems.
But I've now got issues running NCID!
sudo invoke-rc.d ncidd start - this runs and returns to the command prompt.
But when I check the status I get
● ncidd.service - LSB: NCID (Network Caller ID) Server
Loaded: loaded (/etc/init.d/ncidd; generated; vendor preset: enabled)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
invoke-rc.d: initscript ncidd, action "status" failed.
Then wieh I run: ncid &
I get this:
pi@pi-zero2:~ $ ncid & [1] 599
pi@pi-zero2:~ $ invalid command name "font"
while executing
"font families"
(procedure "scanFonts" line 7)
invoked from within
"scanFonts"
(procedure "makeWindow" line 43)
invoked from within
"makeWindow"
invoked from within
"if {!$NoGUI} {
doVerbose "GUI Display" 1
doVerbose "Popup time: $PopupTime" 1
if {$NoExit} {
set ExitOn do_nothing
doVerbo..."
(file "/usr/bin/ncid" line 2326)
To help debug I ran: ncidd -Dv3
The result is below. This looks OK to me, and indeed when I ring in I NCID responds correctly.
I'm probably doing something simple wrong and would value some help.
ncidd -Dv3
Started: 12/27/2017 20:26:48
Server: ncidd (NCID) 1.6
API: 1.5 Feature Set 1 2 3 4 5
Sysname: Linux
Machine: armv6l
Release: 4.9.59+
Version: #1047 Sun Oct 29 11:47:10 GMT 2017
Command line: ncidd
-Dv3
/var/log/ncidd.log: Permission denied
Processed config file: /etc/ncid/ncidd.conf
Verbose level: 3
Configured to send 'cidlog' to clients.
Configured to send 'cidinfo' to clients.
Helper tools:
/usr/bin/cidupdate
/usr/bin/ncidutil
Using simple expressions for aliases
Using simple expressions for blacklist/whitelist entries
Begin: Loading alias, blacklist, and whitelist files [20:26:49]
Processed alias file: /etc/ncid/ncidd.alias
Alias Table:
Number of Entries: 1
Processed blacklist file: /etc/ncid/ncidd.blacklist
Blacklist Table:
Number of Entries: 18
Calls in the blacklist file will be terminated
Processed whitelist file: /etc/ncid/ncidd.whitelist
Whitelist Table:
Number of Entries: 0
Calls in the whitelist file will not be terminated
Leading 1 in call & alias/blacklist/whitelist not ignored
End: Loaded alias, blacklist, and whitelist files [20:26:49]
/var/log/cidcall.log: Permission denied
Data logfile not present: /var/log/ciddata.log
Maximum number of clients/gateways: 50
Telephone Line Identifier: -
TTY port opened: /dev/ttyACM0
TTY port speed: 115200
TTY lock file: /var/lock/LCK..ttyACM0
TTY port control signals enabled
TTY port initialized in ICANON mode.
Checking Modem Capabilities...
TTY port changed to RAW mode.
Sent Modem 20 of 20 characters:
AT Z S0=0 E1 V1 Q0
Modem response: 26 characters in 1 read:
AT Z S0=0 E1 V1 Q0
OK
Modem Initialized
Sent Modem 6 of 6 characters:
ATI3
Modem response: 39 characters in 1 read:
ATI3
CX93001-EIS_V0.2002-V92
OK
Modem Identifier: CX93001-EIS_V0.2002-V92
Sent Modem 9 of 9 characters:
AT+GCI?
Modem response: 27 characters in 1 read:
AT+GCI?
+GCI: B4
OK
Modem country code: B4 United Kingdom
Sent Modem 6 of 6 characters:
AT&V
Modem response: 824 characters in 1 read:
AT&V
ACTIVE PROFILE:
B1 E1 L2 M1 N0 Q0 T V1 W0 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R1 &S0 &T5 &X0 &Y0
S00:000 S01:000 S02:043 S03:013 S04:010 S05:008 S06:003 S07:090 S08:001 S09:006
S10:014 S11:085 S12:050 S18:000 S25:005 S26:001 S36:007 S38:020 S46:138 S48:007
S95:000
TELEPHONE NUMBERS:
0= 1=
2= 3=
Sent Modem 13 of 13 characters:
AT+FCLASS=?
Modem response: 32 characters in 1 read:
AT+FCLASS=?
0,1,1.0,8
OK
Modem supports Data Mode
Modem supports FAX Mode 1
Modem supports VOICE Mode
TTY port changed to ICANON mode.
TTY port changed to RAW mode.
Sent Modem 20 of 20 characters:
AT Z S0=0 E1 V1 Q0
Modem response: 26 characters in 1 read:
AT Z S0=0 E1 V1 Q0
OK
Modem initialized.
Sent Modem 11 of 11 characters:
AT+VCID=1
Modem response: 17 characters in 1 read:
AT+VCID=1
OK
Modem set for CallerID.
TTY port changed to ICANON mode.
CallerID from AT Modem and optional gateways
Does not handle modem calls without Caller ID
Modem used for CallerID and to terminate calls
Internal Hangup Mode = 1: hangup on a blacklisted call
Network Port: 3333
Debug Mode
Not using PID file, there was no '-P' option.
Modem is fd 3
NCID connection socket is sd 4 pos 1
End of startup: 12/27/2017 20:26:49
Client 5 pos 2 from 192.168.0.110 [Sandy-iMac.home] connected 12/27/2017 20:26:54
200 Server: ncidd (NCID) 1.6
210 API: 1.5 Feature Set 1 2 3 4 5
Client Sent: no data
253 No Call log: /var/log/cidcall.log
Sent 'hangup-1' option to client
300 End of connection startup
MESG = 110101
DATE = 1227
TIME = 2038
NMBR = **
RING
CIDINFO: LINEPOTSRING1TIME20:38:07
Whitelist empty
Checked Blacklist for match flag=0 ret=0 nmbrmatch=0
CID: DATE12272017TIME2038LINEPOTSNMBR*MESG110101NAME110101
RING
CIDINFO: LINEPOTSRING2TIME20:38:07*
RING
CIDINFO: LINEPOTSRING3TIME20:38:10
CIDINFO: LINEPOTSRING0TIME20:38:19
Last edit: Sandy Matheson 2017-12-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your report on the issue with Raspbian Stretch. I don't think any of us developers have installed Stretch yet (I know I haven't because I don't have a spare SD card; I'll have to order one).
Regarding 1.6.1 that you were able to successfully install:
But when I check the status I get
● ncidd.service - LSB: NCID (Network Caller ID) Server
Loaded: loaded (/etc/init.d/ncidd; generated; vendor preset: enabled)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
invoke-rc.d: initscript ncidd, action "status" failed.
Something appears to be preventing ncidd from starting up. If you could attach your ncidd.log file to this thread, or if you'd rather you can send it via private email attachment to John (jlc@users.sf.net) and to me (tandrews@users.sf.net). Your privacy is assured, however, feel free to obfuscate phone numbers and caller names.
Regarding the ncid client:
pi@pi-zero2:~ $ ncid & [1] 599
pi@pi-zero2:~ $ invalid command name "font"
while executing
"font families"
(snip)
By default ncid expects to be running in a GUI terminal. If you try to launch ncid from an SSH session, you'll get errors like the above.
Use 'sudo' when testing ncidd to prevent the permission errors: sudo ncidd -Dv3
I'm surprised your test worked because usually the same issue that prevents ncidd from running via sudo invoke-rc.d ncidd start will show up when doing sudo ncidd -Dv3. Getting ncidd.log as an attachment will provide us with more info.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There was also an error in the server install package that prevents the install of the client package. The fix is in deb packages 1.7-3. You need to install both the ncid and ncid-client packages for the fix.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The good news - both server and client install without any errors.
Unfortunately I'm still not able to start NCID using sudo invoke-rc.d ncidd start - same issue as with 1.6.1 Happy to send over the log file, but I can't find one. It's not in /var/log and I can't see a configuration option in ncidd.conf to set the location.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was concerned with fixing the client install problem. Todd is still working on your problem startup problem but it might be a Raspbian Stretch issue with the startup script. We will install Raspbian Stretch and continue to work the startup issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't have a definitive answer, but I have a workaround that should be stable for you. I have tried this workaround about half a dozen times on my RPi and it is working for me.
If I try to launch ncidd with invoke-rc.d ncidd startwithout first enabling it across run levels with update-rc.d, I can duplicate the issue. Normally we recommend, after an initial install, to launch ncidd with invoke-rc.d first and test, before enabling the permanent autostart with update-rc.d but for some reason it isn't working in Raspbian Stretch.
So the workaround is:
Make sure set ttyport in ncidd.conf is pointing to a real modem.
Just to make sure there wasn't anything left over from previous installs and uninstalls I started over by reinstalling Raspbian so I had a clean system.
Everything installed OK with 1.7.3 and following your sequence ncidd started as well. I can also confirm that ncidd was loaded correctly on reboot.
The results of searching for ncidd.service are below:
pi@raspberrypi:~ $ sudo find / -name ncidd.service
/run/systemd/generator.late/graphical.target.wants/ncidd.service
/run/systemd/generator.late/multi-user.target.wants/ncidd.service
/run/systemd/generator.late/ncidd.service
/sys/fs/cgroup/devices/system.slice/ncidd.service
/sys/fs/cgroup/systemd/system.slice/ncidd.service
I also use ncid-notify to run alerts of incoming calls to various screens in my house. I can confirm that using the same sequence this loaded OK and survives reboots.
Thanks for working on this problem, especially over this Christmas period.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, My first post here and I hope someone can help. I’ve been using NCID on a GetChip for the past 9-12 months and it has been great, until the CHIP stopped connecting to WiFI. I decided to install instead on a brand new Pi Zero.
The Pi is setup as a headless unit with Raspbian Stretch Lite release date 2017-11-29 kernel version 4.9
I ran: sudo apt-get install libpcap0.8-dev
I downloaded and installed the following files:
https://sourceforge.net/projects/ncid/files/ncid/1.7/ncid_1.7-1_armhf.deb
https://sourceforge.net/projects/ncid/files/ncid/1.7/ncid-client_1.7-1_all.deb
However when I install the client package I get the error below:
Unpacking ncid-client (1.7-1) ...
dpkg: error processing archive ncid-client_1.7-1_all.deb (--install):
trying to overwrite directory '/usr/share/ncid/images' in package ncid 1.7-1 with nondirectory
Processing triggers for systemd (232-25+deb9u1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
ncid-client_1.7-1_all.deb
I’ve tried setting the ncid and images directories to 777 and this doesn’t make any difference. I’ve also tried installing the client first and again the server then fails to install with the same message.
I'm now going to try installing 1.6.1 to see if I can get that to install.
I've now installed 1.6.1 both server and client and they installed OK with no problems.
But I've now got issues running NCID!
sudo invoke-rc.d ncidd start - this runs and returns to the command prompt.
But when I check the status I get
● ncidd.service - LSB: NCID (Network Caller ID) Server
Loaded: loaded (/etc/init.d/ncidd; generated; vendor preset: enabled)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
invoke-rc.d: initscript ncidd, action "status" failed.
Then wieh I run: ncid &
I get this:
pi@pi-zero2:~ $ ncid &
[1] 599
pi@pi-zero2:~ $ invalid command name "font"
while executing
"font families"
(procedure "scanFonts" line 7)
invoked from within
"scanFonts"
(procedure "makeWindow" line 43)
invoked from within
"makeWindow"
invoked from within
"if {!$NoGUI} {
doVerbose "GUI Display" 1
doVerbose "Popup time: $PopupTime" 1
if {$NoExit} {
set ExitOn do_nothing
doVerbo..."
(file "/usr/bin/ncid" line 2326)
To help debug I ran: ncidd -Dv3
The result is below. This looks OK to me, and indeed when I ring in I NCID responds correctly.
I'm probably doing something simple wrong and would value some help.
ncidd -Dv3
Started: 12/27/2017 20:26:48
Server: ncidd (NCID) 1.6
API: 1.5 Feature Set 1 2 3 4 5
Sysname: Linux
Machine: armv6l
Release: 4.9.59+
Version: #1047 Sun Oct 29 11:47:10 GMT 2017
Command line: ncidd
-Dv3
/var/log/ncidd.log: Permission denied
Processed config file: /etc/ncid/ncidd.conf
Verbose level: 3
Configured to send 'cidlog' to clients.
Configured to send 'cidinfo' to clients.
Helper tools:
/usr/bin/cidupdate
/usr/bin/ncidutil
Using simple expressions for aliases
Using simple expressions for blacklist/whitelist entries
Begin: Loading alias, blacklist, and whitelist files [20:26:49]
Processed alias file: /etc/ncid/ncidd.alias
Alias Table:
Number of Entries: 1
Processed blacklist file: /etc/ncid/ncidd.blacklist
Blacklist Table:
Number of Entries: 18
Calls in the blacklist file will be terminated
Processed whitelist file: /etc/ncid/ncidd.whitelist
Whitelist Table:
Number of Entries: 0
Calls in the whitelist file will not be terminated
Leading 1 in call & alias/blacklist/whitelist not ignored
End: Loaded alias, blacklist, and whitelist files [20:26:49]
/var/log/cidcall.log: Permission denied
Data logfile not present: /var/log/ciddata.log
Maximum number of clients/gateways: 50
Telephone Line Identifier: -
TTY port opened: /dev/ttyACM0
TTY port speed: 115200
TTY lock file: /var/lock/LCK..ttyACM0
TTY port control signals enabled
TTY port initialized in ICANON mode.
Checking Modem Capabilities...
TTY port changed to RAW mode.
Sent Modem 20 of 20 characters:
AT Z S0=0 E1 V1 Q0
Modem response: 26 characters in 1 read:
AT Z S0=0 E1 V1 Q0
OK
Modem Initialized
Sent Modem 6 of 6 characters:
ATI3
Modem response: 39 characters in 1 read:
ATI3
CX93001-EIS_V0.2002-V92
OK
Modem Identifier: CX93001-EIS_V0.2002-V92
Sent Modem 9 of 9 characters:
AT+GCI?
Modem response: 27 characters in 1 read:
AT+GCI?
+GCI: B4
OK
Modem country code: B4 United Kingdom
Sent Modem 6 of 6 characters:
AT&V
Modem response: 824 characters in 1 read:
AT&V
ACTIVE PROFILE:
B1 E1 L2 M1 N0 Q0 T V1 W0 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R1 &S0 &T5 &X0 &Y0
S00:000 S01:000 S02:043 S03:013 S04:010 S05:008 S06:003 S07:090 S08:001 S09:006
S10:014 S11:085 S12:050 S18:000 S25:005 S26:001 S36:007 S38:020 S46:138 S48:007
S95:000
STORED PROFILE 0:
B1 E1 L1 M1 N0 Q0 T V1 W0 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R1 &S0 &T5 &X0
S00:000 S02:043 S06:003 S07:090 S08:001 S09:006 S10:014 S11:085 S12:050 S18:000
S36:007 S40:104 S41:195 S46:138 S95:000
STORED PROFILE 1:
B1 E1 L1 M1 N0 Q0 T V1 W0 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R1 &S0 &T5 &X0
S00:000 S02:043 S06:003 S07:090 S08:001 S09:006 S10:014 S11:085 S12:050 S18:000
S36:007 S40:104 S41:195 S46:138 S95:000
TELEPHONE NUMBERS:
0= 1=
2= 3=
OK
Modem ACTIVE PROFILE:
B1 E1 L2 M1 N0 Q0 T V1 W0 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R1 &S0 &T5 &X0 &Y0
S00:000 S01:000 S02:043 S03:013 S04:010 S05:008 S06:003 S07:090 S08:001 S09:006
S10:014 S11:085 S12:050 S18:000 S25:005 S26:001 S36:007 S38:020 S46:138 S48:007
S95:000
STORED PROFILE 0:
B1 E1 L1 M1 N0 Q0 T V1 W0 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R1 &S0 &T5 &X0
S00:000 S02:043 S06:003 S07:090 S08:001 S09:006 S10:014 S11:085 S12:050 S18:000
S36:007 S40:104 S41:195 S46:138 S95:000
STORED PROFILE 1:
B1 E1 L1 M1 N0 Q0 T V1 W0 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R1 &S0 &T5 &X0
S00:000 S02:043 S06:003 S07:090 S08:001 S09:006 S10:014 S11:085 S12:050 S18:000
S36:007 S40:104 S41:195 S46:138 S95:000
TELEPHONE NUMBERS:
0= 1=
2= 3=
Sent Modem 13 of 13 characters:
AT+FCLASS=?
Modem response: 32 characters in 1 read:
AT+FCLASS=?
0,1,1.0,8
OK
Modem supports Data Mode
Modem supports FAX Mode 1
Modem supports VOICE Mode
TTY port changed to ICANON mode.
TTY port changed to RAW mode.
Sent Modem 20 of 20 characters:
AT Z S0=0 E1 V1 Q0
Modem response: 26 characters in 1 read:
AT Z S0=0 E1 V1 Q0
OK
Modem initialized.
Sent Modem 11 of 11 characters:
AT+VCID=1
Modem response: 17 characters in 1 read:
AT+VCID=1
OK
Modem set for CallerID.
TTY port changed to ICANON mode.
CallerID from AT Modem and optional gateways
Does not handle modem calls without Caller ID
Modem used for CallerID and to terminate calls
Internal Hangup Mode = 1: hangup on a blacklisted call
Network Port: 3333
Debug Mode
Not using PID file, there was no '-P' option.
Modem is fd 3
NCID connection socket is sd 4 pos 1
End of startup: 12/27/2017 20:26:49
Client 5 pos 2 from 192.168.0.110 [Sandy-iMac.home] connected 12/27/2017 20:26:54
200 Server: ncidd (NCID) 1.6
210 API: 1.5 Feature Set 1 2 3 4 5
Client Sent: no data
253 No Call log: /var/log/cidcall.log
Sent 'hangup-1' option to client
300 End of connection startup
MESG = 110101
DATE = 1227
TIME = 2038
NMBR = **
RING
CIDINFO: LINEPOTSRING1TIME20:38:07
Whitelist empty
Checked Blacklist for match flag=0 ret=0 nmbrmatch=0
CID: DATE12272017TIME2038LINEPOTSNMBR*MESG110101NAME110101
RING
CIDINFO: LINEPOTSRING2TIME20:38:07*
RING
CIDINFO: LINEPOTSRING3TIME20:38:10
CIDINFO: LINEPOTSRING0TIME20:38:19
Last edit: Sandy Matheson 2017-12-27
Hi Sandy,
Thank you for your report on the issue with Raspbian Stretch. I don't think any of us developers have installed Stretch yet (I know I haven't because I don't have a spare SD card; I'll have to order one).
Regarding 1.6.1 that you were able to successfully install:
Something appears to be preventing
nciddfrom starting up. If you could attach your ncidd.log file to this thread, or if you'd rather you can send it via private email attachment to John (jlc@users.sf.net) and to me (tandrews@users.sf.net). Your privacy is assured, however, feel free to obfuscate phone numbers and caller names.ncidclient:By default
ncidexpects to be running in a GUI terminal. If you try to launchncidfrom an SSH session, you'll get errors like the above.nciddto prevent the permission errors:sudo ncidd -Dv3I'm surprised your test worked because usually the same issue that prevents
nciddfrom running viasudo invoke-rc.d ncidd startwill show up when doingsudo ncidd -Dv3. Getting ncidd.log as an attachment will provide us with more info.Hi Sandy,
There was a problem in the rules that built the debian client package. I fixed it and created a new client package:
https://sourceforge.net/projects/ncid/files/ncid/1.7/ncid-client_1.7-2_all.deb
The problem Todd is helping you with may still be there in the new 1.7 server package:
https://sourceforge.net/projects/ncid/files/ncid/1.7/ncid_1.7-2_armhf.deb
As additional information on launching ncid from SSH session, you can only launch it in non-GUI mode:
Please try installing version 1.7 again to verify my fix to the client package.
Hi Sandy,
There was also an error in the server install package that prevents the install of the client package. The fix is in deb packages 1.7-3. You need to install both the ncid and ncid-client packages for the fix.
Hi,
Thanks for the quick replies.
The good news - both server and client install without any errors.
Unfortunately I'm still not able to start NCID using sudo invoke-rc.d ncidd start - same issue as with 1.6.1 Happy to send over the log file, but I can't find one. It's not in /var/log and I can't see a configuration option in ncidd.conf to set the location.
I was concerned with fixing the client install problem. Todd is still working on your problem startup problem but it might be a Raspbian Stretch issue with the startup script. We will install Raspbian Stretch and continue to work the startup issue.
Hi Sandy,
I have an SD card now and have my RPi running Raspbian Stretch.
I have been able to duplicate your issue and I'm working to track down the cause.
You're right about no ncidd.log being created. This means
ncidddoesn't start and stay running long enough to create it.Hi Sandy,
I don't have a definitive answer, but I have a workaround that should be stable for you. I have tried this workaround about half a dozen times on my RPi and it is working for me.
If I try to launch ncidd with
invoke-rc.d ncidd startwithout first enabling it across run levels withupdate-rc.d, I can duplicate the issue. Normally we recommend, after an initial install, to launch ncidd withinvoke-rc.dfirst and test, before enabling the permanent autostart withupdate-rc.dbut for some reason it isn't working in Raspbian Stretch.So the workaround is:
set ttyportin ncidd.conf is pointing to a real modem.The above survives across boots for me, i.e., I don't need to repeat any of the above.
Could you do me a favor and type the following after you've got it working:
and post back the results. For comparison purposes, what I get is:
Hi Todd, Thanks for the reply and workaround.
Just to make sure there wasn't anything left over from previous installs and uninstalls I started over by reinstalling Raspbian so I had a clean system.
Everything installed OK with 1.7.3 and following your sequence ncidd started as well. I can also confirm that ncidd was loaded correctly on reboot.
The results of searching for ncidd.service are below:
pi@raspberrypi:~ $ sudo find / -name ncidd.service
/run/systemd/generator.late/graphical.target.wants/ncidd.service
/run/systemd/generator.late/multi-user.target.wants/ncidd.service
/run/systemd/generator.late/ncidd.service
/sys/fs/cgroup/devices/system.slice/ncidd.service
/sys/fs/cgroup/systemd/system.slice/ncidd.service
I also use ncid-notify to run alerts of incoming calls to various screens in my house. I can confirm that using the same sequence this loaded OK and survives reboots.
Thanks for working on this problem, especially over this Christmas period.