4wd: I see, I'm now trying to beg, borrow or steal a Sony

Vurbal: I guess you weren't kidding when you promised me the potential of frustration.
VirtualDub was unpacked on the 32bit XP machine and then placed in the c:\Program folder and run from an Admin account.
Everything was connected via EZCAP and VD found the device. In Capture mode, VD displayed the Camera's entry Screen with Date/time display.
Activating play on the Camcorder gave me a functioning playback in VD and sound from the external speakers.
I named the target location for saved files and then started playback on the Camcorder, I selected "test video capture" but VD's display blanked. I had noticed a parameter to suppress the monitor and suspected this was the cause. I didn't bother to change anything but simply stopped the "test" and then proceeded with a live capture. Again the monitor was blank but I could hear the soundrack so I simply continued for a few seconds and then "stopped" the capture.
When I tried to open the file in VD the target directory was displayed but explorer crashed.
Error Signature: AppName: explorer.exe AppVer: 6.0.2900.5512 ModName: shmedia.dll ModVer: 6.0.2900.5512 Offset: 0000ac54
The detailed error report can't be cut and pasted and because I chose the option not to send the report to MS the anticipated detailed log file (C:\DOCUME~1\THEFAT~1\LOKALA~1\Temp\c002_appcompat.txt) was never created, or at least, I was never able to find it :-(.
I bit the bullet and tried to do it again, this time to try to capture the log file before saying no or by saying yes to transmit. I now can't see the camcorder output. If I stop playback then a single frame is displayed which seems to be the first frame on the tape. This is a "ghost" from previous attempts because if I access the settings menu it clears and if I restart VD, it resets to the current Camcorder status screen. Any attempt to capture the output in either test or genuine mode simply results in a capture error poppup and the message "unable to start video capture".
Two attempts to capture were made and two small files created. Both files could be opened with VD but were empty. Heres the Media info on one of those files just in case it's significant.
hidden text
General
Complete name : C:\Users\Colin\Downloads\VDtest2.avi
Format : AVI
Format/Info : Audio Video Interleave
File size : 10.0 KiB
Video
ID : 0
Format : YUV
Codec ID : YUY2
Codec ID/Info : YUV 4:2:2 as for UYVY but with different component ordering within the u_int32 macropixel
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 3:2
Frame rate : 29.970 fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:2
Compression mode : Lossless
Audio
ID : 1
Format : PCM
Format settings, Endianness : Little
Format settings, Sign : Signed
Codec ID : 1
Bit rate mode : Constant
Bit rate : 3 072 Kbps
Channel(s) : 2 channels
Sampling rate : 96.0 KHz
Bit depth : 16 bits
Alignment : Aligned on interleaves
I now can't re-create the first error conditions because of the "new" capture error status so I simply can't provide a representative windows crash log file.
Is there a VD log/crash file that I can inspect?
As soon as the explorer error condition is acknowledged then Explorer (not the machine) re-boots. If I then try to use the Start Menu to get to the file location it still crashes immediately the location is accessed. However, if I take the route through Computer\C:\Docs and Settings\etc I can at least "open" the appropriate folder but as soon as I attempt to even right click the supposed video file then Explorer crashes. I do briefly get the right click context menu. I can access other files/folders in that directory but not the offending video clip - even mouse-over causes a crash.
I was able to remove the file only by capturing it in a marquee and then deleting it AND I EMPTIED THE WASTE BIN AND REBOOTED FOR GOOD MEASURE so, NO, I can't provide any kind of header or any other information from that particular menace!
For the record, a subsequent capture test utilising Showbiz successfully completed, so, if there are any common .dlls or CODECS they remain in functioning condition.