1. MSG-1@groups.io
   Date   
The Earth - a disk! Or not?

Ulrich G. Kliegis
 

Hi all,
strange phenomenon here: After getting my boxes back on the track here
(SATA-controller failure in the receiver PC, RAM failure in the viewing machine),
almost everything works fine and smooth again - except: The animation of the
"whole disk" view. I did not change anything in the configuration, it works in the
same way it did before the double-failure. All other animations (subsections of the
various channel images) work flawlessly, only the whole disk views not. I've treid to
change them to partial views, to other channels - no avail.

I guess something's been broken in the registry part of the setup, although it
sounds unlikely.

Anyone with an idea?

Another observation: The receiver PC had continued to collect data for some
weeks before I switched it off. Some directories hat collected monstrous content:
Specially the EPS-Global contained about 12 GB in about 60.000 files - in one
directory. Then the very long file names - I can imagine that our good old XP
systems are suffering under that burden - and need their time to get it all sorted. I
finally purged most of it but the most recent data - when I finished that last night,
the missed data rate immediately fell down to zero.

The third observation concerns the AVHRR-manager - more on that in the
SatSignal group.

Cheers,
U.
Re: Unusual tc error condition

James Brown
 

At one time, I was plagued by intermittent EKU errors when I changed to a new motherboard (sorry, but I can't remember the exact errors reported). The cure was to run the EKU on its own via an externally-powered USB hub.

I am using one of the early EKUs - just what combination of hardware needed the extra buffering provided by the hub I have no idea, but it might be worth a try if this becomes too troublesome.

Francis Breame

Thanks Frances - I have a newer EKU as of a few years ago, and haven't had this problem before in all the years of running the station. It is remotely possible the PSU is giving problems, or even the MB, but I would have expected to see more general errors. It happened overnight, and on a machine I go to very infrequently as it is dedicated to 24hr recption of EUMETCAST and a small weather station programme.
Cheers

James
Re: Unusual tc error condition

fbreame
 

--- In MSG-1@yahoogroups.com, James Brown <satellite@...> wrote:

On 15/05/2013 12:33, Ian Deans wrote:
Hello James.

I occasionally get a critical Dongle error probably averaging about twice a
year although I am not sure if it was a critical dongle "server" error.

I have no idea what causes the problem and usually it re-starts itself
without intervention, although data is lost until re-start.

Sorry I cannot be of more help.

Regards
Ian.

Many thanks Ian - it's helpful just to know I am not alone!
Unfortunately the process didn't start again, I lost about 5 hours. I
did wonder if the defrag programme had taken too much processor power,
though the CPU graphs don't seem to show that I am approaching maximum
usage.
James
At one time, I was plagued by intermittent EKU errors when I changed to a new motherboard (sorry, but I can't remember the exact errors reported). The cure was to run the EKU on its own via an externally-powered USB hub.

I am using one of the early EKUs - just what combination of hardware needed the extra buffering provided by the hub I have no idea, but it might be worth a try if this becomes too troublesome.

Francis Breame
Re: Permanent yellow T icon

Neil <neilthackrey@...>
 

Thanks to everyone for all the advice on how to get windows 7 64 bit working.
Just a quick review for any other budding windows 7 64 bit installers based on all the valued feedback I have received over the past few days;
1) make sure you install into a separate directory and NOT into the default installation folders
2) install the 64 bit etoken driver
3) run msconfig.exe then untick PKImonitor in start up to prevent the password window coming up each time you power up
4) make sure the IP address in your network settings for the DVB receiver is the same as the recv.ini file i.e. 192.168.238.238
5) if you have a LAN which maybe conflicting with your IP addresses run David's DOS prompt command line under administrator.
6) don't know why but allow five minutes to connect.. in XP pro it was almost straight away. I can live with though.
7) once connected and only getting the announcement channel go into windows firewall and tick all the tc-rcv boxes to allow bypassing the firewall.

Hope this summary is useful for others upgrading.

atb Neil ea7vpg/gm0vpg

--- In MSG-1@yahoogroups.com, "Ian Deans" <iandeans142@...> wrote:

Hello Neil,

I am not sure if you looked at the page on David Taylor's site which James
Brown mentioned in a mail to you. I have pasted it below again for
reference.

If you page down to the section "Using a LAN at the same time as the
DVB/TelliCast software" and follow the instructions you may find your
problem is resolved. It is important to note that once you have entered
the command and completed the procedure you need to reboot the computer.
Hope that helps.

http://www.satsignal.eu/wxsat/Dexatek/ip-address.html

Regards
Ian.

-----Original Message-----
From: Neil
Sent: Tuesday, May 14, 2013 6:13 AM
To: MSG-1@yahoogroups.com
Subject: [MSG-1] Permanent yellow T icon

