Mustek 1200 III EP undetectable in any image program

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

In the past, this old scanner has occasionally complained about its
Twain interface after some scanning but would work again after a warm
computer restart. The lid-detect function always worked, though I
couldn't use it.

Now, suddently, using any image program, including the one supplied
with it (iPhoto Plus 4, I get the flag "Flatbed scanner not ready",
and then, in the case of iPhoto Plus 4, I get "Twain error T009; error
opening twain data source T015; unable to find twain source mgr,
twain.dll -- copy twain.dll from source disk to Windows folder T039".
No dialog window now displays when I open the scanner cover. The
illumination lamp is on.

All the Twain and Twunk files are in place. I did copy over the
twain.dll file from the CD supplied with the scanner. No change. I
then uninstalled iPhoto Plus 4 and manually removed all the twain and
twunk folders and files, and then reinstalled iPhoto Plus 4, which
apparently installs whatever software runs the scanner. I have never
found, on my hard drive, whatever the latter is. No change. Since a
Mustek tech-support page says says the peripheral configuration mode
should be set to EPP, I tried that. No change. The scanner has
previously always been used with this mode set to the D850GB
motherboard's default, "Bi-directional".

Mustek also claims that, given such non-detection of its scanner from
an image program, if Windows in Safe Mode does detect the scanner, the
problem is a software conflict. In may case, the problem persisted in
Safe Mode. Actually, I didn't install any new programs between the
time the scanner worked and when it didn't.

I also tried running the copy of iPhoto Plus 4 that I had in the
contents of my previous HD, which I have existing on my present one.
Same symptoms. (That copy of iPhoto was never installed, just copied,
onto my present HD. The same resulted from a backup HD I shoved into
a module for it on my computer, but only set it as a slave. Same
symptoms.

I stronly doubt that the optical lid detector (LED-phototransistor
sensor) has gone bad. Maybe other hardware in the scanner is bad, but
I suspect some silly software problem. Of course, I loosened and
reseated the parallel cable, to no avail. The line-lug-mounted power
supply for the scanner seems to be at its normal temperature.

What could I further check? What files constitute the scanner-driving
software anyhow? How would I get Mustek -- US or Taiwan -- to solve
this problem on this scanner I bought in 1998? ;-) Hmm. It's still
a good scanner. . .once I replace the double-sided sticky tape holding
its glass down -- with metal clips held by screws, so that the copy
would stay evenly spaced from the scanning piece, even with a heavy
book laid on top of it to keep it flat.

Ray

 

[ken]

Archived from groups: alt.comp.periphs.scanner (More info?)

Raymond A. Chamberlin wrote:

> In the past, this old scanner has occasionally complained about its
> Twain interface after some scanning but would work again after a warm
> computer restart. The lid-detect function always worked, though I
> couldn't use it.
>
> Now, suddently, using any image program, including the one supplied
> with it (iPhoto Plus 4, I get the flag "Flatbed scanner not ready",
> and then, in the case of iPhoto Plus 4, I get "Twain error T009; error
> opening twain data source T015; unable to find twain source mgr,
> twain.dll -- copy twain.dll from source disk to Windows folder T039".
> No dialog window now displays when I open the scanner cover. The
> illumination lamp is on.
>
> All the Twain and Twunk files are in place. I did copy over the
> twain.dll file from the CD supplied with the scanner. No change. I
> then uninstalled iPhoto Plus 4 and manually removed all the twain and
> twunk folders and files, and then reinstalled iPhoto Plus 4, which
> apparently installs whatever software runs the scanner. I have never
> found, on my hard drive, whatever the latter is. No change. Since a
> Mustek tech-support page says says the peripheral configuration mode
> should be set to EPP, I tried that. No change. The scanner has
> previously always been used with this mode set to the D850GB
> motherboard's default, "Bi-directional".
>
> Mustek also claims that, given such non-detection of its scanner from
> an image program, if Windows in Safe Mode does detect the scanner, the
> problem is a software conflict. In may case, the problem persisted in
> Safe Mode. Actually, I didn't install any new programs between the
> time the scanner worked and when it didn't.
>
> I also tried running the copy of iPhoto Plus 4 that I had in the
> contents of my previous HD, which I have existing on my present one.
> Same symptoms. (That copy of iPhoto was never installed, just copied,
> onto my present HD. The same resulted from a backup HD I shoved into
> a module for it on my computer, but only set it as a slave. Same
> symptoms.
>
> I stronly doubt that the optical lid detector (LED-phototransistor
> sensor) has gone bad. Maybe other hardware in the scanner is bad, but
> I suspect some silly software problem. Of course, I loosened and
> reseated the parallel cable, to no avail. The line-lug-mounted power
> supply for the scanner seems to be at its normal temperature.
>
> What could I further check? What files constitute the scanner-driving
> software anyhow? How would I get Mustek -- US or Taiwan -- to solve
> this problem on this scanner I bought in 1998? ;-) Hmm. It's still
> a good scanner. . .once I replace the double-sided sticky tape holding
> its glass down -- with metal clips held by screws, so that the copy
> would stay evenly spaced from the scanning piece, even with a heavy
> book laid on top of it to keep it flat.
>
> Ray

It is sort of hard to follow the two prior messages and understand who
has the problem, but perhaps I can help? I have the same scanner and
have installed it on Win 98 and XP. Which OS are you dealing with?

If all the software loads without a problem, there should have been a
test to see if the scanner was detected. I assume you reached that
point and it was NOT detected? Do you know that the parallel port your
scanner is attached to works? You might want to attach your printer
without the scanner to prove in the port.

If you are using the pass through method (where the scanner is the
first device on the port), I would remove the printer after you
establish the port works, and get your scanner working by itself. In my
case, I had so many problems with the pass through method that I
installed a second parallel port in my computer. That solved a lot of
problems. But first just get the scanner to work with a single port and
no printer attached. Make sure your data cable is attached to the
correct connector on the rear of the scanner and to the working parallel
port on your computer. (Recently I took my scanner to a friends house
to establish if her scanner was bad, and upon re-attaching my scanner
hooked the data cable to the wrong connector on the scanner. I
encountered the same type of problem as you have. Duh!!)

Also check that your PS is getting power when you try to run the
scanner. You could test the output with a DVM. The lamp on the scanner
is controlled by the software if I recall correctly, so I don't believe
it will come on unless the scanner is detected via the parallel port.
Detection is also dependent upon the power reaching the scanner so that
it can respond to the software. C:\WINDOWS\TWAIN_32\A4S2_600\WATCH.exe
is the file that should turn on the scanner lamp.

C:\Program Files\iPhoto Plus 4\PROGRAMS\IPE.EXE is the file that start
Iphoto4 software. You could go to the individual files and double click
on them to start the sequence.

Write back after you see if your port is good, the software is present,
the data cable is attached properly, and maybe I can help more.

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

On Mon, 03 Jan 2005 13:42:29 GMT, Ken <user@domain.invalid> wrote:

>Raymond A. Chamberlin wrote:
>
>> In the past, this old scanner has occasionally complained about its
>> Twain interface after some scanning but would work again after a warm
>> computer restart. The lid-detect function always worked, though I
>> couldn't use it.
>>
>> Now, suddently, using any image program, including the one supplied
>> with it (iPhoto Plus 4, I get the flag "Flatbed scanner not ready",
>> and then, in the case of iPhoto Plus 4, I get "Twain error T009; error
>> opening twain data source T015; unable to find twain source mgr,
>> twain.dll -- copy twain.dll from source disk to Windows folder T039".
>> No dialog window now displays when I open the scanner cover. The
>> illumination lamp is on.
>>
>> All the Twain and Twunk files are in place. I did copy over the
>> twain.dll file from the CD supplied with the scanner. No change. I
>> then uninstalled iPhoto Plus 4 and manually removed all the twain and
>> twunk folders and files, and then reinstalled iPhoto Plus 4, which
>> apparently installs whatever software runs the scanner. I have never
>> found, on my hard drive, whatever the latter is. No change. Since a
>> Mustek tech-support page says says the peripheral configuration mode
>> should be set to EPP, I tried that. No change. The scanner has
>> previously always been used with this mode set to the D850GB
>> motherboard's default, "Bi-directional".
>>
>> Mustek also claims that, given such non-detection of its scanner from
>> an image program, if Windows in Safe Mode does detect the scanner, the
>> problem is a software conflict. In may case, the problem persisted in
>> Safe Mode. Actually, I didn't install any new programs between the
>> time the scanner worked and when it didn't.
>>
>> I also tried running the copy of iPhoto Plus 4 that I had in the
>> contents of my previous HD, which I have existing on my present one.
>> Same symptoms. (That copy of iPhoto was never installed, just copied,
>> onto my present HD. The same resulted from a backup HD I shoved into
>> a module for it on my computer, but only set it as a slave. Same
>> symptoms.
>>
>> I stronly doubt that the optical lid detector (LED-phototransistor
>> sensor) has gone bad. Maybe other hardware in the scanner is bad, but
>> I suspect some silly software problem. Of course, I loosened and
>> reseated the parallel cable, to no avail. The line-lug-mounted power
>> supply for the scanner seems to be at its normal temperature.
>>
>> What could I further check? What files constitute the scanner-driving
>> software anyhow? How would I get Mustek -- US or Taiwan -- to solve
>> this problem on this scanner I bought in 1998? ;-) Hmm. It's still
>> a good scanner. . .once I replace the double-sided sticky tape holding
>> its glass down -- with metal clips held by screws, so that the copy
>> would stay evenly spaced from the scanning piece, even with a heavy
>> book laid on top of it to keep it flat.
>>
>> Ray

Please see interleaved below:

> It is sort of hard to follow the two prior messages and understand who
>has the problem, but perhaps I can help? I have the same scanner and
>have installed it on Win 98 and XP. Which OS are you dealing with?

Win98SE

> If all the software loads without a problem, there should have been a
>test to see if the scanner was detected. I assume you reached that
>point and it was NOT detected?

I don't recall its having included that test. I do know that
immediately thereafter, on trying to "Acquire" the scanner, I got the
stated error messages.

>Do you know that the parallel port your
>scanner is attached to works?

It was working with the scanner the last time I used it -- I think the
day before. I did not try to use it with any other peripheral between
times, or even remove either end of its cable to the scanner.

>You might want to attach your printer
>without the scanner to prove in the port.

My printer uses USB. I found out some time ago that my printer (HP
5650) won't work right with a parallel bus chained through my scanner.
I don't think it will work right, in the mode I'm using it, with a
dedicated parallel bus. It's hard to believe that my parallel bus
suddenly quit working, when I didn't touch its connections at all.

> If you are using the pass through method (where the scanner is the
>first device on the port), I would remove the printer after you
>establish the port works, and get your scanner working by itself.

I don't have a pass-through hookup. The scanner is on my only
parallel computer I/O and my printer uses USB only.

>In my
>case, I had so many problems with the pass through method that I
>installed a second parallel port in my computer.

My old HP 932c printer USUALLY worked OK with that hookup, but I had
to be told that the reason I couldn't get my new much-faster printer
to work right, in that configuration, was due to that kluge. Luckily,
I had an extra USB port (but a 7-ft cable just barely makes to the
location of my printer.

>That solved a lot of
>problems. But first just get the scanner to work with a single port and
>no printer attached. Make sure your data cable is attached to the
>correct connector on the rear of the scanner and to the working parallel
>port on your computer.

Yes, I haven't changed either connection since it worked. My computer
has only one parallel I/O connection.

>(Recently I took my scanner to a friends house
>to establish if her scanner was bad, and upon re-attaching my scanner
>hooked the data cable to the wrong connector on the scanner. I
>encountered the same type of problem as you have. Duh!!)

Yeah, well, I didn't touch MINE. It went south by itself. ;-)

> Also check that your PS is getting power when you try to run the
>scanner. You could test the output with a DVM. The lamp on the scanner
>is controlled by the software if I recall correctly, so I don't believe
>it will come on unless the scanner is detected via the parallel port.

No, no, no! The lamp stays on on this model, whenever its plug is
engaged with a hot power strip. Since this lamp stays lit, power is
at least getting to part of the scanner.

>Detection is also dependent upon the power reaching the scanner so that
>it can respond to the software. C:\WINDOWS\TWAIN_32\A4S2_600\WATCH.exe
>is the file that should turn on the scanner lamp.

It can't be for that purpose, because the lamp, as stated above, is
ALWAYS on. Watch.exe is installed at that location [vers. 1.0.0.1,
180K].

>C:\Program Files\iPhoto Plus 4\PROGRAMS\IPE.EXE is the file that start
>Iphoto4 software. You could go to the individual files and double click
>on them to start the sequence.

I have done that with Ipe.exe and it brings up iPhoto 4 fine. I just
did that, then clicked 'Start', in that program's main window, and
then 'Scan'. The source window came up properly as it still has done
starting from the Desktop item. Then, instead of clicking 'Acquire'
in that window, I double-clicked Watch.exe in Windows Explorer.
Absolutely nothing happened; I didn't even get any error flags.

> Write back after you see if your port is good, the software is present,
>the data cable is attached properly, and maybe I can help more.

If YOUR scanner doesn't keep its illumination lamp on at all times
that scanner is plugged into an AC source, you have a different model
than mine, because I was informed by Mustek USA once (when I
complained about the lamp's needless usage [I had to replace it
once.]) that that is how the scanner I have is supposed to work.

If this is a hardware problem on the scanner's circuit board, I
suppose I'm out of luck, unless I run across a junked such board
somewhere. Fat chance. I certainly don't think trouble-shooting at
the board's component level is reasonable. But I think it's a
software problem. (Naturally, I'm a retired hardware type.) I just
wish I understood exactly which software files are involved in
detecting the scanner IN MY EXACT UNIT.

Ray

 

[ken]

Archived from groups: alt.comp.periphs.scanner (More info?)

Raymond A. Chamberlin wrote:
> On Mon, 03 Jan 2005 13:42:29 GMT, Ken <user@domain.invalid> wrote:
>
>
>>Raymond A. Chamberlin wrote:
>>
>>
>>>In the past, this old scanner has occasionally complained about its
>>>Twain interface after some scanning but would work again after a warm
>>>computer restart. The lid-detect function always worked, though I
>>>couldn't use it.
>>>
>>>Now, suddently, using any image program, including the one supplied
>>>with it (iPhoto Plus 4, I get the flag "Flatbed scanner not ready",
>>>and then, in the case of iPhoto Plus 4, I get "Twain error T009; error
>>>opening twain data source T015; unable to find twain source mgr,
>>>twain.dll -- copy twain.dll from source disk to Windows folder T039".
>>>No dialog window now displays when I open the scanner cover. The
>>>illumination lamp is on.
>>>
>>>All the Twain and Twunk files are in place. I did copy over the
>>>twain.dll file from the CD supplied with the scanner. No change. I
>>>then uninstalled iPhoto Plus 4 and manually removed all the twain and
>>>twunk folders and files, and then reinstalled iPhoto Plus 4, which
>>>apparently installs whatever software runs the scanner. I have never
>>>found, on my hard drive, whatever the latter is. No change. Since a
>>>Mustek tech-support page says says the peripheral configuration mode
>>>should be set to EPP, I tried that. No change. The scanner has
>>>previously always been used with this mode set to the D850GB
>>>motherboard's default, "Bi-directional".
>>>
>>>Mustek also claims that, given such non-detection of its scanner from
>>>an image program, if Windows in Safe Mode does detect the scanner, the
>>>problem is a software conflict. In may case, the problem persisted in
>>>Safe Mode. Actually, I didn't install any new programs between the
>>>time the scanner worked and when it didn't.
>>>
>>>I also tried running the copy of iPhoto Plus 4 that I had in the
>>>contents of my previous HD, which I have existing on my present one.
>>>Same symptoms. (That copy of iPhoto was never installed, just copied,
>>>onto my present HD. The same resulted from a backup HD I shoved into
>>>a module for it on my computer, but only set it as a slave. Same
>>>symptoms.
>>>
>>>I stronly doubt that the optical lid detector (LED-phototransistor
>>>sensor) has gone bad. Maybe other hardware in the scanner is bad, but
>>>I suspect some silly software problem. Of course, I loosened and
>>>reseated the parallel cable, to no avail. The line-lug-mounted power
>>>supply for the scanner seems to be at its normal temperature.
>>>
>>>What could I further check? What files constitute the scanner-driving
>>>software anyhow? How would I get Mustek -- US or Taiwan -- to solve
>>>this problem on this scanner I bought in 1998? ;-) Hmm. It's still
>>>a good scanner. . .once I replace the double-sided sticky tape holding
>>>its glass down -- with metal clips held by screws, so that the copy
>>>would stay evenly spaced from the scanning piece, even with a heavy
>>>book laid on top of it to keep it flat.
>>>
>>>Ray
>
>
> Please see interleaved below:
>
>
>> It is sort of hard to follow the two prior messages and understand who
>>has the problem, but perhaps I can help? I have the same scanner and
>>have installed it on Win 98 and XP. Which OS are you dealing with?
>
>
> Win98SE

Ray,

That is the same OS that I use most of the time and am using now.
>
>
>> If all the software loads without a problem, there should have been a
>>test to see if the scanner was detected. I assume you reached that
>>point and it was NOT detected?
>
>
> I don't recall its having included that test. I do know that
> immediately thereafter, on trying to "Acquire" the scanner, I got the
> stated error messages.

It might be that the test occurs after it detects your scanner as being
present? It has been a while since I installed the software, but there
is a test during the installation. I thought it asked you if you wanted
to do such a test? It really is a moot point, since detection would
come first anyway.

>
>
>>Do you know that the parallel port your
>>scanner is attached to works?
>
>
> It was working with the scanner the last time I used it -- I think the
> day before. I did not try to use it with any other peripheral between
> times, or even remove either end of its cable to the scanner.
>
I don't mean to be sarcastic, but often people assume that what worked
yesterday still works today. In trouble shooting you must take nothing
for granted and establish one building block at a time until you reach
only one possibility left. Until it is established that it works on a
printer, it is still a possible cause of your problem.
>
>>You might want to attach your printer
>>without the scanner to prove in the port.
>
>
> My printer uses USB. I found out some time ago that my printer (HP
> 5650) won't work right with a parallel bus chained through my scanner.
> I don't think it will work right, in the mode I'm using it, with a
> dedicated parallel bus. It's hard to believe that my parallel bus
> suddenly quit working, when I didn't touch its connections at all.

So much for the pass through option. It is good to know that the
cables have not been moved however. That doesn't mean they are good,
just not connected improperly.
>
>
>> If you are using the pass through method (where the scanner is the
>>first device on the port), I would remove the printer after you
>>establish the port works, and get your scanner working by itself.
>
>
> I don't have a pass-through hookup. The scanner is on my only
> parallel computer I/O and my printer uses USB only.
>
>
>>In my
>>case, I had so many problems with the pass through method that I
>>installed a second parallel port in my computer.
>
>
> My old HP 932c printer USUALLY worked OK with that hookup, but I had
> to be told that the reason I couldn't get my new much-faster printer
> to work right, in that configuration, was due to that kluge. Luckily,
> I had an extra USB port (but a 7-ft cable just barely makes to the
> location of my printer.
>
>
>>That solved a lot of
>>problems. But first just get the scanner to work with a single port and
>>no printer attached. Make sure your data cable is attached to the
>>correct connector on the rear of the scanner and to the working parallel
>>port on your computer.
>
>
> Yes, I haven't changed either connection since it worked. My computer
> has only one parallel I/O connection.

As suggested above, I would establish the parallel port functioned
properly on some other device. The CMOS settings should of course be
EPP or ECP (bi-directional) and not standard parallel port.
>
>
>>(Recently I took my scanner to a friends house
>>to establish if her scanner was bad, and upon re-attaching my scanner
>>hooked the data cable to the wrong connector on the scanner. I
>>encountered the same type of problem as you have. Duh!!)
>
>
> Yeah, well, I didn't touch MINE. It went south by itself. ;-)
>
>
>> Also check that your PS is getting power when you try to run the
>>scanner. You could test the output with a DVM. The lamp on the scanner
>>is controlled by the software if I recall correctly, so I don't believe
>>it will come on unless the scanner is detected via the parallel port.
>
>
> No, no, no! The lamp stays on on this model, whenever its plug is
> engaged with a hot power strip. Since this lamp stays lit, power is
> at least getting to part of the scanner.

The lamp might come on by default, but it should come on when the
WATCH.exe is executed. When you load the installation software, this
command is installed in your startup list. My guess is the icon for the
scanner is in the bottom right hand corner indicating the scanner scan
software is started. In my computer I stopped the scanner software from
starting and created a batch file to start it only when I want it started.

Seeing the light on would indicate a couple things however: First,
power is getting to the scanner. It might not be the 15 volts that it
is supposed to be, but it PROBABLY is.

Secondly, it does indicate that some of the parallel port works if you
can control it as mentioned below. It might not be working 100%, but
some of it must be working.
>
>
>>Detection is also dependent upon the power reaching the scanner so that
>>it can respond to the software. C:\WINDOWS\TWAIN_32\A4S2_600\WATCH.exe
>>is the file that should turn on the scanner lamp.
>
>
> It can't be for that purpose, because the lamp, as stated above, is
> ALWAYS on. Watch.exe is installed at that location [vers. 1.0.0.1,
> 180K].

If your light is on for the scanner, check to see if the scanner icon
is in the bottom right hand corner of your screen. Right click on it
and choose EXIT, YES. Did the light go out? Go to the WATCH.EXE file
and double click on the file. Did it come on again?

If so, you can control the light through the software.
>
>
>>C:\Program Files\iPhoto Plus 4\PROGRAMS\IPE.EXE is the file that start
>>Iphoto4 software. You could go to the individual files and double click
>>on them to start the sequence.
>
>
> I have done that with Ipe.exe and it brings up iPhoto 4 fine. I just
> did that, then clicked 'Start', in that program's main window, and
> then 'Scan'. The source window came up properly as it still has done
> starting from the Desktop item. Then, instead of clicking 'Acquire'
> in that window, I double-clicked Watch.exe in Windows Explorer.
> Absolutely nothing happened; I didn't even get any error flags.

If the icon for the scanner is not in the bottom right corner, the
WATCH program did not start. If is there, then start IPE.exe and go to
FILE, ACQUIRE, SELECT SOURCE and your scanner should be listed there.
Is it?
>
>
>> Write back after you see if your port is good, the software is present,
>>the data cable is attached properly, and maybe I can help more.
>
>
> If YOUR scanner doesn't keep its illumination lamp on at all times
> that scanner is plugged into an AC source, you have a different model
> than mine, because I was informed by Mustek USA once (when I
> complained about the lamp's needless usage [I had to replace it
> once.]) that that is how the scanner I have is supposed to work.

You are right, the light comes on by default. I used the batch file to
control the scanner and only plug in the power when I am about to use
it. The control of the light with WATCH.exe is valid however. Run the
test above and you should be able to turn it on and off.

>
> If this is a hardware problem on the scanner's circuit board, I
> suppose I'm out of luck, unless I run across a junked such board
> somewhere. Fat chance. I certainly don't think trouble-shooting at
> the board's component level is reasonable. But I think it's a
> software problem. (Naturally, I'm a retired hardware type.) I just
> wish I understood exactly which software files are involved in
> detecting the scanner IN MY EXACT UNIT.
Anything is possible, but I would not arrive at that conclusion yet.

Ken
>
> Ray
>

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

On Tue, 04 Jan 2005 14:42:11 GMT, Ken <user@domain.invalid> wrote:

>Raymond A. Chamberlin wrote:
>> On Mon, 03 Jan 2005 13:42:29 GMT, Ken <user@domain.invalid> wrote:
>>
>>
>>>Raymond A. Chamberlin wrote:
>>>
>>>
>>>>In the past, this old scanner has occasionally complained about its
>>>>Twain interface after some scanning but would work again after a warm
>>>>computer restart. The lid-detect function always worked, though I
>>>>couldn't use it.
>>>>
>>>>Now, suddently, using any image program, including the one supplied
>>>>with it (iPhoto Plus 4, I get the flag "Flatbed scanner not ready",
>>>>and then, in the case of iPhoto Plus 4, I get "Twain error T009; error
>>>>opening twain data source T015; unable to find twain source mgr,
>>>>twain.dll -- copy twain.dll from source disk to Windows folder T039".
>>>>No dialog window now displays when I open the scanner cover. The
>>>>illumination lamp is on.
>>>>
>>>>All the Twain and Twunk files are in place. I did copy over the
>>>>twain.dll file from the CD supplied with the scanner. No change. I
>>>>then uninstalled iPhoto Plus 4 and manually removed all the twain and
>>>>twunk folders and files, and then reinstalled iPhoto Plus 4, which
>>>>apparently installs whatever software runs the scanner. I have never
>>>>found, on my hard drive, whatever the latter is. No change. Since a
>>>>Mustek tech-support page says says the peripheral configuration mode
>>>>should be set to EPP, I tried that. No change. The scanner has
>>>>previously always been used with this mode set to the D850GB
>>>>motherboard's default, "Bi-directional".
>>>>
>>>>Mustek also claims that, given such non-detection of its scanner from
>>>>an image program, if Windows in Safe Mode does detect the scanner, the
>>>>problem is a software conflict. In may case, the problem persisted in
>>>>Safe Mode. Actually, I didn't install any new programs between the
>>>>time the scanner worked and when it didn't.
>>>>
>>>>I also tried running the copy of iPhoto Plus 4 that I had in the
>>>>contents of my previous HD, which I have existing on my present one.
>>>>Same symptoms. (That copy of iPhoto was never installed, just copied,
>>>>onto my present HD. The same resulted from a backup HD I shoved into
>>>>a module for it on my computer, but only set it as a slave. Same
>>>>symptoms.
>>>>
>>>>I stronly doubt that the optical lid detector (LED-phototransistor
>>>>sensor) has gone bad. Maybe other hardware in the scanner is bad, but
>>>>I suspect some silly software problem. Of course, I loosened and
>>>>reseated the parallel cable, to no avail. The line-lug-mounted power
>>>>supply for the scanner seems to be at its normal temperature.
>>>>
>>>>What could I further check? What files constitute the scanner-driving
>>>>software anyhow? How would I get Mustek -- US or Taiwan -- to solve
>>>>this problem on this scanner I bought in 1998? ;-) Hmm. It's still
>>>>a good scanner. . .once I replace the double-sided sticky tape holding
>>>>its glass down -- with metal clips held by screws, so that the copy
>>>>would stay evenly spaced from the scanning piece, even with a heavy
>>>>book laid on top of it to keep it flat.
>>>>
>>>>Ray
>>
>>
>> Please see interleaved below:
>>
>>
>>> It is sort of hard to follow the two prior messages and understand who
>>>has the problem, but perhaps I can help? I have the same scanner and
>>>have installed it on Win 98 and XP. Which OS are you dealing with?
>>
>>
>> Win98SE
>
>Ray,
>
> That is the same OS that I use most of the time and am using now.
>>
>>
>>> If all the software loads without a problem, there should have been a
>>>test to see if the scanner was detected. I assume you reached that
>>>point and it was NOT detected?
>>
>>
>> I don't recall its having included that test. I do know that
>> immediately thereafter, on trying to "Acquire" the scanner, I got the
>> stated error messages.
>
> It might be that the test occurs after it detects your scanner as being
>present? It has been a while since I installed the software, but there
>is a test during the installation. I thought it asked you if you wanted
>to do such a test? It really is a moot point, since detection would
>come first anyway.
>
>>
>>
>>>Do you know that the parallel port your
>>>scanner is attached to works?
>>
>>
>> It was working with the scanner the last time I used it -- I think the
>> day before. I did not try to use it with any other peripheral between
>> times, or even remove either end of its cable to the scanner.
>>
> I don't mean to be sarcastic, but often people assume that what worked
>yesterday still works today. In trouble shooting you must take nothing
>for granted and establish one building block at a time until you reach
>only one possibility left. Until it is established that it works on a
>printer, it is still a possible cause of your problem.

True, but I just think the probability of a flipped software bit
somewhere, or a dead electrical component in the scanner, is much more
probably the problem than this is.

>>
>>>You might want to attach your printer
>>>without the scanner to prove in the port.
>>
>>
>> My printer uses USB. I found out some time ago that my printer (HP
>> 5650) won't work right with a parallel bus chained through my scanner.
>> I don't think it will work right, in the mode I'm using it, with a
>> dedicated parallel bus. It's hard to believe that my parallel bus
>> suddenly quit working, when I didn't touch its connections at all.
>
> So much for the pass through option. It is good to know that the
>cables have not been moved however. That doesn't mean they are good,
>just not connected improperly.
>>
>>
>>> If you are using the pass through method (where the scanner is the
>>>first device on the port), I would remove the printer after you
>>>establish the port works, and get your scanner working by itself.
>>
>>
>> I don't have a pass-through hookup. The scanner is on my only
>> parallel computer I/O and my printer uses USB only.
>>
>>
>>>In my
>>>case, I had so many problems with the pass through method that I
>>>installed a second parallel port in my computer.
>>
>>
>> My old HP 932c printer USUALLY worked OK with that hookup, but I had
>> to be told that the reason I couldn't get my new much-faster printer
>> to work right, in that configuration, was due to that kluge. Luckily,
>> I had an extra USB port (but a 7-ft cable just barely makes to the
>> location of my printer.
>>
>>
>>>That solved a lot of
>>>problems. But first just get the scanner to work with a single port and
>>>no printer attached. Make sure your data cable is attached to the
>>>correct connector on the rear of the scanner and to the working parallel
>>>port on your computer.
>>
>>
>> Yes, I haven't changed either connection since it worked. My computer
>> has only one parallel I/O connection.
>
> As suggested above, I would establish the parallel port functioned
>properly on some other device.

I have no device that can use a parallel bus, other than my present
and past printers. I'd very much like not to disturb my present
printer USB connection and its USB driver, in order to run it on the
parallel-I/O bus; because my memory for tedious stuff is presently not
all that good and I get fed up with fussing with computer problems all
the time.

>The CMOS settings should of course be
>EPP or ECP (bi-directional) and not standard parallel port.

According to my BIOS Setup instructions, there is the choice of:

1. Output Only
2. Bi-directional (default)
3. EPP
4. ECP.

I think that matches what I've seen when accessing this setup. I have
always had my machine in its default mode, and my scanner has always
before worked fine in that mode. (Well, sometimes TWAIN screwed up
and I had to warm-start my computer.) I tried EPP, after the current
problem occurred, but that did not correct the problem, so I set my
BIOS back to the default.

>>
>>
>>>(Recently I took my scanner to a friends house
>>>to establish if her scanner was bad, and upon re-attaching my scanner
>>>hooked the data cable to the wrong connector on the scanner. I
>>>encountered the same type of problem as you have. Duh!!)
>>
>>
>> Yeah, well, I didn't touch MINE. It went south by itself. ;-)
>>
>>
>>> Also check that your PS is getting power when you try to run the
>>>scanner. You could test the output with a DVM. The lamp on the scanner
>>>is controlled by the software if I recall correctly, so I don't believe
>>>it will come on unless the scanner is detected via the parallel port.
>>
>>
>> No, no, no! The lamp stays on on this model, whenever its plug is
>> engaged with a hot power strip. Since this lamp stays lit, power is
>> at least getting to part of the scanner.
>
> The lamp might come on by default,

I'm not sure what you mean by "default" here, but the bottom line on
the lamp is that whenever there is AC power into the power supply at
the scanner's plug, and the scanner power cable is connected to the
scanner, that lamp is ON, perior. It's always been that way, and
Mustek said it's supposed to be that way.

>but it should come on when the
>WATCH.exe is executed. When you load the installation software, this
>command is installed in your startup list.

Yes, it's there.

>My guess is the icon for the
>scanner is in the bottom right hand corner

Yes, it's there.

>indicating the scanner scan
>software is started.

Whatever, but I get the two mentioned flags in sequence.

>In my computer I stopped the scanner software from
>starting and created a batch file to start it only when I want it started.
>
> Seeing the light on would indicate a couple things however: >First,
>power is getting to the scanner. It might not be the 15 volts that it
>is supposed to be, but it PROBABLY is.

That's just for the lamp, right? The lamp is at its normal
brightness. I might be able to find a test point for the power bus
for the electronic circuitry, but I don't know what voltage that's
supposed to be and would hope a problem showing up there would be less
likely than a software problem.

> Secondly, it does indicate that some of the parallel port works if you
>can control it as mentioned below. It might not be working 100%, but
>some of it must be working.
>>
>>
>>>Detection is also dependent upon the power reaching the scanner so that
>>>it can respond to the software. C:\WINDOWS\TWAIN_32\A4S2_600\WATCH.exe
>>>is the file that should turn on the scanner lamp.
>>
>>
>> It can't be for that purpose, because the lamp, as stated above, is
>> ALWAYS on. Watch.exe is installed at that location [vers. 1.0.0.1,
>> 180K].
>
> If your light is on for the scanner, check to see if the scanner icon
>is in the bottom right hand corner of your screen.

It's there.

>Right click on it
>and choose EXIT, YES. Did the light go out?

No.

>Go to the WATCH.EXE file
>and double click on the file. Did it come on again?

It stayed on.
> If so, you can control the light through the software.

So, obviously, I CAN'T do that.

>>>C:\Program Files\iPhoto Plus 4\PROGRAMS\IPE.EXE is the file that start
>>>Iphoto4 software. You could go to the individual files and double click
>>>on them to start the sequence.
>>
>>
>> I have done that with Ipe.exe and it brings up iPhoto 4 fine. I just
>> did that, then clicked 'Start', in that program's main window, and
>> then 'Scan'. The source window came up properly as it still has done
>> starting from the Desktop item. Then, instead of clicking 'Acquire'
>> in that window, I double-clicked Watch.exe in Windows Explorer.
>> Absolutely nothing happened; I didn't even get any error flags.
>
> If the icon for the scanner is not in the bottom right corner, >the
>WATCH program did not start. If is there, then start IPE.exe and go to
>FILE, ACQUIRE, SELECT SOURCE and your scanner should be listed there.
>Is it?

Yes.

>>> Write back after you see if your port is good, the software is present,
>>>the data cable is attached properly, and maybe I can help more.
>>
>>
>> If YOUR scanner doesn't keep its illumination lamp on at all times
>> that scanner is plugged into an AC source, you have a different model
>> than mine, because I was informed by Mustek USA once (when I
>> complained about the lamp's needless usage [I had to replace it
>> once.]) that that is how the scanner I have is supposed to work.
>
> You are right, the light comes on by default. I used the batch file to
>control the scanner and only plug in the power when I am about to use
>it. The control of the light with WATCH.exe is valid however. Run the
>test above and you should be able to turn it on and off.

Well, I can't turn it off. See above.

There is the file: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini that says:

--------------
[Watch]
LampStatus=1
GreenTime=15
ActiveTime=7352272

[CaseInfo]
NewSetting=0
--------------

Is that a correct setup? If I set 'LamStatus' to '0' and save that,
the lamp still stays on. I have no idea what the other three settings
relate to.

>> If this is a hardware problem on the scanner's circuit board, I
>> suppose I'm out of luck, unless I run across a junked such board
>> somewhere. Fat chance. I certainly don't think trouble-shooting at
>> the board's component level is reasonable. But I think it's a
>> software problem. (Naturally, I'm a retired hardware type.) I just
>> wish I understood exactly which software files are involved in
>> detecting the scanner IN MY EXACT UNIT.
> Anything is possible, but I would not arrive at that conclusion yet.

The problem is probably due to the tsunami. Sick joke, here in CA.US.

Ray

>Ken
>>
>> Ray
>>

 

[ken]

Archived from groups: alt.comp.periphs.scanner (More info?)

Ray,

I did a lot of clipping of old text.

Raymond A. Chamberlin wrote:
>
>>
>>Ray,
>>
>> That is the same OS that I use most of the time and am using now.
>>
>>>

>>
>> It might be that the test occurs after it detects your scanner as being
>>present? It has been a while since I installed the software, but there
>>is a test during the installation. I thought it asked you if you wanted
>>to do such a test? It really is a moot point, since detection would
>>come first anyway.
>>
>>
>>>
>>>>Do you know that the parallel port your
>>>>scanner is attached to works?
>>>
>>>

>>>
>>
>> I don't mean to be sarcastic, but often people assume that what worked
>>yesterday still works today. In trouble shooting you must take nothing
>>for granted and establish one building block at a time until you reach
>>only one possibility left. Until it is established that it works on a
>>printer, it is still a possible cause of your problem.
>
>
> True, but I just think the probability of a flipped software bit
> somewhere, or a dead electrical component in the scanner, is much more
> probably the problem than this is.

You are probably right, but until you establish for sure that the
parallel port works, it remains a POSSIBLE cause of your problem.
>
>
>>>>You might want to attach your printer
>>>>without the scanner to prove in the port.
>>>
>>>

>>
>> So much for the pass through option. It is good to know that the
>>cables have not been moved however. That doesn't mean they are good,
>>just not connected improperly.
>>


>>
>> As suggested above, I would establish the parallel port functioned
>>properly on some other device.
>
>
> I have no device that can use a parallel bus, other than my present
> and past printers. I'd very much like not to disturb my present
> printer USB connection and its USB driver, in order to run it on the
> parallel-I/O bus; because my memory for tedious stuff is presently not
> all that good and I get fed up with fussing with computer problems all
> the time.
I understand your reluctance, but unless you run a test on the port you
can't know for sure.
>
>
>>The CMOS settings should of course be
>>EPP or ECP (bi-directional) and not standard parallel port.
>
>
> According to my BIOS Setup instructions, there is the choice of:
>
> 1. Output Only
> 2. Bi-directional (default)
> 3. EPP
> 4. ECP.
>
> I think that matches what I've seen when accessing this setup. I have
> always had my machine in its default mode, and my scanner has always
> before worked fine in that mode. (Well, sometimes TWAIN screwed up
> and I had to warm-start my computer.) I tried EPP, after the current
> problem occurred, but that did not correct the problem, so I set my
> BIOS back to the default.
>
>
If your CMOS setting is set for default, it should be fine.
>>>

>>
>> The lamp might come on by default,
>
>
> I'm not sure what you mean by "default" here, but the bottom line on
> the lamp is that whenever there is AC power into the power supply at
> the scanner's plug, and the scanner power cable is connected to the
> scanner, that lamp is ON, perior. It's always been that way, and
> Mustek said it's supposed to be that way.

What I mean is even if NO software was loaded the lamp would come on.
Once the software is loaded for the control of the lamp, it should turn
off and on the lamp if you follow the procedure I described using WATCH.EXE.
>
>
>>but it should come on when the
>>WATCH.exe is executed. When you load the installation software, this
>>command is installed in your startup list.
>
>
> Yes, it's there.
>
>
>>My guess is the icon for the
>>scanner is in the bottom right hand corner
>
>
> Yes, it's there.
>
>
>>indicating the scanner scan
>>software is started.
>
>
> Whatever, but I get the two mentioned flags in sequence.

The flags simply are stating that it did NOT see the scanner at the end
of the cable attached to the parallel port. This could be due to
several reasons, but one of them (power) is not likely since you see the
lamp lit. That would indicate power is reaching the scanner.

Other reasons could be corrupted software, bad parallel port or cable
from the port, or defective logic in the scanner.
>
>
>>In my computer I stopped the scanner software from
>>starting and created a batch file to start it only when I want it started.
>>
>> Seeing the light on would indicate a couple things however: >First,
>>power is getting to the scanner. It might not be the 15 volts that it
>>is supposed to be, but it PROBABLY is.
>
>
> That's just for the lamp, right?

The power to the scanner is used for both the logic and the lamp.
There is a regulator in the scanner (5 volt I think) that takes the 15
volts and converts it for the logic. The 15 volt input also is used for
the lamp through an oscillator that provides a higher voltage for the
lamp. Even it goes through a regulator, but I think it is a 12 volt one?

The lamp is at its normal
> brightness.


I would assume that your input voltage is good, since if it were low
the lamp would probably not light. This does not mean everything is
working on the scanner, but that the input is probably good.

I might be able to find a test point for the power bus
> for the electronic circuitry, but I don't know what voltage that's
> supposed to be and would hope a problem showing up there would be less
> likely than a software problem.

If I were to guess, (and I don't care much for guessing) that is what I
would guess. For what it is worth, you could open up the scanner and
see if you can reach the two regulators. A simple DVM should allow you
to measure their output as they are both three terminal through-hole
components if my memory serves me. I agree however, that you are more
likely to find software or the port to be the problem.
>
>
>> Secondly, it does indicate that some of the parallel port works if you
>>can control it as mentioned below. It might not be working 100%, but
>>some of it must be working.
>>

>> If your light is on for the scanner, check to see if the scanner icon
>>is in the bottom right hand corner of your screen.
>
>
> It's there.

Now this would seem to indicate that the software loaded properly and
that all the files necessary were OK.
>
>
>>Right click on it
>>and choose EXIT, YES. Did the light go out?
>
>
> No.

This is probably due to the fact it cannot see the scanner. It should
have gone out if everything was working.

>
>
>>Go to the WATCH.EXE file
>>and double click on the file. Did it come on again?
>
>
> It stayed on.
>
>> If so, you can control the light through the software.
>
>
> So, obviously, I CAN'T do that.

Since you do not want to test the parallel port (and I understand why),
removing ALL the software and reloading it is about all you can do.
Remember to delete the directories created by the current installation
so that no file such as the initialization files remain.
>
>

>>
>> If the icon for the scanner is not in the bottom right corner, >the
>>WATCH program did not start. If is there, then start IPE.exe and go to
>>FILE, ACQUIRE, SELECT SOURCE and your scanner should be listed there.
>>Is it?
>
>
> Yes.

This is a little surprising in that I would have thought there would
have been no scanner listed there. Who knows, it might be placed there
even if it was not detected?

>
>


>>
>> You are right, the light comes on by default. I used the batch file to
>>control the scanner and only plug in the power when I am about to use
>>it. The control of the light with WATCH.exe is valid however. Run the
>>test above and you should be able to turn it on and off.
>
>
> Well, I can't turn it off. See above.
>
> There is the file: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini that says:
>
> --------------
> [Watch]
> LampStatus=1
> GreenTime=15
> ActiveTime=7352272
>
> [CaseInfo]
> NewSetting=0
> --------------

That portion of my file reads:

[Watch]
Model=A4S2600_Watch
LampStatus=0
ActiveTime=4923599
GreenTime=20
CoverDriven=1
Timer3=500
ShowStartup=1
HasIcon=1
HasCoverDriven=1
HasStartup=1
HasMustUI=1

[CaseInfo]
SettingSectionName=1200 III EP
DSSectionName=A4S2INFO_600
NewSetting=1
UsePrivateSettingFile=1

>
> Is that a correct setup? If I set 'LamStatus' to '0' and save that,
> the lamp still stays on. I have no idea what the other three settings
> relate to.

That does not appear to be a complete setting as compared to mine.
>
>
Listed below is another significant portion of that file. Notice the
LPT1 setting. My guess you have no such setting?

[A4S2INFO_600]
Language=English
DSLanguage=English
Brand=Mustek
DSName=1200 III EP
UITitle="Mustek 1200 III EP "
ScanSetting=NMLSPD
Version=V1.0
DriverVer=2.02
F/WVersion=None
Interface=EPP/LPT1
TestMode=0
MemBufSize=256
PreScanDpi=36
PreScanWidth=306
PreScanHeight=414
TAPreScanWidth=216
TAPreScanHeight=252
PreScanFile=MSTC0000.BMP
TAPreScanFile=MSTC0001.BMP
X_OptiMaxRes=600
Y_OptiMaxRes=1200
WtimeTick=60
Bbricon=0
BcolorMatch=0
CMTable=A32PCM.INI
SupportResCount=13
SupportRes=72 100 150 200 300 400 600 900 1200 2400 4800 7200 9600
SupportCustomRes=0
CustomRes=72 9600
ResetRes=300
ResetResIndex=4
TextMaxRes=600
TextMaxResIndex=6
SlideInstall=1
MaxBufSize=672768
>>
>> Anything is possible, but I would not arrive at that conclusion yet.
>
>
> The problem is probably due to the tsunami. Sick joke, here in CA.US.
>
> Ray
>
>
>>Ken
>>

When I was working as a technician years ago, we used to say we were
about to call in an Indian to dance with feathers and beads when we
could not figure out the solution. Needless to say we did not do that,
but it is a little frustrating to have tried many things and still not
have succeeded. Rest assured, that the answer is there. You just need
to ask the correct question after having eliminated other potential
problems. It is NOT magic!! Look at it as a challenge.

Ken

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

On Wed, 05 Jan 2005 13:53:26 GMT, Ken <user@domain.invalid> wrote:

> I did a lot of clipping of old text.
>
>Raymond A. Chamberlin wrote:
>>
>>>
>>>Ray,
>>>
>>> That is the same OS that I use most of the time and am using now.
>>>
>>>>
>
>>>
>>> It might be that the test occurs after it detects your scanner as being
>>>present? It has been a while since I installed the software, but there
>>>is a test during the installation. I thought it asked you if you wanted
>>>to do such a test? It really is a moot point, since detection would
>>>come first anyway.
>>>
>>>
>>>>
>>>>>Do you know that the parallel port your
>>>>>scanner is attached to works?
>>>>
>>>>
>
>>>>
>>>
>>> I don't mean to be sarcastic, but often people assume that what worked
>>>yesterday still works today. In trouble shooting you must take nothing
>>>for granted and establish one building block at a time until you reach
>>>only one possibility left. Until it is established that it works on a
>>>printer, it is still a possible cause of your problem.
>>
>>
>> True, but I just think the probability of a flipped software bit
>> somewhere, or a dead electrical component in the scanner, is much more
>> probably the problem than this is.
>
> You are probably right, but until you establish for sure that the
>parallel port works, it remains a POSSIBLE cause of your problem.
>>
>>
>>>>>You might want to attach your printer
>>>>>without the scanner to prove in the port.
>>>>
>>>>
>
>>>
>>> So much for the pass through option. It is good to know that the
>>>cables have not been moved however. That doesn't mean they are good,
>>>just not connected improperly.
>>>
>
>
>>>
>>> As suggested above, I would establish the parallel port functioned
>>>properly on some other device.
>>
>>
>> I have no device that can use a parallel bus, other than my present
>> and past printers. I'd very much like not to disturb my present
>> printer USB connection and its USB driver, in order to run it on the
>> parallel-I/O bus; because my memory for tedious stuff is presently not
>> all that good and I get fed up with fussing with computer problems all
>> the time.
> I understand your reluctance, but unless you run a test on the port you
>can't know for sure.
>>
>>
>>>The CMOS settings should of course be
>>>EPP or ECP (bi-directional) and not standard parallel port.
>>
>>
>> According to my BIOS Setup instructions, there is the choice of:
>>
>> 1. Output Only
>> 2. Bi-directional (default)
>> 3. EPP
>> 4. ECP.
>>
>> I think that matches what I've seen when accessing this setup. I have
>> always had my machine in its default mode, and my scanner has always
>> before worked fine in that mode. (Well, sometimes TWAIN screwed up
>> and I had to warm-start my computer.) I tried EPP, after the current
>> problem occurred, but that did not correct the problem, so I set my
>> BIOS back to the default.
>>
>>
> If your CMOS setting is set for default, it should be fine.
>>>>
>
>>>
>>> The lamp might come on by default,
>>
>>
>> I'm not sure what you mean by "default" here, but the bottom line on
>> the lamp is that whenever there is AC power into the power supply at
>> the scanner's plug, and the scanner power cable is connected to the
>> scanner, that lamp is ON, perior. It's always been that way, and
>> Mustek said it's supposed to be that way.
>
> What I mean is even if NO software was loaded the lamp would come on.
>Once the software is loaded for the control of the lamp, it should turn
>off and on the lamp if you follow the procedure I described using WATCH.EXE.

Well, in its present condition, the lamp stays on no matter what.
When the scanner was working right, the light was always ON as long as
power was applied to the scanner. However, I never tried, at that
time, to see what would happen if I double-clicked Watch.exe.

>>>but it should come on when the
>>>WATCH.exe is executed. When you load the installation software, this
>>>command is installed in your startup list.
>>
>>
>> Yes, it's there.
>>
>>
>>>My guess is the icon for the
>>>scanner is in the bottom right hand corner
>>
>>
>> Yes, it's there.
>>
>>
>>>indicating the scanner scan
>>>software is started.
>>
>>
>> Whatever, but I get the two mentioned flags in sequence.
>
> The flags simply are stating that it did NOT see the scanner at the end
>of the cable attached to the parallel port. This could be due to
>several reasons, but one of them (power) is not likely since you see the
>lamp lit. That would indicate power is reaching the scanner.

The power input at the scanner's main board measures 15 v.

> Other reasons could be corrupted software, bad parallel port or cable
>from the port, or defective logic in the scanner.
>>
>>
>>>In my computer I stopped the scanner software from
>>>starting and created a batch file to start it only when I want it started.
>>>
>>> Seeing the light on would indicate a couple things however: >First,
>>>power is getting to the scanner. It might not be the 15 volts that it
>>>is supposed to be, but it PROBABLY is.
>>
>>
>> That's just for the lamp, right?
>
> The power to the scanner is used for both the logic and the lamp.
>There is a regulator in the scanner (5 volt I think) that takes the 15
>volts and converts it for the logic. The 15 volt input also is used for
>the lamp through an oscillator that provides a higher voltage for the
>lamp. Even it goes through a regulator, but I think it is a 12 volt one?

I located two components on the main board that appeared to be power
regulators. I don't know their pinouts, but the only pins that
measured significant voltages other than 15 v showed 3 and 12 v,
respectively.

>> The lamp is at its normal
>> brightness.
>
>
> I would assume that your input voltage is good, since if it were low
>the lamp would probably not light. This does not mean everything is
>working on the scanner, but that the input is probably good.

See above.

>> I might be able to find a test point for the power bus
>> for the electronic circuitry, but I don't know what voltage that's
>> supposed to be and would hope a problem showing up there would be less
>> likely than a software problem.
>
> If I were to guess, (and I don't care much for guessing) that is what I
>would guess. For what it is worth, you could open up the scanner and
>see if you can reach the two regulators. A simple DVM should allow you
>to measure their output as they are both three terminal through-hole
>components if my memory serves me.

See above.

>I agree however, that you are more
>likely to find software or the port to be the problem.
>>
>>
>>> Secondly, it does indicate that some of the parallel port works >>>if you
>>>can control it as mentioned below. It might not be working 100%, but
>>>some of it must be working.
>>>
>
>>> If your light is on for the scanner, check to see if the scanner >>>icon
>>>is in the bottom right hand corner of your screen.
>>
>>
>> It's there.
>
> Now this would seem to indicate that the software loaded properly
> and that all the files necessary were OK.

How would that assure that ALL the files were loaded properly?

>>
>>
>>>Right click on it
>>>and choose EXIT, YES. Did the light go out?
>>
>>
>> No.
>
> This is probably due to the fact it cannot see the scanner. It should
>have gone out if everything was working.

>>>Go to the WATCH.EXE file
>>>and double click on the file. Did it come on again?

>> It stayed on.

>>> If so, you can control the light through the software.

>> So, obviously, I CAN'T do that.

> Since you do not want to test the parallel port (and I understand why),
>removing ALL the software and reloading it is about all you can do.
>Remember to delete the directories created by the current installation
>so that no file such as the initialization files remain.

>>> If the icon for the scanner is not in the bottom right corner, >>>the
>>>WATCH program did not start. If is there, then start IPE.exe and go >>>to
>>>FILE, ACQUIRE, SELECT SOURCE and your scanner should be listed there.
>>>Is it?

>> Yes.

> This is a little surprising in that I would have thought there >would
>have been no scanner listed there. Who knows, it might be placed there
>even if it was not detected?

>>> You are right, the light comes on by default. I used the batch >>>file to
>>>control the scanner and only plug in the power when I am about to use
>>>it. The control of the light with WATCH.exe is valid however. Run >>>the
>>>test above and you should be able to turn it on and off.

>> Well, I can't turn it off. See above.
>>
>> There is the file: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini that says:
>>
>> --------------
>> [Watch]
>> LampStatus=1
>> GreenTime=15
>> ActiveTime=7352272
>>
>> [CaseInfo]
>> NewSetting=0
>> --------------
>
> That portion of my file reads:
>
>[Watch]
>Model=A4S2600_Watch
>LampStatus=0
>ActiveTime=4923599
>GreenTime=20
>CoverDriven=1
>Timer3=500
>ShowStartup=1
>HasIcon=1
>HasCoverDriven=1
>HasStartup=1
>HasMustUI=1
>
>[CaseInfo]
>SettingSectionName=1200 III EP
>DSSectionName=A4S2INFO_600
>NewSetting=1
>UsePrivateSettingFile=1

This file, in my case, now reads the same as before, except for a
different value of 'ActiveTime'.

>> Is that a correct setup? If I set 'LamStatus' to '0' and save that,
>> the lamp still stays on. I have no idea what the other three settings
>> relate to.
>
> That does not appear to be a complete setting as compared to mine.

Well, I have no idea how to get there from here. But I guess that
would indicate the problem is not hardware in the scanner. I don't
find any file by that name (with or without its extension) on the CD
for my scanner. Is it somehow generated during installation?

> Listed below is another significant portion of that file. Notice >the
>LPT1 setting. My guess you have no such setting?

Where, in my case? As I mentioned, in my case, my BIOS is set to
"Bidirectional", not EPP.

>[A4S2INFO_600]
>Language=English
>DSLanguage=English
>Brand=Mustek
>DSName=1200 III EP
>UITitle="Mustek 1200 III EP "
>ScanSetting=NMLSPD
>Version=V1.0
>DriverVer=2.02
>F/WVersion=None
>Interface=EPP/LPT1
>TestMode=0
>MemBufSize=256
>PreScanDpi=36
>PreScanWidth=306
>PreScanHeight=414
>TAPreScanWidth=216
>TAPreScanHeight=252
>PreScanFile=MSTC0000.BMP
>TAPreScanFile=MSTC0001.BMP
>X_OptiMaxRes=600
>Y_OptiMaxRes=1200
>WtimeTick=60
>Bbricon=0
>BcolorMatch=0
>CMTable=A32PCM.INI
>SupportResCount=13
>SupportRes=72 100 150 200 300 400 600 900 1200 2400 4800 7200 9600
>SupportCustomRes=0
>CustomRes=72 9600
>ResetRes=300
>ResetResIndex=4
>TextMaxRes=600
>TextMaxResIndex=6
>SlideInstall=1
>MaxBufSize=672768
>>>
>>> Anything is possible, but I would not arrive at that conclusion >>>yet.
>>
>>
>> The problem is probably due to the tsunami. Sick joke, here in CA.US.
>>
>> Ray
>>
>>
>>>Ken
>>>
>
> When I was working as a technician years ago, we used to say we >were
>about to call in an Indian to dance with feathers and beads when we
>could not figure out the solution. Needless to say we did not do that,
>but it is a little frustrating to have tried many things and still not
>have succeeded. Rest assured, that the answer is there. You just need
>to ask the correct question after having eliminated other potential
>problems. It is NOT magic!! Look at it as a challenge.

I'm not really into challenges anymore. I suppose Mustek, either US
or Taiwan, would really laugh if I asked them how to make one of their
scanners bought in 1998 work. ;-) I couldn't find any answers to my
problem on the Web anywhere.

Incidentally, after Murphy got loose once and a bottle fell off a
shelf above this scanner and broke its glass, I had the glass replaced
at a glass shop, but the double-sided tape that held it didn't work
very well thereafter, particularly when I would place a heavy book
over the copy in order to keep it flat (the carriage even would hang
up); so I improved that flaky method of securing the glass with four
screwed-down metal clips. That totally did the job. I wonder if they
still use sticky tape for this purpose in Taiwan.

Ray

>Ken

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

Attached is the install log (found in Twain_32\A4s2_600) of my last
installation. I see 2 failures, FWIW.

Ray

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

On Wed, 05 Jan 2005 13:53:26 GMT, Ken <user@domain.invalid> wrote:

This $%^*&))*&%$&* newsgroup wouldn't let me attach my last install
log to a post here, calling it a 'binary file'. Maybe it was too
long. It shows 2 failures and a "could not", but I don't know what
they mean. I'll try to stick it herebelow:

Ray

*** Installation Started 1/5/5 21:52 ***
Title: Mustek 1200 III EP V1.5
Source: D:\RUN.EXE
INI File: C:\WINDOWS\S2600.INI
INI Sect: OCR
INI Item: setup
INI Val: 0
INI Old: 0
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: INSTALL
INI Val: FAIL
INI Old: OK
Made Dir: C:\WINDOWS\TWAIN_32
Made Dir: C:\WINDOWS\TWAIN_32\A4S2_600
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\UNWISE.EXE
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\tutorial.exe
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\eng.exe
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\help6l.exe
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\612ep_e.hlp
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\612ep_d.hlp
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\612ep_f.hlp
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\612ep_g.hlp
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\612ep_i.hlp
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\612ep_s.hlp
File Copy: C:\WINDOWS\SYSTEM\A4S2600.VXD
File Copy: C:\WINDOWS\SYSTEM\A4S2600.386
Date/Time: Following file not copied.
File Copy: C:\WINDOWS\TWAIN_32.DLL
File Copy: C:\WINDOWS\TWUNK_16.EXE
File Copy: C:\WINDOWS\TWUNK_32.EXE
Date/Time: Following file not copied.
File Copy: C:\WINDOWS\TWAIN.DLL
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\FREE_EXE.EXE
Made Dir: C:\WINDOWS\TWAIN
Made Dir: C:\WINDOWS\TWAIN\A4S2_600
File Copy: C:\WINDOWS\TWAIN\A4S2_600\A4S2_600.DS
File Copy: C:\WINDOWS\TWAIN\A4S2_600\LOGO0601.BMP
File Copy: C:\WINDOWS\TWAIN\A4S2_600\A4S2_600.IOB
File Copy: C:\WINDOWS\TWAIN\A4S2_600\PRESCAN.DLL
File Copy: C:\WINDOWS\TWAIN\A4S2_600\Lead52.dll
File Copy: C:\WINDOWS\TWAIN\A4S2_600\UI.EXE
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\WATCH.EXE
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\A4S2_600.IOB
File Copy: C:\WINDOWS\MSVCRT40.DLL
File Copy: C:\WINDOWS\MFC40.DLL
File Copy: C:\WINDOWS\MFC40.DLL
File Copy: C:\WINDOWS\system\msvcirt.dll
File Copy: C:\WINDOWS\TWAIN\A4S2_600\MSTC0000.BMP
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\MSTC0000.BMP
File Copy: C:\WINDOWS\moffice.ini
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\MOCR.EXE
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\MSVCRT40.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\ImgView.exe
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Inbox.exe
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\LEAD51N.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\MFC40.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\MOffice.try
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\DeIsLog.1
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\PANEL.EXE
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\mustui.exe
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\SCANMED.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\English.hlp
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\German.hlp
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\French.hlp
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Italian.hlp
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Spanish.hlp
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Dutch.hlp
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\PANEL_LD.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\PANEL_LF.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\PANEL_LG.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\PANEL_LI.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\PANEL_LS.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\PANEL_LC.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Mail_lc.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Mail_ld.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Mail_lf.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Mail_lg.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Mail_li.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Mail_ls.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\Maildll.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\SCAN_LD.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\SCAN_LF.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\SCAN_LG.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\SCAN_LI.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\SCAN_LS.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\SCAN_LC.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\INBOX_D.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\INBOX_F.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\INBOX_G.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\INBOX_I.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\INBOX_S.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\INBOX_C.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\IMGVEW_D.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\IMGVEW_F.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\IMGVEW_G.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\IMGVEW_I.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\IMGVEW_S.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice\IMGVEW_C.DLL
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Annot
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Annot\A2363.ant
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Annot\A2647.ant
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Data
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Data\FISH.JPG
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Data\BUTERFLY.JPG
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Data\BALOON.JPG
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Data\SAIL.JPG
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Data\SFC.JPG
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Data\SFX1.JPG
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Data\SFX2.JPG
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Thumb
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Thumb\T2647.jpg
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Thumb\T2363.jpg
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Thumb\T2419.jpg
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Thumb\T2322.jpg
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Thumb\T2786.jpg
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Thumb\T2824.jpg
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Thumb\T3109.jpg
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Ipplus
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IPPLUS.EXE
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IPPCAP.EXE
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IPPFIND.DLL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IPPHELP.DLL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IPGAMMA.TIF
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IPPLUS.HLP
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IPPLUS.INI
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IPPTW.EXE
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\KEYHOOK.DLL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\README.TXT
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Ipplus\IMAGES
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IMAGES\IPGAMMA.JPG
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IMAGES\BIRDS.JPG
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IMAGES\ORCH256.JPG
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Ipplus\INSTALL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\INSTALL\IPPLOGO.UBM
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\INSTALL\IPHOTO.UBM
Made Dir: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PALETTES
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PALETTES\GREEN.PAL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PALETTES\BROWN.PAL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PALETTES\CYAN.PAL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PALETTES\FIRE.PAL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PALETTES\GOLD.PAL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PALETTES\BLUE.PAL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PALETTES\MAGENTA.PAL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PALETTES\PSEUDO.PAL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PALETTES\YELLOW.PAL
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\MsOffice\Ipplus\PLUG_IN
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PLUG_IN\ICI.DLL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PLUG_IN\CU.DLL
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\PLUG_IN\IPICI.EXE
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\Acroread
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Acroread\license.txt
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Acroread\ACROREAD.REG
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Acroread\ACROREAD.EXE
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Acroread\ACROCORE.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Acroread\ACROGRAF.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Acroread\ACROPFS.DLL
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Acroread\VIEWLIB.DLL
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\ACROREAD\FONTS
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\ACROREAD\FONTS\ZD______.PFB
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\ACROREAD\FONTS\SY______.PFB
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\ACROREAD\FONTS\ZX______.PFB
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\ACROREAD\FONTS\ZY______.PFB
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\ACROREAD\HELP
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\ACROREAD\HELP\HELP_R.PDF
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\ACROREAD\HELP\README_R.TXT
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\ACROREAD\PLUG_INS
File Copy: C:\Program Files\iPhoto Plus
4\MSCAN\ACROREAD\PLUG_INS\WEBLINK.API
File Copy: C:\WINDOWS\ACROREAD.INI
File Copy: C:\WINDOWS\ACROGRAF.INI
File Copy: C:\WINDOWS\ATM.INI
Made Dir: C:\Program Files\iPhoto Plus 4\MSCAN\Manual
File Copy: C:\Program Files\iPhoto Plus 4\MSCAN\Manual\Iphoto_e.pdf
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: BRAND
INI Val: Mustek
INI Old: Mustek
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: VERSION
INI Val: V1.5
INI Old: V1.5
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: DSLANGUAGE
INI Val: None
INI Old: None
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: SCANSETTING
INI Val: NMLSPD
INI Old: NMLSPD
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: 06000
INI Val: 600 III EP
INI Old: 600 III EP
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: 08000
INI Val: 800 III EP
INI Old: 800 III EP
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: 06060
INI Val: 606 III EP
INI Old: 606 III EP
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: 12000
INI Val: 1200 III EP
INI Old: 1200 III EP
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: DRIVER
INI Val: A4S2_600.iob
INI Old: A4S2_600.iob
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: WARMUPTICKS
INI Val: 60000
INI Old: 60000
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: LANGUAGE
INI Val: English
INI Old: English
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: DSNAME
INI Val: 1200 III EP
INI Old: 1200 III EP
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: PACKAGENAME
INI Val: Flatbed Scanner [EPP]
INI Old: Flatbed Scanner [EPP]
INI File: C:\WINDOWS\WIN.INI
INI Sect: A4S2INFO_600
INI Item: INSTALL
INI Val: OK
INI Old: FAIL
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: ScanMode
INI Val: 2
INI Old: 2
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: DpiScale
INI Val: 0
INI Old: 0
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: ScanRes
INI Val: 300
INI Old: 300
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: ResIndex
INI Val: 4
INI Old: 4
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: PaperSize
INI Val: 3
INI Old: 3
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: Frame
INI Val: 0 0 305 414
INI Old: 0 0 305 414
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: Brightness
INI Val: 0 0 0 0
INI Old: 0 0 0 0
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: Gamma
INI Val: 14 14 14 10
INI Old: 14 14 14 10
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: Contrast
INI Val: 0 0 0 0
INI Old: 0 0 0 0
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: DeMoire
INI Val: 0
INI Old: 0
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: FilterMode
INI Val: 0
INI Old: 0
INI File: C:\WINDOWS\WIN.INI
INI Sect: Slim New UI
INI Item: Language
INI Val: 0
INI Old: 0
INI File: C:\WINDOWS\WIN.INI
INI Sect: EasyScan
INI Item: Brand
INI Val: Mustek
INI Old: Mustek
INI File: C:\WINDOWS\WIN.INI
INI Sect: EasyScan
INI Item: Model
INI Val: 1200 III EP
INI Old: 1200 III EP
INI File: C:\WINDOWS\WIN.INI
INI Sect: EasyScan
INI Item: Package
INI Val: cover sensor
INI Old: cover sensor
INI File: C:\WINDOWS\WIN.INI
INI Sect: EasyScan
INI Item: Ver
INI Val: Ver1.5
INI Old: Ver1.5
INI File: C:\WINDOWS\WIN.INI
INI Sect: EasyScan
INI Item: Help
INI Val: C:\WINDOWS\TWAIN_32\A4S2_600\612EP
INI Old: C:\WINDOWS\TWAIN_32\A4S2_600\612EP
INI File: C:\WINDOWS\WIN.INI
INI Sect: EasyScan
INI Item: Type
INI Val: ""
INI File: C:\WINDOWS\WIN.INI
INI Sect: Scanning Desktop
INI Item: Brand
INI Val: Mustek
INI Old: Mustek
INI File: C:\WINDOWS\WIN.INI
INI Sect: Scanning Desktop
INI Item: Package
INI Val: Scanning Desktop
INI Old: Scanning Desktop
INI File: C:\WINDOWS\WIN.INI
INI Sect: Scanning Desktop
INI Item: Ver
INI Val: V1.5
INI Old: V1.5
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Scanning Desktop
INI Item: Path
INI Val: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice
INI Old: C:\Program Files\iPhoto Plus 4\MSCAN\Msoffice
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Cover Driven
INI Item: Cover Driven
INI Val: Yes
INI Old: Yes
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Cover Driven
INI Item: Method
INI Val: Close2Open
INI Old: Close2Open
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Cover Driven
INI Item: Status
INI Val: Open
INI Old: Open
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Cover Driven
INI Item: Timer3
INI Val: 500
INI Old: 500
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Show Startup Screen
INI Item: Show Startup
INI Val: Yes
INI Old: Yes
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Model Information
INI Item: Model
INI Val: A4S2600
INI Old: A4S2600
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Model Information
INI Item: Path
INI Val: A4S2_600
INI Old: A4S2_600
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Model Information
INI Item: Driver
INI Val: A4S2_600.IOB
INI Old: A4S2_600.IOB
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Model Information
INI Item: DS
INI Val: A4S2_600.DS
INI Old: A4S2_600.DS
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Model Information
INI Item: Info
INI Val: A4S2INFO_600
INI Old: A4S2INFO_600
INI File: C:\WINDOWS\WATCH.INI
INI Sect: Model Information
INI Item: Style
INI Val: 1200 III EP
INI Old: 1200 III EP
INI New: Created INI
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: Watch
INI Item: LampStatus
INI Val: 0
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: Watch
INI Item: GreenTime
INI Val: 15
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: CaseInfo
INI Item: NewSetting
INI Val: 0
INI File: C:\WINDOWS\moffice.ini
INI Sect: Language
INI Item: Name
INI Val: English
INI File: C:\WINDOWS\moffice.ini
INI Sect: Scan Setting
INI Item: ImageAp
INI Val: C:\Program Files\iPhoto Plus
4\MSCAN\msoffice\ipplus\ipplus.exe
INI File: C:\WINDOWS\moffice.ini
INI Sect: Scan Setting
INI Item: FileName
INI Val: Ipplus.exe
Shell Link: C:\WINDOWS\Start Menu\Programs\StartUp\Watch.lnk
Icon Group: Mustek 1200IIIEP
Icon Name: Direct Scan
Icon Cmd: C:\WINDOWS\TWAIN_32\A4S2_600\watch.exe
Icon Group: Mustek 1200IIIEP
Icon Name: iPhotoPlus 1.2
Icon Cmd: C:\Program Files\iPhoto Plus
4\MSCAN\MsOffice\Ipplus\IPPLUS.EXE
Icon Group: Mustek 1200IIIEP
Icon Name: Tutorial
Icon Cmd: C:\WINDOWS\TWAIN_32\A4S2_600\tutorial.exe
Icon Group: Mustek 1200IIIEP
Icon Name: Mustek 1200 III EP Help
Icon Cmd: C:\WINDOWS\TWAIN_32\A4S2_600\612ep_e.hlp
Icon Group: Mustek 1200IIIEP
Icon Name: iPhotoPlus 1.2 User Manual
Icon Cmd: C:\Program Files\iPhoto Plus 4\MSCAN\Acroread\ACROREAD.EXE
C:\Program Files\iPhoto Plus 4\MSCAN\Manual\Iphoto_e.pdf
Icon Group: Mustek 1200IIIEP
Icon Name: Uninstall
Icon Cmd: C:\WINDOWS\TWAIN_32\A4S2_600\UNWISE.EXE
C:\WINDOWS\TWAIN_32\A4S2_600\INSTALL.LOG
Could not Self-Register: C:\WINDOWS\TWAIN_32\A4S2_600\UNWISE.EXE

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

Please ignore this and refer to a later post that includes the
attachment mentioned here in its body. (Apparently attachments aren't
allowed here.)

Ray

On Thu, 06 Jan 2005 01:42:43 -0800, Raymond A. Chamberlin
<raych@znet.com> wrote:

>Attached is the install log (found in Twain_32\A4s2_600) of my last
>installation. I see 2 failures, FWIW.
>
>Ray

 

[ken]

Archived from groups: alt.comp.periphs.scanner (More info?)

Raymond A. Chamberlin wrote:
> On Wed, 05 Jan 2005 13:53:26 GMT, Ken <user@domain.invalid> wrote:
>
>
>> I did a lot of clipping of old text.

>> What I mean is even if NO software was loaded the lamp would come on.
>>Once the software is loaded for the control of the lamp, it should turn
>>off and on the lamp if you follow the procedure I described using WATCH.EXE.
>
>
> Well, in its present condition, the lamp stays on no matter what.
> When the scanner was working right, the light was always ON as long as
> power was applied to the scanner. However, I never tried, at that
> time, to see what would happen if I double-clicked Watch.exe.

The reason it stays on presently, is the scanner is not recognized and
therefore the software (watch.exe) is unable to control the lamp. Since
the lamp will come one even if the scanner is not connected to the
computer, it will always be on. Remember, to make the lamp go OFF once
the icon exists in the lower right corner of your screen, you must do
the "Right click on it and choose EXIT, YES" routine. It is NOT working
that way now because the software is unable to see the scanner. The
software is loaded by virtue of the icon being present, and there not
having been an error message saying that a file could not be found
during the loading of that program.
>
>


>
>
> The power input at the scanner's main board measures 15 v.

That is correct for the wall wart.
>
>
>> Other reasons could be corrupted software, bad parallel port or cable
>
>>from the port, or defective logic in the scanner.
>


>
>
> I located two components on the main board that appeared to be power
> regulators. I don't know their pinouts, but the only pins that
> measured significant voltages other than 15 v showed 3 and 12 v,
> respectively.

One of the outside pins (the left one if I recall correctly, but don't
hold me to this) should be the input voltage. In this case, 15v. The
center pin is Ground. The right terminal is the output voltage, 12v.
You might not be placing your common lead of your DVM to true ground
when you measured the center terminal. Sometimes these circuits do not
use the same ground as your computer uses.

The other regulator should work the same way, but the output should be
+5v. (I think) The marking on the regulators should read something
like 9805 and 9812 indicating the +5 and +12 volt output.
>
>

>
>
> See above.
>
>

>>
>> If I were to guess, (and I don't care much for guessing) that is what I
>>would guess. For what it is worth, you could open up the scanner and
>>see if you can reach the two regulators. A simple DVM should allow you
>>to measure their output as they are both three terminal through-hole
>>components if my memory serves me.
>
>
> See above.
>
>
>>I agree however, that you are more
>>likely to find software or the port to be the problem.
>>


>>
>> Now this would seem to indicate that the software loaded properly
>>and that all the files necessary were OK.
>
>
> How would that assure that ALL the files were loaded properly?

If the software were NOT loaded properly, there should have been an
error message saying that a file was not found or could not load.
Nothing is 100%, but that would be the case most of the time.
>
>

>>
>> This is probably due to the fact it cannot see the scanner. It should
>>have gone out if everything was working.
>
>

>
>
>>>It stayed on.
>
>

>
>
>> Since you do not want to test the parallel port (and I understand why),
>>removing ALL the software and reloading it is about all you can do.
>>Remember to delete the directories created by the current installation
>>so that no file such as the initialization files remain.
>
>

>
>
>> This is a little surprising in that I would have thought there >would
>>have been no scanner listed there. Who knows, it might be placed there
>>even if it was not detected?
>
>


>>
>> That portion of my file reads:
>>
>>[Watch]
>>Model=A4S2600_Watch
>>LampStatus=0
>>ActiveTime=4923599
>>GreenTime=20
>>CoverDriven=1
>>Timer3=500
>>ShowStartup=1
>>HasIcon=1
>>HasCoverDriven=1
>>HasStartup=1
>>HasMustUI=1
>>
>>[CaseInfo]
>>SettingSectionName=1200 III EP
>>DSSectionName=A4S2INFO_600
>>NewSetting=1
>>UsePrivateSettingFile=1
>
>
> This file, in my case, now reads the same as before, except for a
> different value of 'ActiveTime'.
>
>
>>>Is that a correct setup? If I set 'LamStatus' to '0' and save that,
>>>the lamp still stays on. I have no idea what the other three settings
>>>relate to.
>>
>> That does not appear to be a complete setting as compared to mine.
>
>
> Well, I have no idea how to get there from here. But I guess that
> would indicate the problem is not hardware in the scanner. I don't
> find any file by that name (with or without its extension) on the CD
> for my scanner. Is it somehow generated during installation?

The text I posted is NOT a new file, but part of the one you posted.
mtwm.ini I would think much of that segment is not in your file of the
same name due to the scanner not being detected. I simply pasted it to
show you more was needed in that file besides the segment you cited.
>
>
>> Listed below is another significant portion of that file. Notice >the
>>LPT1 setting. My guess you have no such setting?
>
>
> Where, in my case? As I mentioned, in my case, my BIOS is set to
> "Bidirectional", not EPP.

If your setting in CMOS is bidirectional, that should be FINE.
Different computers have different settings and verbiage. It is just
important that it is able to communicate both ways, and either EPP, ECP
or Bidirectional will do that.
>
>
>>[A4S2INFO_600]
>>Language=English
>>DSLanguage=English
>>Brand=Mustek
>>DSName=1200 III EP
>>UITitle="Mustek 1200 III EP "
>>ScanSetting=NMLSPD
>>Version=V1.0
>>DriverVer=2.02
>>F/WVersion=None
>>Interface=EPP/LPT1
>>TestMode=0
>>MemBufSize=256
>>PreScanDpi=36
>>PreScanWidth=306
>>PreScanHeight=414
>>TAPreScanWidth=216
>>TAPreScanHeight=252
>>PreScanFile=MSTC0000.BMP
>>TAPreScanFile=MSTC0001.BMP
>>X_OptiMaxRes=600
>>Y_OptiMaxRes=1200
>>WtimeTick=60
>>Bbricon=0
>>BcolorMatch=0
>>CMTable=A32PCM.INI
>>SupportResCount=13
>>SupportRes=72 100 150 200 300 400 600 900 1200 2400 4800 7200 9600
>>SupportCustomRes=0
>>CustomRes=72 9600
>>ResetRes=300
>>ResetResIndex=4
>>TextMaxRes=600
>>TextMaxResIndex=6
>>SlideInstall=1
>>MaxBufSize=672768
>>

>>>>
>>
>>
>> When I was working as a technician years ago, we used to say we >were
>>about to call in an Indian to dance with feathers and beads when we
>>could not figure out the solution. Needless to say we did not do that,
>>but it is a little frustrating to have tried many things and still not
>>have succeeded. Rest assured, that the answer is there. You just need
>>to ask the correct question after having eliminated other potential
>>problems. It is NOT magic!! Look at it as a challenge.
>
>
> I'm not really into challenges anymore. I suppose Mustek, either US
> or Taiwan, would really laugh if I asked them how to make one of their
> scanners bought in 1998 work. ;-) I couldn't find any answers to my
> problem on the Web anywhere.

Hell, they would laugh at you right after you bought the scanner. All
they wanted to do with me is sell me a scanner. Two of the shipments
arrived broken and I had one hell of a time getting it straightened out.
There is NO WAY they will help you with this scanner.
>
> Incidentally, after Murphy got loose once and a bottle fell off a
> shelf above this scanner and broke its glass, I had the glass replaced
> at a glass shop, but the double-sided tape that held it didn't work
> very well thereafter, particularly when I would place a heavy book
> over the copy in order to keep it flat (the carriage even would hang
> up); so I improved that flaky method of securing the glass with four
> screwed-down metal clips. That totally did the job. I wonder if they
> still use sticky tape for this purpose in Taiwan.
>
> Ray

I sort of enjoy challenges, since I am retired and have time for them.
Even when I was a tech, I always viewed a problem as a puzzle. It was
like a game, in that the problem was hiding and my job was to find it.
True, there is frustration along the way, but it is also rewarding when
you succeed. You also become a LITTLE smarter in the process.

If I were you, I would first go back to your measurements of the
voltage regulators making sure of their values with respect to the
scanner ground. A good place to pick up ground would be on one of the
electrolytic's negative lead. If they measured properly, I would assume
your scanner was OK. Next since it doesn't sound like you will test the
parallel port, I would COMPLETELY remove the software and load it again
making sure the scanner is powered up while doing so. Be sure to delete
the directories created by the current load of the software, because
removal of software sometimes keeps files such as INI files. That might
screw up your next installation.

Finally, I saw your pasting of the install log in another message, but
the install log is probably of little value and hard to decipher. Try
the re-installation of the software as mentioned above.

Ken
>
>
>>Ken
>
>

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

On Thu, 06 Jan 2005 14:00:41 GMT, Ken <user@domain.invalid> wrote:

>Raymond A. Chamberlin wrote:
>> On Wed, 05 Jan 2005 13:53:26 GMT, Ken <user@domain.invalid> wrote:
>>
>>
>>> I did a lot of clipping of old text.
>
>>> What I mean is even if NO software was loaded the lamp would come on.
>>>Once the software is loaded for the control of the lamp, it should turn
>>>off and on the lamp if you follow the procedure I described using WATCH.EXE.
>>
>>
>> Well, in its present condition, the lamp stays on no matter what.
>> When the scanner was working right, the light was always ON as long as
>> power was applied to the scanner. However, I never tried, at that
>> time, to see what would happen if I double-clicked Watch.exe.
>
> The reason it stays on presently, is the scanner is not recognized and
>therefore the software (watch.exe) is unable to control the lamp. Since
>the lamp will come one even if the scanner is not connected to the
>computer, it will always be on. Remember, to make the lamp go OFF once
>the icon exists in the lower right corner of your screen, you must do
>the "Right click on it and choose EXIT, YES" routine. It is NOT working
>that way now because the software is unable to see the scanner. The
>software is loaded by virtue of the icon being present, and there not
>having been an error message saying that a file could not be found
>during the loading of that program.

Well, an email request to Mostek USA (automatically, I guess) got me
instructions on exactly how to pull all the twains and twunks and
reinstall new ones. Apparently I didn't have to uninstall the image
program bundled with the scanner, as I did before. The only
significant difference I could see between what these instructions
said and what I did before to remove this stuff (I still don't
understand whether their term 'scanner driver' refers to all these
twains and twunks or something else.) was that I didn't disable my
virus auto-protect program. Their instructions included getting a
different "driver" from their Website, which I did -- '123ep22.exe',
which came out in 1999. The one on my CD, that I used before, is
'd12epe22.exe'. Which one do you use? So I installed this newer
"driver". I note that it leaves out the 'Twain' folder, only
installing the 'Twain32' folder into the Windows folder. Isn't the
'Twain' folder just for 16=bit-word machines anyhow?

So, OK, now I don't get a flag saying it can't detect the scanner, but
I still get one that says it can't find 'twain.dll' in the Windows
folder, although this file IS in the Windows folder. So I guess I'll
uninstall that driver collection and reinstall the d12epe22 one per
their instructions and see if that works.

We can certainly forget all this discussion about when the scanner
lamp should be ON though. At present, when it DOESN'T say it can't
find the scanner, that light still does NOT go on and off with the
tray icon; it's ALWAYS ON. If it does in your case, it must be that
units having some ranges of serial
do that, while others don't.

>> The power input at the scanner's main board measures 15 v.
>
> That is correct for the wall wart.
>>
>>
>>> Other reasons could be corrupted software, bad parallel port or cable
>>
>>>from the port, or defective logic in the scanner.

>> I located two components on the main board that appeared to be power
>> regulators. I don't know their pinouts, but the only pins that
>> measured significant voltages other than 15 v showed 3 and 12 v,
>> respectively.
>
> One of the outside pins (the left one if I recall correctly, but don't
>hold me to this) should be the input voltage. In this case, 15v. The
>center pin is Ground. The right terminal is the output voltage, 12v.
>You might not be placing your common lead of your DVM to true ground
>when you measured the center terminal. Sometimes these circuits do not
>use the same ground as your computer uses.
>
> The other regulator should work the same way, but the output should be
>+5v. (I think) The marking on the regulators should read something
>like 9805 and 9812 indicating the +5 and +12 volt output.

I don't think there's any problem there. I measured with respect to
the INPUT power-cable ground. I measured the +12 and +3 on different
pins relative to the same physical start of pin count. The other
non-15-v pins on the two regulators had very low voltages. There are
no markings on the regulators.

>> See above.

>>> If I were to guess, (and I don't care much for guessing) that is what I
>>>would guess. For what it is worth, you could open up the scanner and
>>>see if you can reach the two regulators. A simple DVM should allow you
>>>to measure their output as they are both three terminal through-hole
>>>components if my memory serves me.
>>
>>
>> See above.
>>
>>
>>>I agree however, that you are more
>>>likely to find software or the port to be the problem.
>>>
>
>
>>>
>>> Now this would seem to indicate that the software loaded properly
>>>and that all the files necessary were OK.
>>
>>
>> How would that assure that ALL the files were loaded properly?
>
> If the software were NOT loaded properly, there should have been an
>error message saying that a file was not found or could not load.
>Nothing is 100%, but that would be the case most of the time.

Whatever. Software types have no constraints. It's all
seat-of-the-pants. It's all chaos to me.

>>> This is probably due to the fact it cannot see the scanner. It should
>>>have gone out if everything was working.

>>>>It stayed on.

>>> Since you do not want to test the parallel port (and I understand why),
>>>removing ALL the software and reloading it is about all you can do.
>>>Remember to delete the directories created by the current installation
>>>so that no file such as the initialization files remain.

>>> This is a little surprising in that I would have thought there >would
>>>have been no scanner listed there. Who knows, it might be placed there
>>>even if it was not detected?

>>> That portion of my file reads:
>>>
>>>[Watch]
>>>Model=A4S2600_Watch
>>>LampStatus=0
>>>ActiveTime=4923599
>>>GreenTime=20
>>>CoverDriven=1
>>>Timer3=500
>>>ShowStartup=1
>>>HasIcon=1
>>>HasCoverDriven=1
>>>HasStartup=1
>>>HasMustUI=1
>>>
>>>[CaseInfo]
>>>SettingSectionName=1200 III EP
>>>DSSectionName=A4S2INFO_600
>>>NewSetting=1
>>>UsePrivateSettingFile=1
>>
>>
>> This file, in my case, now reads the same as before, except for a
>> different value of 'ActiveTime'.
>>
>>
>>>>Is that a correct setup? If I set 'LamStatus' to '0' and save that,
>>>>the lamp still stays on. I have no idea what the other three settings
>>>>relate to.
>>>
>>> That does not appear to be a complete setting as compared to >>> mine.
>>
>>
>> Well, I have no idea how to get there from here. But I guess that
>> would indicate the problem is not hardware in the scanner. I don't
>> find any file by that name (with or without its extension) on the CD
>> for my scanner. Is it somehow generated during installation?
>
> The text I posted is NOT a new file, but part of the one you >posted.
>mtwm.ini

I'm aware of that.

> I would think much of that segment is not in your file of the
>same name due to the scanner not being detected. I simply pasted it to
>show you more was needed in that file besides the segment you cited.

OK.

>>> Listed below is another significant portion of that file. Notice >the
>>>LPT1 setting. My guess you have no such setting?
>>
>>
>> Where, in my case? As I mentioned, in my case, my BIOS is set to
>> "Bidirectional", not EPP.
>
> If your setting in CMOS is bidirectional, that should be FINE.
>Different computers have different settings and verbiage. It is just
>important that it is able to communicate both ways, and either EPP, ECP
>or Bidirectional will do that.
>>
>>
>>>[A4S2INFO_600]
>>>Language=English
>>>DSLanguage=English
>>>Brand=Mustek
>>>DSName=1200 III EP
>>>UITitle="Mustek 1200 III EP "
>>>ScanSetting=NMLSPD
>>>Version=V1.0
>>>DriverVer=2.02
>>>F/WVersion=None
>>>Interface=EPP/LPT1
>>>TestMode=0
>>>MemBufSize=256
>>>PreScanDpi=36
>>>PreScanWidth=306
>>>PreScanHeight=414
>>>TAPreScanWidth=216
>>>TAPreScanHeight=252
>>>PreScanFile=MSTC0000.BMP
>>>TAPreScanFile=MSTC0001.BMP
>>>X_OptiMaxRes=600
>>>Y_OptiMaxRes=1200
>>>WtimeTick=60
>>>Bbricon=0
>>>BcolorMatch=0
>>>CMTable=A32PCM.INI
>>>SupportResCount=13
>>>SupportRes=72 100 150 200 300 400 600 900 1200 2400 4800 7200 9600
>>>SupportCustomRes=0
>>>CustomRes=72 9600
>>>ResetRes=300
>>>ResetResIndex=4
>>>TextMaxRes=600
>>>TextMaxResIndex=6
>>>SlideInstall=1
>>>MaxBufSize=672768

>>> When I was working as a technician years ago, we used to say we >>>were
>>>about to call in an Indian to dance with feathers and beads when we
>>>could not figure out the solution. Needless to say we did not do >>>that,
>>>but it is a little frustrating to have tried many things and still not
>>>have succeeded. Rest assured, that the answer is there. You just >>>need
>>>to ask the correct question after having eliminated other potential
>>>problems. It is NOT magic!! Look at it as a challenge.
>>
>>
>> I'm not really into challenges anymore. I suppose Mustek, either US
>> or Taiwan, would really laugh if I asked them how to make one of their
>> scanners bought in 1998 work. ;-) I couldn't find any answers to my
>> problem on the Web anywhere.
>
> Hell, they would laugh at you right after you bought the scanner. All
>they wanted to do with me is sell me a scanner. Two of the shipments
>arrived broken and I had one hell of a time getting it straightened out.
> There is NO WAY they will help you with this scanner.

They (SoCal, USA) did once when my lamp burnt out and I wanted to know
why it had to stay on all the time. Also, once when I downloaded and
installed something that indicated it was for this model but wasn't.
Maybe it was this very 1999 driver that isn't working for me.

>> Incidentally, after Murphy got loose once and a bottle fell off a
>> shelf above this scanner and broke its glass, I had the glass replaced
>> at a glass shop, but the double-sided tape that held it didn't work
>> very well thereafter, particularly when I would place a heavy book
>> over the copy in order to keep it flat (the carriage even would hang
>> up); so I improved that flaky method of securing the glass with four
>> screwed-down metal clips. That totally did the job. I wonder if they
>> still use sticky tape for this purpose in Taiwan.
>>
>> Ray
>
> I sort of enjoy challenges, since I am retired and have time for >them.
> Even when I was a tech, I always viewed a problem as a puzzle. It was
>like a game, in that the problem was hiding and my job was to find it.
>True, there is frustration along the way, but it is also rewarding when
>you succeed. You also become a LITTLE smarter in the process.

Well, I got spoilt by playing design engineer. That was interesting;
trying to figure out why somebody ELSE designed something some
cockamany way never was fun for me. And software is pretty much
however you can hack it out, and it was far too serial for my mind,
even then -- and less memory-recording capability at present makes it
worse. I needed to get in from the side of designs and tweak them a
little (my stack was never that deep, for arbitrary stuff).
Collecting the results of fixing all that arbitrary stuff isn't my
idea of "smart"ness.

> If I were you, I would first go back to your measurements of the
>voltage regulators making sure of their values with respect to the
>scanner ground. A good place to pick up ground would be on one of the
>electrolytic's negative lead.

Maybe I'll check that AFTER I try the original driver again, loaded
exactly as per Mustek's instructions.

>If they measured properly, I would assume
>your scanner was OK. Next since it doesn't sound like you will test the
>parallel port, I would COMPLETELY remove the software and load it again
>making sure the scanner is powered up while doing so. Be sure to delete
>the directories created by the current load of the software, because
>removal of software sometimes keeps files such as INI files. That might
>screw up your next installation.
>
> Finally, I saw your pasting of the install log in another message, but
>the install log is probably of little value and hard to decipher. Try
>the re-installation of the software as mentioned above.

Herebelow is what is presently in several files:

Ray

In Twain.log:

************

TWAIN_32.DLL - MESSAGE - CTwunk ::AppInitialize - Reset Log

TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Starting Thunker

TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Startup Complete
To Twain
TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Received Startup
Complete From Thunker

TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Posting Close To
Thunker

TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Shutdown Complete
To Twain
TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Received Shutdown
Complete From Thunker


************

In mtwm.ini:

************

[Scanner]
TwainDS=scanobj.ds
ScanDll=scanobj.dll
DevDll=spicall.dll
FilterDLL=filter.dll
UIProg=ui.exe

[CaseInfo]
SettingSectionName=1200 III EP
DSSectionName=A4S2INFO_600
NewSetting=1
UsePrivateSettingFile=1

[A4S2INFO_600]
Language=English
DSLanguage=English
Brand=Mustek
DSName=1200 III EP
UITitle="Mustek 1200 III EP "
ScanSetting=NMLSPD
Version=2.2
DriverVer=2.2
F/WVersion=NONE
Interface=EPP/LPT2
TestMode=0
MemBufSize=256
PreScanDpi=36
PreScanWidth=306
PreScanHeight=414
TAPreScanWidth=216
TAPreScanHeight=252
PreScanFile=MSTC0000.BMP
TAPreScanFile=MSTC0001.BMP
X_OptiMaxRes=600
Y_OptiMaxRes=1200
WtimeTick=0
Bbricon=0
BcolorMatch=0
CMTable=A32PCM.INI
SupportResCount=13
SupportRes=72 100 150 200 300 400 600 900 1200 2400 4800 7200 9600
SupportCustomRes=0
CustomRes=72 9600
ResetRes=300
ResetResIndex=4
TextMaxRes=600
TextMaxResIndex=6
SlideInstall=1

[Watch]
Model=A4S2600_Watch
LampStatus=1
ActiveTime=433625
GreenTime=20
CoverDriven=1
Timer3=500
ShowStartup=1
HasIcon=1
HasCoverDriven=1
HasStartup=1
HasMustUI=1

[EasyScan]
Model=1200 III EP
Package=cover sensor
Ver=2.2
Help=C:\WINDOWS\TWAIN_32\A4S2_600\A4ui1

[Scanning Desktop]
Path=C:\MSCAN\Msoffice

[SupportSize]
Count=3
TACount=4
ResetPaperIndex=0
PaperName=A4 A5 Letter
TAPaperName=35x40mm 60x60mm 60x70mm 101x127mm
A4=826 1150
A5=582 826
Letter=850 1100
35x40mm=157 137
60x60mm=236 236
60x70mm=275 236
101x127mm=500 397

[English]
A4=A4
A5=A5
Letter=Letter
35x40mm=35x40mm
60x60mm=60x60mm
60x70mm=60x70mm
101x127mm=101x127mm

[German]
A4=DIN A4
A5=DIN A5
Letter=US-Letter
35x40mm=35x40mm
60x60mm=60x60mm
60x70mm=60x70mm
101x127mm=101x127mm

[French]
A4=A 4
A5=A5
Letter=Lettre US
35x40mm=35x40mm
60x60mm=60x60mm
60x70mm=60x70mm
101x127mm=101x127mm

[Italian]
A4=A4
A5=A5
Letter=Lettera
35x40mm=35x40mm
60x60mm=60x60mm
60x70mm=60x70mm
101x127mm=101x127mm

[Spanish]
A4=A4
A5=A5
Letter=Carta
35x40mm=35x40mm
60x60mm=60x60mm
60x70mm=60x70mm
101x127mm=101x127mm

[Dutch]
A4=A4
A5=A5
Letter=Letter
35x40mm=35x40mm
60x60mm=60x60mm
60x70mm=60x70mm
101x127mm=101x127mm

[Russian]
A4=A4
A5=A5
Letter=ðÉÓØÍÏ
35x40mm=35x40mm
60x60mm=60x60mm
60x70mm=60x70mm
101x127mm=101x127mm

[Chinese]
A4=A4
A5=A5
Letter=Letter
35x40mm=35x40mm
60x60mm=60x60mm
60x70mm=60x70mm
101x127mm=101x127mm

[Japanese]
A4=A4
A5=A5
Letter=ƒŒƒ^?[
35x40mm=35x40mm
60x60mm=60x60mm
60x70mm=60x70mm
101x127mm=101x127mm

[Simple]
A4=A4
A5=A5
Letter=Letter
35x40mm=35x40mm
60x60mm=60x60mm
60x70mm=60x70mm
101x127mm=101x127mm

[Slim New UI]
Language=0
ScanMode=0
ScanRes=300
ResIndex=4
PaperSize=3
Frame=0 0 306 414
Brightness=0 0 0 0
Gamma=14 14 14 10
Contrast=0 0 0 0
DpiScale=0
DeMoire=0
FilterMode=0
ColorBalance=1
ColorMatch=0
DescreenIndex=0
InRulerUnit=0
OutUnit=0
CustomRes=0

*************

In Install.log

*************

*** Installation Started 1/6/5 23:48 ***
Title:
Source: C:\PROGRA~1\MUSTEK~2\123EP22.EXE
File Copy: C:\WINDOWS\system\a4s2600.vxd
Made Dir: C:\WINDOWS\TWAIN_32
Made Dir: C:\WINDOWS\TWAIN_32\A4S2_600
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\spicall.dll
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
File Copy: C:\WINDOWS\TWAIN.DLL
File Copy: C:\WINDOWS\TWAIN_32.DLL
File Copy: C:\WINDOWS\TWUNK_32.EXE
File Copy: C:\WINDOWS\TWUNK_16.EXE
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Free_EXE.exe
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\filter.dll
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\lang_e.dll
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Scanobj.dll
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Scanobj.ds
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\WATCH.exe
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Lead52.dll
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\UI.EXE
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\ABOUT.BMP
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\LOGO0601.BMP
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\MSTC0001.BMP
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\MSTC0000.BMP
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: CaseInfo
INI Item: NewSetting
INI Val: 1
INI Old: 1
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: CaseInfo
INI Item: SettingSectionName
INI Val: 1200 III EP
INI Old: 1200 III EP
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: CaseInfo
INI Item: DSSectionName
INI Val: A4S2INFO_600
INI Old: A4S2INFO_600
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: CaseInfo
INI Item: UsePrivateSettingFile
INI Val: 1
INI Old: 1
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: DSLanguage
INI Val: English
INI Old: English
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: BRAND
INI Val: Mustek
INI Old: Mustek
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: DSNAME
INI Val: 1200 III EP
INI Old: 1200 III EP
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: UITITLE
INI Val: "Mustek 1200 III EP "
INI Old: Mustek 1200 III EP
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: Version
INI Val: 2.2
INI Old: V1.0
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: DriverVer
INI Val: 2.2
INI Old: 2.0
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: F/WVersion
INI Val: NONE
INI Old: None
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: ScanSetting
INI Val: NMLSPD
INI Old: NMLSPD
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: WtimeTick
INI Val: 0
INI Old: 60
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: ResetRes
INI Val: 300
INI Old: 300
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: A4S2INFO_600
INI Item: ResetResIndex
INI Val: 4
INI Old: 4
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: EasyScan
INI Item: Model
INI Val: 1200 III EP
INI Old: 1200 III EP
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: EasyScan
INI Item: Package
INI Val: cover sensor
INI Old: cover sensor
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: EasyScan
INI Item: Ver
INI Val: 2.2
INI Old: Ver1.6
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: EasyScan
INI Item: Help
INI Val: C:\WINDOWS\TWAIN_32\A4S2_600\A4ui1
INI Old: C:\WINDOWS\TWAIN_32\A4S2_600\A4UI1
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
INI Sect: Scanning Desktop
INI Item: Path
INI Val: C:\MSCAN\Msoffice
INI Old: C:\MSCAN\Msoffice
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
INI Sect: A4S2INFO_600
INI Item: Language
INI Val: English
INI Old: English
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
INI Sect: A4S2INFO_600
INI Item: DSLanguage
INI Val: English
INI Old: English
INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
INI Sect: Slim New UI
INI Item: Language
INI Val: 0
INI Old: 0
File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\a4ui1_e.hlp

***********

 

[ken]

Archived from groups: alt.comp.periphs.scanner (More info?)

Raymond A. Chamberlin wrote:

> On Thu, 06 Jan 2005 14:00:41 GMT, Ken <user@domain.invalid> wrote:

>>>> I did a lot of clipping of old text.
>>

>
>
> Well, an email request to Mostek USA (automatically, I guess) got me
> instructions on exactly how to pull all the twains and twunks and
> reinstall new ones. Apparently I didn't have to uninstall the image
> program bundled with the scanner, as I did before. The only
> significant difference I could see between what these instructions
> said and what I did before to remove this stuff (I still don't
> understand whether their term 'scanner driver' refers to all these
> twains and twunks or something else.) was that I didn't disable my
> virus auto-protect program.

Rarely does the A/V program cause a problem, but if when loading
software does not give you the result you want, it is a wise thing to do.
Their instructions included getting a
> different "driver" from their Website, which I did -- '123ep22.exe',
> which came out in 1999. The one on my CD, that I used before, is
> 'd12epe22.exe'. Which one do you use?

I have used both of them, and I saw no real difference. I think my
current installation was from the CD.

So I installed this newer
> "driver". I note that it leaves out the 'Twain' folder, only
> installing the 'Twain32' folder into the Windows folder. Isn't the
> 'Twain' folder just for 16=bit-word machines anyhow?

Could be? I am looking at a Win 98 OS and that Dir IS there.
>
> So, OK, now I don't get a flag saying it can't detect the scanner, but
> I still get one that says it can't find 'twain.dll' in the Windows
> folder, although this file IS in the Windows folder. So I guess I'll
> uninstall that driver collection and reinstall the d12epe22 one per
> their instructions and see if that works.

It is hard to say exactly why you got that message, but it sounds like
it is a path problem. It could be that some remnant left behind is
incorrect and it cannot find the file because it is looking in the wrong
location.
>
> We can certainly forget all this discussion about when the scanner
> lamp should be ON though. At present, when it DOESN'T say it can't
> find the scanner, that light still does NOT go on and off with the
> tray icon; it's ALWAYS ON. If it does in your case, it must be that
> units having some ranges of serial
> do that, while others don't.

I doubt that. But it doesn't matter until we get your scanner working.
Then we will see if this is true.
>
>
>>>The power input at the scanner's main board measures 15 v.
>>
>> That is correct for the wall wart.
>>
>>>

>
>>>I located two components on the main board that appeared to be power
>>>regulators. I don't know their pinouts, but the only pins that
>>>measured significant voltages other than 15 v showed 3 and 12 v,
>>>respectively.
>>
>> One of the outside pins (the left one if I recall correctly, but don't
>>hold me to this) should be the input voltage. In this case, 15v. The
>>center pin is Ground. The right terminal is the output voltage, 12v.
>>You might not be placing your common lead of your DVM to true ground
>>when you measured the center terminal. Sometimes these circuits do not
>>use the same ground as your computer uses.
>>
>> The other regulator should work the same way, but the output should be
>>+5v. (I think) The marking on the regulators should read something
>>like 9805 and 9812 indicating the +5 and +12 volt output.
>
>
> I don't think there's any problem there. I measured with respect to
> the INPUT power-cable ground. I measured the +12 and +3 on different
> pins relative to the same physical start of pin count. The other
> non-15-v pins on the two regulators had very low voltages. There are
> no markings on the regulators.

Most of the time there are, but if you say there are not, then so be
it. You can generally tell what it might be by the voltage rating of
the caps tied to their output. That is, if the caps are rated at 10
volts, then the output of the regulator is probably in the neighborhood
of 5 volts. If the caps are rated 16-25 volts, the regulator is
probably no larger than +12. Most designers place caps with voltage
ratings approx. twice the voltage used on the bus.

Again, I cannot say with certainty that there is an isolated ground,
but I CAN assure you that the +3v is WRONG! If my memory serves me
right, there is a +5 volt regulator used for the logic. The input lead
was +12v if I recall, and the output MUST be +5v. The center terminal
is GROUND. If it is reading +3v, then either your meter is not on the
same ground plain or your ground lead has opened for the regulator.

There are very few semiconductors that operate at less than 5 volts.
In fact, the cut over level is generally recognized as 1.6 volts. That
is a zero is close to ground and certainly never over .6 volts. A one
is never less than 1.6 volts and normally close to the supply voltage.
(This is a GENERAL statement and depends upon many factors including the
type of semiconductor material.)

If you are truly hanging on circuit ground with your meter's common
lead and measuring less than either +12 or +5 on the output of these
regulators, you have a problem. Certainly the center lead on the
regulator is ground, and should read 0 volts.
>
>



>>
>> If the software were NOT loaded properly, there should have been an
>>error message saying that a file was not found or could not load.
>>Nothing is 100%, but that would be the case most of the time.
>
>
> Whatever. Software types have no constraints. It's all
> seat-of-the-pants. It's all chaos to me.
>
>

>>
>> The text I posted is NOT a new file, but part of the one you >posted.
>>mtwm.ini
>
>
> I'm aware of that.
>
>
>> I would think much of that segment is not in your file of the
>>same name due to the scanner not being detected. I simply pasted it to
>>show you more was needed in that file besides the segment you cited.
>
>
> OK.
>
>

>>
>> If your setting in CMOS is bidirectional, that should be FINE.
>>Different computers have different settings and verbiage. It is just
>>important that it is able to communicate both ways, and either EPP, ECP
>>or Bidirectional will do that.
>>
>>>

>>
>> Hell, they would laugh at you right after you bought the scanner. All
>>they wanted to do with me is sell me a scanner. Two of the shipments
>>arrived broken and I had one hell of a time getting it straightened out.
>> There is NO WAY they will help you with this scanner.
>
>
> They (SoCal, USA) did once when my lamp burnt out and I wanted to know
> why it had to stay on all the time. Also, once when I downloaded and
> installed something that indicated it was for this model but wasn't.
> Maybe it was this very 1999 driver that isn't working for me.
>
>

>>>
>>>Ray
>>
>> I sort of enjoy challenges, since I am retired and have time for >them.
>> Even when I was a tech, I always viewed a problem as a puzzle. It was
>>like a game, in that the problem was hiding and my job was to find it.
>>True, there is frustration along the way, but it is also rewarding when
>>you succeed. You also become a LITTLE smarter in the process.
>
>
> Well, I got spoilt by playing design engineer. That was interesting;
> trying to figure out why somebody ELSE designed something some
> cockamany way never was fun for me. And software is pretty much
> however you can hack it out, and it was far too serial for my mind,
> even then -- and less memory-recording capability at present makes it
> worse. I needed to get in from the side of designs and tweak them a
> little (my stack was never that deep, for arbitrary stuff).
> Collecting the results of fixing all that arbitrary stuff isn't my
> idea of "smart"ness.
>
>
>> If I were you, I would first go back to your measurements of the
>>voltage regulators making sure of their values with respect to the
>>scanner ground. A good place to pick up ground would be on one of the
>>electrolytic's negative lead.
>
>
> Maybe I'll check that AFTER I try the original driver again, loaded
> exactly as per Mustek's instructions.

Nothing lost. I can assure you however that those measurements if
measure correctly are wrong. Make sure you measure them with reference
to circuit ground. Which MIGHT NOT be PS ground.
>
>
>>If they measured properly, I would assume
>>your scanner was OK. Next since it doesn't sound like you will test the
>>parallel port, I would COMPLETELY remove the software and load it again
>>making sure the scanner is powered up while doing so. Be sure to delete
>>the directories created by the current load of the software, because
>>removal of software sometimes keeps files such as INI files. That might
>>screw up your next installation.
>>
>> Finally, I saw your pasting of the install log in another message, but
>>the install log is probably of little value and hard to decipher. Try
>>the re-installation of the software as mentioned above.
>
>
> Herebelow is what is presently in several files:
>
> Ray
>
> In Twain.log:
>
> ************
>
> TWAIN_32.DLL - MESSAGE - CTwunk ::AppInitialize - Reset Log
>
> TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Starting Thunker
>
> TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Startup Complete
> To Twain
> TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Received Startup
> Complete From Thunker
>
> TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Posting Close To
> Thunker
>
> TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Shutdown Complete
> To Twain
> TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Received Shutdown
> Complete From Thunker
>
>
> ************
>
> In mtwm.ini:
>
> ************
>
> [Scanner]
> TwainDS=scanobj.ds
> ScanDll=scanobj.dll
> DevDll=spicall.dll
> FilterDLL=filter.dll
> UIProg=ui.exe
>
> [CaseInfo]
> SettingSectionName=1200 III EP
> DSSectionName=A4S2INFO_600
> NewSetting=1
> UsePrivateSettingFile=1
>
> [A4S2INFO_600]
> Language=English
> DSLanguage=English
> Brand=Mustek
> DSName=1200 III EP
> UITitle="Mustek 1200 III EP "
> ScanSetting=NMLSPD
> Version=2.2
> DriverVer=2.2
> F/WVersion=NONE
> Interface=EPP/LPT2
> TestMode=0
> MemBufSize=256
> PreScanDpi=36
> PreScanWidth=306
> PreScanHeight=414
> TAPreScanWidth=216
> TAPreScanHeight=252
> PreScanFile=MSTC0000.BMP
> TAPreScanFile=MSTC0001.BMP
> X_OptiMaxRes=600
> Y_OptiMaxRes=1200
> WtimeTick=0
> Bbricon=0
> BcolorMatch=0
> CMTable=A32PCM.INI
> SupportResCount=13
> SupportRes=72 100 150 200 300 400 600 900 1200 2400 4800 7200 9600
> SupportCustomRes=0
> CustomRes=72 9600
> ResetRes=300
> ResetResIndex=4
> TextMaxRes=600
> TextMaxResIndex=6
> SlideInstall=1
>
> [Watch]
> Model=A4S2600_Watch
> LampStatus=1
> ActiveTime=433625
> GreenTime=20
> CoverDriven=1
> Timer3=500
> ShowStartup=1
> HasIcon=1
> HasCoverDriven=1
> HasStartup=1
> HasMustUI=1
>
> [EasyScan]
> Model=1200 III EP
> Package=cover sensor
> Ver=2.2
> Help=C:\WINDOWS\TWAIN_32\A4S2_600\A4ui1
>
> [Scanning Desktop]
> Path=C:\MSCAN\Msoffice
>
> [SupportSize]
> Count=3
> TACount=4
> ResetPaperIndex=0
> PaperName=A4 A5 Letter
> TAPaperName=35x40mm 60x60mm 60x70mm 101x127mm
> A4=826 1150
> A5=582 826
> Letter=850 1100
> 35x40mm=157 137
> 60x60mm=236 236
> 60x70mm=275 236
> 101x127mm=500 397
>
> [English]
> A4=A4
> A5=A5
> Letter=Letter
> 35x40mm=35x40mm
> 60x60mm=60x60mm
> 60x70mm=60x70mm
> 101x127mm=101x127mm
>
> [German]
> A4=DIN A4
> A5=DIN A5
> Letter=US-Letter
> 35x40mm=35x40mm
> 60x60mm=60x60mm
> 60x70mm=60x70mm
> 101x127mm=101x127mm
>
> [French]
> A4=A 4
> A5=A5
> Letter=Lettre US
> 35x40mm=35x40mm
> 60x60mm=60x60mm
> 60x70mm=60x70mm
> 101x127mm=101x127mm
>
> [Italian]
> A4=A4
> A5=A5
> Letter=Lettera
> 35x40mm=35x40mm
> 60x60mm=60x60mm
> 60x70mm=60x70mm
> 101x127mm=101x127mm
>
> [Spanish]
> A4=A4
> A5=A5
> Letter=Carta
> 35x40mm=35x40mm
> 60x60mm=60x60mm
> 60x70mm=60x70mm
> 101x127mm=101x127mm
>
> [Dutch]
> A4=A4
> A5=A5
> Letter=Letter
> 35x40mm=35x40mm
> 60x60mm=60x60mm
> 60x70mm=60x70mm
> 101x127mm=101x127mm
>
> [Russian]
> A4=A4
> A5=A5
> Letter=ðÉÓØÍÏ
> 35x40mm=35x40mm
> 60x60mm=60x60mm
> 60x70mm=60x70mm
> 101x127mm=101x127mm
>
> [Chinese]
> A4=A4
> A5=A5
> Letter=Letter
> 35x40mm=35x40mm
> 60x60mm=60x60mm
> 60x70mm=60x70mm
> 101x127mm=101x127mm
>
> [Japanese]
> A4=A4
> A5=A5
> Letter=ƒŒƒ^?[
> 35x40mm=35x40mm
> 60x60mm=60x60mm
> 60x70mm=60x70mm
> 101x127mm=101x127mm
>
> [Simple]
> A4=A4
> A5=A5
> Letter=Letter
> 35x40mm=35x40mm
> 60x60mm=60x60mm
> 60x70mm=60x70mm
> 101x127mm=101x127mm
>
> [Slim New UI]
> Language=0
> ScanMode=0
> ScanRes=300
> ResIndex=4
> PaperSize=3
> Frame=0 0 306 414
> Brightness=0 0 0 0
> Gamma=14 14 14 10
> Contrast=0 0 0 0
> DpiScale=0
> DeMoire=0
> FilterMode=0
> ColorBalance=1
> ColorMatch=0
> DescreenIndex=0
> InRulerUnit=0
> OutUnit=0
> CustomRes=0
>
> *************
>
> In Install.log
>
> *************
>
> *** Installation Started 1/6/5 23:48 ***
> Title:
> Source: C:\PROGRA~1\MUSTEK~2\123EP22.EXE
> File Copy: C:\WINDOWS\system\a4s2600.vxd
> Made Dir: C:\WINDOWS\TWAIN_32
> Made Dir: C:\WINDOWS\TWAIN_32\A4S2_600
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\spicall.dll
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
> File Copy: C:\WINDOWS\TWAIN.DLL
> File Copy: C:\WINDOWS\TWAIN_32.DLL
> File Copy: C:\WINDOWS\TWUNK_32.EXE
> File Copy: C:\WINDOWS\TWUNK_16.EXE
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Free_EXE.exe
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\filter.dll
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\lang_e.dll
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Scanobj.dll
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Scanobj.ds
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\WATCH.exe
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Lead52.dll
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\UI.EXE
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\ABOUT.BMP
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\LOGO0601.BMP
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\MSTC0001.BMP
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\MSTC0000.BMP
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: CaseInfo
> INI Item: NewSetting
> INI Val: 1
> INI Old: 1
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: CaseInfo
> INI Item: SettingSectionName
> INI Val: 1200 III EP
> INI Old: 1200 III EP
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: CaseInfo
> INI Item: DSSectionName
> INI Val: A4S2INFO_600
> INI Old: A4S2INFO_600
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: CaseInfo
> INI Item: UsePrivateSettingFile
> INI Val: 1
> INI Old: 1
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: DSLanguage
> INI Val: English
> INI Old: English
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: BRAND
> INI Val: Mustek
> INI Old: Mustek
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: DSNAME
> INI Val: 1200 III EP
> INI Old: 1200 III EP
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: UITITLE
> INI Val: "Mustek 1200 III EP "
> INI Old: Mustek 1200 III EP
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: Version
> INI Val: 2.2
> INI Old: V1.0
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: DriverVer
> INI Val: 2.2
> INI Old: 2.0
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: F/WVersion
> INI Val: NONE
> INI Old: None
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: ScanSetting
> INI Val: NMLSPD
> INI Old: NMLSPD
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: WtimeTick
> INI Val: 0
> INI Old: 60
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: ResetRes
> INI Val: 300
> INI Old: 300
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: A4S2INFO_600
> INI Item: ResetResIndex
> INI Val: 4
> INI Old: 4
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: EasyScan
> INI Item: Model
> INI Val: 1200 III EP
> INI Old: 1200 III EP
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: EasyScan
> INI Item: Package
> INI Val: cover sensor
> INI Old: cover sensor
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: EasyScan
> INI Item: Ver
> INI Val: 2.2
> INI Old: Ver1.6
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: EasyScan
> INI Item: Help
> INI Val: C:\WINDOWS\TWAIN_32\A4S2_600\A4ui1
> INI Old: C:\WINDOWS\TWAIN_32\A4S2_600\A4UI1
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
> INI Sect: Scanning Desktop
> INI Item: Path
> INI Val: C:\MSCAN\Msoffice
> INI Old: C:\MSCAN\Msoffice
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
> INI Sect: A4S2INFO_600
> INI Item: Language
> INI Val: English
> INI Old: English
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
> INI Sect: A4S2INFO_600
> INI Item: DSLanguage
> INI Val: English
> INI Old: English
> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
> INI Sect: Slim New UI
> INI Item: Language
> INI Val: 0
> INI Old: 0
> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\a4ui1_e.hlp
>
> ***********

To be honest with you, it is difficult to decipher exactly what all
that means. I will attempt after you take your voltage readings and
they prove correct. Error messages don't mean much if the hardware does
not work.

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

Top post because of so "stuff".

Your TWAIN.LOG shows that the TWAIN interface worked correctly.
I woud guess that the software is working and you have a hardware problem
with the scanner.

One other thing, If you have any virus software on your computer, Disable it
and remove all previous attempts to install. Then Install the software again
without the virus scanner running.
--
CSM1
http://www.carlmcmillan.com
--

"Ken" <user@domain.invalid> wrote in message
news:UXwDd.76323$uM5.68724@bgtnsc05-news.ops.worldnet.att.net...
> Raymond A. Chamberlin wrote:
>
>> On Thu, 06 Jan 2005 14:00:41 GMT, Ken <user@domain.invalid> wrote:
>
>>>>> I did a lot of clipping of old text.
>>>
>
>>
>>
>> Well, an email request to Mostek USA (automatically, I guess) got me
>> instructions on exactly how to pull all the twains and twunks and
>> reinstall new ones. Apparently I didn't have to uninstall the image
>> program bundled with the scanner, as I did before. The only
>> significant difference I could see between what these instructions
>> said and what I did before to remove this stuff (I still don't
>> understand whether their term 'scanner driver' refers to all these
>> twains and twunks or something else.) was that I didn't disable my
>> virus auto-protect program.
>
> Rarely does the A/V program cause a problem, but if when loading software
> does not give you the result you want, it is a wise thing to do.
> Their instructions included getting a
>> different "driver" from their Website, which I did -- '123ep22.exe',
>> which came out in 1999. The one on my CD, that I used before, is
>> 'd12epe22.exe'. Which one do you use?
>
> I have used both of them, and I saw no real difference. I think my
> current installation was from the CD.
>
> So I installed this newer
>> "driver". I note that it leaves out the 'Twain' folder, only
>> installing the 'Twain32' folder into the Windows folder. Isn't the
>> 'Twain' folder just for 16=bit-word machines anyhow?
>
> Could be? I am looking at a Win 98 OS and that Dir IS there.
>>
>> So, OK, now I don't get a flag saying it can't detect the scanner, but
>> I still get one that says it can't find 'twain.dll' in the Windows
>> folder, although this file IS in the Windows folder. So I guess I'll
>> uninstall that driver collection and reinstall the d12epe22 one per
>> their instructions and see if that works.
>
> It is hard to say exactly why you got that message, but it sounds like it
> is a path problem. It could be that some remnant left behind is incorrect
> and it cannot find the file because it is looking in the wrong location.
>>
>> We can certainly forget all this discussion about when the scanner
>> lamp should be ON though. At present, when it DOESN'T say it can't
>> find the scanner, that light still does NOT go on and off with the
>> tray icon; it's ALWAYS ON. If it does in your case, it must be that
>> units having some ranges of serial do that, while others don't.
>
> I doubt that. But it doesn't matter until we get your scanner working.
> Then we will see if this is true.
>>
>>
>>>>The power input at the scanner's main board measures 15 v.
>>>
>>> That is correct for the wall wart.
>>>
>>>>
>
>>
>>>>I located two components on the main board that appeared to be power
>>>>regulators. I don't know their pinouts, but the only pins that
>>>>measured significant voltages other than 15 v showed 3 and 12 v,
>>>>respectively.
>>>
>>> One of the outside pins (the left one if I recall correctly, but don't
>>> hold me to this) should be the input voltage. In this case, 15v. The
>>> center pin is Ground. The right terminal is the output voltage, 12v.
>>> You might not be placing your common lead of your DVM to true ground
>>> when you measured the center terminal. Sometimes these circuits do not
>>> use the same ground as your computer uses.
>>>
>>> The other regulator should work the same way, but the output should be
>>> +5v. (I think) The marking on the regulators should read something
>>> like 9805 and 9812 indicating the +5 and +12 volt output.
>>
>>
>> I don't think there's any problem there. I measured with respect to
>> the INPUT power-cable ground. I measured the +12 and +3 on different
>> pins relative to the same physical start of pin count. The other
>> non-15-v pins on the two regulators had very low voltages. There are
>> no markings on the regulators.
>
> Most of the time there are, but if you say there are not, then so be it.
> You can generally tell what it might be by the voltage rating of the caps
> tied to their output. That is, if the caps are rated at 10 volts, then
> the output of the regulator is probably in the neighborhood of 5 volts.
> If the caps are rated 16-25 volts, the regulator is probably no larger
> than +12. Most designers place caps with voltage ratings approx. twice
> the voltage used on the bus.
>
> Again, I cannot say with certainty that there is an isolated ground, but I
> CAN assure you that the +3v is WRONG! If my memory serves me right, there
> is a +5 volt regulator used for the logic. The input lead was +12v if I
> recall, and the output MUST be +5v. The center terminal is GROUND. If it
> is reading +3v, then either your meter is not on the same ground plain or
> your ground lead has opened for the regulator.
>
> There are very few semiconductors that operate at less than 5 volts. In
> fact, the cut over level is generally recognized as 1.6 volts. That is a
> zero is close to ground and certainly never over .6 volts. A one is never
> less than 1.6 volts and normally close to the supply voltage. (This is a
> GENERAL statement and depends upon many factors including the type of
> semiconductor material.)
>
> If you are truly hanging on circuit ground with your meter's common lead
> and measuring less than either +12 or +5 on the output of these
> regulators, you have a problem. Certainly the center lead on the
> regulator is ground, and should read 0 volts.
>>
>>
>
>
>
>>>
>>> If the software were NOT loaded properly, there should have been an
>>> error message saying that a file was not found or could not load.
>>> Nothing is 100%, but that would be the case most of the time.
>>
>>
>> Whatever. Software types have no constraints. It's all
>> seat-of-the-pants. It's all chaos to me.
>>
>>
>
>>>
>>> The text I posted is NOT a new file, but part of the one you >posted.
>>> mtwm.ini
>>
>>
>> I'm aware of that.
>>
>>
>>> I would think much of that segment is not in your file of the same name
>>> due to the scanner not being detected. I simply pasted it to show you
>>> more was needed in that file besides the segment you cited.
>>
>>
>> OK.
>>
>>
>
>>>
>>> If your setting in CMOS is bidirectional, that should be FINE. Different
>>> computers have different settings and verbiage. It is just important
>>> that it is able to communicate both ways, and either EPP, ECP or
>>> Bidirectional will do that.
>>>
>>>>
>
>>>
>>> Hell, they would laugh at you right after you bought the scanner. All
>>> they wanted to do with me is sell me a scanner. Two of the shipments
>>> arrived broken and I had one hell of a time getting it straightened out.
>>> There is NO WAY they will help you with this scanner.
>>
>>
>> They (SoCal, USA) did once when my lamp burnt out and I wanted to know
>> why it had to stay on all the time. Also, once when I downloaded and
>> installed something that indicated it was for this model but wasn't.
>> Maybe it was this very 1999 driver that isn't working for me.
>>
>
>>>>
>>>>Ray
>>>
>>> I sort of enjoy challenges, since I am retired and have time for >them.
>>> Even when I was a tech, I always viewed a problem as a puzzle. It was
>>> like a game, in that the problem was hiding and my job was to find it.
>>> True, there is frustration along the way, but it is also rewarding when
>>> you succeed. You also become a LITTLE smarter in the process.
>>
>>
>> Well, I got spoilt by playing design engineer. That was interesting;
>> trying to figure out why somebody ELSE designed something some
>> cockamany way never was fun for me. And software is pretty much
>> however you can hack it out, and it was far too serial for my mind,
>> even then -- and less memory-recording capability at present makes it
>> worse. I needed to get in from the side of designs and tweak them a
>> little (my stack was never that deep, for arbitrary stuff).
>> Collecting the results of fixing all that arbitrary stuff isn't my
>> idea of "smart"ness.
>>
>>
>>> If I were you, I would first go back to your measurements of the voltage
>>> regulators making sure of their values with respect to the scanner
>>> ground. A good place to pick up ground would be on one of the
>>> electrolytic's negative lead.
>>
>>
>> Maybe I'll check that AFTER I try the original driver again, loaded
>> exactly as per Mustek's instructions.
>
> Nothing lost. I can assure you however that those measurements if measure
> correctly are wrong. Make sure you measure them with reference to circuit
> ground. Which MIGHT NOT be PS ground.
>>
>>
>>>If they measured properly, I would assume your scanner was OK. Next
>>>since it doesn't sound like you will test the parallel port, I would
>>>COMPLETELY remove the software and load it again making sure the scanner
>>>is powered up while doing so. Be sure to delete the directories created
>>>by the current load of the software, because removal of software
>>>sometimes keeps files such as INI files. That might screw up your next
>>>installation.
>>>
>>> Finally, I saw your pasting of the install log in another message, but
>>> the install log is probably of little value and hard to decipher. Try
>>> the re-installation of the software as mentioned above.
>>
>>
>> Herebelow is what is presently in several files:
>>
>> Ray
>>
>> In Twain.log:
>>
>> ************
>>
>> TWAIN_32.DLL - MESSAGE - CTwunk ::AppInitialize - Reset Log
>>
>> TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Starting Thunker
>>
>> TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Startup Complete
>> To Twain
>> TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Received Startup
>> Complete From Thunker
>>
>> TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Posting Close To
>> Thunker
>>
>> TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Shutdown Complete
>> To Twain
>> TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Received Shutdown
>> Complete From Thunker
>>
>>
>> ************
>>
>> In mtwm.ini:
>>
>> ************
>>
>> [Scanner]
>> TwainDS=scanobj.ds
>> ScanDll=scanobj.dll
>> DevDll=spicall.dll
>> FilterDLL=filter.dll
>> UIProg=ui.exe
>>
>> [CaseInfo]
>> SettingSectionName=1200 III EP
>> DSSectionName=A4S2INFO_600
>> NewSetting=1
>> UsePrivateSettingFile=1
>>
>> [A4S2INFO_600]
>> Language=English
>> DSLanguage=English
>> Brand=Mustek
>> DSName=1200 III EP
>> UITitle="Mustek 1200 III EP "
>> ScanSetting=NMLSPD
>> Version=2.2
>> DriverVer=2.2
>> F/WVersion=NONE
>> Interface=EPP/LPT2
>> TestMode=0
>> MemBufSize=256
>> PreScanDpi=36
>> PreScanWidth=306
>> PreScanHeight=414
>> TAPreScanWidth=216
>> TAPreScanHeight=252
>> PreScanFile=MSTC0000.BMP
>> TAPreScanFile=MSTC0001.BMP
>> X_OptiMaxRes=600
>> Y_OptiMaxRes=1200
>> WtimeTick=0
>> Bbricon=0
>> BcolorMatch=0
>> CMTable=A32PCM.INI
>> SupportResCount=13
>> SupportRes=72 100 150 200 300 400 600 900 1200 2400 4800 7200 9600
>> SupportCustomRes=0
>> CustomRes=72 9600
>> ResetRes=300
>> ResetResIndex=4
>> TextMaxRes=600
>> TextMaxResIndex=6
>> SlideInstall=1
>>
>> [Watch]
>> Model=A4S2600_Watch
>> LampStatus=1
>> ActiveTime=433625
>> GreenTime=20
>> CoverDriven=1
>> Timer3=500
>> ShowStartup=1
>> HasIcon=1
>> HasCoverDriven=1
>> HasStartup=1
>> HasMustUI=1
>>
>> [EasyScan]
>> Model=1200 III EP
>> Package=cover sensor
>> Ver=2.2
>> Help=C:\WINDOWS\TWAIN_32\A4S2_600\A4ui1
>>
>> [Scanning Desktop]
>> Path=C:\MSCAN\Msoffice
>>
>> [SupportSize]
>> Count=3
>> TACount=4
>> ResetPaperIndex=0
>> PaperName=A4 A5 Letter
>> TAPaperName=35x40mm 60x60mm 60x70mm 101x127mm A4=826 1150
>> A5=582 826
>> Letter=850 1100
>> 35x40mm=157 137
>> 60x60mm=236 236
>> 60x70mm=275 236
>> 101x127mm=500 397
>>
>> [English]
>> A4=A4
>> A5=A5
>> Letter=Letter
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [German]
>> A4=DIN A4 A5=DIN A5
>> Letter=US-Letter 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [French]
>> A4=A 4
>> A5=A5
>> Letter=Lettre US
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Italian]
>> A4=A4
>> A5=A5
>> Letter=Lettera
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Spanish]
>> A4=A4
>> A5=A5
>> Letter=Carta
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Dutch]
>> A4=A4
>> A5=A5
>> Letter=Letter
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Russian]
>> A4=A4
>> A5=A5
>> Letter=ðÉÓØÍÏ
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Chinese]
>> A4=A4
>> A5=A5
>> Letter=Letter
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Japanese]
>> A4=A4
>> A5=A5
>> Letter=ƒŒƒ^?[
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Simple]
>> A4=A4
>> A5=A5
>> Letter=Letter
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Slim New UI]
>> Language=0
>> ScanMode=0
>> ScanRes=300
>> ResIndex=4
>> PaperSize=3
>> Frame=0 0 306 414
>> Brightness=0 0 0 0
>> Gamma=14 14 14 10
>> Contrast=0 0 0 0
>> DpiScale=0
>> DeMoire=0
>> FilterMode=0
>> ColorBalance=1
>> ColorMatch=0
>> DescreenIndex=0
>> InRulerUnit=0
>> OutUnit=0
>> CustomRes=0
>>
>> *************
>>
>> In Install.log
>>
>> *************
>>
>> *** Installation Started 1/6/5 23:48 ***
>> Title: Source: C:\PROGRA~1\MUSTEK~2\123EP22.EXE
>> File Copy: C:\WINDOWS\system\a4s2600.vxd
>> Made Dir: C:\WINDOWS\TWAIN_32
>> Made Dir: C:\WINDOWS\TWAIN_32\A4S2_600
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\spicall.dll
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
>> File Copy: C:\WINDOWS\TWAIN.DLL
>> File Copy: C:\WINDOWS\TWAIN_32.DLL
>> File Copy: C:\WINDOWS\TWUNK_32.EXE
>> File Copy: C:\WINDOWS\TWUNK_16.EXE
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Free_EXE.exe
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\filter.dll
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\lang_e.dll
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Scanobj.dll
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Scanobj.ds
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\WATCH.exe
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Lead52.dll
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\UI.EXE
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\ABOUT.BMP
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\LOGO0601.BMP
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\MSTC0001.BMP
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\MSTC0000.BMP
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: CaseInfo
>> INI Item: NewSetting
>> INI Val: 1
>> INI Old: 1
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: CaseInfo
>> INI Item: SettingSectionName
>> INI Val: 1200 III EP
>> INI Old: 1200 III EP
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: CaseInfo
>> INI Item: DSSectionName
>> INI Val: A4S2INFO_600
>> INI Old: A4S2INFO_600
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: CaseInfo
>> INI Item: UsePrivateSettingFile
>> INI Val: 1
>> INI Old: 1
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: DSLanguage
>> INI Val: English
>> INI Old: English
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: BRAND
>> INI Val: Mustek
>> INI Old: Mustek
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: DSNAME
>> INI Val: 1200 III EP
>> INI Old: 1200 III EP
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: UITITLE
>> INI Val: "Mustek 1200 III EP "
>> INI Old: Mustek 1200 III EP INI File:
>> C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: Version
>> INI Val: 2.2
>> INI Old: V1.0
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: DriverVer
>> INI Val: 2.2
>> INI Old: 2.0
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: F/WVersion
>> INI Val: NONE
>> INI Old: None
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: ScanSetting
>> INI Val: NMLSPD
>> INI Old: NMLSPD
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: WtimeTick
>> INI Val: 0
>> INI Old: 60
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: ResetRes
>> INI Val: 300
>> INI Old: 300
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: ResetResIndex
>> INI Val: 4
>> INI Old: 4
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: EasyScan
>> INI Item: Model
>> INI Val: 1200 III EP
>> INI Old: 1200 III EP
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: EasyScan
>> INI Item: Package
>> INI Val: cover sensor
>> INI Old: cover sensor
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: EasyScan
>> INI Item: Ver
>> INI Val: 2.2
>> INI Old: Ver1.6
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: EasyScan
>> INI Item: Help
>> INI Val: C:\WINDOWS\TWAIN_32\A4S2_600\A4ui1
>> INI Old: C:\WINDOWS\TWAIN_32\A4S2_600\A4UI1
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: Scanning Desktop
>> INI Item: Path
>> INI Val: C:\MSCAN\Msoffice
>> INI Old: C:\MSCAN\Msoffice
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
>> INI Sect: A4S2INFO_600
>> INI Item: Language
>> INI Val: English
>> INI Old: English
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
>> INI Sect: A4S2INFO_600
>> INI Item: DSLanguage
>> INI Val: English
>> INI Old: English
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
>> INI Sect: Slim New UI
>> INI Item: Language
>> INI Val: 0
>> INI Old: 0
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\a4ui1_e.hlp
>>
>> ***********
>
> To be honest with you, it is difficult to decipher exactly what all that
> means. I will attempt after you take your voltage readings and they prove
> correct. Error messages don't mean much if the hardware does not work.

 

[ken]

Archived from groups: alt.comp.periphs.scanner (More info?)

Ken wrote:
> Raymond A. Chamberlin wrote:
>
>> On Thu, 06 Jan 2005 14:00:41 GMT, Ken <user@domain.invalid> wrote:
>
>
>>>>> I did a lot of clipping of old text.
>>>
>>>
>
>>
>>
>> Well, an email request to Mostek USA (automatically, I guess) got me
>> instructions on exactly how to pull all the twains and twunks and
>> reinstall new ones. Apparently I didn't have to uninstall the image
>> program bundled with the scanner, as I did before. The only
>> significant difference I could see between what these instructions
>> said and what I did before to remove this stuff (I still don't
>> understand whether their term 'scanner driver' refers to all these
>> twains and twunks or something else.) was that I didn't disable my
>> virus auto-protect program.
>
>
> Rarely does the A/V program cause a problem, but if when loading
> software does not give you the result you want, it is a wise thing to do.
> Their instructions included getting a
>
>> different "driver" from their Website, which I did -- '123ep22.exe',
>> which came out in 1999. The one on my CD, that I used before, is
>> 'd12epe22.exe'. Which one do you use?
>
>
> I have used both of them, and I saw no real difference. I think my
> current installation was from the CD.
>
> So I installed this newer
>
>> "driver". I note that it leaves out the 'Twain' folder, only
>> installing the 'Twain32' folder into the Windows folder. Isn't the
>> 'Twain' folder just for 16=bit-word machines anyhow?
>
>
> Could be? I am looking at a Win 98 OS and that Dir IS there.
>
>>
>> So, OK, now I don't get a flag saying it can't detect the scanner, but
>> I still get one that says it can't find 'twain.dll' in the Windows
>> folder, although this file IS in the Windows folder. So I guess I'll
>> uninstall that driver collection and reinstall the d12epe22 one per
>> their instructions and see if that works.
>
>
> It is hard to say exactly why you got that message, but it sounds
> like it is a path problem. It could be that some remnant left behind is
> incorrect and it cannot find the file because it is looking in the wrong
> location.
>
>>
>> We can certainly forget all this discussion about when the scanner
>> lamp should be ON though. At present, when it DOESN'T say it can't
>> find the scanner, that light still does NOT go on and off with the
>> tray icon; it's ALWAYS ON. If it does in your case, it must be that
>> units having some ranges of serial do that, while others don't.
>
>
> I doubt that. But it doesn't matter until we get your scanner
> working. Then we will see if this is true.
>
>>
>>
>>>> The power input at the scanner's main board measures 15 v.
>>>
>>>
>>> That is correct for the wall wart.
>>>
>>>>
>
>>
>>>> I located two components on the main board that appeared to be power
>>>> regulators. I don't know their pinouts, but the only pins that
>>>> measured significant voltages other than 15 v showed 3 and 12 v,
>>>> respectively.
>>>
>>>
>>> One of the outside pins (the left one if I recall correctly, but
>>> don't hold me to this) should be the input voltage. In this case,
>>> 15v. The center pin is Ground. The right terminal is the output
>>> voltage, 12v. You might not be placing your common lead of your DVM
>>> to true ground when you measured the center terminal. Sometimes
>>> these circuits do not use the same ground as your computer uses.
>>>
>>> The other regulator should work the same way, but the output
>>> should be +5v. (I think) The marking on the regulators should read
>>> something like 9805 and 9812 indicating the +5 and +12 volt output.
>>
>>
>>
>> I don't think there's any problem there. I measured with respect to
>> the INPUT power-cable ground. I measured the +12 and +3 on different
>> pins relative to the same physical start of pin count. The other
>> non-15-v pins on the two regulators had very low voltages. There are
>> no markings on the regulators.
>
>
> Most of the time there are, but if you say there are not, then so be
> it. You can generally tell what it might be by the voltage rating of
> the caps tied to their output. That is, if the caps are rated at 10
> volts, then the output of the regulator is probably in the neighborhood
> of 5 volts. If the caps are rated 16-25 volts, the regulator is
> probably no larger than +12. Most designers place caps with voltage
> ratings approx. twice the voltage used on the bus.
>
> Again, I cannot say with certainty that there is an isolated ground,
> but I CAN assure you that the +3v is WRONG! If my memory serves me
> right, there is a +5 volt regulator used for the logic. The input lead
> was +12v if I recall, and the output MUST be +5v. The center terminal
> is GROUND. If it is reading +3v, then either your meter is not on the
> same ground plain or your ground lead has opened for the regulator.
>
> There are very few semiconductors that operate at less than 5 volts.
> In fact, the cut over level is generally recognized as 1.6 volts. That
> is a zero is close to ground and certainly never over .6 volts. A one
> is never less than 1.6 volts and normally close to the supply voltage.
> (This is a GENERAL statement and depends upon many factors including the
> type of semiconductor material.)
>
> If you are truly hanging on circuit ground with your meter's common
> lead and measuring less than either +12 or +5 on the output of these
> regulators, you have a problem. Certainly the center lead on the
> regulator is ground, and should read 0 volts.

Here is a link for a graphic of the type regulator I believe is in the
scanner. http://www.nteinc.com/specs/900to999/pdf/nte960.pdf
I was wrong about the 9805 number, it is a 7805. (Had another brain
fart.) Notice however that the input voltage is on the left of the
device, ground is the center terminal, and the output is the left terminal.


>
>>
>>
>
>
>
>>>
>>> If the software were NOT loaded properly, there should have been
>>> an error message saying that a file was not found or could not load.
>>> Nothing is 100%, but that would be the case most of the time.
>>
>>
>>
>> Whatever. Software types have no constraints. It's all
>> seat-of-the-pants. It's all chaos to me.
>>
>>
>
>>>
>>> The text I posted is NOT a new file, but part of the one you
>>> >posted. mtwm.ini
>>
>>
>>
>> I'm aware of that.
>>
>>
>>> I would think much of that segment is not in your file of the same
>>> name due to the scanner not being detected. I simply pasted it to
>>> show you more was needed in that file besides the segment you cited.
>>
>>
>>
>> OK.
>>
>>
>
>>>
>>> If your setting in CMOS is bidirectional, that should be FINE.
>>> Different computers have different settings and verbiage. It is just
>>> important that it is able to communicate both ways, and either EPP,
>>> ECP or Bidirectional will do that.
>>>
>>>>
>
>>>
>>> Hell, they would laugh at you right after you bought the
>>> scanner. All they wanted to do with me is sell me a scanner. Two of
>>> the shipments arrived broken and I had one hell of a time getting it
>>> straightened out. There is NO WAY they will help you with this scanner.
>>
>>
>>
>> They (SoCal, USA) did once when my lamp burnt out and I wanted to know
>> why it had to stay on all the time. Also, once when I downloaded and
>> installed something that indicated it was for this model but wasn't.
>> Maybe it was this very 1999 driver that isn't working for me.
>>
>>
>
>>>>
>>>> Ray
>>>
>>>
>>> I sort of enjoy challenges, since I am retired and have time for
>>> >them. Even when I was a tech, I always viewed a problem as a
>>> puzzle. It was like a game, in that the problem was hiding and my
>>> job was to find it. True, there is frustration along the way, but it
>>> is also rewarding when you succeed. You also become a LITTLE smarter
>>> in the process.
>>
>>
>>
>> Well, I got spoilt by playing design engineer. That was interesting;
>> trying to figure out why somebody ELSE designed something some
>> cockamany way never was fun for me. And software is pretty much
>> however you can hack it out, and it was far too serial for my mind,
>> even then -- and less memory-recording capability at present makes it
>> worse. I needed to get in from the side of designs and tweak them a
>> little (my stack was never that deep, for arbitrary stuff).
>> Collecting the results of fixing all that arbitrary stuff isn't my
>> idea of "smart"ness.
>>
>>
>>> If I were you, I would first go back to your measurements of the
>>> voltage regulators making sure of their values with respect to the
>>> scanner ground. A good place to pick up ground would be on one of
>>> the electrolytic's negative lead.
>>
>>
>>
>> Maybe I'll check that AFTER I try the original driver again, loaded
>> exactly as per Mustek's instructions.
>
>
> Nothing lost. I can assure you however that those measurements if
> measure correctly are wrong. Make sure you measure them with reference
> to circuit ground. Which MIGHT NOT be PS ground.
>
>>
>>
>>> If they measured properly, I would assume your scanner was OK. Next
>>> since it doesn't sound like you will test the parallel port, I would
>>> COMPLETELY remove the software and load it again making sure the
>>> scanner is powered up while doing so. Be sure to delete the
>>> directories created by the current load of the software, because
>>> removal of software sometimes keeps files such as INI files. That
>>> might screw up your next installation.
>>>
>>> Finally, I saw your pasting of the install log in another
>>> message, but the install log is probably of little value and hard to
>>> decipher. Try the re-installation of the software as mentioned above.
>>
>>
>>
>> Herebelow is what is presently in several files:
>>
>> Ray
>>
>> In Twain.log:
>>
>> ************
>>
>> TWAIN_32.DLL - MESSAGE - CTwunk ::AppInitialize - Reset Log
>>
>> TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Starting Thunker
>>
>> TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Startup Complete
>> To Twain
>> TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Received Startup
>> Complete From Thunker
>>
>> TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Posting Close To
>> Thunker
>>
>> TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Shutdown Complete
>> To Twain
>> TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Received Shutdown
>> Complete From Thunker
>>
>>
>> ************
>>
>> In mtwm.ini:
>>
>> ************
>>
>> [Scanner]
>> TwainDS=scanobj.ds
>> ScanDll=scanobj.dll
>> DevDll=spicall.dll
>> FilterDLL=filter.dll
>> UIProg=ui.exe
>>
>> [CaseInfo]
>> SettingSectionName=1200 III EP
>> DSSectionName=A4S2INFO_600
>> NewSetting=1
>> UsePrivateSettingFile=1
>>
>> [A4S2INFO_600]
>> Language=English
>> DSLanguage=English
>> Brand=Mustek
>> DSName=1200 III EP
>> UITitle="Mustek 1200 III EP "
>> ScanSetting=NMLSPD
>> Version=2.2
>> DriverVer=2.2
>> F/WVersion=NONE
>> Interface=EPP/LPT2
>> TestMode=0
>> MemBufSize=256
>> PreScanDpi=36
>> PreScanWidth=306
>> PreScanHeight=414
>> TAPreScanWidth=216
>> TAPreScanHeight=252
>> PreScanFile=MSTC0000.BMP
>> TAPreScanFile=MSTC0001.BMP
>> X_OptiMaxRes=600
>> Y_OptiMaxRes=1200
>> WtimeTick=0
>> Bbricon=0
>> BcolorMatch=0
>> CMTable=A32PCM.INI
>> SupportResCount=13
>> SupportRes=72 100 150 200 300 400 600 900 1200 2400 4800 7200 9600
>> SupportCustomRes=0
>> CustomRes=72 9600
>> ResetRes=300
>> ResetResIndex=4
>> TextMaxRes=600
>> TextMaxResIndex=6
>> SlideInstall=1
>>
>> [Watch]
>> Model=A4S2600_Watch
>> LampStatus=1
>> ActiveTime=433625
>> GreenTime=20
>> CoverDriven=1
>> Timer3=500
>> ShowStartup=1
>> HasIcon=1
>> HasCoverDriven=1
>> HasStartup=1
>> HasMustUI=1
>>
>> [EasyScan]
>> Model=1200 III EP
>> Package=cover sensor
>> Ver=2.2
>> Help=C:\WINDOWS\TWAIN_32\A4S2_600\A4ui1
>>
>> [Scanning Desktop]
>> Path=C:\MSCAN\Msoffice
>>
>> [SupportSize]
>> Count=3
>> TACount=4
>> ResetPaperIndex=0
>> PaperName=A4 A5 Letter
>> TAPaperName=35x40mm 60x60mm 60x70mm 101x127mm A4=826 1150
>> A5=582 826
>> Letter=850 1100
>> 35x40mm=157 137
>> 60x60mm=236 236
>> 60x70mm=275 236
>> 101x127mm=500 397
>>
>> [English]
>> A4=A4
>> A5=A5
>> Letter=Letter
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [German]
>> A4=DIN A4 A5=DIN A5
>> Letter=US-Letter 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [French]
>> A4=A 4
>> A5=A5
>> Letter=Lettre US
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Italian]
>> A4=A4
>> A5=A5
>> Letter=Lettera
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Spanish]
>> A4=A4
>> A5=A5
>> Letter=Carta
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Dutch]
>> A4=A4
>> A5=A5
>> Letter=Letter
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Russian]
>> A4=A4
>> A5=A5
>> Letter=ðÉÓØÍÏ
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Chinese]
>> A4=A4
>> A5=A5
>> Letter=Letter
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Japanese]
>> A4=A4
>> A5=A5
>> Letter=ƒŒƒ^?[
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Simple]
>> A4=A4
>> A5=A5
>> Letter=Letter
>> 35x40mm=35x40mm
>> 60x60mm=60x60mm
>> 60x70mm=60x70mm
>> 101x127mm=101x127mm
>>
>> [Slim New UI]
>> Language=0
>> ScanMode=0
>> ScanRes=300
>> ResIndex=4
>> PaperSize=3
>> Frame=0 0 306 414
>> Brightness=0 0 0 0
>> Gamma=14 14 14 10
>> Contrast=0 0 0 0
>> DpiScale=0
>> DeMoire=0
>> FilterMode=0
>> ColorBalance=1
>> ColorMatch=0
>> DescreenIndex=0
>> InRulerUnit=0
>> OutUnit=0
>> CustomRes=0
>>
>> *************
>>
>> In Install.log
>>
>> *************
>>
>> *** Installation Started 1/6/5 23:48 ***
>> Title: Source: C:\PROGRA~1\MUSTEK~2\123EP22.EXE
>> File Copy: C:\WINDOWS\system\a4s2600.vxd
>> Made Dir: C:\WINDOWS\TWAIN_32
>> Made Dir: C:\WINDOWS\TWAIN_32\A4S2_600
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\spicall.dll
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
>> File Copy: C:\WINDOWS\TWAIN.DLL
>> File Copy: C:\WINDOWS\TWAIN_32.DLL
>> File Copy: C:\WINDOWS\TWUNK_32.EXE
>> File Copy: C:\WINDOWS\TWUNK_16.EXE
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Free_EXE.exe
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\filter.dll
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\lang_e.dll
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Scanobj.dll
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Scanobj.ds
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\WATCH.exe
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\Lead52.dll
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\UI.EXE
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\ABOUT.BMP
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\LOGO0601.BMP
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\MSTC0001.BMP
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\MSTC0000.BMP
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: CaseInfo
>> INI Item: NewSetting
>> INI Val: 1
>> INI Old: 1
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: CaseInfo
>> INI Item: SettingSectionName
>> INI Val: 1200 III EP
>> INI Old: 1200 III EP
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: CaseInfo
>> INI Item: DSSectionName
>> INI Val: A4S2INFO_600
>> INI Old: A4S2INFO_600
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: CaseInfo
>> INI Item: UsePrivateSettingFile
>> INI Val: 1
>> INI Old: 1
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: DSLanguage
>> INI Val: English
>> INI Old: English
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: BRAND
>> INI Val: Mustek
>> INI Old: Mustek
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: DSNAME
>> INI Val: 1200 III EP
>> INI Old: 1200 III EP
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: UITITLE
>> INI Val: "Mustek 1200 III EP "
>> INI Old: Mustek 1200 III EP INI File:
>> C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: Version
>> INI Val: 2.2
>> INI Old: V1.0
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: DriverVer
>> INI Val: 2.2
>> INI Old: 2.0
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: F/WVersion
>> INI Val: NONE
>> INI Old: None
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: ScanSetting
>> INI Val: NMLSPD
>> INI Old: NMLSPD
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: WtimeTick
>> INI Val: 0
>> INI Old: 60
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: ResetRes
>> INI Val: 300
>> INI Old: 300
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: A4S2INFO_600
>> INI Item: ResetResIndex
>> INI Val: 4
>> INI Old: 4
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: EasyScan
>> INI Item: Model
>> INI Val: 1200 III EP
>> INI Old: 1200 III EP
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: EasyScan
>> INI Item: Package
>> INI Val: cover sensor
>> INI Old: cover sensor
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: EasyScan
>> INI Item: Ver
>> INI Val: 2.2
>> INI Old: Ver1.6
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: EasyScan
>> INI Item: Help
>> INI Val: C:\WINDOWS\TWAIN_32\A4S2_600\A4ui1
>> INI Old: C:\WINDOWS\TWAIN_32\A4S2_600\A4UI1
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\MTWM.INI
>> INI Sect: Scanning Desktop
>> INI Item: Path
>> INI Val: C:\MSCAN\Msoffice
>> INI Old: C:\MSCAN\Msoffice
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
>> INI Sect: A4S2INFO_600
>> INI Item: Language
>> INI Val: English
>> INI Old: English
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
>> INI Sect: A4S2INFO_600
>> INI Item: DSLanguage
>> INI Val: English
>> INI Old: English
>> INI File: C:\WINDOWS\TWAIN_32\A4S2_600\mtwm.ini
>> INI Sect: Slim New UI
>> INI Item: Language
>> INI Val: 0
>> INI Old: 0
>> File Copy: C:\WINDOWS\TWAIN_32\A4S2_600\a4ui1_e.hlp
>>
>> ***********
>
>
> To be honest with you, it is difficult to decipher exactly what all
> that means. I will attempt after you take your voltage readings and
> they prove correct. Error messages don't mean much if the hardware does
> not work.

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

