Posts by mckee25

You forgot something buddy:

Introductions

:taxman:

Do you mean mount your HDD buddy???

press the blue button on your remote twice, select Devices manager. Then press the red button for mountpoints, select your HDD and use the right/left arrows on the remote to select media/hdd.

It will tell you to do a full restart after this....

Strange yes, but at least your sorted bud. Can I close this thread now??? :snicker:

Quote from carmine

you are kidding buddy surely there is another way ?

Nope, not kidding at all bud. I would actually go as far as flashing on the original Vu Duo image first and initialize the HDD with that loaded on. Then flash on BH 2.0.6 and setup again. For all the time it would take it's well worth it, give your box a good clean out...

If it was me I would re-flash the box, start again...

I think your going to need to initialize the hdd... the usb stick remove it and then format it to fat32 then plug it back into the box then check in device manager to see it it shows.

Press the blue button twice, select devices manager. In here press the red button for mountpoints, then change your usb drive to be mounted as media/usb by pressing the right or left arrow on the remote. You will need to do a full restart after this. Then repeat for the HDD and mount this as media/hdd

Try doing a full restart again buddy, at least one of the devices should show up, mount it correctly then restart the box again, next time you go into device manager you will then see the one that is not mounted, mount this and then restart again...

USB Sandisk CRuzer Blade size 3.996 GB Mount:/media/usb

HDD (whatever make it is) Mount:/media/HDD

Have a read of post #17 again, this tells you how to do it with the remote....

is this good friend the same one that told you to put your picons on the hdd :snicker:

You have your devices mounted incorrectly...

You have your usb stick mounted as the Hdd, and your hdd is not mounted at all.

Using device manager you can change them very easily.

Did you mount the usb drive???? press the blue button twice, select devices manager. In here press the red button for mountpoints, then change your usb drive to be mounted as media/usb by pressing the right or left arrow on the remote. You will need to do a full restart after this.

Cams for ViX are available here buddy:

ViX cams

Hello buddy,

First thing we need to know is what image you have on your box?? that way we can tell you exactly how to configure either to work correctly....

http://linuxsat-support.com/showthread.php?t=30915 Follow this link if you would like to read a tutorial on using crossepg with ViX.

Hello kierangalway,

A Introduction post is required buddy before asking for support... Introductions

Can you tell what image is currently running on your solo at the minute?

Hello Jassinho,

Your video was quite good right up to the bit where you mentioned people could buy a c line from you for £55 for the year..., what a pity you didn't read the rules!

Goodbye, your banned!

Picons would be better on a usb stick bud, otherwise when you channel hopping the hdd will keep working until you stop flicking....

Using a ftp program you would place the folder which contains your picons named "picon" on your desktopfirst , then copy it over to media/usb if you decide to place them on a usb stick. if you want to go ahead and put them on your hdd then place the picon folder in media/hdd.

All the Picons you would ever need are available here: Picons Download

Bit of both at the minute to be honest....

Bit of a technical explanation but this is what makes up a lamedb file...

Lamedb format
File format of lamedb explained.
Taken from /lib/dvb/db.cpp and Tools/Transponder.py.
File is basically a fixed format file where some fields contain multiple values separated by commas of colons. Lines may not exceed 256 characters.
It contains two sections.

Transponders started by a line transponders. Contains transponder frequencies, symbol rates, polarization and satellite position.
Services started by a line services. Contains SSID, Card ID for channels on a particular transponder.

Header Line
The file starts with a line eDVB services /%d/, where %d is format version.

eDVB services /4/

Transponders section
Section starts with a line transponders.
Followed by a DVB line and transponder data line tuples. The DVB data line starts at col 0, the transponder data line immediatly follows and starts with a <TAB>.
Lines starting at col0 contains three fields encoded in hexadecimal:
DVB namespace
Transport stream id
Original network id

Lines starting with a <TAB> character and contain DVB transponder data such as frequency and symbol rate. Three types of DVB transponders can be encoded here:

