Terrible news. It seems that the windows scanning solutions leaks handles. I have seen it consume tens of thousands, if not hundreds of thousands of handles. After enough handles are used, Windows crashes 🙁 Rest of the text is kept for posterity.
Recently my father gave me his old multifunction printer. It is a Samsung SCX-3205. It does not have Ethernet port for easy wired connectivity, so I decided to add it as a networked printer via my virtual Windows 7 installation running on my ESXi host. Everything worked fine after installation of the drivers, with one exception, the physical “Scan to”-button. It just didn’t do anything.
After I realized the Scan To button did nothing, I thought that the virtual environment was to blame. I tried to fidlle around in ESXi settings but the button remained mute. Then I hooked up the printer to my desktop machine and started investigating.
I arrived to Samsung support download page at http://www.samsung.com/uk/support/model/SCX-3205/SEE . It was kind of hard to realize what drivers to download, so I downloaded the Universal Print Driver and Universal Scan Driver. Then I took a look at the manual.
Then I installed the actual drivers.
After this I tried to press the “Scan to”-button. Nothing happened. I fiddled around with the installed software. I was able to initiate scan via mouse.
So, now everything else was working but the “Scan to”-button. I called Samsung tech support. They offered firmware upgrade to the printer. I upgraded the firmware, but it did not help. Then I reasoned that I should try the initially distributed drivers because released software is almost always tested extensively. They must have had the button working. So I proceeded to delete all Samsung drivers and software via the Add/Remove Programs functionality in Windows. I downloaded the oldest drivers first from the driver page and started installing them.
It seemed that I just needed to install the oldest drivers first in order to get the Samsung Scan and Fax manager software to installed. It is not bundled with the never drivers! Now I was able to finally scan documents by pressing a button.
Afterwards I updated the drivers to newer version from the support page. Everything is still working correctly.
Moral of the story: 1) Debug installation first with regular hardware (no virtual machines) 2) If unable to get things working, try to use the setup disk which came with the hardware. Or try to find old version of drivers from the net. 3) In case nobody else has written about the issues, do so to spread the knowledge!