To Ken and CSM1: See interleaved below:

On Fri, 07 Jan 2005 20:29:51 GMT, Ken <user@domain.invalid> wrote:

>Ken wrote:
>> Raymond A. Chamberlin wrote:
>>
>>> On Thu, 06 Jan 2005 14:00:41 GMT, Ken <user@domain.invalid> wrote:
>>
>>
>>>>>> I did a lot of clipping of old text.
>>>>
>>>>
>>
>>>
>>>
>>> Well, an email request to Mostek USA (automatically, I guess) got me
>>> instructions on exactly how to pull all the twains and twunks and
>>> reinstall new ones. Apparently I didn't have to uninstall the image
>>> program bundled with the scanner, as I did before. The only
>>> significant difference I could see between what these instructions
>>> said and what I did before to remove this stuff (I still don't
>>> understand whether their term 'scanner driver' refers to all these
>>> twains and twunks or something else.) was that I didn't disable my
>>> virus auto-protect program.
>>
>>
>> Rarely does the A/V program cause a problem, but if when loading
>> software does not give you the result you want, it is a wise thing to do.
>> Their instructions included getting a
>>
>>> different "driver" from their Website, which I did -- '123ep22.exe',
>>> which came out in 1999. The one on my CD, that I used before, is
>>> 'd12epe22.exe'. Which one do you use?
>>
>>
>> I have used both of them, and I saw no real difference. I think my
>> current installation was from the CD.

