On a new XP Pro installed CanoScan N670U with newest downloaded software.
I wanted to see the scanned picture in ACDSee so I directed the scansoftware to ACDSee but I got an error message
saying the ACDAppInfo.dll is missing, with the suggestion of reinstall...

I re-reinstalled ACDsee standard and PowerPack both in 5.0 and 5.01 versions and none contained ACDAppInfo.dll.
I tried to direct to FotoCanvas instead of ACDsee.exe,, nope!

Finally I put on IRFANView and it works, but I'd prefer to edit the scanned pictures right in ACDSee-FotoCanvas.

Can somebody help me with sending me this DLL? No search on the NET gave any result.

TIA
samsamu@bigfoot.com

I found this on Google:

I assume since it's under the Newsgroups: alt.2600.cracks section that the user is using a crack. If this is the case with you, I'm sorry we can't help.

If not, can you give us more information?

i am an ACDSee 5.0 PowerPack user but I don't have ACDAppInfo.dll either. sorry about that.

and just realised you are a newcomer to BetaONE.
Welcome to the board. :)

i hope you have read the rules in BetaONE. http://www.betaone.net/rules.php

We here at BetaONE, don't support or believe in cracks and such. We buy our software so we can guarantee top-notch performance

To get an image from the scanner to AcDC, use the Aquire menu in AcDC & the scanner software will be recognised by AcDC & the image picked up from the scanner & put into AcDC.

Thanks for all replies... in the meantime I got an idea and made a search
on my C: drive and found all the requested files (half dozen) in the
c:\Program Files\Common Files\ACD Systems...
Putting them in the Windows\System32 directory resolved the problem.
It is an interesting question why ACDSEE looks for the files in this system32
directory when itself has put them elswhere in the install process.

samsamu

BTW the crack aspect is not relevant here... I never mentioned crack, hack
or any similar

actually, it might not be acdsee that can't find the dll directly, it could be your scanner drivers, scanner app, or windows' TWAIN drivers and the Windows Image Acquisition service. most programs look for dll's that they need either in the folder they are in, or anything in path (to see, click start, run, type cmd.exe, hit ok, type path, hit enter), which includes system32, so another app, driver, or service might not have been able to find it