Recent content by Black Hole

You admit you have no IT background and yet you won't acknowledge advice that Linux tools will handle a Linux file system better than Windows tools? This is stupid. fixdisk is a CF script for automating the use of Linux tools. Just do it.

Anyone who's read my commissioning thread. You seem to want to forge your own path, so good luck to you.

Some of the more recent additions to HTML dimension units allow for the visible window.

It looks like the OP has minimised the apps-home-back bottom menu, like auto-hiding the task bar in Linux or Windows. Nonetheless, the app's presentation layer really ought to be reactive to the actual screen area available rather than the physical size of the screen, as per modern web design...

The thread I referred you to tells you how to test a fan. We have no published schematics so everything that's been done so far is by reverse engineering. I was working on a CPU fan add-on but that went by the wayside – there's no easy way for a non-engineer to pick up the existing fan power...

To answer this, the only source of on-board temperature data is the HDD diagnostics. I have done some work on this in the past, and there are unused internal USB points on the PCB.

Just a left-field suggestion: have you tried scrolling the menu?

In addition to the above: HDR-FOX Hardware: Commissioning, Disassembly, Repair (which is pinned near the top of the HDR-FOX section of the forum [ie this section] and, frankly, should not have escaped your attention!).

I think that's a fault with the app itself, the UI designers should be told.

Posts crossed, see above. The "hidden directory" seems to be the manifestation of the table/database I was talking about. The Foxsat CF newk package will have to be modified to take care of it.

There's obviously some kind of process (within the Humax "blob") consulting some kind of table/database of what it thinks should be there (the recording with title unaltered) and generating a place-holder when not, and not registering the altered version because that's not what got recorded. I...

How?

I can't understand why the .hmt files would reappear, presuming the rm command completed successfully. A zero length .hmt indicate a failed recording (in HDR-FOXland), probably one which didn't get triggered because the start flag was not received during the required window.

So it doesn't! I missed that (the rule is too long). Like I said, if these rules were hand-crafted rather than GUI-generated, they are very prone to error (particularly with this level of complexity).