Hi John....
Well putting everything into a separate directory certainly worked. The
red icon has now gone... unfortunately it is sitting in a state of yellow
trying to connect permanently. I have checked my recv.ini and compared it
to others which look identical. I have edited my recv-channels.ini to
reflect the new computer configuration. If the recv-channels.ini file is
incorrect would it prevent connecting.


from the log file in the html shell
MSG:2013-05-14 04:43:52.951:Starting new child...
MSG:2013-05-14 04:43:52.951:Started new child [4484].
MSG:2013-05-14 04:43:52.951:Starting new child...
MSG:2013-05-14 04:43:52.951:Started new child [4484].

atb Neil
Re: Unusual tc error condition

James Brown
 

On 15/05/2013 12:33, Ian Deans wrote:
Hello James.

I occasionally get a critical Dongle error probably averaging about twice a
year although I am not sure if it was a critical dongle "server" error.

I have no idea what causes the problem and usually it re-starts itself
without intervention, although data is lost until re-start.

Sorry I cannot be of more help.

Regards
Ian.

Many thanks Ian - it's helpful just to know I am not alone! Unfortunately the process didn't start again, I lost about 5 hours. I did wonder if the defrag programme had taken too much processor power, though the CPU graphs don't seem to show that I am approaching maximum usage.

Many thanks

James
Re: Unusual tc error condition

Ian Deans
 

Hello James.

I occasionally get a critical Dongle error probably averaging about twice a year although I am not sure if it was a critical dongle "server" error.

I have no idea what causes the problem and usually it re-starts itself without intervention, although data is lost until re-start.

Sorry I cannot be of more help.

Regards
Ian.

-----Original Message-----
From: James Brown
Sent: Wednesday, May 15, 2013 11:24 AM
To: MSG-1@yahoogroups.com
Subject: [MSG-1] Unusual tc error condition

Folks, I haven't seen this before, wonder if anyone else has encountered
this - the client log runs like this:

MSG:2013-05-15 09:49:06.637:tc-recv.exe shutting down... [4000]
MSG:2013-05-15 09:49:06.740:tc-recv.exe stopped [4000].
MSG:2013-05-15 09:49:06.980:Watchdog child requested restart.
MSG:2013-05-15 09:49:06.984:Watchdog child quits properly. Restarting.
MSG:2013-05-15 09:49:07.985:Starting new child...
MSG:2013-05-15 09:49:07.985:Started new child [352].
MSG:2013-05-15 09:49:08.198:Log level is "normal".
MSG:2013-05-15 09:49:55.824:tc-recv.exe starting... [352]
MSG:2013-05-15 09:49:55.824:tc-recv.exe version is 2.5.17
(200906051529668) win32-i86pc ( 6.1.7601, Service Pack 1 on a
4-processor (GenuineIntel, Pentium III (Model 30, Stepping 5)) system)
ERR:2013-05-15 09:49:55.824:The eToken manager timed out after start.
ERR:2013-05-15 09:49:55.824:Critical dongle server error (EToken server
timed out). Trying to restart child.
MSG:2013-05-15 09:49:55.824:tc-recv.exe shutting down... [352]
MSG:2013-05-15 09:49:55.945:tc-recv.exe stopped [352].
MSG:2013-05-15 09:49:56.217:Watchdog child requested restart.
MSG:2013-05-15 09:49:56.221:Watchdog child quits properly. Restarting.
MSG:2013-05-15 09:49:57.221:Starting new child...
MSG:2013-05-15 09:49:57.221:Started new child [3884].
MSG:2013-05-15 09:49:57.438:Log level is "normal".
MSG:2013-05-15 09:50:45.107:tc-recv.exe starting... [3884]
MSG:2013-05-15 09:50:45.107:tc-recv.exe version is 2.5.17
(200906051529668) win32-i86pc ( 6.1.7601, Service Pack 1 on a
4-processor (GenuineIntel, Pentium III (Model 30, Stepping 5)) system)
ERR:2013-05-15 09:50:45.107:The eToken manager timed out after start.
ERR:2013-05-15 09:50:45.107:Critical dongle server error (EToken server
timed out). Trying to restart child.
MSG:2013-05-15 09:50:45.107:tc-recv.exe shutting down... [3884]
MSG:2013-05-15 09:50:45.240:tc-recv.exe stopped [3884].

And thereafter remains in this loop. I stopped the tc processes and
re-started them and for now all seems to have returned except RSS.

Any thoughts folks?

Cheers
Jamess
Unusual tc error condition

James Brown
 

Folks, I haven't seen this before, wonder if anyone else has encountered this - the client log runs like this:

