Hi Everyone

I did not know where to place this query so I am choosing the Scripting section.

I am working on packaging InputAccel Cleint 5.3.
We had to do a custom install of InputAccel by selecting only the Scan and Index features for users.
(Its a vendor MSI and I had no issues creating a transform there)

Fujitsu 5750c Scanner driver files are installed along with this app. The drivers are perfectly installed and the scanner works fine.

Now, my issue is that whenever I launch the application shortcut (Scan), instead of detecting the scanner on the machine, it asks the user to select the scanner from a bunch of options (ofcourse only one of them works cos only one scanner is installed). If I choose the right scanner from the list, it works for that batch and when I close the app and again launch the shortcut, it asks me to select the scanner all over again. I have tried finding help online and also used procmon to figure what's causing this.
There is a file "SetScan.ini" which gets created in C:\Windows on XP and %userprofile%\AppData\Local\VirtualStore\Windows which has the entries that come up in the scanner selection screen. Now, when I modify/delete this file from the location, the app keeps creating this file along with another pixcache.ini in the same location every single time.

This could be the basic functionality of the app but if someone knows a little more about this application, please help me out cos the requirement is that I automate this whole scanner selection thing which am now thinking is impossible.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


It could be a rights issue
Try InstallWatch - install it. do the capture, run your program and perform yr actions, then do the snap and see what's getting created modified...
Answered 07/14/2009 by: ditch_nz
Purple Belt

Please log in to comment
you could always try putting placeholders for these files in your package and preemptively setting security on them so your application users can modify them.
Answered 07/14/2009 by: pjgeutjens
Red Belt

Please log in to comment
Thanks both of you for your replies.
The problem was not with my package. It is a vendor MSI and it was happening with the vendor supplied package too.
Well, we got back to the vendor and apparently this was a bug in their SP2 version of the software.
They have provided us with the SP3 software.
Now anyone facing a similar problem like this, can try this. select the scanner the first time and copy the setscan.ini, pixcache.ini and win.ini files created in the "%userprofile%\appdata\local\virtualstore\windows" in Vista and make it available in every user profile who logs in.
And the same files have to be copied into "%userprofile%\appdata\roaming\ISIS Drivers" folder for it to work for a roaming profile.
I have not had a problem with it until now. [8|]
Answered 07/20/2009 by: sirisha.js
Senior Yellow Belt

Please log in to comment