progdvb.com

This card works with progdvb free latest version, but...
When i shutdown progdvb, and want to start it again it just drops some kind of JIT-debugger errors and terminates. It stays active in taskbar, and i have to manually kill the application. It sometimes works when i start it again, but usually terminates. Can you help? I tried all combinations of filters, codecs and stuff in settings, so i suppose it isnt because of that.

You should at least provide all relevant details on your system, as (at least) OS + SP, driver name and version, full device name (from inside of ProgDVB - device list), full DVB hardware name (as provided by Gigabyte), plus the relevant detail on what's crashing (from the JIT error message).

ok, i found what crashed it... it was timeshift. I turned it off, and now it works. So how to enable timeshift to work maybe?

You did not even answer to one of my questions.
So how could anybody try to help you without help of ye ol' magic crystal ball?

This includes timeshift parameters, of course

Thought that's an trivial problem with timeshift, and you know the answer. I'll answer to all of that questions later, didnt have time, sorry

Juergen wrote:You should at least provide all relevant details on your system, as (at least) OS + SP, driver name and version, full device name (from inside of ProgDVB - device list), full DVB hardware name (as provided by Gigabyte), plus the relevant detail on what's crashing (from the JIT error message).

Ok, here it is

Gigabyte GT-U8000-RH (1.0)
winxp pro sp2 + latest updates (all newest frameworks)
about progdvb http://picozilla.com/en/152430/about_progdvb.png.html
device list http://picozilla.com/en/152431/device_list.png.html

jit error i cannot copy because it crashes, shows jit error, then crashes again fast another jit error and then closes, but i saw something saying memory

Timeshift is far from being trivial, as it causes high traffic and disk or memory bus activity, added to the normal one for live TV, that's not really low already...

Try to set timeshift into file, make it reside in a location, you as a user have full writing access and enough disk quota for.
Or, if set to work in RAM, reduce the amount to a value, that's not exceeding your free physical RAM normally.
E.g., if equipped with 512 MB of RAM, don't allow more than ~ 100 MB for timeshift.
Won't help on anything, to allow timeshift eating all your RAM and by this forcing extreme swap file usage. In most cases, the machine would run into severe trouble then.

Best would surely be, to have a second physical disk (not just partition) in a machine, with either the timeshift file or the swap file on it.

Disable indexing for all drives, don't allow any background disk activities, like virus scanning, defragging or similar. Don't just quick format, as after this, full formatting would start as a hidden background job, eating resources without informing you.
If available, locate timeshift file on a big FAT32 partition, as that file system in most cases is a lot faster, specially with quite big clusters.

However, timeshift means, to put quite some extra load to your system bus. Permanent writing and reading must work in close real time with quite limited buffers, any disturbance might make the system fail somehow.
Windows is very sensible on this, supposingly due to it's complexity and still most buggy structure.
Pretty similar to burning CD or DVD with maximum speed, and no proper buffer management...
SP3 may but not must bring some improvement, last chance for XP...

On Linux VDR, I've managed to have perfect timeshift on file, on a vintage computer of 450 MHz PII CPU, i440 BX chipset, with my NEXUS in HW mode. Even recording was perfect then, if using another IDE (ATA66) drive for this. Never made this on Windows 98SE or 2000SP4...

Honestly, the best would be, to simply forget about timeshift, or invest in extra HDD(s).

i can just tell you i'm not an ordinary, i'm power user, and all of this you wrote i know allready but thank you for your reply. I know how is memory management done, and i can just say i didn't exceed the boundaries of my system bus or memory.
Ok, so i wait for better programming times