MSG:2013-05-15 09:49:06.637:tc-recv.exe shutting down... [4000]
MSG:2013-05-15 09:49:06.740:tc-recv.exe stopped [4000].
MSG:2013-05-15 09:49:06.980:Watchdog child requested restart.
MSG:2013-05-15 09:49:06.984:Watchdog child quits properly. Restarting.
MSG:2013-05-15 09:49:07.985:Starting new child...
MSG:2013-05-15 09:49:07.985:Started new child [352].
MSG:2013-05-15 09:49:08.198:Log level is "normal".
MSG:2013-05-15 09:49:55.824:tc-recv.exe starting... [352]
MSG:2013-05-15 09:49:55.824:tc-recv.exe version is 2.5.17 (200906051529668) win32-i86pc ( 6.1.7601, Service Pack 1 on a 4-processor (GenuineIntel, Pentium III (Model 30, Stepping 5)) system)
ERR:2013-05-15 09:49:55.824:The eToken manager timed out after start.
ERR:2013-05-15 09:49:55.824:Critical dongle server error (EToken server timed out). Trying to restart child.
MSG:2013-05-15 09:49:55.824:tc-recv.exe shutting down... [352]
MSG:2013-05-15 09:49:55.945:tc-recv.exe stopped [352].
MSG:2013-05-15 09:49:56.217:Watchdog child requested restart.
MSG:2013-05-15 09:49:56.221:Watchdog child quits properly. Restarting.
MSG:2013-05-15 09:49:57.221:Starting new child...
MSG:2013-05-15 09:49:57.221:Started new child [3884].
MSG:2013-05-15 09:49:57.438:Log level is "normal".
MSG:2013-05-15 09:50:45.107:tc-recv.exe starting... [3884]
MSG:2013-05-15 09:50:45.107:tc-recv.exe version is 2.5.17 (200906051529668) win32-i86pc ( 6.1.7601, Service Pack 1 on a 4-processor (GenuineIntel, Pentium III (Model 30, Stepping 5)) system)
ERR:2013-05-15 09:50:45.107:The eToken manager timed out after start.
ERR:2013-05-15 09:50:45.107:Critical dongle server error (EToken server timed out). Trying to restart child.
MSG:2013-05-15 09:50:45.107:tc-recv.exe shutting down... [3884]
MSG:2013-05-15 09:50:45.240:tc-recv.exe stopped [3884].

And thereafter remains in this loop. I stopped the tc processes and re-started them and for now all seems to have returned except RSS.

Any thoughts folks?

Cheers
Jamess
Re: Permanent yellow T icon

Ian Deans
 

Hello Neil,

I am not sure if you looked at the page on David Taylor's site which James Brown mentioned in a mail to you. I have pasted it below again for reference.

If you page down to the section "Using a LAN at the same time as the DVB/TelliCast software" and follow the instructions you may find your problem is resolved. It is important to note that once you have entered the command and completed the procedure you need to reboot the computer.
Hope that helps.

http://www.satsignal.eu/wxsat/Dexatek/ip-address.html

Regards
Ian.

-----Original Message-----
From: Neil
Sent: Tuesday, May 14, 2013 6:13 AM
To: MSG-1@yahoogroups.com
Subject: [MSG-1] Permanent yellow T icon

Hi John....
Well putting everything into a separate directory certainly worked. The red icon has now gone... unfortunately it is sitting in a state of yellow trying to connect permanently. I have checked my recv.ini and compared it to others which look identical. I have edited my recv-channels.ini to reflect the new computer configuration. If the recv-channels.ini file is incorrect would it prevent connecting.


from the log file in the html shell
MSG:2013-05-14 04:43:52.951:Starting new child...
MSG:2013-05-14 04:43:52.951:Started new child [4484].
MSG:2013-05-14 04:43:52.951:Starting new child...
MSG:2013-05-14 04:43:52.951:Started new child [4484].

atb Neil
Permanent yellow T icon

Neil <neilthackrey@...>
 

Hi John....
Well putting everything into a separate directory certainly worked. The red icon has now gone... unfortunately it is sitting in a state of yellow trying to connect permanently. I have checked my recv.ini and compared it to others which look identical. I have edited my recv-channels.ini to reflect the new computer configuration. If the recv-channels.ini file is incorrect would it prevent connecting.


from the log file in the html shell
MSG:2013-05-14 04:43:52.951:Starting new child...
MSG:2013-05-14 04:43:52.951:Started new child [4484].
MSG:2013-05-14 04:43:52.951:Starting new child...
MSG:2013-05-14 04:43:52.951:Started new child [4484].

atb Neil

--- In MSG-1@yahoogroups.com, "Neil" <neilthackrey@...> wrote:

Cheers John.... I will give it a go.

atb Neil

--- In MSG-1@yahoogroups.com, "seggins@..." <seggins@> wrote:

Install all in a separate folder eg Eumesat, preferably on its own partition. Not in either program files.
Cheers
John

Sent from my HTC

----- Reply message -----
From: "Neil" <neilthackrey@>
To: <MSG-1@yahoogroups.com>
Subject: [MSG-1] Re: EKU no being recognised and the red T icon
Date: Mon, May 13, 2013 09:18
Thanks to all for your constructive replies. Yes, I agree I wish I had stayed with XP pro now. This issue is driving me nuts.

