R
RegisRMAN
I've been trying to setup my DV capture device on a dedicated desktop under Windows10 and hit the common problem of unexistent drivers for the FW400 interface. After googling for answers I found many posts describing the known workaround.
First I've tried under Win10 x64 LTSC 1803, but the "Legacy" driver didn't appear in the available options.
So, I downloaded the 1394_OHCI_LegacyDriver from this site, but upon installation nothing happened after a fleeting window appeared, no result window or anything, and the Legacy driver still didn't appear in the driver options !
So I unpacked the .msi file, and noticed there were TWO driver versions inside, x86 and x64 but with the files renamed with a leading "_" and either a "1" or "2" at the end, while the corresponding .inf files text pointed to "normal" filenames., and there was no script to parse the filenames anywhere.. (it sure wasn't going to work like that ! I'm surprised this package worked for ANYONE !)
After renaming the files correctly, then forcing the install by right-clicking on the .inf files, the legacy driver option FINALLY appeared in the driver options for the controller, but after selecting it it gives a code 10 error "this device cannot start"...
Same thing with the other version of the driver (x86) contained in the package.
I've tried with 2 different brands of FW adapters (both PCI), a NEC and a Texas Instruments.
The strangest thing is that on my Win7 laptop (HP Elitebook 8560w. It has a 4-pin FW connector), the legacy driver and capture equipment work just fine !!!
So I tried downgrading to a fresh install on Win7 x64 SP1, this time the legacy driver appears in the driver options, but selecting it gives the same code 10 error ! :'(
The installed legacy driver version is exactly the same (6.1.7601.17514) on both machines though.
So, what the F could be the problem that's plaguing my desktop's FW interface, and how the hell can I solve it plz ???
I'm at my wits end, and terribly pi$$ed off by this stoopid decision to remove the drivers for an industry standard such as the Firewire bus !! I've lost 2 weeks of time because of this "bug", and my blood pressure is dangerously rising...
(if it matters, the desktop machine's hardware is as follows :
Gigabyte Z97P-D3 mobo
I7-5775C
32G DDR3 1600MHz
Radeon RX590
PCI Firewire adapter (NEC or TI)
Latest X64 drivers)
Continue reading...
First I've tried under Win10 x64 LTSC 1803, but the "Legacy" driver didn't appear in the available options.
So, I downloaded the 1394_OHCI_LegacyDriver from this site, but upon installation nothing happened after a fleeting window appeared, no result window or anything, and the Legacy driver still didn't appear in the driver options !
So I unpacked the .msi file, and noticed there were TWO driver versions inside, x86 and x64 but with the files renamed with a leading "_" and either a "1" or "2" at the end, while the corresponding .inf files text pointed to "normal" filenames., and there was no script to parse the filenames anywhere.. (it sure wasn't going to work like that ! I'm surprised this package worked for ANYONE !)
After renaming the files correctly, then forcing the install by right-clicking on the .inf files, the legacy driver option FINALLY appeared in the driver options for the controller, but after selecting it it gives a code 10 error "this device cannot start"...
Same thing with the other version of the driver (x86) contained in the package.
I've tried with 2 different brands of FW adapters (both PCI), a NEC and a Texas Instruments.
The strangest thing is that on my Win7 laptop (HP Elitebook 8560w. It has a 4-pin FW connector), the legacy driver and capture equipment work just fine !!!
So I tried downgrading to a fresh install on Win7 x64 SP1, this time the legacy driver appears in the driver options, but selecting it gives the same code 10 error ! :'(
The installed legacy driver version is exactly the same (6.1.7601.17514) on both machines though.
So, what the F could be the problem that's plaguing my desktop's FW interface, and how the hell can I solve it plz ???
I'm at my wits end, and terribly pi$$ed off by this stoopid decision to remove the drivers for an industry standard such as the Firewire bus !! I've lost 2 weeks of time because of this "bug", and my blood pressure is dangerously rising...
(if it matters, the desktop machine's hardware is as follows :
Gigabyte Z97P-D3 mobo
I7-5775C
32G DDR3 1600MHz
Radeon RX590
PCI Firewire adapter (NEC or TI)
Latest X64 drivers)
Continue reading...