have been using the custom firmware/webif for a few months now (brilliant work BTW!)
Following the initial install (v15) I received error messages whenever I used the dedup utility from webif. This was a minor thing that I could live with.
Recently, however, I now receive the following error message whenever I 'Browse Media Files'. This happens all the time. The first 10 of my recorded file list is shown and then the error below.
Also if I click on any of my recorded files, I also get this error.
Runtime Error: /mod/var/mongoose/lib/ts.class:169: no such table: tblresource in procedure 'entry' called at file "browse.jim", line 286 in procedure '.00000000000000000002>' called at file "browse.jim", line 184 in procedure 'ts dlnaloc' called at file "/mod/lib/jim/oo.tcl", line 46 at file "/mod/lib/jim/oo.tcl", line 62 at file "/mod/var/mongoose/lib/ts.class", line 169
I've upgraded to the latest mod version (v17) but still have this issue
I saw a thread which seemed related (posted by Tobyjuggler) - I've run df diagnostics but do not get the busybox perm issue so I'm not sure if it's related. Results of the df are at the bottom of this post.
Thanks in advance for any help here....
Following the initial install (v15) I received error messages whenever I used the dedup utility from webif. This was a minor thing that I could live with.
Recently, however, I now receive the following error message whenever I 'Browse Media Files'. This happens all the time. The first 10 of my recorded file list is shown and then the error below.
Also if I click on any of my recorded files, I also get this error.
Runtime Error: /mod/var/mongoose/lib/ts.class:169: no such table: tblresource in procedure 'entry' called at file "browse.jim", line 286 in procedure '.00000000000000000002>' called at file "browse.jim", line 184 in procedure 'ts dlnaloc' called at file "/mod/lib/jim/oo.tcl", line 46 at file "/mod/lib/jim/oo.tcl", line 62 at file "/mod/var/mongoose/lib/ts.class", line 169
I've upgraded to the latest mod version (v17) but still have this issue
I saw a thread which seemed related (posted by Tobyjuggler) - I've run df diagnostics but do not get the busybox perm issue so I'm not sure if it's related. Results of the df are at the bottom of this post.
Thanks in advance for any help here....
>>> Beginning diagnostic df Running: df Filesystem Size Used Available Use% Mounted on /dev/sda2 447.6G 165.4G 259.5G 39% /mnt/hd2 Filesystem Size Used Available Use% Mounted on /dev/sda2 447.6G 165.4G 259.5G 39% /mnt/hd2 Welcome to Jim version 0.73 . . . 447.6G 165.4G 39 . * /mod/bin/busybox/busybox -rwxr-xr-x 1 root root 545224 Jan 23 21:27 /mod/bin/busybox/busybox Removing package busybox from root... Installing busybox (1.19.3-3) to root... Downloading http://hummypkg.org.uk/hdrfoxt2/base/busybox_1.19.3-3_mipsel.opk. Configuring busybox. * /mod/bin/busybox/busybox -rwxr-xr-x 1 root root 545224 Jan 23 21:27 /mod/bin/busybox/busybox * /mod/bin/busybox/busybox -rwxr-xr-x 1 root root 545224 Jan 23 21:27 /mod/bin/busybox/busybox >>> Ending diagnostic df