The password issue was resolved via msconfig, startup. The problem now is the T icon in task is permanent red indicating tc-recv Connect failed. I have checked in the html shell under licence which shows the following;

Client identification appears all correct with user and a host 1 to 4 all showing some parameters. The Active Clients shows the TSL announcement channel with a status of error. Under licence, not sure about this one;

Tellicast server licence, server address not yet received, OEM and description the same.

The tick boxes under what I can get and what is activated are Tellicast, File Broadcast, Datastreams.



The only anomaly I can see is the actual Client licence with Version 2.4.4q 200610301329200 win32-i86pc. Being a 64bit OS here could this be a problem?



In the top left of the HTML it indicates config problem. Now here is the weird one. When I copy my recv.ini file into the program I lose the red T in the task bar all together even though it is identical to the one generated when you load the Tellicast client software. The only way I can get the red T back is to re-install the Tellicast.

And yet another weirdy is I cannot edit the original rcv.ini file as when I come to save I get a window saying Access denied. The only way I can do is to replace the file with my original which I can edit in notepad.

When I installed the three applications (DVB, Etoken, Tellicast) some went into programs files whilst one defaulted into programs files (x86). I then uninstalled the lot and re-installed everything into program files which made no difference.



So all in all it is becoming annoyingly frustrating.



If there any windows 7 64 bit users out there it would be appreciated if you could send me a sample of your recv.ini and recv.channels.ini file to compare. I suppose ultimately I will have to send this to the eumetcast support desk.



I look forward to your comments.



atb Neil



--- In MSG-1@yahoogroups.com, Alan Sewards <alan@> wrote:

Hello James,
Thank you for your comment. From the subsequent postings my effort
appears to be rather inadequate: perhaps I should have said it was for
Windows XP. Clearly Win 7 introduces a new lot of problems, not the
least being poor availability of suitable software (3 years after it
appeared!). Many people find the installation process too arcane or
complicated - it is a pity that Eumetsat did not pull all the items
together with a single Installer that leads users through the
installation process, preferably all on one CDROM. Sometimes, I think it
is miraculous that it works at all! I'm glad I stayed with XP on my
Eumetcast machine.
Best regards - Alan S
On 12/05/2013 5:10 PM, James Brown wrote:
That would be useful as a 'sticky' somewhere Alan - I have archived it
for future reference.
Cheers
On 12/05/2013 13:47, Alan Sewards wrote:
Hi Neil,
I have a feeling that you have used the wrong order in installing the
software. Some notes I have on this are as follows
------------------------------------
Unsure what a term means? Check the Glossary at:
http://www..satsignal.eu/wxsat/glossary.htm
Join GEO - the Group for Earth Observation
for the informative GEO Quarterly magazine:
http://www.geo-web.org.uk/
Yahoo! Groups Links
--
Alan Sewards
émail: alan@
web site: http://asewards.free.fr










[Non-text portions of this message have been removed]
Re: EKU no being recognised and the red T icon

James Brown
 

Would this page be of help Neil?

http://www.satsignal.eu/wxsat/Dexatek/ip-address.html

Cheers
James

On 13/05/2013 20:21, Neil wrote:
Hi Ian,
I have changed the IP address.. what subnet mask, default gateway, preferred DNS and alternative DNS server should I use ?

atb Neil

--- In MSG-1@yahoogroups.com, James Brown <satellite@...> wrote:
On 13/05/2013 09:31, Ian Deans wrote:
If you have a permanent red "T" then either your interface address is wrong
or your firewall is causing a problem.

Your IPv4 address in your network connection should be fixed and not
automatic and should of course be the same as that showing in your recv.ini
( usually 192.168.238.238 ). If that is all correct then your firewall must
be the problem.

Hope that helps.
Ian.

I imagine that will probably be the trouble - although when I was
changing to a Windows 7 machine I also installed the wrong software for
the EKU and ended up with a dead EKU which needed replacing. I then
needed one extra tweak to set the route.

All the best

james


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

Unsure what a term means? Check the Glossary at:
http://www.satsignal.eu/wxsat/glossary.htm

Join GEO - the Group for Earth Observation
for the informative GEO Quarterly magazine:
http://www.geo-web.org.uk/

Yahoo! Groups Links
Re: EKU no being recognised and the red T icon

Neil <neilthackrey@...>
 

Hi Ian,
I have changed the IP address.. what subnet mask, default gateway, preferred DNS and alternative DNS server should I use ?

atb Neil

--- In MSG-1@yahoogroups.com, James Brown <satellite@...> wrote:

On 13/05/2013 09:31, Ian Deans wrote:
If you have a permanent red "T" then either your interface address is wrong
or your firewall is causing a problem.

Your IPv4 address in your network connection should be fixed and not
automatic and should of course be the same as that showing in your recv.ini
( usually 192.168.238.238 ). If that is all correct then your firewall must
be the problem.

Hope that helps.
Ian.

