Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code 20 at installation then nothing... #36

Open
nlgranger opened this issue Feb 17, 2018 · 4 comments
Open

Code 20 at installation then nothing... #36

nlgranger opened this issue Feb 17, 2018 · 4 comments
Assignees
Labels

Comments

@nlgranger
Copy link

nlgranger commented Feb 17, 2018

Thank you for this project that I have used for while.
Currently it does not seem to work on windows 10 64bits. During installation it opens the window to ask for server and port, then windows says something about an error with the driver and a code 20 (or 22?).

I have tried to run winsane-dgb 192.168.1.20 6566 but it returns immediately without output.
FWIW, scanimage -L on linux returns: device 'net:192.168.1.20:snapscan:libusb:004:005' is a AGFA SNAPSCAN flatbed scanner

Any clues?

@mback2k
Copy link
Owner

mback2k commented Feb 19, 2018

I will have to look into this one. I cannot get it to work on Windows 10 x64 anymore either. It seems like Microsoft changed some driver APIs and I will have to figure out what changed.

@mback2k mback2k self-assigned this Feb 19, 2018
@mback2k mback2k added the bug label Feb 19, 2018
@Failure404
Copy link

Any progress on this?
I was happily using Wiasane on my Win10 x64 for a long time, but since Windows 1803 it's game over.
It installs fine, Scanner is detected, but every application tells me Scanner not found.

@orosam
Copy link

orosam commented Jun 18, 2018

I had a Code 22 (Device disabled) issue on Windows 10 1803.
The underlying cause appeared to be that the scanner got installed with the default localhost:6566 address, with no chance to set the correct IP address of saned.

I could work it around with these steps:

  • Go to Device Manager. See that the scanner device under "Imaging devices" is disabled with Code 22.
  • Right-click on the scanner device, and select "Enable device". The disabled icon should disappear.
  • Right-click on the scanner device again, and select "Properties". The device properties dialog will open.
  • Navigate to the Driver tab, and click "Update driver". The update drivers wizard will open.
  • Click "Browse my computer for driver software".
  • Click "Let me pick from a list of available drivers on my computer". A list should appear, containing the Scanner Access Now Easy - WIA Driver item.
  • Select Scanner Access Now Easy - WIA Driver. Click Next.

At this point, installation should begin, and the IP and port config dialog should appear, where the correct IP and port can be set.

@raidenii
Copy link

raidenii commented Oct 6, 2018

I had a Code 22 (Device disabled) issue on Windows 10 1803.
The underlying cause appeared to be that the scanner got installed with the default localhost:6566 address, with no chance to set the correct IP address of saned.

I could work it around with these steps:

* Go to Device Manager. See that the scanner device under "Imaging devices" is disabled with Code 22.

* Right-click on the scanner device, and select "Enable device". The disabled icon should disappear.

* Right-click on the scanner device again, and select "Properties". The device properties dialog will open.

* Navigate to the Driver tab, and click "Update driver". The update drivers wizard will open.

* Click "Browse my computer for driver software".

* Click "Let me pick from a list of available drivers on my computer". A list should appear, containing the `Scanner Access Now Easy - WIA Driver` item.

* Select `Scanner Access Now Easy - WIA Driver`. Click Next.

At this point, installation should begin, and the IP and port config dialog should appear, where the correct IP and port can be set.

Seems that not working for 1809 any more, after those steps the IP is still locked to localhost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants