Hi Michael, Nice, looks as if a basic device driver which merely copies the windows-driver is not so very far away. Two quick remarks from scanning your source. It should not be very difficult to implement the polling process with PIE_READ_STATUS. There is a device-ready bit in the returned status which is helpful. Secondly: the PIE_IMAGE_CLOSE command is sent to the scanner after all data processing is done. Sometimes it may take a couple of repeats before the scanner accepts is, but the command also occurs after a (possibly very long) communication break at large dpis. Cyberview takes a long time processing, and then communication only resumes after PIE_IMAGE_CLOSE is sent.
I'll proceed with the settings analysis (auto exposure, auto gamma, noise reduction, ICE, ...). After that, the calibration process may need a closer look. I would be surprised if there would be no way of sending calibration data to the scanner. Do you know how other scanners do this, or how calibration works in general? Finally: it would be nice to have a kind of experimentation backend and frontend, which allows easy modification of bits and bytes without having to recompile before every experiment. I suppose that has been done before in SANE? With respect to getting SANE built: I'll let you know when I'm ready for that, your help is appreciated. I work with Ubuntu 10.04. Yours, Jan
