USB and NT 4.0: What about digi-cams?
Hallo! Some notes and questions referring to USB for Windows NT: DELL's USB-software for NT with the Inside-Outside Drivers works great with mem-sticks. Sticks don't come up with special drivers, they are plugged and recognized at once, a drive with new letter is created.
Hallo!
Some notes and questions referring to USB for Windows NT:
DELL's USB-software for NT with the Inside-Outside Drivers works great with mem-sticks. Sticks don't come up with special drivers, they are plugged and recognized at once, a drive with new letter is created. The USB-Software even plays in combination with hubs, when the usbhub-driver in R62200 has been changed against a new version from Inside-Outside.
Now the problems:
The digi-cam is recognized at once plugging it into one of the four hub-ports, but ... here the log-file of UsbTray.exe for the digi-cam (it's that tiny "cult"-JamCam!)
VID ?????????????????? (obviously there is no vendor-Id to be found in the registry!)
Device Descriptor: 12011001FF01FF084E080100000101020001
Config Descriptor: 09021900010100C0000904000001FF010000070581020800FF
Class: 255 (0xFF)
Class Name: Vendor Specific
SubClass: 1 (0x1)
Protocol: 255 (0xFF)
Power (mA): 0 (0x0)
Powered by: Power Supply
Manufacturer: KBGear Interactive
Product Name: JamCam
Driver ;(??????????? (The USB-software doesn't know which driver to take!)
Load Status: Loaded
NT Error Status: -1073741275 (0xC0000225)
USBD Error Status: 0 (0x0)
Error Msg: No Registry Entry Found for Device ID
and here the log for the mem-stick:
VID08EC_PID0012_RootHub0_Port1_Port3 (from where does the software know the Vendor-Id of the stick?)
Device Descriptor: 1201000200000040EC081200000201020301
Config Descriptor: 0902200001010080590904000002080650000705810240000007050202400000
Class: 8 (0x8)
Class Name: Storage
SubClass: 0 (0x0)
Protocol: 0 (0x0)
Power (mA): 178 (0xB2)
Powered by: USB BUS
Manufacturer: Kingston
Serial Number: 08709C3504000AF1
Product Name: DataTraveler2.0
Driver: usbms (obviously the USB-software takes this driver automatically)
Load Status: Loaded
NT Error Status: 0 (0x0)
USBD Error Status: 0 (0x0)
Error Msg:
1. Why doesn't this happen with the camera, it's a storage-device too?! Or does the USB-software "see" something different?
2. From where can I get a registry-entry for the camera's device ID? There is an INF-File and a driver supplied with the camera, unfortunately it's provided for Windows98 and ME not for NT.
3. Any chance to enter manually the specific data into the registry, above all the device-entry?
Any hint appreciated!
Bye, Hajo
Some notes and questions referring to USB for Windows NT:
DELL's USB-software for NT with the Inside-Outside Drivers works great with mem-sticks. Sticks don't come up with special drivers, they are plugged and recognized at once, a drive with new letter is created. The USB-Software even plays in combination with hubs, when the usbhub-driver in R62200 has been changed against a new version from Inside-Outside.
Now the problems:
The digi-cam is recognized at once plugging it into one of the four hub-ports, but ... here the log-file of UsbTray.exe for the digi-cam (it's that tiny "cult"-JamCam!)
VID ?????????????????? (obviously there is no vendor-Id to be found in the registry!)
Device Descriptor: 12011001FF01FF084E080100000101020001
Config Descriptor: 09021900010100C0000904000001FF010000070581020800FF
Class: 255 (0xFF)
Class Name: Vendor Specific
SubClass: 1 (0x1)
Protocol: 255 (0xFF)
Power (mA): 0 (0x0)
Powered by: Power Supply
Manufacturer: KBGear Interactive
Product Name: JamCam
Driver ;(??????????? (The USB-software doesn't know which driver to take!)
Load Status: Loaded
NT Error Status: -1073741275 (0xC0000225)
USBD Error Status: 0 (0x0)
Error Msg: No Registry Entry Found for Device ID
and here the log for the mem-stick:
VID08EC_PID0012_RootHub0_Port1_Port3 (from where does the software know the Vendor-Id of the stick?)
Device Descriptor: 1201000200000040EC081200000201020301
Config Descriptor: 0902200001010080590904000002080650000705810240000007050202400000
Class: 8 (0x8)
Class Name: Storage
SubClass: 0 (0x0)
Protocol: 0 (0x0)
Power (mA): 178 (0xB2)
Powered by: USB BUS
Manufacturer: Kingston
Serial Number: 08709C3504000AF1
Product Name: DataTraveler2.0
Driver: usbms (obviously the USB-software takes this driver automatically)
Load Status: Loaded
NT Error Status: 0 (0x0)
USBD Error Status: 0 (0x0)
Error Msg:
1. Why doesn't this happen with the camera, it's a storage-device too?! Or does the USB-software "see" something different?
2. From where can I get a registry-entry for the camera's device ID? There is an INF-File and a driver supplied with the camera, unfortunately it's provided for Windows98 and ME not for NT.
3. Any chance to enter manually the specific data into the registry, above all the device-entry?
Any hint appreciated!
Bye, Hajo
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
