Re: Trying to get a Kodak EasyShare C875 working

Hi Mentore

Mentore Siesto wrote:
Il giorno Fri, 14 Sep 2007 15:06:58 UTC, Peter Brown <losepeteSPAM-ME-NOT@xxxxxxxxxxxx> ha scritto nientepopodimenoche:

Hi Mentore


What buildlevels are the USB drivers at?

The current base (USBEHCD, USBOHCD, USBD, USBHID) and USBMSD drivers are 10.162

I updated the entire base to the latest level some months ago.
You should also be using the current os2dasd:-

[H:\OS2\BOOT]bldlevel os2dasd.dmd
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature: @#IBM:14.104#@ IBM DASD Manager
Vendor: IBM
Revision: 14.104
File Version: 14.104
Description: IBM DASD Manager
E:\os2\boot>bldlevel os2dasd.dmd
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature: @#IBM:14.091#@ IBM DASD Manager
Vendor: IBM
Revision: 14.91
File Version: 14.91
Description: IBM DASD Manager

So this is not the latest. Do you think it is related to camera detection? The Kodak C875 isn't a MSD.



Not sure if it will have any effect on using the camera but will be of benefit to any other drive device that uses it.


I don't know if the USBMSD.ADD directive is doing something strange.
Maybe I should remove /REMOVABLES and /CHS options? I tried those
options when I tried to convince my Creative Zen MP3 player to
cooperate with eCS (No success).
USBcfg is a handy tool to help configure USB to your requirements. It also contains some Help and Tips http://hobbes.nmsu.edu/pub/os2/system/usbcfgb7a.zip

I think I would try this line:-

BASEDEV=USBMSD.ADD /FLOPPIES:0 /REMOVABLES:1


Come to think of it the "rule" seems to be Known Removables + 1 so maybe that line should be

BASEDEV=USBMSD.ADD /FLOPPIES:0 /REMOVABLES:2



The same I thought: I'll let you know the results asap. I must also try and play with gPhoto/2 options.

USB Resource Manager Device Driver:

5/09/06 20:47 32.750 0 a--- usbresmg.sys
(From Cameraderie 1.5)

USBCALLS DLL:

20/09/06 14:35 7.724 0 a--- usbcalls.dll

This DLL too is taken from Cameraderie 1.5.

On my system, there are some other USBCALLS.DLL libraries:

Directory of F:\mmedia\grafica\camera15

20/09/06 14:35 7.724 0 a--- usbcalls.dll

Directory of F:\mmedia\grafica\GPHOTO2\bin

9/07/06 22:03 11.805 54 a--- usbcalls.dll

Directory of F:\mmedia\grafica\tame

19/07/05 20:59 30.467 0 a--- usbcalls.dll

Is there any chance that 1 of the above usbcalls.dll is in the LibPath? - that could be causing problems.

I thought about this issue, but the only usbcalls into LIBPATH is in \ecs\dll. So no conflict about it.



Maybe there is.

As you have several different versions of usbcalls.dll for different apps I would suggest that you do *Not* put a copy in [BootDrive]:\ecs\dll as I think that could get used instead of the required usbcalls.dll


Maybe there should be a "unified" usbcalls.dll file rather than loads of different versions for different apps...


On a related note: I had a problem awhile back after installing USBDock - Tame no longer worked.

I think this was something to do with the USBRESMG.SYS supplied with USBDock was not compatible with Tame...

aha! Here is a copy of my post to Eugene (USBDock):-

"Hi

I recently (couple of weeks ago) installed USBDock and updated usbresmg.sys with the version supplied with USBDock.

Today, for the 1st time in several weeks, I needed to use my usb scanner so plugged it in and ran Tame.

Tame Failed to scan.

Using the command line
scanimage -L
does not show the scanner attached.

Both USBDock and USB Resource Manager show the scanner attached.

The scanner works on other systems so it is not hardware failure.

Reverting from the usbresmg.sys file supplied with USBDock to the version supplied with Tame104b and rebooting I found that the scanner now worked.

Conclusion: The usbresmg.sys file supplied with USBDock_20061201 does not allow the scanner to work.

Thought you might like to know."


Maybe you want to check if the problem there is usbresmg.sys related.

Regards

Pete






.

Relevant Pages

  • Re: Digital Camera
    ... scanner plugged into a USB hub, and you didn't mention that a network was ... then checking to see if the camera USB connection works? ... , to see if an extra driver letter ...
    (microsoft.public.windowsxp.general)
  • Re: USB bus fails to see devices
    ... devices (camera and scanner) are no longer seen by the USB bus. ... The printer and scanner are connected to the root hub; ...
    (Debian-User)
  • Forgot to mention !
    ... Have installed latest Manufacturer Vista drivers ... scanner and camera working perfectly if connected closer to the computer ... ending wit a USB powered Hub, then another pieces of 1 meter cable to reach each peripherial. ...
    (alt.sys.pc-clone.dell)
  • Re: Musteck Scanner / Canon CameraCanon
    ... >> Do you have the latest software for the Canon IXUS 40 camera? ... Model number of Mustek Scanner. ... USB, SCSI, Parallel port? ... USB devices have a connector at the device itself, ...
    (comp.periphs.scanners)
  • trying to get a Benq4300U USB scanner working .....
    ... I have tried to get my scanner to work a number of times under Fedora Core 6 on my machine but have not succeeded. ... # For SCSI scanners specify the generic device, ... # These USB devices will be probed automatically ...
    (Debian-User)