Getting your Nikon Coolscan to work on W7 x64  

sygnus21 said:

Then if the FireWire ports work, you really need to look at either the scanner of cable. We (you) now Know the FireWire ports work... your LaCie proves it. So that isn't the issue.

That said, have you tried another cable?

Also, just to double check, since you keep saying the scanner worked someplace else, have you made sure the power cord was properly seated and plugged into a working power outlet? You can check the scanner is getting power by checking the LED light on the front of the scanner.

Yes, power cord was properly seated & plugged into power outlet and green LED on the tront panel lights, I waited about 40s untill the light stoped to blink, than runed VueScan.

I tried also FireWire cable that was supplied with Lacie scanner (both sides have 6PIN) and nothing changed - VueScan do not see the scanner. But this cable is much thiner compared to the one I have got with Ratoc card and the scanner. Hoped to get today a new cable for double checking, but will have it on Friday.

I confirm, I saw the scanner working and scanning under XP 32-bit with Nikon Scan software and the devices (scanner and PC) were connected with Ratoc FireWire card and the cable which both I got with the scanner.

Well at this point in time I'm at a loss because we know the FireWire ports works - Device Manager. and your physical test confirms it. So that leaves the scanner, but you say the scanner works. Well, the leaves the cable, but you say the cable you used is a 6-pin cable and works. With that said, I'm at a loss at the moment.

The only other suggestion I can think of is to try the scanner on a completely different computer and try Vuescan. If that works well...

sygnus21 said:

Well at this point in time I'm at a loss because we know the FireWire ports works - Device Manager. and your physical test confirms it. So that leaves the scanner, but you say the scanner works. Well, the leaves the cable, but you say the cable you used is a 6-pin cable and works. With that said, I'm at a loss at the moment.

The only other suggestion I can think of is to try the scanner on a completely different computer and try Vuescan. If that works well...

I thought the same to check the scanner on different PC. But if that works well... what than can we check again on my PC?

As I said, I'm at a loss because we know the ports are working. And since Vuescan can't see the scanner, that suggests either the scanner or cable.

Since you say you bought the scanner from someone else, are you sure everything was on the up and up? Never know.

Bachus said:

Scanner works for sure, we have checked it in a seller home and it was working on XP 32bit Nicon Scan, so OC "seen" it and the device made scanning. It was connected with Nikon (Ratoc) FireWire card and FireWire cable I got together with LS-8000ED, so they are also good.

This is why I would find another machine and check the scanner again. Can't hurt. I'm sure you know other people who have computers. Maybe they can check. Show them this post.

sygnus21 said:

This is why I would find another machine and check the scanner again. Can't hurt. I'm sure you know other people who have computers. Maybe they can check. Show them this post.

Thanks. I am now arranging such possibility with someone, hope it will give the devinitive answer.

BTW, I have check all informations about controller's driver which my Windows7 64-bit found and automaticly installed. In Driver Details it is shown where the driver is placed and it's in C:\Windows\system32\DRIVERS\1394ohci. The driver version is 6.1.7601.17514 and it's dated form 2006. Is this all ok? I am not experienced in computer system but if Windows put the driver in system32 drivers folder, it seems it's 32-bit controller driver? should not it be 64-bit driver? (in case if "system32" means 32-bit). And it's sounds strange to me that Windows7 64-bit uses diver for controller that was made in 2006 when nobody yet heard about Windows7... unless it found and used last updated version driver which in case of my controllers were only 32-bit... but they supposedly need to be 64-bit. Am I still confusing something?

ohci1394.sys in C:\Windows\System32\drivers version 6.1.7600.16385, 71.1 Kb, Date Modified: 13/07/2009 21:06 - in my computer.
1394bus.sys just above, same version, same date, 66.5 Kb.

Fernando1 said:

ohci1394.sys in C:\Windows\System32\drivers version 6.1.7600.16385, 71.1 Kb, Date Modified: 13/07/2009 21:06 - in my computer.
1394bus.sys just above, same version, same date, 66.5 Kb.

both of my drivers are dated 21/06/2006, are generic install .inf, but based on the version number it seems that mine (6.1.7601.17514) is newer than yours... but it's dated 2006...

Bachus,

I've not taken the time to look into driver versions the way you're doing them, nor do I plan to. Sorry.

I've told you time and time again, and you confirmed it, that your FireWire ports are working, and that there appears to be an issue with either the cable or scanner. I’ve also given you a number of suggestions, some of which you’ve not done. At this point in time I can be of no further help.

If you feel your computer isn't working properly you need to create your own thread in one of the other forums as this is strictly for getting the Nikon Scan software working under Windows 7.

Good luck.

EVENTUALLY by re-reading the instruction time and time again and several fresh starts, got to the finishing line!!!!

Success was really down to ONLY switching on the scanner at the appropriate time, completely disabling ESET during installation and realising that you install the software twice.

Having the PC card as part of the hardware supplied was a real bonus and the fact that we were traversing a path that was assured to lead to a pot of gold.

How you dreamed up this solution is beyond my comprehension but we are certainly grateful that a valued piece of kit has an extended life with its new cell mate of Windows 7 Pro 64 bit.

With grateful thanks.

I'm sorry but I have no idea what you're talking about

But somehow I'm guessing you got it working?