New VIX Image ET 9x00 Series Version 2.4 15/05/2012 - DISCUSSION ONLY -

[Tkr001]

setup, information from the remote

[twol]

setup, information from the remote

I guess this depends on your skin, as mine just says 2.4 and date, which is why I OPKG'ed. So where is the version number stored?

[Rob van der Does]

I guess this depends on your skin, as mine just says 2.4 and date, which is why I OPKG'ed. So where is the version number stored?

Indeed: if a skin is not ViX-compatible, the version will not show.
You can manually open etc/image-version

[Flyingpig]

How do I get my Picons to work again? All of a sudden they have gone, and that is to do with Silverfox's wish - however, I have uploaded Picons to numerous folders and still they dont work...

Help please folks!!

FP.

[Rob van der Does]

You have them in /picon (not /picons)?

[Flyingpig]

That may be my first error - I guess then the folder should be called /picons Changed

Secondly - is there a place where i select the location or where does my ET9000 look for the Picons?

Thanks,

[Rob van der Does]

Just in the root (so /picon) on any medium (preferably flash, worst option is HDD).

[river-rat]

new update wont update? no plugins? feed down?

when i go to update, it says there is 2 updates, i click the green to update, warns about update and reboots. Yet nothing is installed. Also for 2-3 days in plugins, says feeds down?

box is on kernal 3.3.0
drivers:31/3/2012
2.4
build 149
last update it says was 6/9

on vix update

it says 2 packages, i go to view changes , it says build 210 and build 214 but does update

[Maxwell]

try it with telnet

init4
opkg update && opkg upgrade

reboot when finished

[river-rat]

try it with telnet

init4
opkg update && opkg upgrade

reboot when finished

Collected errors:
* pkg_parse_from_stream_nomalloc: Excessively long line at 7. Corrupt file?
root@et9x00:~#


i have just downloaded 210 from the site as well as 214, put both on a usb stick to try that way and wont pick them up?

[The Lambton Worm]

Collected errors:
* pkg_parse_from_stream_nomalloc: Excessively long line at 7. Corrupt file?
root@et9x00:~#


i have just downloaded 210 from the site as well as 214, put both on a usb stick to try that way and wont pick them up?

You can't put two versions on the same stick. Just put 214 on the stick and make sure there's nothing else on there too.

[river-rat]

i don`t mean at the same time, i`m not that dumb lol

i have flash boxes all day long when i used to mod cable boxes and eurovoxs ect, last time i had a update to do, NO FILES from here worked, i had to go else where and this is the site that makes the image for it....

i have the folder et9x00 and 5 files in there, tried back and front usb, a 8gb, 4 gb and 64gb stick and nothing.


#it does my head in, as the site makes the image and the updates, yet a 5-10 min job takes ages and wont work, as well as the online part of the support, plugins ect and down as well

[river-rat]

after reading the vu+ people are having issules, i have tried to go from 149 to 151 and was picked up straight away on the usb

[river-rat]

ok guys, the manual move to 151 is the way to go if still on a old one like i was, after hitting update have gone to 213 with no issues

maybe the people who do the firmware, may want to look into why i could not update via the web?? while i was on 149, as well as the 2 files i tried on here didn't work.

the download plugin list now works as well

[Larry-G]

There is nothing wrong with the images as hosted here or via the OpenViX server, it's certainly odd that they would not work for you but there the same images that others then host on their own sites, also by downloading the images from other sites you dont know what your getting as quite a few upload backups they have made and we have no way of knowing what additions they have placed into that image.

as for your update problems it may be because you were trying to update from such a old image but i would not compare it to the Duo, Solo problems as most of them are because of the anti clone measures Vu implemented into their drivers which prevent clones using any of the newer build images.

in future can you also state which exact build you are using when you encounter problems, as far as i remember 149 was a unstable build where as 155 was a stable build and certain older builds did have some issues with updating, but were solved by making a settings backup and flashing a fresh image, then restoring that backup.