Maybe the disk temperature is being reported by the hard disk rather than a sensor, and some disks might not support the monitoring function hence the stupid results?
Hidden menu found on Thomsons :)
2 of 3
Originally Posted by pearce_jj:
“Maybe the disk temperature is being reported by the hard disk rather than a sensor, and some disks might not support the monitoring function hence the stupid results?”
“Maybe the disk temperature is being reported by the hard disk rather than a sensor, and some disks might not support the monitoring function hence the stupid results?”
You're right. Hard disks support something called SMART, which is a table of interesting numbers, such as the temperature, the seek time and so on. The idea is you run a program that looks for sudden changes in these numbers that signifies a failure in the near future. Each manufacturer seems to do it slightly differently.
On my Seagate drives but not on my Western Digital ones the temperature is attribute number 194. Attributes usually run from 0 to 255 and have to be scaled, hence silly temps like 253.
If you can look at drives under Linux there are some SMART tools
Originally Posted by jazzster:
“Had Yellow light on this morning, it just needed unpluging to get it going again.
I have the logging on and instead of the usual 13 pages its logged 331 pages.
Everything is normal until page 11 after "OADS: EPG download started" on page 10, It says "EIT:CRC failure"on page 11
Followed by "EIT offset of 4095 > lenght of 3748" on page 12
then repeats with slightl;y different numbers for offset land lenght until 03:38 am page 330, the next entry is when I turn off the power and back on 10:14 were it reset itself for another download tonight.”
“Had Yellow light on this morning, it just needed unpluging to get it going again.
I have the logging on and instead of the usual 13 pages its logged 331 pages.
Everything is normal until page 11 after "OADS: EPG download started" on page 10, It says "EIT:CRC failure"on page 11
Followed by "EIT offset of 4095 > lenght of 3748" on page 12
then repeats with slightl;y different numbers for offset land lenght until 03:38 am page 330, the next entry is when I turn off the power and back on 10:14 were it reset itself for another download tonight.”
I guess that this is the first "real" proof that some of the incidents that some users have experienced is not *entirely* the fault of Thomson - though of course, if it could handle these errors better then that would be ideal.
I suppose these incidents are like the classic buffer underun's (or similar) which you hear about being exploited on Windows PCs to enable malicious software to run / install - errors cause programs to crash etc etc
I don't know if it is feasible, but I'm sure that Thomson would like to see the details of the log files in case they have never seen these particular errors in their test environment.
Matt
I've also had log entries about EIT offset of 4022 > length 4006 but I didn't get the CRC message nor did I get a YLD. On that day I found that the log was 25 pages long immediately after coming out of standby but was 300 odd pages long when I looked at it later in the day. The entries in it seemed to be timestamped in groups coinciding with when we'd looked at the EPG. And, the EPG for ITV1 was missing for that day but all the other channels were OK.
Hmm, just had another look at the log files from recent downloads. The one for the 25th is 2688 pages long, the first 14 or so look normal then followed by 'EIT: CRC failure' for as many pages as I could be bothered to look at! The same thing when starting from the other end of the log - last two were different, all others were the CRC failure. No YLD though and no 'offset' errors in this one.
Cool looking like this menu is worth it then - I only hope what my mate said about the new firmware is correct 
I have a minor YLD this morning - reboot cured it. Nothing in the logs, just the normal 13 page stuff. Did a short HDD test - nothing. Kicked off a long HDD test 45mins ago and its still going
I have a minor YLD this morning - reboot cured it. Nothing in the logs, just the normal 13 page stuff. Did a short HDD test - nothing. Kicked off a long HDD test 45mins ago and its still going
Originally Posted by larkim:
“I suppose these incidents are like the classic buffer underun's (or similar) which you hear about being exploited on Windows PCs to enable malicious software to run / install - errors cause programs to crash etc etc”
“I suppose these incidents are like the classic buffer underun's (or similar) which you hear about being exploited on Windows PCs to enable malicious software to run / install - errors cause programs to crash etc etc”
Sorry, but no. The CRC failed, so that says the bitstream is corrupt. The log says the software catches attempts to write or read beyond a boundary.
Larkim has it right in my opinion, Thomson are doing a good job.
Hi, my mate's Thomson is displaying on the 'System Log File' for 25/1/06: "3:18(am) - OADS: EPG Download Started - (page 10 of 4596).
Page 11 reads: "3:28(am) - EIT: CRC failure".
Log file for 26/1/06 is only four pages:
Page 1: "3:00(am) - OADS: Starting Data Pipe."
Page 2: "3:00(am) - OADS: Tuned to...OK."
Page 3: "3:00(am) - OADS: Data Pipe ...enabled OK."
Page 4: "3:00(am) - _CheckDownloadStop: OAD program time set to 3:00 on 27/1/06."
Log for 27/1/06 is usual thirteen pages.
No YLD, or missing lights.
I think it's to do with high-current appliances' thermostats / switch-gear (i.e.; immersion heaters, storage heaters, fridge-freezers) causing corruption of the broadcast datastream... Impulse interference...!
Page 11 reads: "3:28(am) - EIT: CRC failure".
Log file for 26/1/06 is only four pages:
Page 1: "3:00(am) - OADS: Starting Data Pipe."
Page 2: "3:00(am) - OADS: Tuned to...OK."
Page 3: "3:00(am) - OADS: Data Pipe ...enabled OK."
Page 4: "3:00(am) - _CheckDownloadStop: OAD program time set to 3:00 on 27/1/06."
Log for 27/1/06 is usual thirteen pages.
No YLD, or missing lights.
I think it's to do with high-current appliances' thermostats / switch-gear (i.e.; immersion heaters, storage heaters, fridge-freezers) causing corruption of the broadcast datastream... Impulse interference...!
Originally Posted by larkim:
“First question then, now that this holy grail has been discovered - does the HDD temperature show as 100degC on anyone elses? System temperature shows as 31degC.
I've got an upgraded HDD in there.
How would you access the "logging" files do you think? I suppose you'd have to pull the disk out and read a debug file. Be nice if it could display on screen though!
Wonder if the same code works on the Fusion box?
Matt”
“First question then, now that this holy grail has been discovered - does the HDD temperature show as 100degC on anyone elses? System temperature shows as 31degC.
I've got an upgraded HDD in there.
How would you access the "logging" files do you think? I suppose you'd have to pull the disk out and read a debug file. Be nice if it could display on screen though!
Wonder if the same code works on the Fusion box?
Matt”
just found that the same code works on the fusion fvrt100. Not as many functions there though by the sounds of it - you can change the compression ratios for LP and EP and view a log file. I turned on the logging and rebooted, but there's only one entry - about getting the time from the tuner.
Hi, last night I was reading in the "reviews" section, that pressing the 'Guide' button when the Thomson is in standby, causes it to crash. So I tried it. It remained in standby, but the disc drive clicked several times, then refused to accept any commands at all. A mains reset cured it.
Tonight, "Emmerdallas Farm" and "The Good Life" were both set recording, whilst I tried rewinding "The Good Life" back a few minutes. The box froze up, as it tends to do. So the plug was pulled. "Emmerdale" was recorded; "The Good Life" not.
Checking the "Engineering Menu" reveals that the usual thirteen page log now has an extra two pages:
page 1 (time 00:51)
"_InitDownloadSchedule: System time is 00:51 on 30.01.2006 : OAD program time set to 03:00 on 30.01.2006"
page 15 (time 19:37)
same as above but at 19:37. OAD...set to...on 31.01.2006.
This seems to correspond to the power being disconnected.
When I checked the log, I also found a old file that dates from before the unit was purchased:
(page 1 of 2)
02/09/04 1:00(am) "TotUpdateTask - getting time from tuner 1 (was 1)"
(page 2 of 2)
"PVR_TidyUP - Deleting buffer file - BUFF0.PES"
This file was not there previously. Any ideas?
Tonight, "Emmerdallas Farm" and "The Good Life" were both set recording, whilst I tried rewinding "The Good Life" back a few minutes. The box froze up, as it tends to do. So the plug was pulled. "Emmerdale" was recorded; "The Good Life" not.
Checking the "Engineering Menu" reveals that the usual thirteen page log now has an extra two pages:
page 1 (time 00:51)
"_InitDownloadSchedule: System time is 00:51 on 30.01.2006 : OAD program time set to 03:00 on 30.01.2006"
page 15 (time 19:37)
same as above but at 19:37. OAD...set to...on 31.01.2006.
This seems to correspond to the power being disconnected.
When I checked the log, I also found a old file that dates from before the unit was purchased:
(page 1 of 2)
02/09/04 1:00(am) "TotUpdateTask - getting time from tuner 1 (was 1)"
(page 2 of 2)
"PVR_TidyUP - Deleting buffer file - BUFF0.PES"
This file was not there previously. Any ideas?
Originally Posted by trilobite:
“
(page 1 of 2)
02/09/04 1:00(am) "TotUpdateTask - getting time from tuner 1 (was 1)"
(page 2 of 2)
"PVR_TidyUP - Deleting buffer file - BUFF0.PES"
This file was not there previously. Any ideas?”
“
(page 1 of 2)
02/09/04 1:00(am) "TotUpdateTask - getting time from tuner 1 (was 1)"
(page 2 of 2)
"PVR_TidyUP - Deleting buffer file - BUFF0.PES"
This file was not there previously. Any ideas?”
The buff0.pes entry is the file that stores the buffer (live pause information). I had a similar set of pages to you when I pulled the plug a few days ago. It seems to do something of a clear up, and just confirms that the OAD is scheduled , what time it is etc.
Interesting that an "old" file was there though. Mine had none other than the ones created since I had turned logging on.
Matt
Has anyone else noticed that the log entries appear in the selection box in a very odd order.
From memory, mine started with 3091.log, and then went 3092, 3093, 3094 (all fine!), then 3098, 3097, 3095, 3096.
This is just the order that they cycle through in the selection box; if you review the data then they were created in the proper sequential order, its just peculiar that they appear in the selection box in such an odd order. Perhaps they are ordered by file size or similar, and the bytes for the date strings cause the files to be of subtley different sizes.
Odd anyway
Matt
From memory, mine started with 3091.log, and then went 3092, 3093, 3094 (all fine!), then 3098, 3097, 3095, 3096.
This is just the order that they cycle through in the selection box; if you review the data then they were created in the proper sequential order, its just peculiar that they appear in the selection box in such an odd order. Perhaps they are ordered by file size or similar, and the bytes for the date strings cause the files to be of subtley different sizes.
Odd anyway
Matt
Hi, mine are in numerical sequence from 3096 to 3101, then the odd one: 2305 (from before date of purchase!)
The 23xx files come from when you power it on and they usually have just one message in them that say that it's getting the current time from Tuner 1. Once it has the time, it writes to a different filename.
Originally Posted by TrevorPH:
“The 23xx files come from when you power it on and they usually have just one message in them that say that it's getting the current time from Tuner 1. Once it has the time, it writes to a different filename.”
“The 23xx files come from when you power it on and they usually have just one message in them that say that it's getting the current time from Tuner 1. Once it has the time, it writes to a different filename.”
Thankyou, kind sir
Had a YLD this morning, power cycled three times but still no joy, was resigned to the fact that I’d have no digital TV all day until I could set it up for a fresh EPG download tonight. However I thought I’d investigate the hidden menus before giving up. Disconnected the aerial to get me access to the box and used the hidden menu to ‘delete all EPG’ it took a while but eventually sprang back into life. Reconnected the aerial and its working again (minus EPG data).
At least now I can watch digital whilst awaiting a new EPG download tonight.
At least now I can watch digital whilst awaiting a new EPG download tonight.
Originally Posted by Hubamonster:
“Had a YLD this morning, power cycled three times but still no joy, was resigned to the fact that I’d have no digital TV all day until I could set it up for a fresh EPG download tonight. However I thought I’d investigate the hidden menus before giving up. Disconnected the aerial to get me access to the box and used the hidden menu to ‘delete all EPG’ it took a while but eventually sprang back into life. Reconnected the aerial and its working again (minus EPG data).
At least now I can watch digital whilst awaiting a new EPG download tonight.”
“Had a YLD this morning, power cycled three times but still no joy, was resigned to the fact that I’d have no digital TV all day until I could set it up for a fresh EPG download tonight. However I thought I’d investigate the hidden menus before giving up. Disconnected the aerial to get me access to the box and used the hidden menu to ‘delete all EPG’ it took a while but eventually sprang back into life. Reconnected the aerial and its working again (minus EPG data).
At least now I can watch digital whilst awaiting a new EPG download tonight.”
have you upgraded your HD?
Has anyone tried the Format Disk option yet. Would be interested to see if this works (would try it myself but my disk is nearly full of unwatched programmes)
Originally Posted by peTTe:
“Has anyone tried the Format Disk option yet. Would be interested to see if this works (would try it myself but my disk is nearly full of unwatched programmes)”
“Has anyone tried the Format Disk option yet. Would be interested to see if this works (would try it myself but my disk is nearly full of unwatched programmes)”
No, but I tried the long disk test and it takes about 90 minutes to complete!
Originally Posted by Hubamonster:
“Had a YLD this morning, power cycled three times but still no joy, was resigned to the fact that I’d have no digital TV all day until I could set it up for a fresh EPG download tonight. However I thought I’d investigate the hidden menus before giving up. Disconnected the aerial to get me access to the box and used the hidden menu to ‘delete all EPG’ it took a while but eventually sprang back into life. Reconnected the aerial and its working again (minus EPG data).
At least now I can watch digital whilst awaiting a new EPG download tonight.”
“Had a YLD this morning, power cycled three times but still no joy, was resigned to the fact that I’d have no digital TV all day until I could set it up for a fresh EPG download tonight. However I thought I’d investigate the hidden menus before giving up. Disconnected the aerial to get me access to the box and used the hidden menu to ‘delete all EPG’ it took a while but eventually sprang back into life. Reconnected the aerial and its working again (minus EPG data).
At least now I can watch digital whilst awaiting a new EPG download tonight.”
This is (mild) confirmatory evidence for my long-standing theory that YLD(TM) results from EPG problems.
Came down to a (fully functioning) machine this morning - checked the logs - 10164 pages of errors (all EIT: CRC stuff).
Only 13 days EPG present (surprise surprise!).
Can anyone beat 10164??!!
Matt
Only 13 days EPG present (surprise surprise!).
Can anyone beat 10164??!!
Matt
Originally Posted by larkim:
“Has anyone else noticed that the log entries appear in the selection box in a very odd order.
From memory, mine started with 3091.log, and then went 3092, 3093, 3094 (all fine!), then 3098, 3097, 3095, 3096.
This is just the order that they cycle through in the selection box; if you review the data then they were created in the proper sequential order, its just peculiar that they appear in the selection box in such an odd order. Perhaps they are ordered by file size or similar, and the bytes for the date strings cause the files to be of subtley different sizes.
Odd anyway
Matt”
“Has anyone else noticed that the log entries appear in the selection box in a very odd order.
From memory, mine started with 3091.log, and then went 3092, 3093, 3094 (all fine!), then 3098, 3097, 3095, 3096.
This is just the order that they cycle through in the selection box; if you review the data then they were created in the proper sequential order, its just peculiar that they appear in the selection box in such an odd order. Perhaps they are ordered by file size or similar, and the bytes for the date strings cause the files to be of subtley different sizes.
Odd anyway
Matt”
Hi, the log for last night (3102.log) is showing up on mine as sitting between 3100 & 3101.
The 2305.log has disappeared as suggested by TrevorPH.
Originally Posted by prd:
“This is (mild) confirmatory evidence for my long-standing theory that YLD(TM) results from EPG problems.”
“This is (mild) confirmatory evidence for my long-standing theory that YLD(TM) results from EPG problems.”
and only/mostly on upgraded HD's?
2 of 3
