Terratec Cinergy Digital 1200 DVB-C, Terratec Home Cinema ja Jyväskylän (Jyväsviestimen) kaapeliverkko

Askartelin Terratec Home Cineman taajuustiedostosta version, jossa on Jyväsviestinnän (Elisan) digitaajuudet muxeineen: Terratec-Home-Cinema-Frequencies-Jkl.zip (14 kt). Alkuperäisen Frequencies.xml:n pitäisi löytyä kansiosta C:\Program Files\TerraTec\TerraTec Home Cinema\. Sammuta THC ensin, jos se on käynnissä ja nimeä alkuperäinen uudelleen (vaikkapa .old-päätteiseksi) ennen kuin kopioit paketista löytyvän Frequencies.xml:n kansioon, jotta katastrofin sattuessa alkuperäinen on tallessa.

Tämän jälkeen THC:n asetusten skannausvälilehdellä pitäisi Alue-alasvetovalikossa olla valittavissa “Finland – Jkl”, jonka skannaamalla ainakin minä sain kaikki kanavat Radio Vegaa lukuunottamatta näkymään ja kuulumaan. Näin siis kirjoitushetkellä uusimmilla BDA-ajureilla ja THC:lla (BDA 4.8.11, THC 4.19).

Alkuperäinen tiedosto on asennuksen jälkeen kirjoitussuojattu, siis “Vain luku” -tyyppiä. En tiedä, onko sillä merkitystä, mutta varmuuden vuoksi tein omastanikin sellaisen.

Atspace and 'ftp : connect :unknown error number'

I had problems making an FTP connection to my Atspace account for a couple of weeks, preventing my webcam image from updating. Filezilla kept failing to connect, and the most information I was able to find about what was wrong was from Windows’ commandline ftp (yea, it’s horrible, I know), which kept saying ftp : connect :unknown error number (‘tuntematon virhenumero’ tai jotain sinne päin suomeksi).

Thanks to Juha, I finally realized it was PeerGuardian 2 blocking the connection. Perhaps the fact that they’ve done this is related to Atspace having problems with spyware opening browser windows with their front page. In any case, I uninstalled PG2 since it’s been a source of trouble before. But it hadn’t done this to me before, nor caused any problems in a while, which had lead to me completely forgetting about ever having installed it (like I said in the thread at Atspace’s support forums).

MPEG4 Modifier

“[This program modifies] a MPEG-4 ASP video (XviD, DivX) without re-encoding (change aspect ratio, edit userdata, remove packed bitstream, and change interlaced field order). It can also show information about the video such as the amount of I/P/S/B-VOPs used, whether or not QPel/GMC were used, etc. The video must be in an AVI container, and OpenDML isn’t currently supported.”

Moitah via Moitah

An Open Source Blue Frog

“Our approach: An open source Blue Frog replacement based on P2P technology. No centralized reporting server. No website. Any single point of failure could be switched out on the fly. The entire project would exist in P2P-space. No single node becomes more important than the rest. Simply give your spam to the client, and it goes out on the network where it is processed. ”

CastleCops via Juha

Flashing the iRiver T10

iRiver T10 Today I received the iRiver T10 I’d ordered a week ago. Initially, I had been put off by the fact that the players sold inside EU were Microsoft-only. But then I found out it’s possible to flash the firmware to get rid of the MTP crap.

After having tried the WMP10 approach with my new toy once, this is what I set out to do.

The Pure and Non-Pure versions were explained at MisticRiver forums. The “Non-Pure” version has an FM radio. Mine doesn’t, so it’s “Pure”. The firmware version my player came equipped with was 1.23P.

So I picked up the Pure version from mtp-ums.net and proceeded by the instructions provided there. I missed the verifying question about firmware upgrade after the restart, but you can start it from the advanced menu.

The first flashing took a little under a minute. After the restart there was the ominous “Scan music file…” screen, as promised, and the player was now a UMS device when I plugged the USB cable in. Halfway there!

I then uploaded the Australian firmware, from iRiver, into the player. During flashing this file, the screen was a backlit black, once again as promised. The flashing took closer to two minutes this time. After this, I had a fully working, UMS-abled T10 with the latest firmware version 1.70.

iRiver T10 System Info