PDA

View Full Version : TsMedia crash message (timer file corrupted (timers.xml))



solarteki
30-08-2015, 04:31 PM
Thanks to contributors and "Echelon" in particular for all the prompt feedback over the last couple of weeks.. It,s an ongoing education.

I was finally enjoying my box until last night.
I scrolled through the icons on TsMedia Network tv.
Green screen crash -- after which i got message on reboot (timer file corrupted (timers.xml) and could not be loaded).
Lost SAT channels, EPG and Cool settings but can access terrestrial and plugins. "CCam info" showed my lines not connected (red instead of green). Blue button showed CCam 2.3.0 .Tested LAN connection and all ok except last test which said "nameserver nonconfirmed". In network set up --- interface and dhcp are "yes" IP, netmask and gateway ok. Primary and secondary DNS both show 0.0.0.0. What is the nameserver?
The router is connected direct to STP wth flashing light working. Wireless to laptop and pad good. Disconnected Cable from STB and connected to laptop with wireless disabled--good.

Help please

solarteki
30-08-2015, 04:59 PM
Just got another green crash opening "Network Browse"

echelon
31-08-2015, 09:34 AM
I did tell you in post #15 of this thread https://www.satpimps.co.uk/showthread.php?172071-Can-t-upload-usr-and-etc-to-box-via-DCC about not installing TSMEDIA into BH (clearly you ignored that advice)

any time you install a plugin you mess with files in the box and if that plugin isnt made specifically for the image (plus doesnt have bugs etc) then these are the kind of results you can expect (similarly if you install rogue programs on your laptop)

when you have a basic image installed with your cccam etc and its all as you like it, you should be using the menu to make a full backup, so its easily restored in less than 10 minutes from a usb stick you keep the backup image on (the same was as when you programmed the box) - that is my recommendation

ie:- restore the box using a backup you made earlier (a backup that doesnt have tsmedia installed)

if you havent got a backup then you will have to reinstall from scratch once more , I doubt that you can "repair" the damage done and a clean install will be quicker

also keep the flash memory below 90% and preferably around the 80% mark, or less


so my recommendation (if you havent got a full backup) is a clean install once more

then set the ip address to a chosen FREE ip address and always use the same one for the solo2

telnet in and change the password using the passwd command using VuCC or DCC

mount the rear mounted usb stick (for picons and epg data) and mount the INTERNAL hdd

install the basic plugins only and set up epg etc (no TSMEDIA)

use the software update option to update BH 2.17 to the latest version (from the menu)

once this is all complete and working , BACK IT UP using full backup to the rear mounted usb stick

then ftp the backup to your laptop for safekeeping, deleting the one on the rear usb stick (so it doesnt try to install itself at boot)

now finish off adding anything dubious, preferably NOT tsmedia , preferably only the plugins from the BH server

------------------------------------------------------------------------

on a side note, I have not found BH 2.17 to be error free, mine wont let me telnet in any more, or ftp in, it fails with a communication type error so I think it has flaws or incompatibilities in it, 2.16 seems better to me), clearly its not the box because its only happened in BH 217 if I let it boot up in that mode (flash image mode)

but as I had already installed multiboot and had various other images I am currently using it booted into hades and that works fine, including FTP and telnet etc, this is also on a box with no TSMEDIA installed as I gave up on that plugin ages ago

-------------------------------------------------------------------------

PICONS

I have had various problems with picons like you, one solution is to check the image size of the picons and use ones that display properly

this means checking what sizes are on offer and looking for smaller ones , so if they are say 400 or 200 or 100 by whatever, try a set of smaller ones , so the 100 by blah blah should work , try them before using larger sizes, but I have also found it depends which images and skins you use, plus the output video settings too (720p or 1080p etc)

this is another area where you fall down, let me explain

in your first 2 posts in this thread you went into details about box failures and tsmedia, but you never mentioned the image and version number in use (listed in system info in the main menu). this info is crucial to help people to help you, yet you have omitted this basic info on more than one occasion, as if you are assuming that everyone uses the same as you do

basic info should always include

1) image type and version (like BH 2.17 or BH 2.171 etc)
2) cccam or mgcamd or oscam version (typically cccam v2.30)
3) programs and version being used (if any) (like DCC1.50 , dreamset v2.44 , filezilla)

ps:- NAMESERVER is normally set to your router ip address , but could be changed to use something like googles public servers instead, (or virgin public servers, all depends on what works for the person using the box - depending on the broadband they are using) - if in doubt , use your router ip address to start with

as you have DHCP set to ON, this should be automatic , with it set to off you have to sort out these details yourself, then perform a network test to ensure its all working ok