CompuServe Thread

I posted this message, but perhaps to the wrong address, as I still haven't had any response… So here it is again. ———- I'm not sure who I was writing to at ASDG, but I know how a fairly simple fix for the EPSON Scanner Module and stand-alone software package can be implemented. Add a function to both versions of the scanner modules to check the CPU. If an 68040 with a data cache is found, have the module turn off the data caches just before the scanner is accessed and then turn them back on after the scanner begins to send data. I have done this myself with an ARexx script, but it is very inelegant and is not very clean. This has completely eliminated the E-1 errors… There is something about the way the scanner is being accessed that it has a problem with if the data (copyback) caches are left on. I am currently using an Amiga 4000/040/25mhz with 2m Chip & 8m Fast; as well as an EPSON ES-300C color scanner. Also, I am using v2.15 of the AdPro software and v3.0.4 of your scanner software, with your bundled cable. Hope this helps to finally put this problem to rest. Don Suhr 73117,1337 ———- I certainly do… Don Suhr 73117,1337