Last.To.Know
Member
Good tip.
Although I might just screencap them from Web-IF.
Although I might just screencap them from Web-IF.
Good tip.
Although I might just screencap them from Web-IF.
Thanks for that.I don't think you can see some changes to default settings in the WebIf. Box default volume, digital audio output settings for instance.
Agreed; a point worth making.One point I didn't see mentioned: if you don't decrypt your recordings, and just copy the encrypted recordings to the external disk, then if your Humax dies, your saved external recordings will no longer be playable. So it's a backup, but only for your current Humax.
You haven't said what your problem is, nor why you think it might be related to the state of the disk hardware. "Hope" sounds a bit like "guess" to me.I am replacing the HDD in the hope that that cures the issues and gives my HDR T2 another few years life.
Do you have any feel for an acceptable threshold for Reported_Uncorrect?I don't like the "Reported_Uncorrect" figure though.
Not really. It's hard to come up with a definitive definition of what it's measuring but normally it's zero, so any time it isn't is a cause to start worrying IMHO.Do you have any feel for an acceptable threshold for Reported_Uncorrect?
I can't remember. I do know that subsequent recordings had bad picture breakup losing 10 seconds or more each time.Did fix-disk fix your single bad sector?
Other than that it looks OK-ish. I don't like the "Reported_Uncorrect" figure though.
197 Current_Pending_Sector -O--C- 1 100 100 000 -
198 Offline_Uncorrectable ----C- 1 100 100 000 -
I am not confident that Humax version 1.02.32 will correctly align partitions for a 4K drive. Either do it by hand using the af123 blog http://wiki.hummy.tv/wiki/2TB_Disk_Installation_Blog (chaning thenumbers to match the size of the drive) or temporarily install 1.03.12 to format the new drive.I'm buying a 1TB HDD and this is my firmware
Custom firmware version: 3.02 (build 2295)
Humax Version: 1.02.32 (kernel HDR_CFW_3.00)
Aarrgh!That indicates corruption in the software image rather than a USB stick problem.
Have you checked that the checksum of the downloaded .zip file matches the one shown on the download site?
Did you by any chance just rename the .zip instead of unzipping it? (daft question but it isn't unknown!)