Initial DiSEqC/LOF settings not saved properly...

[NoOne1]

Good afternoon,

*** This should be repeatable WITHOUT resorting to the types of equipment configurations that I normally use.
I believe I’ve reduced it to the simplest form.
I would appreciate confirmation, thanks. ***

== SETUP-ENVIRONMENT ==
W2KP, P4@2.4GHz
TH-1020a(03T) or SS2-rev2.3p
DVBDream 1.2.c (also a and b prior versions, just did not have time to document)

== SETUP-APPLICATION==
TOTALLY clean install. (Installing over a prior working version invalidates results as prior (good) files are retained/accessed.)

== OPPORTUNITY ==
Scan results are sporadic and/or bogus BECAUSE,
DiSEqC configuration information is NOT being recognized/saved.

1) Reverts to default lnb(f) configuration (Ku-Linear (Universal)).
2) Reverts to default UnCommitted Switch setting (Disabled). It is not necessary to actually have an UnCommitted type switch installed for this test.

== REPLICATION SEQUENCE ==
** DO NOT have a folder named DVBDREAM i.e. rename existing functioning install.
3) Execute dvbdreamsetup_12c.exe
3a) Follow the normal screen dialogs as presented after the Install button is clicked accepting all as presented up to DiSEqC Settings.
4) DiSEqC Settings
=
4a) DiSEqC Switch Type; v1.0 or v2.0
=
4b) Port 1; select 1st satellite (0050 Sirus 2/3)
4b1) LOF Settings; Ku-Circular
4b2) Uncommitted; 1
OK
=
4c) Port 2; select 2nd satellite (0070 Eutelsat W3A)
4c1) LOF Settings; C-Band
4c2) Uncommitted; 2
OK
=
4d) Port 3; select 3rd satellite (0100 Eutelsat W1)
4d1) LOF Settings; NA Bandstacked DP Ku-Hi (DBS)
4d2) Uncommitted; 3
OK
=
4e) Port 4; select 4th satellite (0130 HotBird 1-7)
4e1) LOF Settings; NA Bandstacked DP Ku-Low (FSS)
4e2) Uncommitted; 4
OK
==
5) Accept all remaining dialogs as presented.
6) App shows credits video with music playing and SCAN flashing in lower right corner.
6a) Exit/Close app.
7) Execute app.
7a) Menu OPTIONS -> DiSEqC...
7b) Select any Satellite on any Port and click Properties.

=== Here lies the BASIC problem ===
LOF Settings reverted to; Ku-Linear (Universal)
Uncommitted reverted to; Disabled
i.e. neither were selected during the setup process.
===
7b1) LOF and Switch FREQUENCIES may be valid for the original selections.
7b2) Exit the Properties of each satellite via Cancel.
8 ) Exit/Close app.
9) Execute the app.
9a) Menu OPTIONS -> DiSEqC...
9b) Reviewing the Properties of the satellites now most likely will show LOF and Switch FREQUENCIES associated to Ku-Linear (Universal).

====
This whole values read/used gets more convoluted as a scan is actually performed successfully or not, to the point of total confusion. You do not know if you are actually dealing with valid entries at the time of a scan or AFTER the scan and attempting to tune to a channel.

I just do not have the time to document every occurence.

This should shed some light on the subject of scan results.

If it can not be duplicated by others I will do a finite file(s) capture for debugging, It will be at least a week before I have the time.
====

NoOne1

[rel]

Hello NoOne1,

Thanks for the report (it was a big one! I mean the bug)

Fixed in v1.2d, thanks


Just couldnt reproduce the following part. Maybe I can send a test version today. I'm planning the release v1.2d at the weekend.

7b1) LOF and Switch FREQUENCIES may be valid for the original selections.
7b2) Exit the Properties of each satellite via Cancel.
8 ) Exit/Close app.
9) Execute the app.
9a) Menu OPTIONS -> DiSEqC...
9b) Reviewing the Properties of the satellites now most likely will show LOF and Switch FREQUENCIES associated to Ku-Linear (Universal).

[NoOne1]

Good morning,

Looks like you are on a roll squashing bugs!

Send me your test version or PM me with location/access info. It is raining here so I'll make time to test it asap. Rain will clear this afternoon, my test time will become very limited then.

====
NoOne1

[rel]

Morning,

I'm unable to reach dd files at the mo, (I'm at the work unfortunately). I will send it in few hours. but better I'll try to double check the steps you wrote, today again.

Thank you

[rel]

Posted the test version here

[rel]

fixed in v1.2d