I imagine that will probably be the trouble - although when I was
changing to a Windows 7 machine I also installed the wrong software for
the EKU and ended up with a dead EKU which needed replacing. I then
needed one extra tweak to set the route.

All the best

james
Re: EKU no being recognised and the red T icon

Neil <neilthackrey@...>
 

Cheers John.... I will give it a go.

atb Neil

--- In MSG-1@yahoogroups.com, "seggins@btinternet.com" <seggins@...> wrote:

Install all in a separate folder eg Eumesat, preferably on its own partition. Not in either program files.
Cheers
John

Sent from my HTC

----- Reply message -----
From: "Neil" <neilthackrey@...>
To: <MSG-1@yahoogroups.com>
Subject: [MSG-1] Re: EKU no being recognised and the red T icon
Date: Mon, May 13, 2013 09:18
Thanks to all for your constructive replies. Yes, I agree I wish I had stayed with XP pro now. This issue is driving me nuts.

The password issue was resolved via msconfig, startup. The problem now is the T icon in task is permanent red indicating tc-recv Connect failed. I have checked in the html shell under licence which shows the following;

Client identification appears all correct with user and a host 1 to 4 all showing some parameters. The Active Clients shows the TSL announcement channel with a status of error. Under licence, not sure about this one;

Tellicast server licence, server address not yet received, OEM and description the same.

The tick boxes under what I can get and what is activated are Tellicast, File Broadcast, Datastreams.



The only anomaly I can see is the actual Client licence with Version 2.4.4q 200610301329200 win32-i86pc. Being a 64bit OS here could this be a problem?



In the top left of the HTML it indicates config problem. Now here is the weird one. When I copy my recv.ini file into the program I lose the red T in the task bar all together even though it is identical to the one generated when you load the Tellicast client software. The only way I can get the red T back is to re-install the Tellicast.

And yet another weirdy is I cannot edit the original rcv.ini file as when I come to save I get a window saying Access denied. The only way I can do is to replace the file with my original which I can edit in notepad.

When I installed the three applications (DVB, Etoken, Tellicast) some went into programs files whilst one defaulted into programs files (x86). I then uninstalled the lot and re-installed everything into program files which made no difference.



So all in all it is becoming annoyingly frustrating.



If there any windows 7 64 bit users out there it would be appreciated if you could send me a sample of your recv.ini and recv.channels.ini file to compare. I suppose ultimately I will have to send this to the eumetcast support desk.



I look forward to your comments.



atb Neil



--- In MSG-1@yahoogroups.com, Alan Sewards <alan@> wrote:

Hello James,
Thank you for your comment. From the subsequent postings my effort
appears to be rather inadequate: perhaps I should have said it was for
Windows XP. Clearly Win 7 introduces a new lot of problems, not the
least being poor availability of suitable software (3 years after it
appeared!). Many people find the installation process too arcane or
complicated - it is a pity that Eumetsat did not pull all the items
together with a single Installer that leads users through the
installation process, preferably all on one CDROM. Sometimes, I think it
is miraculous that it works at all! I'm glad I stayed with XP on my
Eumetcast machine.
Best regards - Alan S
On 12/05/2013 5:10 PM, James Brown wrote:
That would be useful as a 'sticky' somewhere Alan - I have archived it
for future reference.
Cheers
On 12/05/2013 13:47, Alan Sewards wrote:
Hi Neil,
I have a feeling that you have used the wrong order in installing the
software. Some notes I have on this are as follows
------------------------------------
Unsure what a term means? Check the Glossary at:
http://www..satsignal.eu/wxsat/glossary.htm
Join GEO - the Group for Earth Observation
for the informative GEO Quarterly magazine:
http://www.geo-web.org.uk/
Yahoo! Groups Links
--
Alan Sewards
émail: alan@
web site: http://asewards.free.fr










[Non-text portions of this message have been removed]
Re: EKU no being recognised and the red T icon

Neil <neilthackrey@...>
 

Hi Ian... your correct the IPv4 address is different to the recv.ini address.
The question is how do I change it from 169.254.178.3 to 192.168.238.238 in windows 7?
If I double click the local area connection2 it shows the IPv4 connectivity- No Internet access. I then click on details which shows the IPv4 address as 169.254.178.3 then I click on diagnostics which results in local area connection 2 doesn't have a valid IP configuration NOT FIXED. Then I click on additional options which just gives links to support groups etc. NO help on changing the IP address.

Many thanks
atb Neil

--- In MSG-1@yahoogroups.com, "Ian Deans" <iandeans142@...> wrote:

If you have a permanent red "T" then either your interface address is wrong
or your firewall is causing a problem.

Your IPv4 address in your network connection should be fixed and not
automatic and should of course be the same as that showing in your recv.ini
( usually 192.168.238.238 ). If that is all correct then your firewall must
be the problem.

Hope that helps.
Ian.

