Osx   OSX Support Forum ||  Next   >>
Home Top Change Preferences

anyone using vuescan? November, 25, 2002 3:15 PM danaljohnson
I would like to use vuescan to drive an hp4c scanner on my powerWave. System profiler sees the scanner on the external scsi bus but when I launch vuescan the program hangs. It seems to hang in the stage where the program is looking for attached scanners. If I start the computer without the scanner connected, then vuescan will launch. Is there something modified to the scsi "drivers" with xpostfacto that could affect vuescan?

. RE: anyone using vuescan? December, 07, 2002 3:33 AM joevt
. danaljohnson, ASP shows all kexts installed in /System/Library/ Extensions. kextstat only shows those that are loaded. Some are not loaded because the hardware they refer to is missing or because they require a different version of another kext that you don’t have. Some of the kexts you mention are installed by XpostFacto. XpostFacto installs the following kexts: AppleCurio.kext - code for the SCSI controller (53C94) in the Curio IC that handles the external SCSI bus AppleGrandCentral.kext - Grand Central I/O Subsytem IC AppleMaceEthernet.kext - code for the Mace Ethernet Controller AppleOHare.kext - handles O'Hare IC stuff (ata, serial, floppy, media bay) used in the Performa 6400, PowerMac 5500, 6500, PowerBook 3400 and G3. ApplePowerExpressPE.kext - platform export for Power Express Macs - PowerMac G3 Pro? ApplePowerStarPE.kext - platform export for Power Star Macs including the PowerBook 2400, 3400, 3500, and G3, Performa 54xx, 55xx, and 64xx, UMAX Apus, Power Mac 6500, and 20th Anniversary Mac ApplePowerSurgePE.kext - platform expert for Power Surge Power Macs including the Power Mac 7200, 7300, 7500, 7600, 8500, 8600, 9500, and 9600 and PowerCenter OHareATA.kext - driver for IDE controller in the O'Hare IC. OpenPMU.kext - Power Management Unit code for old hardware PatchedAppleNVRAM.kext - reads and writes to NVRAM on old world Macs PatchedIOSCSICDDrive.kext - fixes a bug on older drives when doing a CD audio read PatchedNDRVSupport.kext - deals with the "squished" cursor in Jaguar on onbaord video (with the name "control") by turning the hardware cursor support off PatchedSCSIDeviceType05.kext - for multimedia devices that comply with the SCSI multimedia commands specification; fixes a problem with SCSI CD, CD-R, CD-RW, DVD, DVD-R etc; originally written by El Gato software; patches GetMechanicalCapabilities. PowerStarCPU.kext – for cpu of Power Star Macs PowerSurgeCPU.kext – for cpu of Power Surge Macs

. RE: anyone using vuescan? December, 04, 2002 12:05 AM tempest
. Hmm, if "anything except Epson and HP SCL...will fail" then why do the HPs fail? The 4p does support HP SCL although it doesn't support everything. Look at http://www.kirchgessner.net/pub/sane/hpinq.4p.txt

. RE: anyone using vuescan? December, 03, 2002 9:44 PM mlilienthal
. This is the post Ed Hamrick made last Nov (2001) in response to several queries: "There's a bug in the driver for the built-in SCSI in the beige G3 on Mac OS X. I've reported this bug to Apple, and they've entered it into their database. Any scanner that uses CDB's more than 6 bytes long (anything except Epson and HP SCL scanners) will fail, and this includes all UMAX scanners." Mark

. The flaw in the SCSI driver December, 03, 2002 1:22 AM OSXGuru
. mlilienthal (or others): Can you point me to the technical description of the flaw in the Mac OS X SCSI driver for the external bus? In theory, it ought to be possible to fix it. And, furthermore, the driver for the external bus is the AppleCurio.kext, which XPostFacto installs, so I guess it's my job to fix it :-)

. RE: anyone using vuescan? December, 02, 2002 10:58 PM danaljohnson
. I notice that ASP lists a number of extensions that don't show up when I execute kextstat. For example, ASP shows a number of entries named Patched*.kext (PatchedSCSIDeviceType05.kext for example). As they used to say, huh?

