Sorry for the delay. Work got in the way of email :). Cable is fine. I tried another and same result. Windows (XP and 10) see the scanner, but not plug-n-play.
Sean, MSPaint was greyed out, probably because no twain driver. I'll see if I can find a generic twain driver that might work. Thanks for the help and ideas. Mark On Tue, Jul 18, 2017 at 12:47 PM, Micheal Espinola Jr < [email protected]> wrote: > I'm guessing that's the crux of the issue, since the scanner is TWAIN > compliant and should work with most any scanning software that can see it. > The problem is plug-n-play. > > Mark, have you confirmed that there isn't an issue with the cable? > > -- > Espi > > > On Tue, Jul 18, 2017 at 9:40 AM, Sean Chapman <[email protected]> > wrote: > >> In the mean time if you have to scan something, MS paint will work for >> that as long as the scanner is installed, just go to From scanner or camera. >> >> >> >> *From:* [email protected] [mailto:[email protected] >> orum.com] *On Behalf Of *Micheal Espinola Jr >> *Sent:* Tuesday, July 18, 2017 11:07 AM >> *To:* [email protected] >> *Subject:* Re: [NTSysADM] Looking for driver for... >> >> >> >> Review your contract or purchase agreement with them (if you can find >> it). I'm pretty sure some of their older contracts state that they will >> provide driver updates for the life of the equipment. You might be able to >> use that against them. >> >> >> -- >> Espi >> >> >> >> >> >> On Tue, Jul 18, 2017 at 8:28 AM, Reimer, Mark <[email protected]> >> wrote: >> >> e-imageData ScanPro 300i (fiche scanner). >> >> >> >> The computer that this scanner was hooked to died, and I can't seem to >> find the software CD anywhere :(. >> >> >> >> The latest drivers the company made was XP drivers (which is fine). >> However the company won't send me the drivers. They want me to buy a new >> scanner (read $5000 give or take). >> >> >> >> I looked at the PID entry when it was plugged in, and googled that. I >> tried the drivers that Google suggested (Mustek), but that didn't work. >> Also looked for the drivers on Google, and no luck. >> >> >> >> Does anyone by any chance have (or had) one of these units that I can get >> the drivers for? >> >> >> >> Thanks in advance. >> >> >> >> *Mark Reimer,* A+, MCSA. >> Servers and Network Administrator >> >> *Prairie College (Prairie Bible Institute)* >> Box 4000, Three Hills, AB T0M 2N0 >> [email protected] | www.prairie.edu >> Office: 403-443-5511 ext. 3476 <(403)%20443-5511> | Toll-Free: >> 1-800-661-2425 <(800)%20661-2425> | Fax: 1-403-443-5540 >> <(403)%20443-5540> >> >> *To Know Christ & Make Him Known...* >> >> *Prairie College equips spiritually transformed leaders through >> biblically integrated education to meet the greatest needs of the world.* >> >> *Follow us on:* Facebook <http://www.facebook.com/prairiecolleges> | >> Twitter <http://www.twitter.com/prairiecolleges> | Youtube >> <http://www.youtube.com/prairiecolleges> | Instagram >> <http://www.instagram.com/prairiecolleges> | iTunesU >> <https://itunes.apple.com/ca/institution/prairie-bible-institute/id626857707> >> >> *Information contained in this email message is intended only for the >> individual to whom it is addressed. * >> *If you are not the intended recipient, please destroy this email and >> notify the sender immediately by reply email. Thank you.* >> >> >> >> >> >> >> >> >> >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> The information contained in this communication and all accompanying >> documents from Coilcraft may be confidential and/or legally privileged, and >> is intended only for the use of the recipient(s) named above. If you are >> not the intended recipient you are hereby notified that any review, >> disclosure, copying, distribution or the taking of any action in reliance >> on the contents of this transmitted information is strictly prohibited. If >> you have received this communication in error, please return it to the >> sender immediately and destroy the original message or accompanying >> materials and any copy thereof. If you have any questions concerning this >> message, please contact the sender. >> > >
