How can I transfer files from defunct HDR FOX T2 to view on HDR 2000T?

[prpr]

1. Is there any mileage in building a Linux boot environment that includes stripts that can be downloaded to bootable USB or posted out on CD - that any PC user can attach and follow standard guide to create playable files from Humax recordings?

If you build it. How would the recordings get in to such an environment?

2. In the WebIf Advanced/encryption key setting that allows setting a different key including one from another FoxT2, is there any key that saves unencrypted recordings, ie. that play via file access (not media share) without an intermediate decryption step?

Don't you think that would have been done by now if it was possible?

So far as I can see, the main stumbling block with the Windows version is ensuring the availability of the libraries it relies on.

Or just build a version that doesn't need any. The VS build I did which uses native DES only needs the standard Micro$oft runtime libraries. I also did a static build just to see what the difference in file size was and its 150k v 50k, and runs on anything from XP onwards.

Just bundling it up with the appropriate DLLs, and perhaps (somehow) sandboxing it might be easier.

Why does it need sandboxing? And the same question about the recordings.

Another thought: is there some kind of utility for Windows which does the equivalent of Wine?

Like WSL you mean?

It does not seem to me that we need worry about any further alternatives.

Quite.

 

[EEPhil]

In summary, Linux non-users can:

1. Use the stripts build for Windows, which requires Cygwin installed;
2. Use the HFODU utility, which requires the Java runtime environment;
3. Wait for @prpr to release the VS build.

It does not seem to me that we need worry about any further alternatives.

Thanks for the mention. Just to point out HFODU has not been updated for a while. I usually point people to stripts because the installation is much easier. Installing Java can be a right pain. Also, to be honest, I've forgotten most of the detail behind HFODU and only have one test file from an HDR- Fox-T2 (provided by af123) so there is always the possibility I couldn't rectify any faults easily. It is there to use if anyone wants it. If it works - it works. If it doesn't I'll attempt to fix it - but no guarantees!

So far as I can see, the main stumbling block with the Windows version is ensuring the availability of the libraries it relies on.

Or just build a version that doesn't need any. The VS build I did which uses native DES only needs the standard Micro$oft runtime libraries. I also did a static build just to see what the difference in file size was and its 150k v 50k, and runs on anything from XP onwards.

The main reason HFODU was Java was I had no access to any C compiler with the necessary runtime library - I still don't (Microsoft bloatware, no thanks!). If I had the library I would have statically built the executable. Making sure you have the correct dynamic library is a pain. (I mean, there are so many versions of Cygwin - and when I gave Windows stripts a try my initial guess as to the version of Cygwin was wrong!)