Recent content by Black Hole

Reallocated sectors are the HDDs normal self-repair mechanism, and should be "transparent" (in other words: handled in the background with no obvious side-effects). Sometimes there is a hitch and the data is unverifiable, and the fault has to be handled with the HDD off-line – Fixdisk can sort...

It irritates me that browsers do that. I realise it's the "safe" option for naive users, but it's also a pain that a simple informational website (such as the modern version of a brochure), with no sensitivity whatsoever, has to be HTTPSed just to keep a web browser from stopping the user...

Yes – Firefox is just baulking at the non-trusted key exchange. IMO HTTP wouldn't be particularly unsafe, it's not like you're communicating bank account details anyone could eavesdrop.

No, much worse than that. You didn't read what I referred you to. Excerpt: Oh FFS. Why are you fiddling around in the dark? HDR-FOX Commissioning, Disassembly, Repair (click)

Oops! :D

So you are probably buggered then (short of a hardware fix). That was a critical point to have forgotten to say. Steps for Resolving HDR-FOX Crash/Reboot Issues (in particular, see section 3Ba). Exactly when the restart occurs in the boot cycle is diagnostic. For information: under normal...

But it sounds like you didn't read this: Quick Guide to Disk Recovery (click) No, you don't have to do "linux type stuff", just get a command session so you can access a set of menus. You can do that in Windows. Nope, can't be done. No you don't. Wherever you're getting your information...

I'm sure there would be somebody willing to take it off your hands.

You can just disconnect the LAN, but then you'll not have access to the WebIF either. You might want to stop (uninstall) any CF services which routinely try to "phone home" or monitor network traffic: rs*, auto-update*, tunefix-update*, network-shares-automount, transmission*, ntpclient*...

Why not just fit it and see what happens? It would be logical, would it not, to assume the machine is capable of formatting it for itself? HDR-FOX certainly is.

I am unable to reproduce that, neither on HD-FOX nor HDR-FOX. If you changed changed channel again after 14s, the info bar would be on-screen for 29s anyway. The OSD remains for the set timeout after the last operation. I am unable to reproduce that, neither on HD-FOX nor HDR-FOX. I have my...

:D So it really was a "system reboot (power cycle)" then! I suspect the log report will always default to "power cycle" if no other reason can be identified, but this time it was not crying wolf1

How can invoking the info bar (i plate) by pressing the i button be described as an edge case? What do you have in mind as not an edge case?

...or just disconnect the network for a while to see what happens. I was distracted by sysmon and whether a new crash/reboot problem had been discovered, otherwise I would simply have referred you to Steps for Resolving HDR-FOX Crash/Reboot Issues (click).

From standby? If so, then the rebooting must be triggered by something which isn't running while recording-in-standby (half awake). You seem to have found the fix, although I can't explain why sysmon wouldn't be running in half-awake.