This has not happened on my Foxsat which is about 1 week old. Next time it happens, see if you can telnet or SSH into the Foxsat
Example:
[anc@slave ~]$ ssh -l root 192.168.254.64
[email protected]'s password:
Foxsat-HDR~#
(The IP needs to be changed to your IP address and the command prompt is from my laptop running Ubuntu, it will look different from windows command prompt.)
At the Foxsat prompt:
Foxsat-HDR~#
You can type the command:
top
This will show you which processes are running and the load average on the Foxsat
Mem: 112220K used, 13316K free, 0K shrd, 37084K buff, 38196K cached
CPU: 14.9% usr 13.0% sys 0.0% nic 71.4% idle 0.3% io 0.0% irq 0.1% sirq
Load average: 0.42 0.34 0.16 2/133 681
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
292 285 root S 306m250.2 0 11.0 /usr/bin/settop
315 285 root S 306m250.2 0 7.9 /usr/bin/settop
383 285 root S 306m250.2 0 2.1 /usr/bin/settop
681 669 root R 1632 1.3 0 1.5 top
--snip--
The colomn under CPU% should never be higher than 50%, you need to press "q" without the quotes to cancel this command.
If you see any line where the CPU % is higher than 50% copy it in your browser and paste result.
You can then try rebooting, enter:
reboot
and this will restart your Foxsat. Depending on the nature of the lockup these commands may not work and I am assuming you have media bundle 4.04 installed and either telnet or SSH plugin.
You did say in original post that this happens viewing the TV guide. There is a small delay in my box sometimes less than 1 second as it pulls down the TV guide but it never freezes. I'm not sure if a very slow network connection would affect this, some ISP's use traffic shaping at night and the broadband usage for all customers is slowed. This may have nothing to do with your problem though.