RE: filmscanners: OT: Device recognition, Win 98: HERE IS REG INFO FOR PRINTSCAN 35
I thought I'd be of help if anyone wants to test this theory with a Microtek scanner to utilize the PolaColor Insight software intended for Sprintscan scanners. Here is a link to an exported registry key from my Win2k machine: http://members.home.net/dilg/Polaroid35LE.re_ Note the capitalization of the filename and the fact I renamed the extension - @Home is on a UNIX box I assume and is case sensitive, and I renamed the file extension so that someone wouldn't accidentally run the reg file without thinking. Here is the key it will create: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Scanner&Ven_Polaroid&P rod_Polaroid_35/LE&Rev_1.40 Good luck, and thank you everyone for contributing to this list! Jared Dilg -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Greenbank Sent: Tuesday, June 12, 2001 3:59 PM To: [EMAIL PROTECTED] Subject: Re: filmscanners: OT: Device recognition, Win 98 On a PC it may be worth trying regedit to fool the software. It should be noted that regedit can completely screw your machine. Before starting save a copy! The relevant part is "HKEY_LOCAL_MACHINE\Enum\SCSI". If someone supplies you with the relevant information for the scanner your trying to emulate it might work - it depends how the software is coded. Steve - Original Message - From: "Richard N. Moyer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 12, 2001 6:47 PM Subject: Re: filmscanners: OT: Device recognition, Win 98 > For Apple only. This type of situation has been rectified sometimes - > for instance in certain CD machines - by using RESEDIT, and changing > the ID in the driver. Do you know if this is an ID issue or what? > Inquiry commands must include some form of ID - - -? No idea what PC > users can do in a similar way. > > > >The Microtek and Polaroid scanners are almost identical, but > >they return different strings from the scsi inquiry command. > >This keeps the Polaroid scanners from working with the > >Microtek software and vice versa. There's nothing to prevent > >Polaroid and Microtek from making their software run on > >each other's scanners, but they haven't done this. > > > >Regards, > >Ed Hamrick > >
Re: filmscanners: OT: Device recognition, Win 98
> This doesn't always work in all systems. With W98SE here it never does, I > have to restart, although with W95 it was fine. Works evertytime on my Win98SE with Artixscan 4000T. I suspect there are a host of issues that allow this to work or not. Some combinations of hardare and software work others don't, it's a particular problem on PCs. I had not disimilar problems with Via USB - after much work I persuaded it to work with Win 98. On 98SE I abandoned my USB mouse + keyboard they just refused to work reliably. Steve
RE: filmscanners: OT: Device recognition, Win 98
On Mon, 11 Jun 2001 22:44:30 -0500 Jared Dilg ([EMAIL PROTECTED]) wrote: > This reminds me, after reading the first part of this thread, I tried to > power on my SprintScan 35LE and refresh the device list in Device > Manager. > Yes, the SprintScan showed up, but upon launching PolaColor Insight the > software could not detect an active scanner on the system. This doesn't always work in all systems. With W98SE here it never does, I have to restart, although with W95 it was fine. Regards Tony Sleep http://www.halftone.co.uk - Online portfolio & exhibit; + film scanner info & comparisons
Re: filmscanners: OT: Device recognition, Win 98
On a PC it may be worth trying regedit to fool the software. It should be noted that regedit can completely screw your machine. Before starting save a copy! The relevant part is "HKEY_LOCAL_MACHINE\Enum\SCSI". If someone supplies you with the relevant information for the scanner your trying to emulate it might work - it depends how the software is coded. Steve - Original Message - From: "Richard N. Moyer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 12, 2001 6:47 PM Subject: Re: filmscanners: OT: Device recognition, Win 98 > For Apple only. This type of situation has been rectified sometimes - > for instance in certain CD machines - by using RESEDIT, and changing > the ID in the driver. Do you know if this is an ID issue or what? > Inquiry commands must include some form of ID - - -? No idea what PC > users can do in a similar way. > > > >The Microtek and Polaroid scanners are almost identical, but > >they return different strings from the scsi inquiry command. > >This keeps the Polaroid scanners from working with the > >Microtek software and vice versa. There's nothing to prevent > >Polaroid and Microtek from making their software run on > >each other's scanners, but they haven't done this. > > > >Regards, > >Ed Hamrick > >
Re: filmscanners: OT: Device recognition, Win 98
For Apple only. This type of situation has been rectified sometimes - for instance in certain CD machines - by using RESEDIT, and changing the ID in the driver. Do you know if this is an ID issue or what? Inquiry commands must include some form of ID - - -? No idea what PC users can do in a similar way. > >The Microtek and Polaroid scanners are almost identical, but >they return different strings from the scsi inquiry command. >This keeps the Polaroid scanners from working with the >Microtek software and vice versa. There's nothing to prevent >Polaroid and Microtek from making their software run on >each other's scanners, but they haven't done this. > >Regards, >Ed Hamrick
Re: filmscanners: OT: Device recognition, Win 98
In a message dated 6/12/2001 9:56:39 AM EST, [EMAIL PROTECTED] writes: > FWIW, I have a Microtek 35t+ and it won't work with the Polaroid software. > I don't know if this means the Microtek software won't work with a Polaroid > scanner or not but I was told there is some firmware code that identifies > which scanner is which and unless the two match, the software won't work. The Microtek and Polaroid scanners are almost identical, but they return different strings from the scsi inquiry command. This keeps the Polaroid scanners from working with the Microtek software and vice versa. There's nothing to prevent Polaroid and Microtek from making their software run on each other's scanners, but they haven't done this. Regards, Ed Hamrick
RE: filmscanners: OT: Device recognition, Win 98
>With the SprintScan LE, you might try downloading (from >Microtek) their driver for the 35t+ scanner. In fact, you >may be able to get the pre-Insight "legacy" driver from >Polaroid's website. All I know is that the screen captures >for the LE's driver program (from Polaroids' PDF files) were >identical to those from Microtek's ScanWizard driver program >at the time. FWIW, I have a Microtek 35t+ and it won't work with the Polaroid software. I don't know if this means the Microtek software won't work with a Polaroid scanner or not but I was told there is some firmware code that identifies which scanner is which and unless the two match, the software won't work. Of course, there's nothing to prevent you from downloading it and trying it out yourself... Jeff Goggin Scottsdale, AZ
RE: filmscanners: OT: Device recognition, Win 98
At 10:44 PM 6/11/01 -0500, Jared Dilg wrote: >This reminds me, after reading the first part of this thread, I tried to >power on my SprintScan 35LE and refresh the device list in Device Manager. >Yes, the SprintScan showed up, but upon launching PolaColor Insight the >software could not detect an active scanner on the system. Sorry, I am >incredibly new and ignorant to film scanning, but are there other software >packages for gathering images with the SprintScan? (VueScan, right?) There may be one or more versions of SilverFast that work with the SprintScans, and of course there's VueScan. With the SprintScan LE, you might try downloading (from Microtek) their driver for the 35t+ scanner. In fact, you may be able to get the pre-Insight "legacy" driver from Polaroid's website. All I know is that the screen captures for the LE's driver program (from Polaroids' PDF files) were identical to those from Microtek's ScanWizard driver program at the time. On my SprintScan Plus, I use the old (V 2.7) Polaroid TWAIN driver, rather than Insight, and it is still posted on Polaroid's website. The SprintScan Plus does *not* have an equivalent in the Microtek lineup, however. As to the "refresh" trick in Device Manager, I am also confused. I remember a couple of years back (on plain-old Win98) that worked just fine. But it doesn't seem to work on Win98 SE, or else something else in my system has changed. I notice also (somehow) that my scanner entries in Device Manager are a bit messed up -- ie., a couple of the scanners have multiple entries. Not sure how that happened. rafe b.
RE: filmscanners: OT: Device recognition, Win 98
This reminds me, after reading the first part of this thread, I tried to power on my SprintScan 35LE and refresh the device list in Device Manager. Yes, the SprintScan showed up, but upon launching PolaColor Insight the software could not detect an active scanner on the system. Sorry, I am incredibly new and ignorant to film scanning, but are there other software packages for gathering images with the SprintScan? (VueScan, right?) Thanks, Jared Dilg -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Lynn Allen Sent: Monday, June 11, 2001 1:29 PM To: [EMAIL PROTECTED] Subject: filmscanners: OT: Device recognition, Win 98 I just discovered that what I'd said about my computer recognizing SCSI devices (viz my Acer Scanwit) without a warm boot does *not* apply to my USP port and HP 6300C. It *definitely* requires a re-boot to be recognized, if it is off-line at first boot-up. This is not terribly important to the World View Of Things, but I saw so many different opinions and versions of what needed rebooting and what didn't, that I thought I would mention it. "So it goes." :-) Best regards--LRA Get 250 color business cards for FREE! http://businesscards.lycos.com/vp/fastpath/
filmscanners: OT: Device recognition, Win 98
I just discovered that what I'd said about my computer recognizing SCSI devices (viz my Acer Scanwit) without a warm boot does *not* apply to my USP port and HP 6300C. It *definitely* requires a re-boot to be recognized, if it is off-line at first boot-up. This is not terribly important to the World View Of Things, but I saw so many different opinions and versions of what needed rebooting and what didn't, that I thought I would mention it. "So it goes." :-) Best regards--LRA Get 250 color business cards for FREE! http://businesscards.lycos.com/vp/fastpath/
