Scanner "on" starts LR2.1

  • Thread starter Thread starter billj
  • Start date Start date
Status
Not open for further replies.
B

billj

Guest
Hi - I'm a new forum member who found this forum because of a problem I have been having since installing LR2. Whenever I turn on my scanner (Epson Perfection 487' Photo, USB) LR automatically starts. This didn't happen with LR 1.x. I can't seem to find any way - either in LR preferences, device manager or control panel - to stop this from occurring.

Any ideas? I am using XPSP2.
 
Hi - I'm a new forum member who found this forum because of a problem I have been having since installing LR2. Whenever I turn on my scanner (Epson Perfection 487' Photo, USB) LR automatically starts. This didn't happen with LR 1.x. I can't seem to find any way - either in LR preferences, device manager or control panel - to stop this from occurring.

Any ideas? I am using XPSP2.

Welcome Bill, to help us help you could you please take a moment to fill in your signature with information similar to what I have, in the "userCP' that is found at the top left of the page - thanks.

I'll defer to a Windows person !!
 
Hi Bill, welcome to the forum!

What a bizarre problem! As far as I remember, you want to be turning off AutoPlay or AutoRun, although where you'd find that for a scanner is anyone's guess. Device Properties possibly?
 
Thanks for the welcome, Victoria and Geoff!

I have tried, within Control Panel - Scanners and Cameras - going into the properties of my scanner. Within that there is an "Events" tab which offers three options to occur when starting the scanner - 1) "Start this Program", which offers 3 "Photoshop" versions and 1 "Scanner" option 2) "Prompt for which program to run" and 3) "Take no action".

It would seem that this is indeed the problem area. There is no change in the behavior no matter which of the options I choose. ie: LR fires up every time I turn the scanner on. When it starts, it brings up the message "Warning! No files found to import." in a box on top of the LR window. Not only that, but now it has two instances of the warning! I noticed a very brief window that appears for an instant before the warning window that has something about a scanner, but it is just a flash...too short a duration to read.

Argggh!
 
I had the same thing happen until I unchecked the (show import dialoge when a memory card is detected) option in preferences.
 
Just wanted to post that I have the solution. I was directed to an Adobe Forum thread. Although the exact instructions did not work (they were for LR1.4) I did find the solution for LR2. I'm posting the solution for LR1.4 as well as my workaround:

"Choose Start; Run, and type in msconfig. Click OK.
Choose the Startup tab.
Deselect Adobe Photo Downloader in the startup list.
Restart windows. "

There was no "Adobe Photo Downloader" in my startup list. However, I did look for any startup file(s) loaded by Lightroom and that turned out to be apdproxy.exe. Disabling that on startup stopped LR2.1 from starting up when the scanner is turned on.

Thanks for the help everyone. I hope that maybe this may help someone else in the future!
 
Adobe Photodownloader 3.' and apdproxy.exe are the same programs with different names. Neither Lr1.4.1 nor Lr2.1 install it, so it must have come with Photoshop. Strange though that it would still launch Lr instead of Photoshop.
 
Adobe Photodownloader 3.' and apdproxy.exe are the same programs with different names. Neither Lr1.4.1 nor Lr2.1 install it, so it must have come with Photoshop. Strange though that it would still launch Lr instead of Photoshop.

According to my research, it is installed by LR and PS. I did install LR2 and CSPS3 at the same time, so I guess it could have come from either. However, the entry in my startup was "F:\Lightroom\apdproxy.exe" so to me it is fairly obvious that LR was the "culprit".
 
It's good to see that you have solved your problem, but if you are curious about what happened have a look at your program files for Adobe. In mine apdproxy.exe/Adobe Photodownloader 3.' is an executable file in the Lightroom 1.4 and Photoshop Elements 5 folders, but not in the Photoshop Elements 7 and Lightroom 2 folders. Installing the updates did not uninstall the downloader. My Startup tab in msconfig still has a line for the Lightroom 1.4 version of the downloader unchecked.
 
The autostart mechanisms of LR were changed over time. At some point adproxy.exe was used. In later versions its use was discontinued, and the Windows Autoplay feature was substituted. That said, I don't remember between which versions the change occurred. Since Ken (and me too) finds adproxy in his LR 1.x directory, and not in the 2.x directory, I'm assuming the change occurred around the time of the 2.' public beta.
 
It's good to see that you have solved your problem, but if you are curious about what happened have a look at your program files for Adobe. In mine apdproxy.exe/Adobe Photodownloader 3.' is an executable file in the Lightroom 1.4 and Photoshop Elements 5 folders, but not in the Photoshop Elements 7 and Lightroom 2 folders. Installing the updates did not uninstall the downloader. My Startup tab in msconfig still has a line for the Lightroom 1.4 version of the downloader unchecked.

Obviously, your setup is different than mine. A search of my entire computer for apdproxy.exe yielded precisely ONE instance. That was in my LightRoom 2 folder. My startup tab also shows the line for my LR2 apdproxy.exe file. There is no other place that it could come from. I did install LR2 over my LR1.3 (never updated to 1.4). If the file was left there from 1.3 then it was defaulted to on by the LR2 install, since it was never turned on when I had 1.3 going. There is no apdproxy.exe in any of my PS version installs. I see no point in arguing this point. It is clear to me that it did come from Lightroom. Whether it was from 1.3 or 2 doesn't really matter to me as much as the fact that installing LR2 activated the file by default, with no obvious way to deactivate it. Whether it was by intent or not I have no way of knowing. I do know that it did happen, and it happened through my install of LR2.
 
Status
Not open for further replies.
Back
Top