Originally Posted by tluxon
...This is absolutely not working satisfactorily the way I've got it set up. Whenever I make a single capture, it seems to "break" the transport functions of the 3416. I've actually had this problem before, but it was completely solved by keeping the 40k turned on and set to the firewire input. That doesn't appear to work anymore with the 3416...
BTW, the transport (FF, REW) functions don't seem to "break" as badly as long as:
1) The 40K's firewire is plugged into the 3416 firewire port nearest the power cable;
2) the 40K is turned on and tuned to the firewire input (usually I-6 now, but sometimes it's label as I-2 and sometimes it "slips" to F-1, whereas it used to always lock in at I-3).
So far I have found that if I don't have the 40K on line as described above, I can't use the PC<-->3416 hookup without breaking the transport functions regardless of which port I use on the 3416.
Originally Posted by ExDeus
Did you use the path to where you had the firestb.msi file, or were you using my example path? I was using an example. Replace "C:\\path\ o\\firestb.msi" with the full path to wherever you have the firestb.msi file. So that may be "C:\\some folder\\some other folder\\firestb.msi", or "D:\\folder for special things\\folder for very special things\\most specialist\\firestb.msi", or wherever...
Yes, I specified the path where the files were on my
Originally Posted by ExDeus
...I don't know what order you did it in, but the last one you must've installed was meitape.sys, while the driver name you selected in Device Mgr was an option associated with the meistb.sys driver you installed earlier.
It doesn't make sense to me that there would be a descrepancy between what files
Device Manager says are installed and which files are specified in the appropriate oemXX.inf file. If anything, I would tend to trust the files listed under the Driver Details button in the properties window of the listed device since it is "live" in Device Manager whereas the oemXX.inf file is resident whether the firewire is connected or not. There must be some other explanation such as perhaps some file other
than the highest numbered serialized file might possibly be current.
Originally Posted by grittree
I think you need to have SP2 to run msiexec. Or maybe you need the updated .net installed.
meitape.sys and meistb.sys are the exact same 22,891 byte driver. Just a rename.
For several reasons the notebook I'm using for this is still on SP1 and yet msiexec seemed to run okay - at least I know it started because I saw the image of the 3412 and then the list of four install selections with three checked by default. I'm not sure if I have .net framework 2.0 (it may still be on 1.1 from way back when) - I'll have to check when I get home.
I suspected that meitape.sys and meistb.sys were the same, so thanks for confirming that for me. What driver comes out of firestb.msi? Also, I noted a few supporting drivers but I can't name them off the top of my head. Perhaps there are some differences there as well.
Thanks for taking the time to try to help me out. Hopefully this will end up being helpful to others who try to do the same thing. Also, it would be nice to get this thing working without requiring the 40K to capture successfully from my 2nd 3416 in the family room.