-----Original Message-----
From: Neil
Sent: Monday, May 13, 2013 9:18 AM
To: MSG-1@yahoogroups.com
Subject: [MSG-1] Re: EKU no being recognised and the red T icon

Thanks to all for your constructive replies. Yes, I agree I wish I had
stayed with XP pro now. This issue is driving me nuts.
The password issue was resolved via msconfig, startup. The problem now is
the T icon in task is permanent red indicating tc-recv Connect failed. I
have checked in the html shell under licence which shows the following;
Client identification appears all correct with user and a host 1 to 4 all
showing some parameters. The Active Clients shows the TSL announcement
channel with a status of error. Under licence, not sure about this one;
Tellicast server licence, server address not yet received, OEM and
description the same.
The tick boxes under what I can get and what is activated are Tellicast,
File Broadcast, Datastreams.

The only anomaly I can see is the actual Client licence with Version 2.4.4q
200610301329200 win32-i86pc. Being a 64bit OS here could this be a
problem?

In the top left of the HTML it indicates config problem. Now here is the
weird one. When I copy my recv.ini file into the program I lose the red T
in the task bar all together even though it is identical to the one
generated when you load the Tellicast client software. The only way I can
get the red T back is to re-install the Tellicast.
And yet another weirdy is I cannot edit the original rcv.ini file as when I
come to save I get a window saying Access denied. The only way I can do is
to replace the file with my original which I can edit in notepad.
When I installed the three applications (DVB, Etoken, Tellicast) some
went into programs files whilst one defaulted into programs files (x86). I
then uninstalled the lot and re-installed everything into program files
which made no difference.

So all in all it is becoming annoyingly frustrating.

If there any windows 7 64 bit users out there it would be appreciated if
you could send me a sample of your recv.ini and recv.channels.ini file to
compare. I suppose ultimately I will have to send this to the eumetcast
support desk.

I look forward to your comments.

atb Neil
Re: EKU no being recognised and the red T icon

seggins2000
 

Install all in a separate folder eg Eumesat, preferably on its own partition. Not in either program files.
Cheers
John

Sent from my HTC

----- Reply message -----
From: "Neil" <neilthackrey@fastmail.es>
To: <MSG-1@yahoogroups.com>
Subject: [MSG-1] Re: EKU no being recognised and the red T icon
Date: Mon, May 13, 2013 09:18
Thanks to all for your constructive replies. Yes, I agree I wish I had stayed with XP pro now. This issue is driving me nuts.

The password issue was resolved via msconfig, startup. The problem now is the T icon in task is permanent red indicating tc-recv Connect failed. I have checked in the html shell under licence which shows the following;

Client identification appears all correct with user and a host 1 to 4 all showing some parameters. The Active Clients shows the TSL announcement channel with a status of error. Under licence, not sure about this one;

Tellicast server licence, server address not yet received, OEM and description the same.

The tick boxes under what I can get and what is activated are Tellicast, File Broadcast, Datastreams.



The only anomaly I can see is the actual Client licence with Version 2.4.4q 200610301329200 win32-i86pc. Being a 64bit OS here could this be a problem?



In the top left of the HTML it indicates config problem. Now here is the weird one. When I copy my recv.ini file into the program I lose the red T in the task bar all together even though it is identical to the one generated when you load the Tellicast client software. The only way I can get the red T back is to re-install the Tellicast.

And yet another weirdy is I cannot edit the original rcv.ini file as when I come to save I get a window saying Access denied. The only way I can do is to replace the file with my original which I can edit in notepad.

When I installed the three applications (DVB, Etoken, Tellicast) some went into programs files whilst one defaulted into programs files (x86). I then uninstalled the lot and re-installed everything into program files which made no difference.



So all in all it is becoming annoyingly frustrating.



If there any windows 7 64 bit users out there it would be appreciated if you could send me a sample of your recv.ini and recv.channels.ini file to compare. I suppose ultimately I will have to send this to the eumetcast support desk.



I look forward to your comments.



atb Neil



--- In MSG-1@yahoogroups.com, Alan Sewards <alan@...> wrote:

Hello James,
Thank you for your comment. From the subsequent postings my effort
appears to be rather inadequate: perhaps I should have said it was for
Windows XP. Clearly Win 7 introduces a new lot of problems, not the
least being poor availability of suitable software (3 years after it
appeared!). Many people find the installation process too arcane or
complicated - it is a pity that Eumetsat did not pull all the items
together with a single Installer that leads users through the
installation process, preferably all on one CDROM. Sometimes, I think it
is miraculous that it works at all! I'm glad I stayed with XP on my
Eumetcast machine.
Best regards - Alan S
On 12/05/2013 5:10 PM, James Brown wrote:
That would be useful as a 'sticky' somewhere Alan - I have archived it
for future reference.
Cheers
On 12/05/2013 13:47, Alan Sewards wrote:
Hi Neil,
I have a feeling that you have used the wrong order in installing the
software. Some notes I have on this are as follows
------------------------------------
Unsure what a term means? Check the Glossary at:
http://www..satsignal.eu/wxsat/glossary.htm
Join GEO - the Group for Earth Observation
for the informative GEO Quarterly magazine:
http://www.geo-web.org.uk/
Yahoo! Groups Links
--
Alan Sewards
émail: alan@...
web site: http://asewards.free.fr










