the network search only one Transponders
ex any 11747 , h,27500,34
when the Transponders file ex 0130.ini not written in the file 0130.ini the
network search get it and automatic written in
example.
new Transponders not add in file 0130.ini the 11223 ,H,27500,34 as example
and the network search example 11747 ,H,27500,34 written in the file 0130.ini the network search find automatic 11223 ,H,27500,34 and written in automatic in file 0130.ini
if the network search find new Transponders
then ,add automatic to 0130.ini
and thank you to all
#2
Some years ago, prog decided, to not let ProgDVB write into the transponder ini files, to increase and preserve the comaptibility with some existing little varieties from different sources.
Besides, some users have to use special transponder files, for non standard proprietary LNBs.
So, if thinking about automatically adding newly found transponders, either there would have to be an option, to forbid that changes without an error message - perhaps by an extra switch - or ProgDVB would have to introduce some kind of a special database in between, to import from 3rd party INI files and optionally from NIT, maybe even with a user interface for special recalculation, like for band stacking LNBs.
Nice idea anyway, but certainly not a really easy job to implement without losing any other benefit or compatibility...
Up to Prog to decide, of course
Besides, some users have to use special transponder files, for non standard proprietary LNBs.
So, if thinking about automatically adding newly found transponders, either there would have to be an option, to forbid that changes without an error message - perhaps by an extra switch - or ProgDVB would have to introduce some kind of a special database in between, to import from 3rd party INI files and optionally from NIT, maybe even with a user interface for special recalculation, like for band stacking LNBs.
Nice idea anyway, but certainly not a really easy job to implement without losing any other benefit or compatibility...
Up to Prog to decide, of course
My signature:
Please read here:
On Bug Reports And Other Complaints
and there:
BOARD RULES - READ THIS!
I don't give support by e-mail or PM.
And I will never assist on PayTV hacking.
PM ME FOR THIS AND YOUR ACCOUNT WILL BE DELETED IMMEDIATELY, WITHOUT ANY WARNING!!!
NEVER EVER DARE TO CONTACT ME FOR PRO VERSION ISSUES!
I am not responsible for that.
Check the 'Activation' section.
Please keep it in English here, or Russian in the Russian section, or German in the German section.
I don't read nor write Klingonian or any other language than English and German.
Addressing me personally in any exotic language will be treated as severe insulting! Be warned!!!
1.)AMD Phenom II x4 940, GA-MA770-UD3, 8 GB DDR2-6400. 7 Pro SP1 x64 + XP Pro SP3 x86
DVB-S2: Cynergy S2 USB HD
2.)P4 3200 i865G (F-S Scenic W600pwr) XP Pro SP3
DVB-S: hauppauge WinTV Nexus-S rev. 2.2, driver TT 2.19h, hardware mode
19.2°,13°,28.x°E,30°W, DiSEqC 1.0
Auf Deutsch:
DVB-Cube <<< Das deutsche DVB-Forum >>>
Please read here:
On Bug Reports And Other Complaints
and there:
BOARD RULES - READ THIS!
I don't give support by e-mail or PM.
And I will never assist on PayTV hacking.
PM ME FOR THIS AND YOUR ACCOUNT WILL BE DELETED IMMEDIATELY, WITHOUT ANY WARNING!!!
NEVER EVER DARE TO CONTACT ME FOR PRO VERSION ISSUES!
I am not responsible for that.
Check the 'Activation' section.
Please keep it in English here, or Russian in the Russian section, or German in the German section.
I don't read nor write Klingonian or any other language than English and German.
Addressing me personally in any exotic language will be treated as severe insulting! Be warned!!!
1.)AMD Phenom II x4 940, GA-MA770-UD3, 8 GB DDR2-6400. 7 Pro SP1 x64 + XP Pro SP3 x86
DVB-S2: Cynergy S2 USB HD
2.)P4 3200 i865G (F-S Scenic W600pwr) XP Pro SP3
DVB-S: hauppauge WinTV Nexus-S rev. 2.2, driver TT 2.19h, hardware mode
19.2°,13°,28.x°E,30°W, DiSEqC 1.0
Auf Deutsch:
DVB-Cube <<< Das deutsche DVB-Forum >>>
#3
Juergen wrote:Some years ago, prog decided, to not let ProgDVB write into the transponder ini files, to increase and preserve the comaptibility with some existing little varieties from different sources.
Besides, some users have to use special transponder files, for non standard proprietary LNBs.
So, if thinking about automatically adding newly found transponders, either there would have to be an option, to forbid that changes without an error message - perhaps by an extra switch - or ProgDVB would have to introduce some kind of a special database in between, to import from 3rd party INI files and optionally from NIT, maybe even with a user interface for special recalculation, like for band stacking LNBs.
Nice idea anyway, but certainly not a really easy job to implement without losing any other benefit or compatibility...
Up to Prog to decide, of course
thank you good work