V5 64-bit Drivers
Has anyone managed to get the 64-bit drivers to work yet? I'm using the pre-release version of Windows 7 64-bit and CO5 doesn't think my P30 exists. It doesn't appear in Device Manager, either. Any success stories elsewhere before I raise a support case?
Andy
Andy
0
-
Have you been able to get your firewire port (I assume it is firewire you connect your P30 to) to work with another device like a disk at all with your Win 7 x64 pre-release? That would be my first check. Next, do you use 4 GB or more RAM? According to release notes of CO5 (page 7) tethered capture is not supported. Last but not least, when you open a support case Phase One might state that only the final release of Windows 7 is supported. 0 -
Thanks Paul - it may the "4GB or more" problem - the machine has 4GB of RAM. Unfortunately I don't have any other firewire device to test it with other than my 1Ds2, which Canon don't provide 64-bit drivers for. I've opened a support case anyway ...
Andy0 -
OK - fixed it. It's not a RAM issue, it's the perennial problem of the buggy P30 firmware which doesn't handle the firewire bus correctly. It works if you apply the fix I gave for 32-bit Windows 7 here: viewtopic.php?f=3&t=7460 - i.e. use the legacy Windows 7 firewire driver and set EnumerateInactiveLink to 1 in the registry. I've now officially asked for the P30 firmware to be updated to bring it in line with the later backs.
For completeness, there might still be a RAM issue as although my laptop has 4GB its hardware/BIOS only allows Windows to see 2.99GB. I can't tell what would happen if the full 4GB were visible!
Andy0 -
[quote="ajmichael" wrote:
For completeness, there might still be a RAM issue as although my laptop has 4GB its hardware/BIOS only allows Windows to see 2.99GB. I can't tell what would happen if the full 4GB were visible!
Andy
Thanks for the feedback, Andy. Do you run Win x64 on your laptop with 4 GB RAM? A 32-bit version of Windows (x86) would show approx. 3 GB because of mapping out memory addresses for the hardware (video adapter and so on). But Win x64 should report the full 4 GB, I would expect.0 -
[quote="Paul_E" wrote:
Thanks for the feedback, Andy. Do you run Win x64 on your laptop with 4 GB RAM? A 32-bit version of Windows (x86) would show approx. 3 GB because of mapping out memory addresses for the hardware (video adapter and so on). But Win x64 should report the full 4 GB, I would expect.
Interestingly enough they both show an identical 2.99GB. I assume that's just the way the hardware was designed and probably dumps things like the video memory in the 4GB space. There's no obvious BIOS setting to remap it, unfortunately.
Andy0 -
Currently I am still operating a Lightphase camera back. I just purchased a new HP HDX16 1370us laptop. It has the 4 pin firewire, and a video card that is appropriate for photography. However it is a Vista Based 64 bit system. I used a Belkin repeated hub to power the back.
At this point in time I've spent 3 days researching, and preparing drivers, recovery discs etc to do a complete reinstall into Vista 32 bit system or XP 32 bit. I am now considering trying out the Windows 7 64 bit system as there are multiple references to it being possible to tether in the 643 bit environment.
If you can, please confirm, deny or answer the following statements / questions to assist me with this issue. They are a jumble of facts I've heard and I'm trying to pick out which I should believe in.
1a: Capture one and tethering your phase backs is not possible in 64 bit mode.
1b: Capture one and tethering your phase backs is possible but not driver supported.
1c: Vista 64 will not work, but Windows 7 64 bit has some work around to allow for tethered capture.
2a: Some PC's have difficulty recognizing the Back through the Belkin Hub. (My camera works fine directly connected to my desktop PC but once I introduce the belkin it is no longer seen)
3a: My vista prompts me to install drivers for my camera, but cannot locate them. When I point to the folder containing them, it does not recognize them. Is this a 64 bit system issue?
4a: Does anyone have an elephant I can borrow to crush my equipment. I think that would be satisfying ta this point.
Andrew0 -
[quote="NN144128UL" wrote:
1a: Capture one and tethering your phase backs is not possible in 64 bit mode.
1b: Capture one and tethering your phase backs is possible but not driver supported.
1c: Vista 64 will not work, but Windows 7 64 bit has some work around to allow for tethered capture.
2a: Some PC's have difficulty recognizing the Back through the Belkin Hub. (My camera works fine directly connected to my desktop PC but once I introduce the belkin it is no longer seen)
3a: My vista prompts me to install drivers for my camera, but cannot locate them. When I point to the folder containing them, it does not recognize them. Is this a 64 bit system issue?
1a: You did not specify the version of Capture One you use but you need Capture One 5 for tethering on Win x64. See release notes CO5.
1b: n/a
1c: CO5 x64 tethering support with Phase One backs is not limited to a particular Windows version, it applies to Win XP/Vista/7 x64. See release notes CO5.
2: See release notes CO5 for powering Phase One backs
3: You need CO5 for tethering on Win x64. See release notes CO5.
Additional note: computer should have less than 4 GB RAM. See release notes CO5.0 -
[quote="Paul_E" wrote:
1a: You did not specify the version of Capture One you use but you need Capture One 5 for tethering on Win x64.
Paul - is that strictly true? The 64-bit drivers are only supplied with CO5, but I can't see any obvious reason why they shouldn't work with CO4 or even CO3 if they're just a device driver?
Andy0 -
I have capture one 5 DB.
I've not attempted to limit my ram to 2.99 gig as of yet. I'm unsure what warnings or symptoms I will receive if I do not.
Since posting this earlier today I've worked with some phase support staff and established the following.
I've completed the IEEE 1394 work around, where you set that registry thing to a value of "1".
I have CaptureOne 5 DB version and Win Vista 64 bit. Lightphase now connects and shows up in device manager under imaging devices.
However a yellow triangle with an exclamation point appears over the icon in device manager.
When I click on the properties, select driver, and then look into the driver details, a driver by the name of ksthunk.sys at the top of the list. Through research I've found reference that it is related to image scanners. The second driver was possibly the proper phase driver (p1c1394).
Tech support had me try to specifically target one of the several files in the drivers folder under the c:/programfilsX86/Phaseone/Divers. p1c1394_x64 or maybe it was p1c1394_x86, but I tried going for both and I was unable to specify which with vistas browsing options.
We had some difficulty figuring out what was actually being installed as a driver. I tried uninstalling the driver, removed the p1c1394_x64 from the folder and attempted to reinstall the driver by pointing at the folder with the missing file, then I tried it the other way around. Strangely it seems the install file or the system information file were all that was required.0 -
[quote="ajmichael" wrote:
[quote="Paul_E" wrote:
1a: You did not specify the version of Capture One you use but you need Capture One 5 for tethering on Win x64.
Paul - is that strictly true? The 64-bit drivers are only supplied with CO5, but I can't see any obvious reason why they shouldn't work with CO4 or even CO3 if they're just a device driver?
Andy
Andy, you are correct that if you have a previous version of CO (CO4, CO3) and are able to install the 64-bits Phase One device driver, it could/should work. Installing CO5 DB for instance could allow you to work with CO4 Pro and provide support on x64 for tethering with Phase One backs. Only an assumption, and probably not supported. And based on various reports, one might need support to get it to work at all. Hence, CO5 seems more as the way to go to me.0 -
[quote="Paul_E" wrote:
[quote="ajmichael" wrote:
[quote="Paul_E" wrote:
1a: You did not specify the version of Capture One you use but you need Capture One 5 for tethering on Win x64.
Paul - is that strictly true? The 64-bit drivers are only supplied with CO5, but I can't see any obvious reason why they shouldn't work with CO4 or even CO3 if they're just a device driver?
Andy
Andy, you are correct that if you have a previous version of CO (CO4, CO3) and are able to install the 64-bits Phase One device driver, it could/should work. Installing CO5 DB for instance could allow you to work with CO4 Pro and provide support on x64 for tethering with Phase One backs. Only an assumption, and probably not supported. And based on various reports, one might need support to get it to work at all. Hence, CO5 seems more as the way to go to me.
The 64-bit drivers supplied with CO5 do work with CO4 as well. I had the same question as well, but they seem to work. First I installed the CO5 trial (with CO4 already set up) and then when the drivers were installed, I then removed the CO5, leaving the drivers installed into the system.
Still, I had to remove 6 GB RAM out of 8 GB to get them working. Here's to hoping that MS will solve the issue as soon as humanly possible.0 -
[quote="NN153202UL" wrote:
Still, I had to remove 6 GB RAM out of 8 GB to get them working. Here's to hoping that MS will solve the issue as soon as humanly possible.
What's interesting is whether or not this is a Microsoft problem at all. The information in Microsoft's KB972038 "Incorrect data received via Isochronous transfer from IEEE 1394 device on a computer with 4GB or more memory" suggests that the problem is with the IEEE 1394 client driver. I take this to mean Phase One's camera driver rather than anything in the OS itself. Would Phase One care to comment?
Andy0 -
The problem exists in the Microsoft driver, however ultimately we were able to reconfigure our driver to overcome such issues. The new driver has been posted to our Knowlegebase today: http://xchange.phaseone.com/content/sup ... nguageid=1 0 -
Brilliant - thanks Jon! 😄
Andy0 -
Hmm, I got no luck with the new drivers. Both CO4 and CO5 trial refuses to work with the back, producing this error:
"Failed to allocate resources. Detail:Failed to setup isochronous buffer via CAPTURE_IMMEDIATE2"
Has anyone else tried the new drivers?0 -
Hi
I am having exactly the same problem with a clean install of CO 5.1 and the 64-bit driver on a new machine running Windows 7 64-bit with 6gb RAM. Tech support suggested a legacy Windows Firewire driver. This connected the camera and immediately gave a 'blue screen' full system crash. The only way to connect the camera (H20) was to remove 4gb of RAM. Tech support then suggested a clean remove and re-install but I cannot see this will achieve anything as it will merely take me back to the day the machine was built. Have you managed to get your system to work?
Regards
Mark Sykes0 -
Hi Mark,
At least when it comes to support cases you case has been an isolated one since we introduced the new 64bit drivers back in December. The supporter you are dealing with currently in your case is the best when it comes to windows troubleshooting so i really suggest testing out what he suggests. You could not be in better hands. If we need to involve a programmer for a special fix we will.0 -
Having the same problem. I dont wait for a sulution anymore 😉
Vista64
48 GB Ram
8 Cores (+8 Virtual ones)0 -
Hi Christian,
You have not replied to your case on the subject since November, long before our fix. All users prior to Mr Sykes to contact us with this issue have been successful thus far. If there are still outstanding issues for some users then we are very keen to get to the bottom of it.0 -
Hi
We have just undertaken a full de-install and re-install of CO5.1 and the 64-bit driver, as per tech support instructions, which basically took the new machine back to it's original state when built. With 2gb. RAM everything works fine. Installing 4gb. or 6gb. we immediately return to the 'isochronos' error so we are back at square one after four weeks. Now awaiting further input from tech support. Very frustrating.
Regards
Mark Sykes0
Post is closed for comments.
Comments
20 comments