Log file fills up the hard drive

[boxxed]

How do I stop a log file from filling up my hard drive?

[sub]

Which log file and how big did it get? There is supposed to be maximum sizes, with the log files rolling over to a new file when this size is reached, and the oldest log file deleted.

[boxxed]

I am not in front of the machine right now, but it something like the gbpvrrecording..something or other. My hdd is 120 gig and the file gets almost that big. Windows tells me that I am running out of disk space.


Thank you...

[sub]

Post back when you've checked the exact filename and size.

I've not seen any other reports of this.

[boxxed]

When I look at the log files it is the gbpvrrecordingservice.exe-native file. It was 1.1 gig and after a reboot the file name changed to .....native-1 and it is now 1.1 gig and the new gbpvrrecordingservice.exe-native file is now 2.2 gig.

I have 2 cards. One is Hauppauge 350 and the other is the 500. About 8 to 10 months ago I had this setup running just fine. Since then I did a fresh install of XP pro, all updates..etc A new install of your latest version and now I have not been to successful at getting this setup.

Now the MVp is telling me contacting MediaMVP Bootsever, Contacting DHCP server...I ' ve tried up-plugging, waiting, rebooting, still the same.

Thank you.

[sub]

I've never seen a log file grow this big. What message was filling the log files?

[boxxed]

When I try and open the file it tells me the file is to large for notepad. I am not able to open the file.

[sub]

Can you try to open it soon after restarting the recording service, but after it starts growing, so that it's still relatively small?

I suspect the bulk of the size of this log is made up of one message repeating.

[boxxed]

Yes sir you are correct. Here is what it fills up with.

2007-10-13 01:03:00.171 VERBOSE GetFilterProperty - IKsPropertySet->QuerySupported property failed

[sub]

You'd usually get this type of error if you capture device type is set wrong. (less likely, but also possible, it can happen when you're using a PVR350 tv out)

What type of capture card(s) do you have? I'd recommend double checking you've got the right device types selected. If you got a mixture of PVR250/350 and PVR150/500, then you may have the device numbers set wrong.

EDIT: just saw you card list above. I'm guessing the device numbers are set wrong.