Ever since upgrading to Silverfast Ai v.6.1 - at least I think that was the version that introduced the "Silverfast Launcher", I have had various problems running Silverfast for both my Epson 1680 Pro and my Nikon 8000ED. These problems are listed in my other posts and I wont bore you with the details. Suffice it to say that "improved" versions of programs are not always better.
Yesterday I serendipitously discovered that as long as I PHYSICALLY shut off all other scanners (I have 3), except the one I wish to use, SilverFast Launcher functions properly.
This did NOT occur before this "Launcher" module came along and somehow the program or module is having trouble identifying and/or initializing the scanner when other scanners are connected. This has given me literally months of headaches; I can now die a fulfilled man!
I pass this on to any others who may be experiencing similar problems and happen to have more than 1 scanner connected to their system.
Something for your team to look into.
HEADACHE SOLVED - Multiple Scanners & Silverfast
- prachun
- SilverFast Beginner
- Posts: 17
- Joined: Sat Apr 27, 2002 1:00 am
- Location: Marietta Ohio
- Contact:
HEADACHE SOLVED - Multiple Scanners & Silverfast
Paul Prachun -- Please feel free to learn from my mistakes -- you won't live long enough to make them all yourself.
Dear Paul
seen from the the SilverFast people's angle, the problem actually is the Nikon drivers which cause the problem, especially with Epson and Minolta scanners.
When the scanners are attached and powered on at system start, the drivers will load and conflict other scanner manufacturers' drivers.
We don't have a solution to this, as we depend on the same manufacturer drivers. For the time being, shutting the scanners not needed off seems to be the only way. As some machines can't be _really_ shut down (even when using a power switch they are in stand by mode), one sometimes needs to disconnect them physically.
The SF_Launcher has its troubles, of course. Windows users should upgrade to version 2.0.6 or higher because in some cases the SF_Launcher 2.0.5 and earlier starts to eat all CPU time and needs to be killed via the Windows task manager.
But apart from that, the SF_Launcher is - from our perspective - unconnected to the Nikon-vs-Epson driver troubles.
Thanks for sharing your insight, though, as we will re-exam this issue.
And please... live long and prosper
Kind regards
Sonny
seen from the the SilverFast people's angle, the problem actually is the Nikon drivers which cause the problem, especially with Epson and Minolta scanners.
When the scanners are attached and powered on at system start, the drivers will load and conflict other scanner manufacturers' drivers.
We don't have a solution to this, as we depend on the same manufacturer drivers. For the time being, shutting the scanners not needed off seems to be the only way. As some machines can't be _really_ shut down (even when using a power switch they are in stand by mode), one sometimes needs to disconnect them physically.
The SF_Launcher has its troubles, of course. Windows users should upgrade to version 2.0.6 or higher because in some cases the SF_Launcher 2.0.5 and earlier starts to eat all CPU time and needs to be killed via the Windows task manager.
But apart from that, the SF_Launcher is - from our perspective - unconnected to the Nikon-vs-Epson driver troubles.
Thanks for sharing your insight, though, as we will re-exam this issue.
And please... live long and prosper
Kind regards
Sonny
Return to “Installation Problems”
Who is online
Users browsing this forum: No registered users and 1 guest
