old scanner with os x??

[foon]

I got a nikon ls 2000 and a microtech scsi to usb adapter, and trying to use it on OS X tiger
i plugged everything in, turned it on
and vuescan says no scanner

after searching for solutions on the internet
i switched the scsi ID to 0,
restarted the computer
open vuescan and it doesn't open like it did last time and tell me there is no scanner
i tired the same thing with silverfast, and it freezes there too

apparently the computer founds something, but can't work very well with it
does anyone have experience with things like this??
can anyone give me some suggestions??

 

[kbg32]

Do you have the proper driver for the scanner in OS X? Otherwise the software/computer will not recognize it. Check the manufacturer's site. A problem with OS X is running older scanners and printers. If there is no updated driver for OS 10, you're shit out of luck. I run certain hardware through Classic as there is no new driver for them.

Possibly some other member here might have a fix.....

 

[JoeFriday]

I was all set to switch over to Tiger, but I've been hearing a lot of stories like this lately.. I think I'll hold off for another 6 months

 

[doubs43]

Joe, I have an IBM Color Scanner that does legal-size scans. It's useless with Windows XP because IBM has not supported XP with a new driver. That forced me to buy a new scanner that will do legal sheets and has soured me on IBM products. A perfectly good scanner sits unused because "Big Blue" isn't prepared to support their equipment. I'm not prepared to support IBM any longer.

Walker

 

[foon]

I was all set to switch over to Tiger, but I've been hearing a lot of stories like this lately.. I think I'll hold off for another 6 months

i seriously doubt it's the problem of tiger...
i can't even find the firmware to install..oh well i got the 1.3.1...but i need the nikon scan 2 to install the firmware....$^&%&

does anyone have the nikon scan 2 for mac??

i really feel shit out of luck now...

 

[phototone]

Do you have the proper driver for the scanner in OS X? Otherwise the software/computer will not recognize it. Check the manufacturer's site. A problem with OS X is running older scanners and printers. If there is no updated driver for OS 10, you're shit out of luck. I run certain hardware through Classic as there is no new driver for them.

Possibly some other member here might have a fix.....

VUESCAN is the scanner driver. There are many older scanners that are considered obsolete and thus no manufacturers driver, this is where VueScan comes in, as they support older scanners on modern OS. It is possible there is an update to VueScan, and you need to check their website to see if there is. Also, you might be having a problem with the SCSI to USB, or SCSI to Firewire adaptor. Some adaptors are more transparent than others. In anycase check the VueScan website, and see if that scanner is supported on OS-X Tiger.

 

[JoeFriday]

I've got Nikon Scan 4.0.2 (Mac and Windows).. but I think Vuescan is probably your best bet.. that one program supports hundreds of scanners

 

[mac_wt]

The problem is probably the SCSI to USB adapter. When I was faced with the same problem (OSX didn't work with the build in SCSI of my beige desktop G3), I installed a SCSI-card in one of the PCI-slots. This allowed me to use my LS-1000 with Vuescan as driver.
I allways found mixed reviews of the SCSI to FireWire (or USB) adapters on the net, so I never invested in one. Search the web for info on your adapter. A quick search gave me this as first result: http://www.applefritter.com/node/6924 ; not very good start.

Wim

 

[phototone]

SCSI to Firewire adaptor for my Betterlight 4000 scanning back to my Titanium powerbook, and it works like a charm. I got the adaptor recommended by Betterlight. FYI: The Betterlight scanning backs are used with 4x5 view cameras in place of a film holder to take a high resolution digital photo. You use continuous light, and the back actually "scans" the image, at higher resolution than a digital SLR.

 

[foon]

thanks for the suggestions

i tried to hook it up to a pc
it actually says the ls2000 is connected to it(yes, it shows the name)
and that makes me excited for two minutes

I installed vuescan, but windows still wants a damn driver
well....i dont want to mess with a pc anyways
I think the adapter's working alright, but I have no idea what driver I need to install(on OSX)



mac_wt, how do you use vuescan as your driver though
that's what i can't figure out....just run it??

 

[foon]

With silverfast, i could actually scan something!
but VERY SLOWLY, i literally have to wait five minutes after i press scan, and five minutes for it to focus and then it starts scanning...
with vuescan, it only says my scanner is not ready to scan, even after i put film in it

does anyone know why??

 

[mac_wt]

thanks for the suggestions

mac_wt, how do you use vuescan as your driver though
that's what i can't figure out....just run it??

Yes, that's what I did. Vuescan is the 'driver' for the scanner. The fact that your adapter works on Windows confirms to me that it's the problem in your setup. You have to make sure that it is supported in OSX. Maybe a SCSI to Firewire adapter that is known to work with OSX and with scanners might be a better solution. Look here:
http://www.xlr8yourmac.com/OSX/panther_scsi_adapters.html

Wim

 

[Doug]

SCSI is as much art as science, but there are some basic rules. One is that ID=0 is reserved for the computer itself... or perhaps more accurately the SCSI host, which in your case might well be the adaptor. Then assign the scanner to some other ID from 1 through 7. You'll probably need a termination block at the end of the chain. If the scanner has a second SCSI port, put the termination block on that otherwise unused port. Some scanners have only one SCSI port, so a "pass-through" terminator can go on that one with the cable hooked to the block's other side. It's possible that a one-port scanner, which necessarily must be the last device on an SCSI chain, might have a built-in block of termination resistors. The purpose of this termination block is to absorb and attenuate reflected signal that would otherwise bounce back and forth through the cabling and confuse the devices trying to interpret what's going on. You don't mention what you're doing in regard to termination...

 

[foon]

Yes, that's what I did. Vuescan is the 'driver' for the scanner. The fact that your adapter works on Windows confirms to me that it's the problem in your setup. You have to make sure that it is supported in OSX. Maybe a SCSI to Firewire adapter that is known to work with OSX and with scanners might be a better solution. Look here:
http://www.xlr8yourmac.com/OSX/panther_scsi_adapters.html

Wim

thanks mac_wt,
i am sure the firewire adapters are much better than the usbs
but the prices is just so...outrageous that I couldnt buy one
and I am not 100% sure that they will work
for the price, i can just sell the scanner and get a newer trouble free scanner

 

[foon]

SCSI is as much art as science, but there are some basic rules. One is that ID=0 is reserved for the computer itself... or perhaps more accurately the SCSI host, which in your case might well be the adaptor. Then assign the scanner to some other ID from 1 through 7. You'll probably need a termination block at the end of the chain. If the scanner has a second SCSI port, put the termination block on that otherwise unused port. Some scanners have only one SCSI port, so a "pass-through" terminator can go on that one with the cable hooked to the block's other side. It's possible that a one-port scanner, which necessarily must be the last device on an SCSI chain, might have a built-in block of termination resistors. The purpose of this termination block is to absorb and attenuate reflected signal that would otherwise bounce back and forth through the cabling and confuse the devices trying to interpret what's going on. You don't mention what you're doing in regard to termination...

I will go try the different id's
i use id 0 because I've read a couple people saying that only 0 works for their mac

my terminator has always been on, isn't that what I suppose to do?