When starting ProgDVB (latest version 6.61.1) ALWAYS the "crash-screen" is appearing asking me whether to b) Reset all settings or c) Normal start ... the Option a) Use last known good configuration is not selectable!
When starting, it seems to run normally, and at exiting/quitting, nothing special seems to happen - and an next start, again the above dialogue box - always at every start!
What's wrong?
Re: ProgDVB 6.61.1 always reports to have crashed at every s
#21. Do you use any plugins?
2. What device?
2. What device?
Re: ProgDVB 6.61.1 always reports to have crashed at every s
#3No, no plug-in.
Pinnacle Quattro Stick - was working until updating to 6.61.1
What I did and could be a cause of the problem:
I had installed 6.61.0 and first downloaded again 6.61.0 instead of 6.61.1 ... after installing new version, I still had the report that 6.61.1 is available ... I then deinstalled ProgDVB totally, but left lists; then I took out onto the desktop the left program-folder and reinstalled from scratch again 6.61.0 ... and had again seen that it is 6.61.0 and not 6.61.1 ... then I installed 6.61.1 over 6.61.0 ... finding channels was no problem - but when starting, always error that it was not correctly closed ...
only option I set is "no one-click program select" and "no visualisation at radio station". all the rest is untouched.
Problem happens both DVB-C and DVB-T - I mostly use DVB-C
Pinnacle Quattro Stick - was working until updating to 6.61.1
What I did and could be a cause of the problem:
I had installed 6.61.0 and first downloaded again 6.61.0 instead of 6.61.1 ... after installing new version, I still had the report that 6.61.1 is available ... I then deinstalled ProgDVB totally, but left lists; then I took out onto the desktop the left program-folder and reinstalled from scratch again 6.61.0 ... and had again seen that it is 6.61.0 and not 6.61.1 ... then I installed 6.61.1 over 6.61.0 ... finding channels was no problem - but when starting, always error that it was not correctly closed ...
only option I set is "no one-click program select" and "no visualisation at radio station". all the rest is untouched.
Problem happens both DVB-C and DVB-T - I mostly use DVB-C
Re: ProgDVB 6.61.1 always reports to have crashed at every s
#5disabling all modules does not change anything ...
Re: ProgDVB 6.61.1 always reports to have crashed at every s
#6Very strange. But please wait next version of ProgDVB.
Also you can try install not in program files directory.
Also you can try install not in program files directory.
Re: ProgDVB 6.61.1 always reports to have crashed at every s
#7Next thing I plan to do is rollback - I still have the old directory that was inside program directory with all .ini etc. files ...
I do not exclude harddisk- or OS-defect as I remember a problem when unpacking .rar-archive: on that netbook it was not possible - it just did not unpack a certain archive that was unpacking on an other notebook without problems ...
I do not exclude harddisk- or OS-defect as I remember a problem when unpacking .rar-archive: on that netbook it was not possible - it just did not unpack a certain archive that was unpacking on an other notebook without problems ...
Re: ProgDVB 6.61.1 always reports to have crashed at every s
#8This is not OS/hdd problem. But ProgDVB crash on exit or not have access to progdvb.ini.
I am recomend install not in program files with data in same directory.
I am recomend install not in program files with data in same directory.
Re: ProgDVB 6.61.1 always reports to have crashed at every s
#9ähm ... that is, what I did ... before, I had installed "in same directory as program" - and it was working fine. now I did install "one for all users" - and it shows that problem ... I will experiment a bit with those install-parameteres ...
Re: ProgDVB 6.61.1 always reports to have crashed at every s
#10Then ProgDVB not have access for user directory. May be some bug or specific. Some time problem if you install ProgDVB in different user account.
Re: ProgDVB 6.61.1 always reports to have crashed at every s
#11when declaring to store configuration-files in program-folder (and not user-specific), the crash does not happen ...
but I consider it as questionable to store stuff in program-folders; those should be untouched at normal use ...
but I consider it as questionable to store stuff in program-folders; those should be untouched at normal use ...