Satellite DVB
Terestrial DVB
Cable DVB

Satellite lines start with <TAB>s like: s 10773250:22000000:0:2:192:2:0:1:2:0:2 fields for version 3 and 4. All fields are separated by colons, values in decimal.

Frequency in Hertz.
Symbol rate in bits per second.
Polarization: 0=Horizontal, 1=Vertical, 2=Circular Left, 3=Circular right.
Forward Error Control (FEC): 0=None , 1=Auto, 2=1/2, 3=2/3, 4=3/4 5=5/6, 6=7/8, 7=3/5, 8=4/5, 9=8/9, 10=9/10.
Orbital Position: in degrees East: 130 is 13.0E, 192 is 19.2E. Negative values are West -123 is 12.3West.
Inversion: 0=Auto, 1=On, 2=Off
Flags (Only in version 4): Field is absent in version 3.
System: 0=DVB-S 1=DVB-S2.
Modulation: 0=Auto, 1=QPSK, 2=QAM16, 3=8PSK.
Rolloff (Only used in DVB-S2): 0=0.35, 1=0.25, 3=0.20
Pilot (Only used in DVB-S2): 0=Auto, 1=Off, 1=On.

Terrestrial lines start with <TAB>t:

frequency in Hertz.
Bandwidth: 0=Auto, 1=8Mhz, 2=7Mhz, 3=6Mhz.
Code rate High Pass FEC: 0=Auto, 1=1/2, 2=2/3, 3=3/4, 4=5/6, 5=7/8.
Code rate Low Pass FEC: 0=Auto, 1=1/2, 2=2/3, 3=3/4, 4=5/6, 5=7/8.
Modulation: 0=Auto, 1=QPSK, 2=QAM16, 3=QAM64.
Transmission mode: 0=Auto, 1=2k, 3=8k
Guard Interval: 0=Auto, 1=1/32, 2=1/16, 3=1/8, 4=1/4
Hierarchy: 0=Auto, 1=None, 2=1, 3=2, 4=4
Inversion: 0=Auto, 1=On, 2=Off.
Flags

Cable lines start with <TAB>c:

Frequency in Hertz.
Symbol rate.
Inversion: 0=Auto, 1=On, 2=Off.
Modulation: 0=Auto, 1=QAM16, 2=QAM32, 3=QAM64, 4=QAM128, 5=QAM256.
Forward Error Control innert (FEC_inner): 0=None, 1=Auto, 2=1/2, 3=2/3, 4=3/4, 5=5/6, 6=7/8, 7=8/9.
Flags

services section

The section starts with the word services on a line by itself.
Followed by a three line tuple: DVB stream data, Channel name, Provider data line.
The DVB stream data line contains six fields:

Service id (SSID value from stream) in Hex
DVB namespace in Hex.
Transport stream id in Hex
Original network id in Hex
Service type in Decimal: 1=TV, 2=Radio
Service number in Decimal.

The Channel name is on a line by itself in some character encoding (to be investigated)
The last line contains Provider Service data. Variable number of fields, separated by commas. Fields formed like <tag>:value. For example p:*** Digital,c:000202,c:010282,c:020242,c:030202,c:0500 01,C:0963,C:0961,C:0960.

Provider name field. Field tag p: Name of provider.
Cached data. Field tag c: followed by two decimal digits and four hexadecimal digits. For example c:010282 is composed of 01 decimal cache id, 0282 hexadecimal value to cache.
Card ID (CIAD). Field tag C: follwed by four hexadecimal digits: Card ID. For example C:0100.
Flag data: Field tag f: followed by hexadecimal digits.

Hello buddy, have a read of this thread:

http://linuxsat-support.com/ca…esnt-use-new-pairing.html

It may help you with the problem you have, but cards seems to be going off all over the place if they are not in a original receiver... might just have to accept the fact that sharing this provider is coming to a end now.

ok have you flashed a image onto your duo2 yet?? or has it come pre-installed with a image already on there?? if so what image is it running?