Page 1 of 1

SF 6.0.1r17(Epson) Install kills Kodak RFS-3570+ Software!

PostPosted: Sat Nov 09, 2002 8:52 pm
by Bill Wood
:cry: I used an Epson Expression 636 [with SF_UK-5.2.0r01(Epson) PS Plugin] and a Kodak RFS 3570+ film scanner (Kodak ver 1.4 PS Plugin) on the same Adaptec 2940UW SCSI external port. The Epson 636 was first in line with a SCSI ID 2. The Kodak RFS 3570+ was at the end with an active SCSI termination and an ID of 2. The computer is a Dell Precision 620 Workstation with dual 1GHz Xeon processors and 1 GB of Rambus RAM. The operating system is Windows XP/Pro with all current Microsoft updates.

This configuration has worked well for the last year or so. However, two days ago I upgraded my Epson SF version online and downloaded SFE-60.1r17(Epson.exe. The install went fine and I started using the new SF version on the Epson 636 Expression.

However, the new installation made some sort of change to Windows XP that causes a Blue Screen error when ever I attempt to do a refocus on the RFS 3570+ Ver 1.4 Twain software. The Blue Screen error reports the DRIVER_IRQL_NOT_LESS_OR_EQUAL and causes a computer restart to recover from the failure. It error appears to be related to the SCSI communication and will continue to occur when a refocus is attempted whether or not the offending SFE-6.0.1r17 software is removed or not.

I was able to get back to a stable state by replacing my Windows XP/Pro partition with one cloned by Ghost 7.5 before I installed the SFE-6.0.1r17 software. Both SF-5.2.0r01 and the Kodak RFS 3570+ Ver 1.4 software packages worked with their respective scanners just fine.

Then I went through the process of uninstalling SF-5.2.0r01 and installing SFE-6.0.1r17 again to see if the problem would return. It DID. I went through this process again twice to make sure the conflict only occurred when both SFE-6.0.1r17 and the Kodak RFS 3570+ ver 1.4 software were both installed.

I suspect that both programs use either a same named file or possibly the same temporary memory byte without clearing or reinitializing that location. Please check this out and let me know what may be happening. In the meantime I have gone back to the non-conflicting configuration.

Bill Wood Photography

PostPosted: Tue Dec 10, 2002 6:08 pm
by LSI_Leschke
We found a work-around for this problem by manually installing the Silverfast- plugin.

Work-Around?

PostPosted: Tue Dec 10, 2002 7:27 pm
by Bill Wood
How about providing details on how to "manually" install Silverfast?

Bill

PostPosted: Tue Dec 10, 2002 7:29 pm
by LSI_Leschke
Didn't we solve this problem through personal e-mail ? I though I sent you the plugin and you manually copied it into the correct folder ?

PostPosted: Tue Dec 10, 2002 7:33 pm
by Bill Wood
Yes, you fixed my problem, but what about anyone else who has a similar problem as you reported in a personal message to me? Provide details for them. Hopefully, the fixed version will be available on the regular update section.

Regards

Bill