. RE: anyone using vuescan? December, 02, 2002 9:57 PM joevt
. You can get more info about kexts by looking at their info.plist files. com.apple.driver.AppleSym8xx is a SCSI Controller driver for the following apple53C8xx Apple53C875Card ATTO,ExpressPCIProLVD ATTO,ExpressPCIProUL2D ATTO,ExpressPCIProUL3D com.apple.driver.AppleHollywood seems to be for SCSI CD or DVD drives. gchron has 4 drivers that depend on com.apple.iokit.IOSCSIFamily: com.acard.driver.ACard62xxM - ACARD IDE card com.apple.driver.AppleCurio - external SCSI (5 MB/s) com.apple.driver.AppleMesh - internal SCSI (10 MB/s) com.apple.driver.AppleSym8xx - Apple or ATTO SCSI card There's an app called IORegistryExplorer included with the developer tools that shows all kinds of interesting info about devices and drivers. It might tell which of mesh or Sym8xx his scanner and CDROM is connected to if ASP will not.

. RE: anyone using vuescan? December, 02, 2002 12:55 PM gchron
. Well I can tell you that. When I turn on the scanner the driver that is used it the: com.apple.driver.AppleHollywood (1.2.1) Now for your questions I can see here The com.apple.driver.AppleUSBIrDA (I don't have IrDA enabled) is for a IRDA USB Adapter I have installed. The com.acard.driver.ACard62xxM (Acard PCI card?) Yes it is from a ACARD card com.apple.driver.AppleSym8xx (Symantec?) This is not a symantec extension. Actually you can see that it is from com.apple so it is an apple extension. The com.apple.iokit.Apple_DEC21x4Ethernet (?) yes it is an apple ethernet card. Sorry but I cannot help you any more for the part of the extensions.

. RE: anyone using vuescan? December, 02, 2002 9:56 AM mlilienthal
. For gchron (and anyone else who might shed light on this): I confirm I am running OS X 10.2.2 (6F21) The only discrepencies between your list and mine (aside from the obvious Logitech, Symantec and Kensington!): You have: com.apple.driver.AppleUSBIrDA (I don't have IrDA enabled) com.acard.driver.ACard62xxM (Acard PCI card?) com.apple.driver.AppleSym8xx (Symantec?) com.apple.iokit.Apple_DEC21x4Ethernet (?) I have: com.apple.driver.AppleHollywood com.apple.nke.ppp Otherwise, all kexts match, including version numbers. It occurs to me that it might be the scanner itself which works in this case. I do recall vaguely somewhere that certain scanner types use a different command set which might work in this case...but I also recall (just as vaguely) that this is a small minority Mark

. RE: anyone using vuescan? November, 29, 2002 2:26 PM gchron
. Well because I would like to know what causes the problem on your machine I am posting here to you a complete list of mu kexts that are now loaded to my machine. These have and the version thay use near them so you can see is you have something older. If you I can send you the newer version. Also I will boot with my scanner turned on in case and I can see if it loading any kext. I do not have installed anything as UMAX does not have any driver so if there is something it will be from the OSX installation disks. [Mac9500:~] george% kextstat Index Refs Address Size Wired Name (Version) 1 1 0x0 0x0 0x0 com.apple.kernel (6.2) 2 11 0x0 0x0 0x0 com.apple.kernel.bsd (6.2) 3 38 0x0 0x0 0x0 com.apple.kernel.iokit (6.2) 4 37 0x0 0x0 0x0 com.apple.kernel.libkern (6.2) 5 27 0x0 0x0 0x0 com.apple.kernel.mach (6.2) 6 2 0x0 0x0 0x0 com.apple.iokit.IOADBFamily (6.2) 7 1 0x0 0x0 0x0 com.apple.iokit.IONVRAMFamily (6.2) 8 1 0x0 0x0 0x0 com.apple.iokit.IOSystemManagementFamily (6.2) 9 1 0x0 0x0 0x0 com.apple.iokit.ApplePlatformFamily (6.2) 10 1 0x0 0x0 0x0 com.apple.driver.AppleNMI (6.2) 11 12 0x13454000 0x9000 0x8000 com.apple.iokit.IOPCIFamily (1.2) <4 3> 12 0 0x1347c000 0x3000 0x2000 com.apple.driver.ApplePowerSurgePE (1.2.2) <11 4 3> 13 0 0x13484000 0x6000 0x5000 com.apple.BootCache (12.1) <5 3 2> 14 2 0x134f1000 0x19000 0x18000 com.apple.iokit.IOGraphicsFamily (1.2.2) <11 4 3> 15 3 0x13555000 0x28000 0x27000 com.apple.iokit.IOHIDFamily (1.2) <4 3> 16 3 0x135a5000 0x2000 0x1000 com.apple.iokit.IOHIDSystem (1.2) <15 4 3> 18 0 0x135e9000 0x4000 0x3000 com.apple.driver.AppleGossamerPE (2.0.0d5) <11 5 4 3> 21 0 0x13641000 0x3000 0x2000 oldworld.support.PowerSurgeCPU (1.1b1) <11 4 3> 22 0 0x13658000 0x6000 0x5000 com.apple.driver.AppleMacRiscPCI (1.3) <11 5 4 3 2> 23 0 0x13691000 0x3000 0x2000 com.apple.driver.AppleGrandCentral (1.0.1) <5 4 3> 24 5 0x137b9000 0xe000 0xd000 com.apple.iokit.IOSCSIFamily (1.2.2) <5 4 3> 25 0 0x137e5000 0x7000 0x6000 com.acard.driver.ACard62xxM (1.5.1) <24 11 5 4 3> 26 0 0x137fe000 0x2000 0x1000 oldworld.support.PatchedAppleNVRAM (1.0) <4 3> 27 1 0x138a0000 0x38000 0x37000 com.apple.iokit.IOFireWireFamily (1.2.2) <4 3> 28 0 0x1393a000 0x11000 0x10000 com.apple.driver.AppleFWOHCI (1.2.3) <27 11 4 3> 29 6 0x139b2000 0x1b000 0x1a000 com.apple.iokit.IOUSBFamily (1.9.4) <5 4 3> 30 0 0x139fe000 0xb000 0xa000 com.apple.driver.AppleUSBOHCI (1.9.4fc5) <29 11 5 4 3> 31 1 0x13a61000 0x16000 0x15000 com.apple.iokit.IONDRVSupport (1.2.2) <14 11 4 3> 33 0 0x13aeb000 0x5000 0x4000 com.apple.driver.AppleCurio (1.0.0f1) <24 5 4 3> 34 2 0x13b2b000 0x1d000 0x1c000 com.apple.iokit.IONetworkingFamily (1.2) <5 4 3 2> 35 0 0x13b7d000 0x7000 0x6000 com.apple.driver.AppleMaceEthernet (1.0.2) <34 5 4 3 2> 36 0 0x13b8c000 0x4000 0x3000 com.apple.driver.AppleVIA (1.1) <5 4 3> 37 0 0x13ba5000 0x7000 0x6000 com.apple.driver.AppleMesh (1.1.1) <24 5 4 3> 38 0 0x13bce000 0x6000 0x5000 com.apple.driver.AppleSym8xx (1.1.0) <24 11 5 4 3> 39 0 0x13c03000 0x9000 0x8000 com.apple.driver.AppleUSBHub (1.9.2) <29 5 4 3> 40 3 0x13c34000 0x14000 0x13000 com.apple.iokit.IOSCSIArchitectureModelFamily (1.2.2) <5 4 3> 41 0 0x13c6c000 0x3000 0x2000 com.apple.iokit.IOSCSIParallelInterfaceProtocolTransport (1.2.2) <40 24 5 4 3> 42 0 0x13cb0000 0xf000 0xe000 com.apple.iokit.Apple_DEC21x4Ethernet (1.1.3b1) <34 11 5 4 3 2> 43 0 0x13cd2000 0x7000 0x6000 com.apple.driver.AppleCuda (1.0.0d3) <5 4 3> 44 0 0x13cfd000 0x3000 0x2000 com.apple.driver.AppleUSBComposite (1.9.2) <29 5 4 3> 45 4 0x13d33000 0x19000 0x18000 com.apple.iokit.IOStorageFamily (1.2.3) <4 3 2> 46 1 0x13da4000 0x11000 0x10000 com.apple.iokit.IOSCSIBlockCommandsDevice (1.2.2) <45 40 5 4 3 2> 48 2 0x13e1a000 0xd000 0xc000 com.apple.iokit.IOCDStorageFamily (1.2) <45 5 4 3 2> 49 1 0x13e60000 0x7000 0x6000 com.apple.iokit.IODVDStorageFamily (1.2) <48 45 5 4 3 2> 50 0 0x13f00000 0x17000 0x16000 com.apple.iokit.IOSCSIMultimediaCommandsDevice (1.2.2) <49 48 46 45 40 5 4 3 2> 51 0 0x13fd5000 0x16000 0x15000 com.Logitech.driver.HIDDevices (1.0.4) <29 16 15 5 4 3> 52 0 0x1401c000 0x3000 0x2000 com.apple.driver.AppleADBKeyboard (2.3.2d1) <16 15 6 5 4 3> 53 2 0x133b0000 0xb000 0xa000 com.apple.iokit.IOSerialFamily (6.0.1d19) 54 0 0x133bb000 0xb000 0xa000 com.apple.driver.AppleSCCSerial (1.2.3) <53> 55 0 0x133c6000 0xa000 0x9000 com.apple.iokit.IOUSBUserClient (1.9.4) <29> 57 0 0x133d8000 0x2f000 0x2e000 com.apple.ATIRadeon (1.2.6) <31 14 11> 58 0 0x1340f000 0x6000 0x5000 com.apple.driver.AppleADBMouse (2.0.5d3) <16> 60 2 0x1341d000 0x1e000 0x1d000 com.apple.iokit.IOAudioFamily (1.3.1) 61 1 0x1343b000 0x7000 0x6000 com.apple.driver.AppleDBDMAAudio (1.8.1b1) <60> 65 0 0x13492000 0x2c000 0x2b000 com.apple.driver.AppleUSBIrDA (1.3) <53 29> 66 0 0x13445000 0x4000 0x3000 com.apple.driver.AppleOWScreamerAudio (1.8.1) <61 60> 67 0 0x13684000 0x6000 0x5000 com.apple.nke.SharedIP (1.2.1) 68 2 0x13794000 0x3000 0x2000 com.Symantec.kext.SymOSXKernelUtilities (1.0.3) 69 1 0x13797000 0x6000 0x5000 com.Symantec.kext.SymEvent (1.0.2) <68> 70 0 0x1379d000 0x3000 0x2000 com.Symantec.kext.KTUM (8.0.4) < 69 68> 71 0 0x135e0000 0x2000 0x1000 com.apple.kext.HFS_MacGreek (1.0) 72 0 0x137a4000 0x3000 0x2000 com.powerlogix.kext.PLKEXT (1.1b2) 73 0 0x1384a000 0x6000 0x5000 com.apple.nke.IPFirewall (1.2.1)

. RE: anyone using vuescan? November, 29, 2002 12:15 PM danaljohnson
. Thanks Mark. Gee, the hard thing to explain is why gchron's system does work. Do the UMAX scanners use different drivers? If not, how can it work? I guess that a potential solution is to replace the scsi drivers, right? I am rather naive about this, but which system files are involved? thanks all

. RE: anyone using vuescan? November, 29, 2002 9:06 AM mlilienthal
. System: PM8500/G3 400//OS X 10.2.x;OS 9.1.x//Adaptec 2906 SCSI//Apple ColorOneScanner 1200/30 (SCSI) Under OS X with this system, ASP is able to "see" the scanner when it is connnected to the 8500's external SCSI bus. So can "VueScan." However, VueScan *appears* to hang when asked to scan...after quite a long period of time (several minutes), VueScan will show what it interprets as a scan-- basically a blank black document. Using the same configuration under OS 9.x works fine. It will also work fine under OS X 10.2 if the scanner is connected to the Adaptec card instead. Similarly, when I moved the Adaptec card and scanner to my new G4 MDD, VueScan continues to work properly under OS X... Ed Hamrick identified the cause about a year ago as a flaw in the OS X SCSI drivers and says he reported the same to Apple. The problem has something to do with the physical length of the commands being allowed by the driver-- commands which identify devices and which control hard drives and the like seem unaffected, but commands to devices like scanners appear to be truncated...There has been on and off discussion since this time last year in the newsgroup he uses for tech support, including a technical description of precisely what is happening. This is not a VueScan problem, nor is it a PostFacto problem...it is an OS X/ legacy hardware issue. Mark

. RE: anyone using vuescan? November, 28, 2002 11:31 AM gchron
. Then how it works with my external SCSI on my 9500???? I do not think that this is the problem. I have to SCSI Buses. One has an internal SCSI Hard disk and the second has the scanner and a CDROM. Also I have an ACARD IDE card seen as SCSI BUS 3 where there is a Hard disk and a DVD ROM. No problems with the scanner. I do not know what could be the problem.

. RE: anyone using vuescan? November, 28, 2002 10:05 AM mlilienthal
. I can confirm wove's assessment. The problem would seem to be within OS X's SCSI driver and the manner in which it handles the two SCSI busses on legacy machines (like my 8500). ASP, and indeed VueScan, can *see* the scanner, but the scanning commands being sent to it by VueScan are misinterpreted or truncated...Using a simple Adaptec SCSI card (and hence a different driver) works fine.

. RE: anyone using vuescan? November, 27, 2002 6:38 PM wove
. There is a SCSI bug in OS X that prevents VueScann from working with the external buss on the machines that have a seperate internal and external buss. The external buss works fine with drives, but it seems to have problems with scanners. If you dig through some of Apple's tech stuff, I believe you will find one that address this. I believe that it relates to a necessary command either being buggy, or perhaps not even being present. bill

. RE: anyone using vuescan? November, 27, 2002 4:23 PM gchron
. Also sorry for the second post the scanner is shown 5 times instead of onw in the ASP. All with the same ID and the same bus.

. RE: anyone using vuescan? November, 27, 2002 4:22 PM gchron
. Yes all the devises are shown in the same bus. This problem was shown from 10.1. I did not made the system to see the disks in a second BUS. But all the system is working with no problem

. RE: anyone using vuescan? November, 27, 2002 1:36 PM danaljohnson
. Thanks for checking that. One last question (I promise???) Does your external scsi bus show up as a separate chain in system profiler? On my system, both internal and external scsi and also the acard controller show up on one bus. In ASP, the LUN is 0, I presume that is the bus # ? I downloaded silverfast demo and it seems to hang the same way as VueScan. It has a more verbose log file that I can read. In the log I see that silverfast discovers the scanner on bus 0 and then hangs after an "INQUIRE" sequence. Maybe a command is sent on the wrong bus?

. RE: anyone using vuescan? November, 27, 2002 12:50 PM gchron
. I can scan with no problems with the downloaded version

. RE: anyone using vuescan? November, 27, 2002 12:05 PM danaljohnson
. Ed is rather terse in his replies, but he restated that the hp 4c won't work with the built-in scsi and osX. He didn't explain why it can be see with ASP. I guess I should try silverfast before arranging my trip to Goodwill....

. RE: anyone using vuescan? November, 27, 2002 11:50 AM gchron
. I can email you my version. But I also can download and test the new version. I am now downloading the version 7.5.63

. RE: anyone using vuescan? November, 26, 2002 10:01 PM danaljohnson
. thanks tempest! it looks like this might be an issue with hp scanners. I am trying to get Ed to shed some light on this. Since Apple System Profiler can see the scanner, I suspect that it could be supported via VueScan. The 4c is good enough for my needs (basic copying mostly) so I hope I can find some solution - seems a waste to pitch it and buy a new scanner.

. RE: anyone using vuescan? November, 26, 2002 7:36 PM tempest
. I have an HP ScanJet 4p and it has never worked under OS X (currently on 10.2.2) connected to my 8500. All versions of VueScan wedge hard upon launch. The scanner works fine under OS 9.

. RE: anyone using vuescan? November, 26, 2002 5:01 PM danaljohnson
. oops, I guess the formatting didn't hold... sorry `bout that...

. RE: anyone using vuescan? November, 26, 2002 5:00 PM danaljohnson
. gee, what do you suggest? >> I am running mac osX 10.2.2 on an "old world" machine, powerWave (like >> 9500) using xPostfacto. If I power up with no scanner attached, then I >> can start VueScan. If I powerup the compuer with my hp 4c attached to >> the external scsi bus, VueScan hangs at the splash screen. >You'll probably need to use an Adaptec SCSI PCI card to get this >to work with SCSI. The built-in SCSI isn't going to work. > >Regards, >Ed Hamrick


Home Top Change Preferences