For a couple of years I've been fighting with a UMAX Mirage II scanner,
trying to get it to work under OS X (currently 10.3.8).

UMAX doesn't support OS X and, for a while I was booting into OS 9 when
I needed to scan, then switching back, which is a pain.

I bought a copy of Hamrick's VueScan, which works for me occasionally,
as does the demo version of LaserSoft's SilverFast SE that I tried out.

Here's the problem: The software won't find the scanner if I boot up
the scanner before I start the Mac, nor will it if I let the Mac boot
up, THEN turn the scanner on. Occasionally, if I start them both
mnore-or-less simultaneously and get them both shouting down the pipe
at each other at the same time, then everything works - assuming that I
don't then wait too long and the scanner goes to standby, or whatever,
at which point they can't find each other again.

Needless to say, this is REALLY annoying.

Has anyone else run into this? Rick at Hamrick couldn't figure it out,
so I'm expecting that I'm pretty much scrod (as we New Englanders say).

Unfortunately, I wprk for a smallish city government, so the likelihood
of finding the money to replace a (more or less) functioning scanner is
unlikely at this time.

In case the specs will help anyone spot the problem, they are as
follows:
*50 MHZ G4 Quicksilver running OS 10.3.8
Asante (I think) SCSI card
UMAX Mirage II scanner attached on the SCSI chain along with a Zip and
a Jaz drive. (Note: Normally I'd suspect some sort of SCSI voodoo
problem and try changing the order of the items. In this case,
unfortunately, each device has a different connector configuration
(15-pin, 25-pin, and 50-pin connectors, IIRC, with adapters where
needed and right now, they only go together one way...)

If anyone else has run into this, or has any deas of where else I could
look for info, I'd greatly appreciate it!

E. Telly Kelly wrote:
> For a couple of years I've been fighting with a UMAX Mirage II scanner,
> trying to get it to work under OS X (currently 10.3.8).
>
> UMAX doesn't support OS X and, for a while I was booting into OS 9 when
> I needed to scan, then switching back, which is a pain.
>
> I bought a copy of Hamrick's VueScan, which works for me occasionally,
> as does the demo version of LaserSoft's SilverFast SE that I tried out.
>
> Here's the problem: The software won't find the scanner if I boot up
> the scanner before I start the Mac, nor will it if I let the Mac boot
> up, THEN turn the scanner on. Occasionally, if I start them both
> mnore-or-less simultaneously and get them both shouting down the pipe
> at each other at the same time, then everything works - assuming that I
> don't then wait too long and the scanner goes to standby, or whatever,
> at which point they can't find each other again.
>
> Needless to say, this is REALLY annoying.
>
> Has anyone else run into this? Rick at Hamrick couldn't figure it out,
> so I'm expecting that I'm pretty much scrod (as we New Englanders say).
>
> Unfortunately, I wprk for a smallish city government, so the likelihood
> of finding the money to replace a (more or less) functioning scanner is
> unlikely at this time.
>
> In case the specs will help anyone spot the problem, they are as
> follows:
> *50 MHZ G4 Quicksilver running OS 10.3.8
> Asante (I think) SCSI card
> UMAX Mirage II scanner attached on the SCSI chain along with a Zip and
> a Jaz drive. (Note: Normally I'd suspect some sort of SCSI voodoo
> problem and try changing the order of the items. In this case,
> unfortunately, each device has a different connector configuration
> (15-pin, 25-pin, and 50-pin connectors, IIRC, with adapters where
> needed and right now, they only go together one way...)
>
> If anyone else has run into this, or has any deas of where else I could
> look for info, I'd greatly appreciate it!


Is your scanner on before booting up?
Have you tried repairing permissions?

--
http://homepage.mac.com/mkatzman/

E. Telly Kelly wrote:
> For a couple of years I've been fighting with a UMAX Mirage II scanner,
> trying to get it to work under OS X (currently 10.3.8).
>
> UMAX doesn't support OS X and, for a while I was booting into OS 9 when
> I needed to scan, then switching back, which is a pain.
>
> I bought a copy of Hamrick's VueScan, which works for me occasionally,
> as does the demo version of LaserSoft's SilverFast SE that I tried out.
>
> Here's the problem: The software won't find the scanner if I boot up
> the scanner before I start the Mac, nor will it if I let the Mac boot
> up, THEN turn the scanner on. Occasionally, if I start them both
> mnore-or-less simultaneously and get them both shouting down the pipe
> at each other at the same time, then everything works - assuming that I
> don't then wait too long and the scanner goes to standby, or whatever,
> at which point they can't find each other again.
>
> Needless to say, this is REALLY annoying.
>
> Has anyone else run into this? Rick at Hamrick couldn't figure it out,
> so I'm expecting that I'm pretty much scrod (as we New Englanders say).
>
> Unfortunately, I wprk for a smallish city government, so the likelihood
> of finding the money to replace a (more or less) functioning scanner is
> unlikely at this time.
>
> In case the specs will help anyone spot the problem, they are as
> follows:
> *50 MHZ G4 Quicksilver running OS 10.3.8
> Asante (I think) SCSI card
> UMAX Mirage II scanner attached on the SCSI chain along with a Zip and
> a Jaz drive. (Note: Normally I'd suspect some sort of SCSI voodoo
> problem and try changing the order of the items. In this case,
> unfortunately, each device has a different connector configuration
> (15-pin, 25-pin, and 50-pin connectors, IIRC, with adapters where
> needed and right now, they only go together one way...)
>
> If anyone else has run into this, or has any deas of where else I could
> look for info, I'd greatly appreciate it!


Is your scanner on before booting up?
Have you tried repairing permissions?

--
http://homepage.mac.com/mkatzman/

In article <uRP_e.16914$L15.11970@trndny01>, Marshall
<notmkatzman@verizon.net> wrote:

> E. Telly Kelly wrote:
> > For a couple of years I've been fighting with a UMAX Mirage II scanner,
> > trying to get it to work under OS X (currently 10.3.8).
> >
> > UMAX doesn't support OS X and, for a while I was booting into OS 9 when
> > I needed to scan, then switching back, which is a pain.
> >
> > I bought a copy of Hamrick's VueScan, which works for me occasionally,
> > as does the demo version of LaserSoft's SilverFast SE that I tried out.
> >
> > Here's the problem: The software won't find the scanner if I boot up
> > the scanner before I start the Mac, nor will it if I let the Mac boot
> > up, THEN turn the scanner on. Occasionally, if I start them both
> > mnore-or-less simultaneously and get them both shouting down the pipe
> > at each other at the same time, then everything works - assuming that I
> > don't then wait too long and the scanner goes to standby, or whatever,
> > at which point they can't find each other again.
> >
> > Needless to say, this is REALLY annoying.
> >
> > Has anyone else run into this? Rick at Hamrick couldn't figure it out,
> > so I'm expecting that I'm pretty much scrod (as we New Englanders say).
> >
> > Unfortunately, I wprk for a smallish city government, so the likelihood
> > of finding the money to replace a (more or less) functioning scanner is
> > unlikely at this time.
> >
> > In case the specs will help anyone spot the problem, they are as
> > follows:
> > *50 MHZ G4 Quicksilver running OS 10.3.8
> > Asante (I think) SCSI card
> > UMAX Mirage II scanner attached on the SCSI chain along with a Zip and
> > a Jaz drive. (Note: Normally I'd suspect some sort of SCSI voodoo
> > problem and try changing the order of the items. In this case,
> > unfortunately, each device has a different connector configuration
> > (15-pin, 25-pin, and 50-pin connectors, IIRC, with adapters where
> > needed and right now, they only go together one way...)
> >
> > If anyone else has run into this, or has any deas of where else I could
> > look for info, I'd greatly appreciate it!
>
>
> Is your scanner on before booting up?
> Have you tried repairing permissions?

Yeah - as noted above: tried with scanner completely started up before
starting the computer, with computer started before starting the
scanner, and with both starting simultaneously... nada.

Pretty sure that I've repaired permissions in the time that I've been
struggling with this. Friday is "Run Cocktail" day, so maybe I'll do a
"repair permissions" as well as the cron scripts. It can't hurt
although, as I said, I'm pretty sure that I've done it s few times
while I've been dealing with this.

I'll report back.

In article <uRP_e.16914$L15.11970@trndny01>, Marshall
<notmkatzman@verizon.net> wrote:

> E. Telly Kelly wrote:
> > For a couple of years I've been fighting with a UMAX Mirage II scanner,
> > trying to get it to work under OS X (currently 10.3.8).
> >
> > UMAX doesn't support OS X and, for a while I was booting into OS 9 when
> > I needed to scan, then switching back, which is a pain.
> >
> > I bought a copy of Hamrick's VueScan, which works for me occasionally,
> > as does the demo version of LaserSoft's SilverFast SE that I tried out.
> >
> > Here's the problem: The software won't find the scanner if I boot up
> > the scanner before I start the Mac, nor will it if I let the Mac boot
> > up, THEN turn the scanner on. Occasionally, if I start them both
> > mnore-or-less simultaneously and get them both shouting down the pipe
> > at each other at the same time, then everything works - assuming that I
> > don't then wait too long and the scanner goes to standby, or whatever,
> > at which point they can't find each other again.
> >
> > Needless to say, this is REALLY annoying.
> >
> > Has anyone else run into this? Rick at Hamrick couldn't figure it out,
> > so I'm expecting that I'm pretty much scrod (as we New Englanders say).
> >
> > Unfortunately, I wprk for a smallish city government, so the likelihood
> > of finding the money to replace a (more or less) functioning scanner is
> > unlikely at this time.
> >
> > In case the specs will help anyone spot the problem, they are as
> > follows:
> > *50 MHZ G4 Quicksilver running OS 10.3.8
> > Asante (I think) SCSI card
> > UMAX Mirage II scanner attached on the SCSI chain along with a Zip and
> > a Jaz drive. (Note: Normally I'd suspect some sort of SCSI voodoo
> > problem and try changing the order of the items. In this case,
> > unfortunately, each device has a different connector configuration
> > (15-pin, 25-pin, and 50-pin connectors, IIRC, with adapters where
> > needed and right now, they only go together one way...)
> >
> > If anyone else has run into this, or has any deas of where else I could
> > look for info, I'd greatly appreciate it!
>
>
> Is your scanner on before booting up?
> Have you tried repairing permissions?

Yeah - as noted above: tried with scanner completely started up before
starting the computer, with computer started before starting the
scanner, and with both starting simultaneously... nada.

Pretty sure that I've repaired permissions in the time that I've been
struggling with this. Friday is "Run Cocktail" day, so maybe I'll do a
"repair permissions" as well as the cron scripts. It can't hurt
although, as I said, I'm pretty sure that I've done it s few times
while I've been dealing with this.

I'll report back.

E. Telly Kelly wrote:
> In article <uRP_e.16914$L15.11970@trndny01>, Marshall
> <notmkatzman@verizon.net> wrote:
>
>
>>E. Telly Kelly wrote:
>>
>>>For a couple of years I've been fighting with a UMAX Mirage II scanner,
>>>trying to get it to work under OS X (currently 10.3.8).
>>>
>>>UMAX doesn't support OS X and, for a while I was booting into OS 9 when
>>>I needed to scan, then switching back, which is a pain.
>>>
>>>I bought a copy of Hamrick's VueScan, which works for me occasionally,
>>>as does the demo version of LaserSoft's SilverFast SE that I tried out.
>>>
>>>Here's the problem: The software won't find the scanner if I boot up
>>>the scanner before I start the Mac, nor will it if I let the Mac boot
>>>up, THEN turn the scanner on. Occasionally, if I start them both
>>>mnore-or-less simultaneously and get them both shouting down the pipe
>>>at each other at the same time, then everything works - assuming that I
>>>don't then wait too long and the scanner goes to standby, or whatever,
>>>at which point they can't find each other again.
>>>
>>>Needless to say, this is REALLY annoying.
>>>
>>>Has anyone else run into this? Rick at Hamrick couldn't figure it out,
>>>so I'm expecting that I'm pretty much scrod (as we New Englanders say).
>>>
>>>Unfortunately, I wprk for a smallish city government, so the likelihood
>>>of finding the money to replace a (more or less) functioning scanner is
>>>unlikely at this time.
>>>
>>>In case the specs will help anyone spot the problem, they are as
>>>follows:
>>>*50 MHZ G4 Quicksilver running OS 10.3.8
>>>Asante (I think) SCSI card
>>>UMAX Mirage II scanner attached on the SCSI chain along with a Zip and
>>>a Jaz drive. (Note: Normally I'd suspect some sort of SCSI voodoo
>>>problem and try changing the order of the items. In this case,
>>>unfortunately, each device has a different connector configuration
>>>(15-pin, 25-pin, and 50-pin connectors, IIRC, with adapters where
>>>needed and right now, they only go together one way...)
>>>
>>>If anyone else has run into this, or has any deas of where else I could
>>>look for info, I'd greatly appreciate it!
>>
>>
>>Is your scanner on before booting up?
>>Have you tried repairing permissions?
>
>
> Yeah - as noted above: tried with scanner completely started up before
> starting the computer, with computer started before starting the
> scanner, and with both starting simultaneously... nada.
>
> Pretty sure that I've repaired permissions in the time that I've been
> struggling with this. Friday is "Run Cocktail" day, so maybe I'll do a
> "repair permissions" as well as the cron scripts. It can't hurt
> although, as I said, I'm pretty sure that I've done it s few times
> while I've been dealing with this.
>
> I'll report back.

Make sure that your scanner is first in the SCSI chain.

Have you tried removing all but the scanner in the SCSI chain?

--
http://homepage.mac.com/mkatzman/

E. Telly Kelly wrote:
> In article <uRP_e.16914$L15.11970@trndny01>, Marshall
> <notmkatzman@verizon.net> wrote:
>
>
>>E. Telly Kelly wrote:
>>
>>>For a couple of years I've been fighting with a UMAX Mirage II scanner,
>>>trying to get it to work under OS X (currently 10.3.8).
>>>
>>>UMAX doesn't support OS X and, for a while I was booting into OS 9 when
>>>I needed to scan, then switching back, which is a pain.
>>>
>>>I bought a copy of Hamrick's VueScan, which works for me occasionally,
>>>as does the demo version of LaserSoft's SilverFast SE that I tried out.
>>>
>>>Here's the problem: The software won't find the scanner if I boot up
>>>the scanner before I start the Mac, nor will it if I let the Mac boot
>>>up, THEN turn the scanner on. Occasionally, if I start them both
>>>mnore-or-less simultaneously and get them both shouting down the pipe
>>>at each other at the same time, then everything works - assuming that I
>>>don't then wait too long and the scanner goes to standby, or whatever,
>>>at which point they can't find each other again.
>>>
>>>Needless to say, this is REALLY annoying.
>>>
>>>Has anyone else run into this? Rick at Hamrick couldn't figure it out,
>>>so I'm expecting that I'm pretty much scrod (as we New Englanders say).
>>>
>>>Unfortunately, I wprk for a smallish city government, so the likelihood
>>>of finding the money to replace a (more or less) functioning scanner is
>>>unlikely at this time.
>>>
>>>In case the specs will help anyone spot the problem, they are as
>>>follows:
>>>*50 MHZ G4 Quicksilver running OS 10.3.8
>>>Asante (I think) SCSI card
>>>UMAX Mirage II scanner attached on the SCSI chain along with a Zip and
>>>a Jaz drive. (Note: Normally I'd suspect some sort of SCSI voodoo
>>>problem and try changing the order of the items. In this case,
>>>unfortunately, each device has a different connector configuration
>>>(15-pin, 25-pin, and 50-pin connectors, IIRC, with adapters where
>>>needed and right now, they only go together one way...)
>>>
>>>If anyone else has run into this, or has any deas of where else I could
>>>look for info, I'd greatly appreciate it!
>>
>>
>>Is your scanner on before booting up?
>>Have you tried repairing permissions?
>
>
> Yeah - as noted above: tried with scanner completely started up before
> starting the computer, with computer started before starting the
> scanner, and with both starting simultaneously... nada.
>
> Pretty sure that I've repaired permissions in the time that I've been
> struggling with this. Friday is "Run Cocktail" day, so maybe I'll do a
> "repair permissions" as well as the cron scripts. It can't hurt
> although, as I said, I'm pretty sure that I've done it s few times
> while I've been dealing with this.
>
> I'll report back.

Make sure that your scanner is first in the SCSI chain.

Have you tried removing all but the scanner in the SCSI chain?

--
http://homepage.mac.com/mkatzman/

In article <pKj%e.268$794.33@trndny01>, Marshall
<notmkatzman@verizon.net> wrote:

> Make sure that your scanner is first in the SCSI chain.
>
> Have you tried removing all but the scanner in the SCSI chain?

It is first in the chain. I'm going to try taking everything else off
the chain, but I'm waiting on the MIS folks to see if they have a
Centronics-type external SCSI terminator since the scanner has none.

The current order is:

scanner -- SCSI ID 4 -- No temination
JAZ -- SCSI ID 3 -- Auto termination selected
Zip SCSI ID 5 -- Termination On

Both of the disks show up properly on the desktop; everything works as
it should except the fershlugginer scanner.

I'll post again if I can get a terminator and try the scanner alone.

Thanks.

In article <pKj%e.268$794.33@trndny01>, Marshall
<notmkatzman@verizon.net> wrote:

> Make sure that your scanner is first in the SCSI chain.
>
> Have you tried removing all but the scanner in the SCSI chain?

It is first in the chain. I'm going to try taking everything else off
the chain, but I'm waiting on the MIS folks to see if they have a
Centronics-type external SCSI terminator since the scanner has none.

The current order is:

scanner -- SCSI ID 4 -- No temination
JAZ -- SCSI ID 3 -- Auto termination selected
Zip SCSI ID 5 -- Termination On

Both of the disks show up properly on the desktop; everything works as
it should except the fershlugginer scanner.

I'll post again if I can get a terminator and try the scanner alone.

Thanks.

In article <031020052232040681%E_Telly_Kelly******.com>, E. Telly Kelly
<E_Telly_Kelly******.com> wrote:

> In article <pKj%e.268$794.33@trndny01>, Marshall
> <notmkatzman@verizon.net> wrote:
>
> > Make sure that your scanner is first in the SCSI chain.
> >
> > Have you tried removing all but the scanner in the SCSI chain?
>
> It is first in the chain. I'm going to try taking everything else off
> the chain, but I'm waiting on the MIS folks to see if they have a
> Centronics-type external SCSI terminator since the scanner has none.
>
> The current order is:
>
> scanner -- SCSI ID 4 -- No temination
> JAZ -- SCSI ID 3 -- Auto termination selected
> Zip SCSI ID 5 -- Termination On
>
> Both of the disks show up properly on the desktop; everything works as
> it should except the fershlugginer scanner.
>
> I'll post again if I can get a terminator and try the scanner alone.
>
> Thanks.

Hokay... I got a terminator, unplugged everything else from the chain,
terminated the scanner, started the said scanner and waited for it to
go through its start-up, blinky-light self-check and, when it was done,
started the computer. When that was done, opened VueScan and... Nope.
Nada. nothing, zilch, ziparoonio...

I guess tomorrow I'll try reversing the terminator and the SCSI cable.
If that does nothing, then I'll try moving the scanner to a Windows
machine next door and see if THAT can see it...

Other than that, I'm stumped.

In article <031020052232040681%E_Telly_Kelly******.com>, E. Telly Kelly
<E_Telly_Kelly******.com> wrote:

> In article <pKj%e.268$794.33@trndny01>, Marshall
> <notmkatzman@verizon.net> wrote:
>
> > Make sure that your scanner is first in the SCSI chain.
> >
> > Have you tried removing all but the scanner in the SCSI chain?
>
> It is first in the chain. I'm going to try taking everything else off
> the chain, but I'm waiting on the MIS folks to see if they have a
> Centronics-type external SCSI terminator since the scanner has none.
>
> The current order is:
>
> scanner -- SCSI ID 4 -- No temination
> JAZ -- SCSI ID 3 -- Auto termination selected
> Zip SCSI ID 5 -- Termination On
>
> Both of the disks show up properly on the desktop; everything works as
> it should except the fershlugginer scanner.
>
> I'll post again if I can get a terminator and try the scanner alone.
>
> Thanks.

Hokay... I got a terminator, unplugged everything else from the chain,
terminated the scanner, started the said scanner and waited for it to
go through its start-up, blinky-light self-check and, when it was done,
started the computer. When that was done, opened VueScan and... Nope.
Nada. nothing, zilch, ziparoonio...

I guess tomorrow I'll try reversing the terminator and the SCSI cable.
If that does nothing, then I'll try moving the scanner to a Windows
machine next door and see if THAT can see it...

Other than that, I'm stumped.

E. Telly Kelly wrote:
> In article <031020052232040681%E_Telly_Kelly******.com>, E. Telly Kelly
> <E_Telly_Kelly******.com> wrote:
>
>
>>In article <pKj%e.268$794.33@trndny01>, Marshall
>><notmkatzman@verizon.net> wrote:
>>
>>
>>>Make sure that your scanner is first in the SCSI chain.
>>>
>>>Have you tried removing all but the scanner in the SCSI chain?
>>
>>It is first in the chain. I'm going to try taking everything else off
>>the chain, but I'm waiting on the MIS folks to see if they have a
>>Centronics-type external SCSI terminator since the scanner has none.
>>
>>The current order is:
>>
>>scanner -- SCSI ID 4 -- No temination
>>JAZ -- SCSI ID 3 -- Auto termination selected
>>Zip SCSI ID 5 -- Termination On
>>
>>Both of the disks show up properly on the desktop; everything works as
>>it should except the fershlugginer scanner.
>>
>>I'll post again if I can get a terminator and try the scanner alone.
>>
>>Thanks.
>
>
> Hokay... I got a terminator, unplugged everything else from the chain,
> terminated the scanner, started the said scanner and waited for it to
> go through its start-up, blinky-light self-check and, when it was done,
> started the computer. When that was done, opened VueScan and... Nope.
> Nada. nothing, zilch, ziparoonio...
>
> I guess tomorrow I'll try reversing the terminator and the SCSI cable.
> If that does nothing, then I'll try moving the scanner to a Windows
> machine next door and see if THAT can see it...
>
> Other than that, I'm stumped.


Can you boot up in OS 9 and try it?



--
http://homepage.mac.com/mkatzman/

E. Telly Kelly wrote:
> In article <031020052232040681%E_Telly_Kelly******.com>, E. Telly Kelly
> <E_Telly_Kelly******.com> wrote:
>
>
>>In article <pKj%e.268$794.33@trndny01>, Marshall
>><notmkatzman@verizon.net> wrote:
>>
>>
>>>Make sure that your scanner is first in the SCSI chain.
>>>
>>>Have you tried removing all but the scanner in the SCSI chain?
>>
>>It is first in the chain. I'm going to try taking everything else off
>>the chain, but I'm waiting on the MIS folks to see if they have a
>>Centronics-type external SCSI terminator since the scanner has none.
>>
>>The current order is:
>>
>>scanner -- SCSI ID 4 -- No temination
>>JAZ -- SCSI ID 3 -- Auto termination selected
>>Zip SCSI ID 5 -- Termination On
>>
>>Both of the disks show up properly on the desktop; everything works as
>>it should except the fershlugginer scanner.
>>
>>I'll post again if I can get a terminator and try the scanner alone.
>>
>>Thanks.
>
>
> Hokay... I got a terminator, unplugged everything else from the chain,
> terminated the scanner, started the said scanner and waited for it to
> go through its start-up, blinky-light self-check and, when it was done,
> started the computer. When that was done, opened VueScan and... Nope.
> Nada. nothing, zilch, ziparoonio...
>
> I guess tomorrow I'll try reversing the terminator and the SCSI cable.
> If that does nothing, then I'll try moving the scanner to a Windows
> machine next door and see if THAT can see it...
>
> Other than that, I'm stumped.


Can you boot up in OS 9 and try it?



--
http://homepage.mac.com/mkatzman/