zero byte files

[Lindsay]

After deleting a recording there is a zero byte file with the name of the recording left in the gbpvr directory. What gives here? Not only that, but I now have three that can't be deleted. A rootkit scan picks these out and shows them as 'showname:metadata.xml' with 300-500 bytes.

Edit:- just noticed, the three that won't delete have at least two stops in their name. This obviously is confusing something.

[sub]

What filesystem are you using?

These metadata.xml files are an alternate datastream on original recording which contains the show details. Even though it looks like it is zero bytes, you can open it notepad. ie, notepad showname:metadata.xml

Are you saying they appeared after you deleted a recording?

[Lindsay]

Thanks, sub. Just checked. No, they are there when the recording starts but don't get deleted when the show is deleted. Sorry for the confusion - I always cleared them after the shows were deleted.

Are they needed for shows that are not deleted?

NTFS file system.

[sub]

Usually the actual recording and this meta data file are part of the same file, delete one and they both get deleted.

The file isnt needed at all. Its just informational.

The bug with the zero byte file was fixed in v0.96.8.

[Lindsay]

Damn. forgot to update my signature. It now shows ver 96.8.

Wonder why my 96.8 still leaves those files?? I think the odd one may get deleted but the vast majority don't.

[sub]

I was never able reproduce the problem myself, so I wasnt 100% sure I fixed it. I fixed the one thing I suspected was creating it.

I think the odd one may get deleted but the vast majority don't.

They should never have to be deleted. They are supposed to be the same file as the video. They never supposed to exist as a separate file. They just two data streams in the same file.

Have you ever seen one of these files while you still have your recording on disk? I starting to wonder if you were on to something when you mentioned it appeared when you deleted the recording. I've always though they must have been created at the same time the file was created.

I also thought they might be related to cancelled recordings.

I dont get them here, so I've never really had a chance to study them.

[Lindsay]

I have now put in some more study! They are created when the recording begins and just stay forever! It is not related to cancelled recordings.

[sub]

I wonder if something has disabled alternate data stream support on your machine?

Unless I work out what is causing it, I'll just add an option in the next release not to create the metadata.xml stream.

[Lindsay]

When a recording starts, should I see a file created in the gbpvr dir other than the alt data stream one? The alt one is all I see.

How would I check to see if alt data sream is disabled?

Another interesting thing. I have just done 48 test recordings and all were free of the machine gun. Then I rebooted 2 min before the end of one recording and it had the MG and now two subsequent recordings have the MG. Mmmmm. Wonder what a reboot could do to set the MG off???

[sub]

When a recording starts, should I see a file created in the gbpvr dir other than the alt data stream one? The alt one is all I see.

No, you should see any file created. The only file that you should see is .mpg of the recording. Hidden inside this .mpg should be this metadata.xml alternate data stream.

How would I check to see if alt data sream is disabled?

I dont if its even possible. It was just me thinking out loud.