#321 ADF scans create upside down pages

[Andrew Pearmund]

HP 8270 (and others) with ADF creates duplexed pages upside down. The problem has been reported with some Canon and Brother scanners too. Other scanner apps have had to add an option to "flip duplexed pages" to handle this - could this be added to iCopy, or is there any other workaround? Once the pages are combined into a pdf it's very difficult to fix them.

[Matteo Rossi]

Dear Andrew,

thank you for reporting this problem. I guess the solution will be to add an option to flip duplex pages also in iCopy. I will look into it and report back to you as soon as possible.

[Andrew Pearmund]

Thanks. I would be happy to help you test this when it's ready.

[Matteo Rossi]

Dear Andrew,
I'm sorry for the super long delay. I wrote a possible fix for your problem and I would like you to test it for me, as I don't have a duplex adf for my scanner.

I added an option in the Settings dialog called "Flip duplexed pages". You should check it and try with duplex acquisition. Only the even pages should be rotated. It should work with every scan mode. Also, the setting should be preserved when you close iCopy and reopen it.

Please give it a try and let me know. To test it, simply extract the content of the zip file in iCopy folder (default is C:\Program Files (x86)\iCopy). Thank you very much for your help.

[Andrew Pearmund]

I get an unhandled exception when I try to scan. I can cofirm it saves the settings correctly though.

[Andrew Pearmund]

When I try to scan anything, I get an unhandled exception: “Value does fall within the expected range.”
Could it be a dll version thing?
I’ve got the latest public version of iCopy installed, 1.6.3
The version you sent me in iCopy_0b65b.zip claims to be 1.6.4.1

** Exception Text **
System.ArgumentException: Value does not fall within the expected range.
at WIA.CommonDialogClass.ShowTransfer(Item Item, String FormatID, Boolean CancelError)
at iCopy.Scanner.ScanNormal(ScanSettings settings)
at iCopy.Scanner.Scan(ScanSettings options)
at iCopy.appControl.Copy(ScanSettings options, Boolean openAfterAcquisition)
at iCopy.mainFrm.btnCopy_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[Matteo Rossi]

I'm sorry, I think this is a regression coming from other bugfixes. Please try with the attached version. It is not a dll problem I think. It is normal that the version shows 1.6.4.1, because this is the latest development version.

Let me know if now it works. In case you still have this exception, please let me know if it happens also with flatbed scan or just with ADF.