I just got to the bottom of this bug after messing with it on and off throughout the day.

I had been capturing HDV files from my Sony HDR-HC3 all this week. On one of them I was getting two dropped frames/packets each time. I eventually came to the conclusion that the problems were on the tape itself, since they kept showing up in the same spots. But, prior to reaching that conclusion, I tried various things in my attempts to eliminate the "droppage". One of them was to try to capture to a file across the network (LAN), to a folder on another PC. The hope was that maybe there was enough buffering in that process to keep from dropping frames. Well, I got the same two dropped frames anyway, BUT, mysteriously, the destination file was not there! So I had no idea where the file had been written.

A few days later I'm cleaning up my main hard drive (C:) and it seems to have more space in use than I'm actually using. After transferring stuff off to an external hard drive, I discovered that the C:\Documents and Settings\Robert\Nethood\ folder had 12GB in it, despite me only being able to see 'link' folders to various Network Places. CHKDSK and other approaches failed to reveal the problem. Browsing each of the folders in the Nethood folder just showed files on other PCs.

Finally I used a CMD shell and did a DIR /S and saw the errant file in "shared on Robert's Computer (VAIO)". Browsing there does not show it. I was able to remove it with the CMD shell.

Bottom line, HDVSplit seems to have a misfeature such that if you try to capture to a file across the network to another PC, it will instead go in a local folder in the Nethood folder such that you can't see it using the graphical file browser. Only by dropping down to a CMD shell can you see or delete such a file.

EDIT: Just a bit more, I was tipped off during my working on this problem today when I defragmented the C: drive after removing most of its contents, and the defragmenter reported that it was moving HDV-Tape2.m2t (the name of the file I captured with HDVSplit), yet a search for a file with that name revealed no results.