[Non-text portions of this message have been removed]
Re: EKU no being recognised and the red T icon

Ian Deans
 

I agree James that there may be an extra tweak needed to set the route ( I have needed this in Vista/Windows 7 and Windows 8 ) but that will manifest itself in a yellow "T" so I am hoping that the red "T" problem is resolved first of all.

Regards
Ian.

-----Original Message-----
From: James Brown
Sent: Monday, May 13, 2013 10:06 AM
To: MSG-1@yahoogroups.com
Subject: Re: [MSG-1] Re: EKU no being recognised and the red T icon

On 13/05/2013 09:31, Ian Deans wrote:
If you have a permanent red "T" then either your interface address is wrong
or your firewall is causing a problem.

Your IPv4 address in your network connection should be fixed and not
automatic and should of course be the same as that showing in your recv.ini
( usually 192.168.238.238 ). If that is all correct then your firewall must
be the problem.

Hope that helps.
Ian.

I imagine that will probably be the trouble - although when I was
changing to a Windows 7 machine I also installed the wrong software for
the EKU and ended up with a dead EKU which needed replacing. I then
needed one extra tweak to set the route.

All the best

james
Re: EKU no being recognised and the red T icon

James Brown
 

On 13/05/2013 09:31, Ian Deans wrote:
If you have a permanent red "T" then either your interface address is wrong
or your firewall is causing a problem.

Your IPv4 address in your network connection should be fixed and not
automatic and should of course be the same as that showing in your recv.ini
( usually 192.168.238.238 ). If that is all correct then your firewall must
be the problem.

Hope that helps.
Ian.

I imagine that will probably be the trouble - although when I was changing to a Windows 7 machine I also installed the wrong software for the EKU and ended up with a dead EKU which needed replacing. I then needed one extra tweak to set the route.

All the best

james
Re: EKU no being recognised and the red T icon

Ian Deans
 

If you have a permanent red "T" then either your interface address is wrong or your firewall is causing a problem.

Your IPv4 address in your network connection should be fixed and not automatic and should of course be the same as that showing in your recv.ini ( usually 192.168.238.238 ). If that is all correct then your firewall must be the problem.

Hope that helps.
Ian.

-----Original Message-----
From: Neil
Sent: Monday, May 13, 2013 9:18 AM
To: MSG-1@yahoogroups.com
Subject: [MSG-1] Re: EKU no being recognised and the red T icon

Thanks to all for your constructive replies. Yes, I agree I wish I had stayed with XP pro now. This issue is driving me nuts.
The password issue was resolved via msconfig, startup. The problem now is the T icon in task is permanent red indicating tc-recv Connect failed. I have checked in the html shell under licence which shows the following;
Client identification appears all correct with user and a host 1 to 4 all showing some parameters. The Active Clients shows the TSL announcement channel with a status of error. Under licence, not sure about this one;
Tellicast server licence, server address not yet received, OEM and description the same.
The tick boxes under what I can get and what is activated are Tellicast, File Broadcast, Datastreams.

The only anomaly I can see is the actual Client licence with Version 2.4.4q 200610301329200 win32-i86pc. Being a 64bit OS here could this be a problem?

In the top left of the HTML it indicates config problem. Now here is the weird one. When I copy my recv.ini file into the program I lose the red T in the task bar all together even though it is identical to the one generated when you load the Tellicast client software. The only way I can get the red T back is to re-install the Tellicast.
And yet another weirdy is I cannot edit the original rcv.ini file as when I come to save I get a window saying Access denied. The only way I can do is to replace the file with my original which I can edit in notepad.
When I installed the three applications (DVB, Etoken, Tellicast) some went into programs files whilst one defaulted into programs files (x86). I then uninstalled the lot and re-installed everything into program files which made no difference.

So all in all it is becoming annoyingly frustrating.

If there any windows 7 64 bit users out there it would be appreciated if you could send me a sample of your recv.ini and recv.channels.ini file to compare. I suppose ultimately I will have to send this to the eumetcast support desk.

I look forward to your comments.

atb Neil
Re: EKU no being recognised and the red T icon

Neil <neilthackrey@...>
 

Thanks to all for your constructive replies. Yes, I agree I wish I had stayed with XP pro now. This issue is driving me nuts.
The password issue was resolved via msconfig, startup. The problem now is the T icon in task is permanent red indicating tc-recv Connect failed. I have checked in the html shell under licence which shows the following;
Client identification appears all correct with user and a host 1 to 4 all showing some parameters. The Active Clients shows the TSL announcement channel with a status of error. Under licence, not sure about this one;
Tellicast server licence, server address not yet received, OEM and description the same.
The tick boxes under what I can get and what is activated are Tellicast, File Broadcast, Datastreams.

