Page 1 of 1
Silverfast AI crashes on startup with Epson 4990
PostPosted: Thu Jul 28, 2005 4:17 pm
by rtway
I recently bought an Epson 4990 pro scanner and cannot get Silverfast AI to startup. When using the standalone application or the Photoshop plugin it gets to the point where it initializes the scanner and then the program just closes (also closes Photoshop). Scans are working fine using Epson scan but would like to get Silverfast up and running. A help ticket has been submitted but hoping someone may have a quick fix. Spent an hour with Epson and eventually they said to work it out with Lasersoft. Running Windows XP SP2 and USB 2.0 interface.
Thanks
Rich
PostPosted: Thu Jul 28, 2005 7:31 pm
by LSI_Leschke
I don't have a "quick fix" but maybe a work-around:
Try disconnecting other scanner/printer/fax units, or the webcam (if applicable).
Re: Silverfast AI crashes on startup with Epson 4990
PostPosted: Fri Mar 24, 2006 8:53 am
by balan
rtway wrote:I recently bought an Epson 4990 pro scanner and cannot get Silverfast AI to startup. When using the standalone application or the Photoshop plugin it gets to the point where it initializes the scanner and then the program just closes (also closes Photoshop). Scans are working fine using Epson scan but would like to get Silverfast up and running. A help ticket has been submitted but hoping someone may have a quick fix. Spent an hour with Epson and eventually they said to work it out with Lasersoft. Running Windows XP SP2 and USB 2.0 interface.
Thanks
Rich
Dear Rich,
Have you got a solution to this problem? If so, I am very interested as I have the same problem (with a film scanner).
Best regards
balan
PostPosted: Fri Mar 24, 2006 9:13 am
by balan
Well, sometimes the solution is close. I looked at all items in the forum and found a suggestion from LSI_Noack that you could delete the Prefs folder that Silverfast places in "..Document and Settings\your_name\application data\lasersoft imaging\silverfast" ) on Windows.
I deleted this folder and Voil?, Silverfast starts up wiithout closing down immediately.
/balan
Problem was due to conflict with older USB hub
PostPosted: Sun Mar 26, 2006 1:31 pm
by rtway
Problem appears to have been due to an older USB hub (1.1). Once disconnected it worked fine. (Just use the newer USB 2.0 hub now).