Recent content by Pheonix

Maybe if the drivers work properly, as we all know TM have a real issue building and keeping their hardware drivers stable,

here is your chance to get involved and help in the development of ABM as part of ViX and the OE-Alliance. It will only take you 5 to 10 minutes of your time. I wont link to the forum incase it's against site rules but i'll include andy's initial post here so you know more. I know the title...

Cant say i have noticed my self, but then again i have not watched much TV recently. funny that I have some 15 plus receivers and on average i watch maybe a hour of TV a week.

some 4:3 content is just not meant to be stretched, this is a limitation by the broadcaster who hard codes it that way, for example old episodes of the Simposns broadcast on sky1 HD, it is not a limitation of the image.

Thats you'r problem there, CrossEPG is known to resource hungry, which why there the image creates a automated swap file when CrossEPG kicks in, but using so many providers can easily grind it to a halt.

Zeus was a total rewrite and a new core which is why it had to be a total reflash with no settings backups used, this is also why it took nearly four months to release after the last ViX 3.0 series image. Helios was unfortunately due to a recent merge with the latest OE (Open Embedded), This...

That was just a corrupt count file on the server and is no way related to the image, we had to wait for the one system admin who has access to correct it, but i did post direct links to the images and posted a announcement about it on the twitter feed.

The problem with that is that all our images ( almost 30 at this moment ) are build pre packed into individual .zip archives, we would then have to download every image, unpack, add the readme then repack and reupload to the server. now i dont know about you but my internet connection is total...

I very clearly stated in the OpenViX Zeus release thread that the Technomate receivers required a new bootloader, I also did the same on the OpenViX twitter account. https://twitter.com/0penViX check the tweets from the 11th of march

How to flash a Vu+ Duo2. Items you need before we start. 1. A suitable USB stick formatted to FAT32. 2. Image of your choice 3. Compression software such as 7zip. 4. HP Format tool ( not essential but highly recommended ) 5. Teracopy ( again not essential but highly recommended ) 6. A clean...

well i can categorically guarantee that ViX will never introduce any thing into any image we produce to in any way harm users receivers if they did i would walk away from the team in a instant, as you pointed out however Vu them selves could as they did recently to stop kernel 3.1.1 images...

as i said to you on another forum, i have yet to meet any one who has ever bought a E2 based receiver specifically for Blindscan capabilities when there are far better purpose built receivers such as the Dr.HD F15 and Dr.HD F16. I dont think you'll be disappointing Nano, I know i certainly am...

See this is how silly nonsensical rumors get started, I can categorically state that ViX have never and will never put any thing into a image that will in any way shape or form tamper with or prevent a image from running be the receiver a clone or not. While it is true that we only support...

As far as i'm aware the memory leak only affects a small amount of Duo's and no other Vu models ( my own Duo hardware revision 1.3 is rock solid on all kernels ). and yes you are correct that Vu are aware of the problem in fact they even had one of the affected models shipped to them by a member...

it was placed in the dreambox section as there was no where fitting for it in the Vu section as this site does not really cater for other E2 based receivers barring a very small subsection. another reason was also that the satellites.xml file generated could indeed be used on any E2 receiver to...