progdvb.com

Tested with 6.85.2:
1. Settings, Options, Time shift buffer, increase Buffer Size above 200 MB (i have 2 GB physical RAM) -> Error Message. Then, the Scheduler Settings are lost. Additional time is set back to default, login for MS Scheduler is lost. Your error handling is - ummm - suboptimal.

Version 6.84.5 has no problem aquiring 400 MB.....

2. Scheduled a record with hibernate on completion. ProgDVB crashed at the end of the record with Popup 'abnormal program termination' - no logs.
Could you please change your code to write a stacktrace to the logfiles (yes, I checked the Log checkbox on Debug&Repair Options) before showing any Windows? And a catch-Block on the Main thread to catch every Exception?

3. After wakeup from hibernate, ProgDVB occasionally blocks a core on my Dual-Core CPU. I have to kill the process.

Switched back to version 6.84.5.


--
OS Windows XP Home Sp3
{BDA} Hauppauge WinTV 88x DVB-S/S2 Tuner/Demod
Demultiplexor: Elecard
Video Renderer VMR-9
MPEG-2 Elecard

1. No changes in timehsift buffer in last versions. Must good working in any size before 500-700mbyte for win32 and unlimited for x64.

2. sleep and hibernate very depended from drivers

1. The size of the installer reduced from ProgDVB6.84.5Pro.exe to ProgDVB6.85.2Pro.exe about an MB. I think you have changed the assembly use (GAC?) and the reduced availability of the buffer is a side effect.

2. OK, it is a difficult topic, but if you write a good log i could provide all the valuable information to fix it. Right now I can only tell that there is something not working....

1. It is possible if different 10-30 mbytes. But not 200.

2. Show me ProgDVBEngine.log at first.

1. Well, ProgDVB displays a Box with "Error set memory" (maybe not exactly) but no log with technical Information what the cause of this error is. And because the scheduler settings are lost it looks like an inproper handled exception.

2. I would like to, but there is no log - not in the Program directory and not in the log Subdirectory. I've searched the entire disk. There is only a startup.log until the moment ProgDVB died. A silent death

Check Settings->Options->Debug->Logs.

Checkmark is set but as I said: The only log that is written is startup.log in the Logs Subdirectory.