D
Deleted member 473
You're being oblique. I thought I had spelled it out well enough.
The DLNA database issue is not CF related. If you get crashes with content sharing turned on but no crashes when turned off, and crashes even with the network disconnected, the hypothesis is that you have a corrupted DLNA database. The only way to reset the database without CF is to format the HDD. With the CF installed, you can use the WebIF to reset the database without formatting the HDD.
Is that clear enough now?
I have the custom f/w on again now---give me time!
I reset the dlna database and let it index everything. Just turned the box on and it crashed almost immediately. The word CRASH shows on the display before it does a timed reboot.
I am not being oblique, I was in no position to try the fix last night, but the fix did not, I repeat, did not work. Is that plain enough?
Code:
>>> Contents of /mod/tmp/crash.log 356 bytes
Humax crashed at Tue Jul 15 20:30:55 UTC 2014 - Uptime: 66
Humax crashed at Tue Jul 15 21:00:04 UTC 2014 - Uptime: 66
Humax crashed at Tue Jul 15 21:05:06 UTC 2014 - Uptime: 67
Humax crashed at Tue Jul 15 21:36:08 UTC 2014 - Uptime: 150
Humax crashed at Wed Jul 16 03:20:54 UTC 2014 - Uptime: 231
Humax crashed at Wed Jul 16 08:59:45 UTC 2014 - Uptime: 67
Oh, and it always starts up on the BBC Red Button channel now. (Installed poc., cured that.)
(I cured BBC1=8 by installing the renumbering package and editing the settings.)
So, it seems that loads of old settings are left behind and are still effective. The button on Diagnostics to remove custom packages and settings isn't working.
Oh, and it is custom f/w related, because the problem didn't even exist until I installed the first version of 3.0.