Yes, the one from the CD does the same thing now -- asks for twain.dll
but no other flags.

>> So I installed this newer
>>
>>> "driver". I note that it leaves out the 'Twain' folder, only
>>> installing the 'Twain32' folder into the Windows folder. Isn't the
>>> 'Twain' folder just for 16=bit-word machines anyhow?
>>
>>
>> Could be? I am looking at a Win 98 OS and that Dir IS there.

Well the CD allows one to set the scanner up for Win 3.1
alternatively.

>>> So, OK, now I don't get a flag saying it can't detect the scanner, but
>>> I still get one that says it can't find 'twain.dll' in the Windows
>>> folder, although this file IS in the Windows folder. So I guess I'll
>>> uninstall that driver collection and reinstall the d12epe22 one per
>>> their instructions and see if that works.
>>
>>
>> It is hard to say exactly why you got that message, but it sounds
>> like it is a path problem. It could be that some remnant left behind is
>> incorrect and it cannot find the file because it is looking in the wrong
>> location.
>>
>>>
>>> We can certainly forget all this discussion about when the scanner
>>> lamp should be ON though. At present, when it DOESN'T say it can't
>>> find the scanner, that light still does NOT go on and off with the
>>> tray icon; it's ALWAYS ON. If it does in your case, it must be that
>>> units having some ranges of serial do that, while others don't.
>>
>>
>> I doubt that. But it doesn't matter until we get your scanner
>> working. Then we will see if this is true.
>>
>>>
>>>
>>>>> The power input at the scanner's main board measures 15 v.
>>>>
>>>>
>>>> That is correct for the wall wart.
>>>>
>>>>>
>>
>>>
>>>>> I located two components on the main board that appeared to be power
>>>>> regulators. I don't know their pinouts, but the only pins that
>>>>> measured significant voltages other than 15 v showed 3 and 12 v,
>>>>> respectively.
>>>>
>>>>
>>>> One of the outside pins (the left one if I recall correctly, but
>>>> don't hold me to this) should be the input voltage. In this case,
>>>> 15v. The center pin is Ground. The right terminal is the output
>>>> voltage, 12v. You might not be placing your common lead of your DVM
>>>> to true ground when you measured the center terminal. Sometimes
>>>> these circuits do not use the same ground as your computer uses.
>>>>
>>>> The other regulator should work the same way, but the output
>>>> should be +5v. (I think) The marking on the regulators should read
>>>> something like 9805 and 9812 indicating the +5 and +12 volt output.
>>>
>>>
>>>
>>> I don't think there's any problem there. I measured with respect to
>>> the INPUT power-cable ground. I measured the +12 and +3 on different
>>> pins relative to the same physical start of pin count. The other
>>> non-15-v pins on the two regulators had very low voltages. There are
>>> no markings on the regulators.
>>
>>
>> Most of the time there are, but if you say there are not, then so be
>> it.

My bad. [red-face emoticon] 7805 and 7812; see above. Not the first
time I've been a bad tech. I could blame my glaucoma, but it was
really lack of ambition to get the right tools.

>> You can generally tell what it might be by the voltage rating of
>> the caps tied to their output. That is, if the caps are rated at 10
>> volts, then the output of the regulator is probably in the neighborhood
>> of 5 volts. If the caps are rated 16-25 volts, the regulator is
>> probably no larger than +12. Most designers place caps with voltage
>> ratings approx. twice the voltage used on the bus.
>>
>> Again, I cannot say with certainty that there is an isolated ground,
>> but I CAN assure you that the +3v is WRONG! If my memory serves me
>> right, there is a +5 volt regulator used for the logic. The input lead
>> was +12v if I recall, and the output MUST be +5v. The center terminal
>> is GROUND. If it is reading +3v, then either your meter is not on the
>> same ground plain or your ground lead has opened for the regulator.

The 12-v regulator is OK -- +15 v in, +12 v out.

The 5-v regulator reads thus:

+15 v --11-ohm/2(?)-w res--o--REG--o---- +0.5 v
| |
47 µ / 25v 100 µ / 10 v
| |
gnd gnd

The above circuit may be rather scrambled when you get it. Hope not.
The aluminum electrolytics, the regular and the resistor are all quite
hot, as is a nearby AIC 1563CN high-efficiency DC/DC converter.
( http://www.scaner.by.ru/data.htm if your Russian is fluent. ) So
I'm not sure how many of these components are bad. Maybe just the
output electrolytic? Possibly something on beyond that. I can't find
those caps in my junk box, so I'll hit Radio Shack tomorrow.

>> There are very few semiconductors that operate at less than 5 volts.

Well, I guess any of that vintage. But there certainly are now a lot
that run on 3 v or so.

>> In fact, the cut over level

What is that?

>> is generally recognized as 1.6 volts. That
>> is a zero is close to ground and certainly never over .6 volts. A one
>> is never less than 1.6 volts and normally close to the supply voltage.
>> (This is a GENERAL statement and depends upon many factors including the
>> type of semiconductor material.)
>>
>> If you are truly hanging on circuit ground with your meter's common
>> lead and measuring less than either +12 or +5 on the output of these
>> regulators, you have a problem. Certainly the center lead on the
>> regulator is ground, and should read 0 volts.

Yes.

> Here is a link for a graphic of the type regulator I believe is in the
>scanner. http://www.nteinc.com/specs/900to999/pdf/nte960.pdf
> I was wrong about the 9805 number, it is a 7805. (Had another brain
>fart.) Notice however that the input voltage is on the left of the
>device, ground is the center terminal, and the output is the left terminal.

Yes, you're right, a 7805 and a 7812. With the board out where I can
get a flashlight on the regulators at just the right angle, and using
a magnifying glass, I can read these old conventional numbers of
positive voltage regulators on them.

<SNIP>

 

[ken]

Archived from groups: alt.comp.periphs.scanner (More info?)

Raymond A. Chamberlin wrote:
> To Ken and CSM1: See interleaved below:
>
> On Fri, 07 Jan 2005 20:29:51 GMT, Ken <user@domain.invalid> wrote:
>
>

>
>
> The 12-v regulator is OK -- +15 v in, +12 v out.
>
> The 5-v regulator reads thus:
>
> +15 v --11-ohm/2(?)-w res--o--REG--o---- +0.5 v
> | |
> 47 µ / 25v 100 µ / 10 v
> | |
> gnd gnd
>
> The above circuit may be rather scrambled when you get it. Hope not.

Ray,

I am not sure I am reading your drawing correctly, but if you mean you
have .5 volts on the output, THAT IS A PROBLEM.
> The aluminum electrolytics, the regular and the resistor are all quite
> hot, as is a nearby AIC 1563CN high-efficiency DC/DC converter.

It will be very difficult to replace any of the logic circuits attached
to this +5 volt bus, but it is possible that a cap is leaking drawing
down your +5 volts. More likely, the regulator failed, but the only way
to tell is to lift some leads. I would first lift the output from the
regulator and measure it. If it is +5, then the problem is on the bus.
Using an Ohm meter and lifting leads from caps would be the next
easiest, then attack the other components if you choose.

For what it is worth, I repaired one of these scanners by replacing the
+5 regulator. Of course your results may vary!!!

> ( http://www.scaner.by.ru/data.htm if your Russian is fluent. ) So
> I'm not sure how many of these components are bad. Maybe just the
> output electrolytic? Possibly something on beyond that. I can't find
> those caps in my junk box, so I'll hit Radio Shack tomorrow.

Remember, if you do find it to be an electrolytic, you can replace it
with any voltage larger than the one installed and any capacitance
larger than the one installed. It is only a filter, so the capacitance
is NOT critical. Needless to say, observe the polarity.
>
>
>>> There are very few semiconductors that operate at less than 5 volts.
>
>
> Well, I guess any of that vintage. But there certainly are now a lot
> that run on 3 v or so.

There are, but they generally are more expensive than the +5 volt
variety. As circuits are designed to operate on lower voltages, they
are becoming more popular. This in turn causes them to become cheaper.
>
>
>>>In fact, the cut over level
>
>
> What is that?

It really becomes quite involved to explain, but simply stated, the
circuits are designed so that stray noise does NOT trigger them. Since
noise is unavoidable in most cases, the threshold is designed so that
only a signal over .6 volts will switch on a semiconductor. Therefore,
most of the time a signal of less than .6 volts is considered a zero,
and one greater than 1.6 is considered a one. The area in between these
levels were referred in my day as "No man's land." That is, the result
of such a voltage was not certain on a circuit. One could turn on,
while another might not.

Disclaimer: News groups are famous for some person who has little to
contribute to a topic jumping in to contradict what another has said.
The topic of logic circuits is long and complex. It also has many
exceptions, and that is why I even hesitate to start to explain the
cross over level topic. I DO NOT HAVE ALL THE ANSWERS!!! Perhaps this
might negate the need for someone to blast me???
>
>
>>>is generally recognized as 1.6 volts. That
>>>is a zero is close to ground and certainly never over .6 volts. A one
>>>is never less than 1.6 volts and normally close to the supply voltage.
>>>(This is a GENERAL statement and depends upon many factors including the
>>>type of semiconductor material.)
>>>
>>> If you are truly hanging on circuit ground with your meter's common
>>>lead and measuring less than either +12 or +5 on the output of these
>>>regulators, you have a problem. Certainly the center lead on the
>>>regulator is ground, and should read 0 volts.
>
>
> Yes.
>
>
>> Here is a link for a graphic of the type regulator I believe is in the
>>scanner. http://www.nteinc.com/specs/900to999/pdf/nte960.pdf
>> I was wrong about the 9805 number, it is a 7805. (Had another brain
>>fart.) Notice however that the input voltage is on the left of the
>>device, ground is the center terminal, and the output is the left terminal.
>
>
> Yes, you're right, a 7805 and a 7812. With the board out where I can
> get a flashlight on the regulators at just the right angle, and using
> a magnifying glass, I can read these old conventional numbers of
> positive voltage regulators on them.
>
> <SNIP>

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

On Sat, 08 Jan 2005 13:45:07 GMT, Ken <user@domain.invalid> wrote:

>Raymond A. Chamberlin wrote:
>> To Ken and CSM1: See interleaved below:
>>
>> On Fri, 07 Jan 2005 20:29:51 GMT, Ken <user@domain.invalid> wrote:
>>
>>
>
>>
>>
>> The 12-v regulator is OK -- +15 v in, +12 v out.
>>
>> The 5-v regulator reads thus:
>>
>> +15 v --11-ohm/2(?)-w res--o--REG--o---- +0.5 v
>> | |
>> 47 µ / 25v 100 µ / 10 v
>> | |
>> gnd gnd
>>
>> The above circuit may be rather scrambled when you get it. Hope not.
>
>Ray,
>
> I am not sure I am reading your drawing correctly, but if you mean you
>have .5 volts on the output, THAT IS A PROBLEM.

Yes, that's what I mean. And yes, that obviously is a problem.

>> The aluminum electrolytics, the regular and the resistor are all quite
>> hot, as is a nearby AIC 1563CN high-efficiency DC/DC converter.
>
> It will be very difficult to replace any of the logic circuits attached
>to this +5 volt bus, but it is possible that a cap is leaking drawing
>down your +5 volts. More likely, the regulator failed, but the only way
>to tell is to lift some leads. I would first lift the output from the
>regulator and measure it. If it is +5, then the problem is on the bus.
> Using an Ohm meter and lifting leads from caps would be the next
>easiest, then attack the other components if you choose.
>
> For what it is worth, I repaired one of these scanners by replacing the
>+5 regulator. Of course your results may vary!!!

Well, I overlooked a pair of tiny chip/surface-mount components on the
other side of the board, one on each side of the regulator to ground.
I would conclude they're either diodes or electrolytics. Do they
suppress high-frequency oscillations? They came after my
time-in-grade.

Anyhow, I yanked the two radial-lead caps and the regulator. All of
those appear fine -- as far as I can tell with a 20,000-ohm/v
ohmmeter. The chip jobby on the regulator input reads 3.3 ohm one way
and 20 ohms the other way (on the 20-ohms-at-center scale. The one on
the regulator output reads a dead short both ways on the same scale.
I assume the latter ist kaputt. Now, how the devil would I be able to
find out the specs of that component -- unless -- ha, ha -- Mostek
will tell me? Hey maybe they would send me a whole schematic. . .so I
could tell them how to make one that doesn't burn up, huh? I could
get a replacement mail-order chip thingy from Digi-Key, I guess.
Dunno what their minimum order is though.

BTW, the resistor I marked as 11 ohms reads 51 ohms cold. I said 11
ohms, because that seemed to be its color code -- but the first stripe
was a lighter brown than the second, so I was always supicious.
Apparently it used to be greeen. :-O

However, when I look at eBay or Craig's List, used and even new
scanners are a dime a dozen! I paid $133 (incl. tax and less rebate)
in San Francisco back in 1998. Craig's List has one of this model
(used of course) for $19 and eBay runs from $0.01 minimum bid on this
model, to $40 buy-it-now for a new, boxed-up Visioneer One Touch 5800
USB scanner. Is the latter any good?

Ray

>> ( http://www.scaner.by.ru/data.htm if your Russian is fluent. ) So
>> I'm not sure how many of these components are bad. Maybe just the
>> output electrolytic? Possibly something on beyond that. I can't find
>> those caps in my junk box, so I'll hit Radio Shack tomorrow.
>
> Remember, if you do find it to be an electrolytic, you can replace it
>with any voltage larger than the one installed and any capacitance
>larger than the one installed. It is only a filter, so the capacitance
>is NOT critical. Needless to say, observe the polarity.
>>
>>
>>>> There are very few semiconductors that operate at less than 5 volts.
>>
>>
>> Well, I guess any of that vintage. But there certainly are now a lot
>> that run on 3 v or so.
>
> There are, but they generally are more expensive than the +5 volt
>variety. As circuits are designed to operate on lower voltages, they
>are becoming more popular. This in turn causes them to become cheaper.
>>
>>
>>>>In fact, the cut over level
>>
>>
>> What is that?
>
> It really becomes quite involved to explain, but simply stated, the
>circuits are designed so that stray noise does NOT trigger them. Since
>noise is unavoidable in most cases, the threshold is designed so that
>only a signal over .6 volts will switch on a semiconductor. Therefore,
>most of the time a signal of less than .6 volts is considered a zero,
>and one greater than 1.6 is considered a one. The area in between these
>levels were referred in my day as "No man's land." That is, the result
>of such a voltage was not certain on a circuit. One could turn on,
>while another might not.
>
> Disclaimer: News groups are famous for some person who has little to
>contribute to a topic jumping in to contradict what another has said.
>The topic of logic circuits is long and complex. It also has many
>exceptions, and that is why I even hesitate to start to explain the
>cross over level topic. I DO NOT HAVE ALL THE ANSWERS!!! Perhaps this
>might negate the need for someone to blast me???
>>
>>
>>>>is generally recognized as 1.6 volts. That
>>>>is a zero is close to ground and certainly never over .6 volts. A one
>>>>is never less than 1.6 volts and normally close to the supply voltage.
>>>>(This is a GENERAL statement and depends upon many factors including the
>>>>type of semiconductor material.)
>>>>
>>>> If you are truly hanging on circuit ground with your meter's common
>>>>lead and measuring less than either +12 or +5 on the output of these
>>>>regulators, you have a problem. Certainly the center lead on the
>>>>regulator is ground, and should read 0 volts.
>>
>>
>> Yes.
>>
>>
>>> Here is a link for a graphic of the type regulator I believe is in the
>>>scanner. http://www.nteinc.com/specs/900to999/pdf/nte960.pdf
>>> I was wrong about the 9805 number, it is a 7805. (Had another brain
>>>fart.) Notice however that the input voltage is on the left of the
>>>device, ground is the center terminal, and the output is the left terminal.
>>
>>
>> Yes, you're right, a 7805 and a 7812. With the board out where I can
>> get a flashlight on the regulators at just the right angle, and using
>> a magnifying glass, I can read these old conventional numbers of
>> positive voltage regulators on them.
>>
>> <SNIP>

 

[ken]

Archived from groups: alt.comp.periphs.scanner (More info?)

Raymond A. Chamberlin wrote:
> On Sat, 08 Jan 2005 13:45:07 GMT, Ken <user@domain.invalid> wrote:
>
>
>>Raymond A. Chamberlin wrote:
>>
>>>To Ken and CSM1: See interleaved below:
>>>
>>>On Fri, 07 Jan 2005 20:29:51 GMT, Ken <user@domain.invalid> wrote:
>>>
>>>
>>
>>>
>>>The 12-v regulator is OK -- +15 v in, +12 v out.
>>>
>>>The 5-v regulator reads thus:
>>>
>>>+15 v --11-ohm/2(?)-w res--o--REG--o---- +0.5 v
>>> | |
>>> 47 µ / 25v 100 µ / 10 v
>>> | |
>>> gnd gnd
>>>
>>>The above circuit may be rather scrambled when you get it. Hope not.
>>
>>Ray,
>>
>> I am not sure I am reading your drawing correctly, but if you mean you
>>have .5 volts on the output, THAT IS A PROBLEM.
>
>
> Yes, that's what I mean. And yes, that obviously is a problem.

Ray,

You have found the problem, now you need to find the solution.
>
>
>>>The aluminum electrolytics, the regular and the resistor are all quite
>>>hot, as is a nearby AIC 1563CN high-efficiency DC/DC converter.
>>
>> It will be very difficult to replace any of the logic circuits attached
>>to this +5 volt bus, but it is possible that a cap is leaking drawing
>>down your +5 volts. More likely, the regulator failed, but the only way
>>to tell is to lift some leads. I would first lift the output from the
>>regulator and measure it. If it is +5, then the problem is on the bus.
>> Using an Ohm meter and lifting leads from caps would be the next
>>easiest, then attack the other components if you choose.
>>
>> For what it is worth, I repaired one of these scanners by replacing the
>>+5 regulator. Of course your results may vary!!!
>
>
> Well, I overlooked a pair of tiny chip/surface-mount components on the
> other side of the board, one on each side of the regulator to ground.

Without looking at the circuit myself, and assuming what you say is
true, I would assume they are caps.

> I would conclude they're either diodes or electrolytics. Do they
> suppress high-frequency oscillations? They came after my
> time-in-grade.

They are not likely electrolytics due to their being SMDs.
>
> Anyhow, I yanked the two radial-lead caps and the regulator.

By "yanking", I assume you mean the leads connected to the output have
been removed from the +5 volt bus and the short is still there? Or is
the short gone from the bus??
All of
> those appear fine -- as far as I can tell with a 20,000-ohm/v
> ohmmeter. The chip jobby on the regulator input reads 3.3 ohm one way
> and 20 ohms the other way (on the 20-ohms-at-center scale. The one on
> the regulator output reads a dead short both ways on the same scale.

I am not quite sure what you mean by the "Chip jobby." If the
regulator has been removed, and the output lead on it is shorted to any
of the other two leads on the regulator, THAT is your problem. You have
a bad regulator.
If on the other hand the regulator has been removed and the short
still exists on the +5v bus, there is a short on the bus. Suspect caps
first, such as those whose leads you have lifted. If the electrolytics
have been lifted and the short still exists, look for SMD caps or any
semiconductor attached to the bus.

> I assume the latter ist kaputt. Now, how the devil would I be able to
> find out the specs of that component -- unless -- ha, ha -- Mostek
> will tell me?

If we are talking about the +5 volt regulator, you can just buy one at
Radio Shack for a few pennies. Most of them are rated at something like
1 amp, and it is doubtful that anywhere near that current is being drawn
on that circuit. Take your old component with you and just buy a +5
regulator with the same physical characteristics, if that is the
component you are talking about.

Hey maybe they would send me a whole schematic. . .so I

You have got to cut back on the weed smoking or heavy drinking. They
are not likely to even ANSWER your request, let alone send you any
information!!!

> could tell them how to make one that doesn't burn up, huh? I could
> get a replacement mail-order chip thingy from Digi-Key, I guess.
> Dunno what their minimum order is though.

Radio Shack. If you can't find one there, I will mail you one. That
is, IF THE REGULATOR is what we are talking about????
>
> BTW, the resistor I marked as 11 ohms reads 51 ohms cold. I said 11
> ohms, because that seemed to be its color code -- but the first stripe
> was a lighter brown than the second, so I was always supicious.
> Apparently it used to be greeen. :-O

If this device is in series with the input voltage of 12 volts, it
might well be a coil (choke). Then the marking would not be ohms at
all, but milihenries. If you measured +12 with your DVM, the input is
OK. Your problem lies with the output.

Secondly, measuring a resistor while it is in a circuit often gives
false readings because of other attached components. The only effective
way would be to lift one lead and measure it. What is important is how
many ohms to ground the output bus reads.

On the other hand, if the component shorted is a SMD cap on the output
bus, then it can probably be replaced with one from a scrap circuit
board. This is not easily done, but I have done it many times. It is
true it might be for RFI, but it is probably not super critical. If you
can find another with similar makings, you will probably be OK.
>
> However, when I look at eBay or Craig's List, used and even new
> scanners are a dime a dozen! I paid $133 (incl. tax and less rebate)
> in San Francisco back in 1998. Craig's List has one of this model
> (used of course) for $19 and eBay runs from $0.01 minimum bid on this
> model, to $40 buy-it-now for a new, boxed-up Visioneer One Touch 5800
> USB scanner. Is the latter any good?
>
> Ray

I don't know anything about other brands of scanners, but you could be
only pennies away from fixing your scanner. It is your call.

Ken
>
>
>>>( http://www.scaner.by.ru/data.htm if your Russian is fluent. ) So
>>>I'm not sure how many of these components are bad. Maybe just the
>>>output electrolytic? Possibly something on beyond that. I can't find
>>>those caps in my junk box, so I'll hit Radio Shack tomorrow.
>>
>> Remember, if you do find it to be an electrolytic, you can replace it
>>with any voltage larger than the one installed and any capacitance
>>larger than the one installed. It is only a filter, so the capacitance
>>is NOT critical. Needless to say, observe the polarity.
>>
>>>
>>>>> There are very few semiconductors that operate at less than 5 volts.
>>>
>>>
>>>Well, I guess any of that vintage. But there certainly are now a lot
>>>that run on 3 v or so.
>>
>> There are, but they generally are more expensive than the +5 volt
>>variety. As circuits are designed to operate on lower voltages, they
>>are becoming more popular. This in turn causes them to become cheaper.
>>
>>>
>>>
>>>
>>>>>In fact, the cut over level
>>>
>>>
>>>What is that?
>>
>> It really becomes quite involved to explain, but simply stated, the
>>circuits are designed so that stray noise does NOT trigger them. Since
>>noise is unavoidable in most cases, the threshold is designed so that
>>only a signal over .6 volts will switch on a semiconductor. Therefore,
>>most of the time a signal of less than .6 volts is considered a zero,
>>and one greater than 1.6 is considered a one. The area in between these
>>levels were referred in my day as "No man's land." That is, the result
>>of such a voltage was not certain on a circuit. One could turn on,
>>while another might not.
>>
>> Disclaimer: News groups are famous for some person who has little to
>>contribute to a topic jumping in to contradict what another has said.
>>The topic of logic circuits is long and complex. It also has many
>>exceptions, and that is why I even hesitate to start to explain the
>>cross over level topic. I DO NOT HAVE ALL THE ANSWERS!!! Perhaps this
>>might negate the need for someone to blast me???
>>
>>>
>>>>>is generally recognized as 1.6 volts. That
>>>>>is a zero is close to ground and certainly never over .6 volts. A one
>>>>>is never less than 1.6 volts and normally close to the supply voltage.
>>>>>(This is a GENERAL statement and depends upon many factors including the
>>>>>type of semiconductor material.)
>>>>>
>>>>> If you are truly hanging on circuit ground with your meter's common
>>>>>lead and measuring less than either +12 or +5 on the output of these
>>>>>regulators, you have a problem. Certainly the center lead on the
>>>>>regulator is ground, and should read 0 volts.
>>>
>>>
>>>Yes.
>>>
>>>
>>>
>>>> Here is a link for a graphic of the type regulator I believe is in the
>>>>scanner. http://www.nteinc.com/specs/900to999/pdf/nte960.pdf
>>>>I was wrong about the 9805 number, it is a 7805. (Had another brain
>>>>fart.) Notice however that the input voltage is on the left of the
>>>>device, ground is the center terminal, and the output is the left terminal.
>>>
>>>
>>>Yes, you're right, a 7805 and a 7812. With the board out where I can
>>>get a flashlight on the regulators at just the right angle, and using
>>>a magnifying glass, I can read these old conventional numbers of
>>>positive voltage regulators on them.
>>>
>>><SNIP>
>
>

 

[Guest]

Archived from groups: alt.comp.periphs.scanner (More info?)

On Sun, 09 Jan 2005 14:35:00 GMT, Ken <user@domain.invalid> wrote:

>Raymond A. Chamberlin wrote:
>> On Sat, 08 Jan 2005 13:45:07 GMT, Ken <user@domain.invalid> wrote:
>>
>>
>>>Raymond A. Chamberlin wrote:
>>>
>>>>To Ken and CSM1: See interleaved below:
>>>>
>>>>On Fri, 07 Jan 2005 20:29:51 GMT, Ken <user@domain.invalid> wrote:
>>>>
>>>>
>>>
>>>>
>>>>The 12-v regulator is OK -- +15 v in, +12 v out.
>>>>
>>>>The 5-v regulator reads thus:
>>>>
>>>>+15 v --11-ohm/2(?)-w res--o--REG--o---- +0.5 v
>>>> | |
>>>> 47 µ / 25v 100 µ / 10 v
>>>> | |
>>>> gnd gnd
>>>>
>>>>The above circuit may be rather scrambled when you get it. Hope not.
>>>
>>>Ray,
>>>
>>> I am not sure I am reading your drawing correctly, but if you mean you
>>>have .5 volts on the output, THAT IS A PROBLEM.
>>
>>
>> Yes, that's what I mean. And yes, that obviously is a problem.
>
> Ray,
>
> You have found the problem, now you need to find the solution.

No, I've just found a symptom.

>>>>The aluminum electrolytics, the regular and the resistor are all quite
>>>>hot, as is a nearby AIC 1563CN high-efficiency DC/DC converter.
>>>
>>> It will be very difficult to replace any of the logic circuits attached
>>>to this +5 volt bus, but it is possible that a cap is leaking drawing
>>>down your +5 volts. More likely, the regulator failed, but the only way
>>>to tell is to lift some leads. I would first lift the output from the
>>>regulator and measure it. If it is +5, then the problem is on the bus.
>>> Using an Ohm meter and lifting leads from caps would be the next
>>>easiest, then attack the other components if you choose.
>>>
>>> For what it is worth, I repaired one of these scanners by replacing the
>>>+5 regulator. Of course your results may vary!!!
>>
>>
>> Well, I overlooked a pair of tiny chip/surface-mount components on the
>> other side of the board, one on each side of the regulator to ground.
>
> Without looking at the circuit myself, and assuming what you say is
>true, I would assume they are caps.
>
>> I would conclude they're either diodes or electrolytics. Do they
>> suppress high-frequency oscillations? They came after my
>> time-in-grade.
>
> They are not likely electrolytics due to their being SMDs.

Well, I see such being advertised in the Digi-Key catalog.

>> Anyhow, I yanked the two radial-lead caps and the regulator.
>
> By "yanking", I assume you mean the leads connected to the output have
>been removed from the +5 volt bus

I mean these parts are sitting on the bench apart from their board.

>and the short is still there?

Yup; from the trace to what was the regulator output, to what was the
regulator ground.

>Or is
>the short gone from the bus??

No.

> All of
>> those appear fine -- as far as I can tell with a 20,000-ohm/v
>> ohmmeter. The chip jobby on the regulator input reads 3.3 ohm one way
>> and 20 ohms the other way (on the 20-ohms-at-center scale. The one on
>> the regulator output reads a dead short both ways on the same scale.
>
> I am not quite sure what you mean by the "Chip jobby."

The SMD. However, I was fed up with this nonsense at that point and
forgot there was still all the other stuff on that regulator-output
bus. So it's likely my conclusion that this SMD is shorted is wrong.

>If the
>regulator has been removed, and the output lead on it is shorted to any
>of the other two leads on the regulator, THAT is your problem. You have
>a bad regulator.

No, NO interlead measurement on the regulator, while out of its
circuit, shows a short. I have to assume it's just fine; but since
the trace that went to its output now still reads shorted to what was
its ground trace, if I want to pursue this silly game further, I
should check what's left connected to that regulator's output trace,
which still shows a short to what was its ground trace. If I got
whatever is shorted beyond that point fixed, perhaps I should check
the regulator unloaded or externally reasonably loaded to see that its
really OK, before puttin it back into its circuit on the board.

> If on the other hand the regulator has been removed and the short
>still exists on the +5v bus, there is a short on the bus.

Yes, that's the case.

>Suspect caps
>first, such as those whose leads you have lifted. If the electrolytics
>have been lifted and the short still exists, look for SMD caps or any
>semiconductor attached to the bus.

Right. . .if I want to further waste my time (which, I agree, is not
worth much at present. But it makes a lot more sense to buy a new
scanner.

>> I assume the latter ist kaputt. Now, how the devil would I be able to
>> find out the specs of that component -- unless -- ha, ha -- Mostek
>> will tell me?
>
> If we are talking about the +5 volt regulator, you can just buy one at
>Radio Shack for a few pennies. Most of them are rated at something like
>1 amp, and it is doubtful that anywhere near that current is being drawn
>on that circuit. Take your old component with you and just buy a +5
>regulator with the same physical characteristics, if that is the
>component you are talking about.

Well, no, it's not! See above. Actually, though, I did first buy
adequate replacements for the regulator input and output radial-lead
caps and the regulator itself, the 7805. Radio Shack finally directed
me to one of their stores in this town that I didn't know of which
actually did have this regulator. I first went to two of their stores
and a local independent electronic parts store, all of which were out
of 7805s.

> Hey maybe they would send me a whole schematic. . .so I
>
> You have got to cut back on the weed smoking or heavy drinking. They
>are not likely to even ANSWER your request, let alone send you any
>information!!!
>
>> could tell them how to make one that doesn't burn up, huh? I could
>> get a replacement mail-order chip thingy from Digi-Key, I guess.
>> Dunno what their minimum order is though.
>
> Radio Shack. If you can't find one there, I will mail you one. That
>is, IF THE REGULATOR is what we are talking about????

No, that's not what I'M talking about.

>> BTW, the resistor I marked as 11 ohms reads 51 ohms cold. I said 11
>> ohms, because that seemed to be its color code -- but the first stripe
>> was a lighter brown than the second, so I was always supicious.
>> Apparently it used to be greeen. :-O
>
> If this device is in series with the input voltage of 12 volts,

No, 12 v.

>it
>might well be a coil (choke). Then the marking would not be ohms at
>all, but milihenries.

No, a millihenry choke would never drop the 4.5 v I measured across it
when the overloaded 5-volt regulator was in the circuit. I has to be
a resistor -- either linear or nonlinear with current.

>If you measured +12 with your DVM, the input is
>OK.

NO! The input to the +5-v regulator is the +15 v from the plub
supply.

>Your problem lies with the output.

Well, something that's HANGING ON the output. I KNOW that.

> Secondly, measuring a resistor while it is in a circuit often gives
>false readings because of other attached components.

Certainly, but I measured it AFTER I took the regulator and its input
electrolytic OUT of the circuit. Thus one end of this resistor was
handing free when I measured it at 51 ohms. Of course, it could be
half burnt up and thus not the value it was born with.

>The only effective
>way would be to lift one lead and measure it.

Right on. Thus I did.

>What is important is how
>many ohms to ground the output bus reads.

Zilch (+\- what I can't see) on the X1-ohm scale of my mirrored 20,000
ohms/v meter.

> On the other hand, if the component shorted is a SMD cap on the output
>bus, then it can probably be replaced with one from a scrap circuit
>board.

Yes, I have a scrapped motherboard I bought for another part, which
board has at least 50 of the little things on it. Of course, I don't
know what size they are, but I agree the size is probably not at all
critical. I find it hard to believe this one's necessary at all.
There're probably others somewhere down the line on this same bus,
where they might make a difference.

>This is not easily done, but I have done it many times. It is
>true it might be for RFI, but it is probably not super critical. If you
>can find another with similar makings, you will probably be OK.
>>
>> However, when I look at eBay or Craig's List, used and even new
>> scanners are a dime a dozen! I paid $133 (incl. tax and less rebate)
>> in San Francisco back in 1998. Craig's List has one of this model
>> (used of course) for $19 and eBay runs from $0.01 minimum bid on this
>> model, to $40 buy-it-now for a new, boxed-up Visioneer One Touch 5800
>> USB scanner. Is the latter any good?
>>
>> Ray
>
> I don't know anything about other brands of scanners, but you could be
>only pennies away from fixing your scanner. It is your call.

Yeah. I could spend hours, maybe days yet, checking out all the parts
hanging on this +5-v bus. Just figuring out where it goes is no easy
thing. The board appears to be a 4-plane one that is not very
translucent. I should run my multimeter over the more than 1000 lead
terminations on this board to see how many are on this bus? Even my
life of upgrading my software and taking out the trash is more
satisfying.

It was certainly interesting to find someone who was so completely
wave-soldered into the exact scanner I was having trouble with, but
this trouble-shooting has gotten way past the limit of reason at this
point, I'm afraid.

Thanks for all your trouble though.

Ray

>Ken
>>
>>
>>>>( http://www.scaner.by.ru/data.htm if your Russian is fluent. ) So
>>>>I'm not sure how many of these components are bad. Maybe just the
>>>>output electrolytic? Possibly something on beyond that. I can't find
>>>>those caps in my junk box, so I'll hit Radio Shack tomorrow.
>>>
>>> Remember, if you do find it to be an electrolytic, you can replace it
>>>with any voltage larger than the one installed and any capacitance
>>>larger than the one installed. It is only a filter, so the capacitance
>>>is NOT critical. Needless to say, observe the polarity.
>>>
>>>>
>>>>>> There are very few semiconductors that operate at less than 5 volts.
>>>>
>>>>
>>>>Well, I guess any of that vintage. But there certainly are now a lot
>>>>that run on 3 v or so.
>>>
>>> There are, but they generally are more expensive than the +5 volt
>>>variety. As circuits are designed to operate on lower voltages, they
>>>are becoming more popular. This in turn causes them to become cheaper.
>>>
>>>>
>>>>
>>>>
>>>>>>In fact, the cut over level
>>>>
>>>>
>>>>What is that?
>>>
>>> It really becomes quite involved to explain, but simply stated, the
>>>circuits are designed so that stray noise does NOT trigger them. Since
>>>noise is unavoidable in most cases, the threshold is designed so that
>>>only a signal over .6 volts will switch on a semiconductor. Therefore,
>>>most of the time a signal of less than .6 volts is considered a zero,
>>>and one greater than 1.6 is considered a one. The area in between these
>>>levels were referred in my day as "No man's land." That is, the result
>>>of such a voltage was not certain on a circuit. One could turn on,
>>>while another might not.
>>>
>>> Disclaimer: News groups are famous for some person who has little to
>>>contribute to a topic jumping in to contradict what another has said.
>>>The topic of logic circuits is long and complex. It also has many
>>>exceptions, and that is why I even hesitate to start to explain the
>>>cross over level topic. I DO NOT HAVE ALL THE ANSWERS!!! Perhaps this
>>>might negate the need for someone to blast me???
>>>
>>>>
>>>>>>is generally recognized as 1.6 volts. That
>>>>>>is a zero is close to ground and certainly never over .6 volts. A one
>>>>>>is never less than 1.6 volts and normally close to the supply voltage.
>>>>>>(This is a GENERAL statement and depends upon many factors including the
>>>>>>type of semiconductor material.)
>>>>>>
>>>>>> If you are truly hanging on circuit ground with your meter's common
>>>>>>lead and measuring less than either +12 or +5 on the output of these
>>>>>>regulators, you have a problem. Certainly the center lead on the
>>>>>>regulator is ground, and should read 0 volts.
>>>>
>>>>
>>>>Yes.
>>>>
>>>>
>>>>
>>>>> Here is a link for a graphic of the type regulator I believe is in the
>>>>>scanner. http://www.nteinc.com/specs/900to999/pdf/nte960.pdf
>>>>>I was wrong about the 9805 number, it is a 7805. (Had another brain
>>>>>fart.) Notice however that the input voltage is on the left of the
>>>>>device, ground is the center terminal, and the output is the left terminal.
>>>>
>>>>
>>>>Yes, you're right, a 7805 and a 7812. With the board out where I can
>>>>get a flashlight on the regulators at just the right angle, and using
>>>>a magnifying glass, I can read these old conventional numbers of
>>>>positive voltage regulators on them.
>>>>
>>>><SNIP>
>>
>>