The only anomaly I can see is the actual Client licence with Version 2.4.4q 200610301329200 win32-i86pc. Being a 64bit OS here could this be a problem?

In the top left of the HTML it indicates config problem. Now here is the weird one. When I copy my recv.ini file into the program I lose the red T in the task bar all together even though it is identical to the one generated when you load the Tellicast client software. The only way I can get the red T back is to re-install the Tellicast.
And yet another weirdy is I cannot edit the original rcv.ini file as when I come to save I get a window saying Access denied. The only way I can do is to replace the file with my original which I can edit in notepad.
When I installed the three applications (DVB, Etoken, Tellicast) some went into programs files whilst one defaulted into programs files (x86). I then uninstalled the lot and re-installed everything into program files which made no difference.

So all in all it is becoming annoyingly frustrating.

If there any windows 7 64 bit users out there it would be appreciated if you could send me a sample of your recv.ini and recv.channels.ini file to compare. I suppose ultimately I will have to send this to the eumetcast support desk.

I look forward to your comments.

atb Neil

--- In MSG-1@yahoogroups.com, Alan Sewards <alan@...> wrote:

Hello James,

Thank you for your comment. From the subsequent postings my effort
appears to be rather inadequate: perhaps I should have said it was for
Windows XP. Clearly Win 7 introduces a new lot of problems, not the
least being poor availability of suitable software (3 years after it
appeared!). Many people find the installation process too arcane or
complicated - it is a pity that Eumetsat did not pull all the items
together with a single Installer that leads users through the
installation process, preferably all on one CDROM. Sometimes, I think it
is miraculous that it works at all! I'm glad I stayed with XP on my
Eumetcast machine.

Best regards - Alan S

On 12/05/2013 5:10 PM, James Brown wrote:
That would be useful as a 'sticky' somewhere Alan - I have archived it
for future reference.

Cheers

On 12/05/2013 13:47, Alan Sewards wrote:
Hi Neil,

I have a feeling that you have used the wrong order in installing the
software. Some notes I have on this are as follows


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

Unsure what a term means? Check the Glossary at:
http://www.satsignal.eu/wxsat/glossary.htm

Join GEO - the Group for Earth Observation
for the informative GEO Quarterly magazine:
http://www.geo-web.org.uk/

Yahoo! Groups Links



--
Alan Sewards
émail: alan@...
web site: http://asewards.free.fr
Re: EKU no being recognised

Alan Sewards
 

Hello James,

Thank you for your comment. From the subsequent postings my effort appears to be rather inadequate: perhaps I should have said it was for Windows XP. Clearly Win 7 introduces a new lot of problems, not the least being poor availability of suitable software (3 years after it appeared!). Many people find the installation process too arcane or complicated - it is a pity that Eumetsat did not pull all the items together with a single Installer that leads users through the installation process, preferably all on one CDROM. Sometimes, I think it is miraculous that it works at all! I'm glad I stayed with XP on my Eumetcast machine.

Best regards - Alan S

On 12/05/2013 5:10 PM, James Brown wrote:
That would be useful as a 'sticky' somewhere Alan - I have archived it
for future reference.

Cheers

On 12/05/2013 13:47, Alan Sewards wrote:
Hi Neil,

I have a feeling that you have used the wrong order in installing the
software. Some notes I have on this are as follows


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

Unsure what a term means? Check the Glossary at:
http://www.satsignal.eu/wxsat/glossary.htm

Join GEO - the Group for Earth Observation
for the informative GEO Quarterly magazine:
http://www.geo-web.org.uk/

Yahoo! Groups Links



--
Alan Sewards
�mail: alan@asewards.net
web site: http://asewards.free.fr
Re: EKU no being recognised

Ian Deans
 

The E-Token password is not required for Eumetcast. Go into start-up and disable PKIMonitor Application. That will stop the window coming up asking for password.

Hope that helps.

Regards
Ian.

-----Original Message-----
From: Neil
Sent: Sunday, May 12, 2013 7:50 PM
To: MSG-1@yahoogroups.com
Subject: [MSG-1] Re: EKU no being recognised

Hi Arne...
Installed the 64 bit version PKI 4.5 then changed my rcv.ini and recv-channels.ini to where all the data should go. When I start the computer the etoken window comes up asking me to change my password which I just then close. Since changing my recv.ini and recv-channels.ini I have lost my 'T' symbol in the task bar. If I look at the html shell with the antenna disconnected I can see my EKU details under license. What should I do when I keep getting the change password etoken window? I tried putting my existing password then keeping the same which it won't allow. Should I try changing it to something else using their password conventions then changing it back to my original password?

The EKU red light is glowing marvelously

atb Neil
14741 - 14760 of 31250