[PROBLEMCHYLD]

jds, on 12 April 2012 - 08:36 AM, said:

Well, you could include the Microsoft driver that I customized and the 'wmdmcmd.exe' utility, this is sufficient for rudimentary support of standard PTP/MTP devices and is fairly small (and it works and it doesn't break TWAIN drivers).

Joe.

Will do sir. Thanks

[Giant2011]

Hey Joe where did you find this wmdmcmd.exe utility

[Giant2011]

I already have found it thank you.

[Giant2011]

Hello there !! Well I became very curious if my scanner would still work after installing wia on my windows 98 computer. One thing changed. In the past I saw scanners &
cameras in control panel. After installing wia I see it in explorer. I installed my fuji camera and the software that was provided with it. It aslo included the ptp driver.
I could see it under cameras & scanners in explorer. Today I connected my scanner to my computer and I saw it under scanners & cameras in explorer.
I started my scan software from hp and it recognized my hp scanner and I could scan normally.

[bphlpt]

Since others have not had your success, in fact have seemed to have had utter failure, would you mind, in excruciating detail, explaining what you used, HW & SW, where you got the software with name, version, and links if possible, what order you installed things HW & SW, etc to see if anyone else can duplicate your efforts? I do realize it might be very hardware specific, so everyone's experience might be different, but so far it has seemed this is too problematic to include for everyone, since it has broken things, unless you have been able to find a method that no one else has until now? The results you describe seem to be the way it is intended to work.

Cheers and Regards

[Giant2011]

I really agree with your answer.

[Giant2011]

I I will try to make a list.

[Giant2011]

Windows 98 SE 4.10.2222B winth kernelex 4.5.2 installed
Motherboard Aopen
Chipset : Intel i440BX/ZX
Processor : Intel Pentium III E @ 850 MHz
Memory : 512 MB (2 x 256 SDRAM )
NVIDIA GeForce2 MX/MX 400
usb 2.0 card Belkin
80 gigabyte harddisk advance 29100 ultra dma100 controller
hp scanjet 5300 C
HP-scannersoftware v3.00
Fujifilm AV200
Finepixviewer 5.4.11E
Wia11
mtp12 which I will remove
DirectX 9.0c (march 2006)
I have also a soundblastercard and
a TV card installed. But I think
that it is not important.

[bphlpt]

You might want to detail your SW install procedures, then we'll just have to see if anyone can duplicate or further improve upon your results.

Cheers and Regards

[Giant2011]

HP-scannersoftware v3.00 was already installed. Later when I bought my Fuji camera I installed first wia11.exe and then
Finepixviewer 5.4.11E. And then mtp12 to experiment. But I understand that can be removed. When I want to transfer a
a picture from my camera Quickdcf2.exe in the finepixviewer directory. And then finepixviewer is started automatically.
In this directory there is another file called ptpbridge.exe. I think that this program is started by quickdfw.exe in the backbround
to build a bridge to the camera using the ptp driver.

[PROBLEMCHYLD]

I still would like to add the mtp/ptp drivers. Any ideas?

[PROBLEMCHYLD]

jds, on 12 April 2012 - 03:05 AM, said:

Well, I added my Fujifilm camera's USB ID, etc. to the INF file, so basically this invoked the same 'PTP' section as for the "Generic" case. The driver installed fine, asking for the location of a DLL or two, after which the camera appeared in the Device Manager as an Imaging Device, and reported as "working properly". It also showed up in 'Scanners & Cameras'.

Joe.

When you tested, did you have WPDUSB9X.SYS on the system? It seems like the two DLL files has gotten us a step closer.
We can probably just use your combined MTPPTP.INF files with the two DLL files and go from there

PTPUSB.DLL 4.90.3000.0
PTPUSD.DLL 4.90.3000.0

[PROBLEMCHYLD]

Is this what the main MTPPTP.INF should look like?
If we can get the inf file working, maybe we can get some devices working.

[Version]
Signature=$CHICAGO$
Class=WPD
ClassGUID={EEC5AD98-8080-425f-922A-DABF3DE3F69A}
Provider=%MSFT%
DriverVer=03/11/2005,1.10.0.0

[ClassInstall]
AddReg=MTPUSBHW,MTPUSBSW

[Manufacturer]
%MfgName%=Generic

[Generic]
%FujiFilm.DeviceDesc%=Generic_MTP,USB\VID_04CB&PID_01FD
%iTouch.DeviceDesc%=Generic_MTP,USB\VID_05AC&PID_1293

[MTPUSBHW]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,WPDUSB9X.SYS

[MTPUSBSW]
HKR,,WMDMSPCLSID,,"{BF7F444B-E759-4EA3-96EA-3DDF7B924919}"
HKR,,ShowInShell,0x10001,0x1
HKR,,"SupressGetStorageSerialNum",0x10001,1
HKR,,"Interfaces",0x00010000,"{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}","{14480d3f-7a47-4a75-aaef-b14f56397153}"
HKCR,CLSID\{BF7F444B-E759-4EA3-96EA-3DDF7B924919},,,"MTPSPServiceProvider Class"
HKCR,CLSID\{BF7F444B-E759-4EA3-96EA-3DDF7B924919}\InProcServer32,,,%11%\MTPSP.DLL
HKCR,CLSID\{BF7F444B-E759-4EA3-96EA-3DDF7B924919}\InProcServer32,ThreadingModel,,Apartment
HKCR,MTPSPServiceProvider.MTPSPServiceProvider,,,"MTPSPServiceProvider Class"
HKCR,MTPSPServiceProvider.MTPSPServiceProvider\CLSID,,,"{BF7F444B-E759-4EA3-96EA-3DDF7B924919}"
HKCR,MTPSPServiceProvider.MTPSPServiceProvider\CurVer,,,"MTPSPServiceProvider.MTPSPServiceProvider.1"
HKCR,MTPSPServiceProvider.MTPSPServiceProvider.1,,,"MTPSPServiceProvider Class"
HKCR,MTPSPServiceProvider.MTPSPServiceProvider.1\CLSID,,,"{BF7F444B-E759-4EA3-96EA-3DDF7B924919}"
HKLM,"SOFTWARE\Microsoft\Windows Media Device Manager\Plugins\SP\MTPSP",ProgID,,"MTPSPServiceProvider.MTPSPServiceProvider"
HKLM,"SOFTWARE\Microsoft\Windows Media Device Manager\Plugins\SP\MTPSP",PnPAware,0x10001,0x1
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AutoplayHandlers\DeviceClasses\{14480d3f-7a47-4a75-aaef-b14f56397153}","DeviceGroup",,"PortableAudioPlayer"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AutoplayHandlers\DeviceClasses\{14480d3f-7a47-4a75-aaef-b14f56397153}","Label",,%Autoplay.Label%
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AutoplayHandlers\DeviceClasses\{14480d3f-7a47-4a75-aaef-b14f56397153}","DeviceHandlers",,"MTPMediaPlayerHandler"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AutoplayHandlers\DeviceClasses\{14480d3f-7a47-4a75-aaef-b14f56397153}","Icons",0x00010000,"%11%\SHELL32.DLL,-299"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AutoplayHandlers\DeviceHandlers\MTPMediaPlayerHandler\EventHandlers\DeviceArrival","MTPMediaPlayerArrival",,""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AutoplayHandlers\EventHandlers\MTPMediaPlayerArrival\",,0x00000012

[Strings]
FujiFilm.DeviceDesc="MTP Device - FujiFilm"
iTouch.DeviceDesc="MTP Device - iTouch"
MfgName="MTP Devices - Generic"
Provider="Microsoft"
;

This post has been edited by PROBLEMCHYLD: 01 May 2012 - 09:42 AM

[PROBLEMCHYLD]

Lets try adding this code to the above code and see what we get

[STI.PTPUSBSection]
Addreg=STI.PTPUSB.AddReg,STI.Usb.AddReg
CopyFiles=STI.PTPUSB.CopyFiles,STI.Usb.CopySys32Files
DeviceData=STI.PTPUSBDeviceData
SubClass=StillImage
DeviceType=2
Capabilities=0x35
UninstallSection=
Events=STI.PTPUSBDeviceEvents
[STI.PTPUSB.CopyFiles]
ptpusd.dll
ptpusb.dll
[STI.PTPUSB.AddReg]
HKR,,HardwareConfig,1,4
HKR,,USDClass,,"{B5EE90B0-D5C5-11D2-82D5-00C04F8EC183}"
HKCR,CLSID\{B5EE90B0-D5C5-11D2-82D5-00C04F8EC183},,,"PIMA15740 Cameras WIA USD"
HKCR,CLSID\{B5EE90B0-D5C5-11D2-82D5-00C04F8EC183}\InProcServer32,,,%11%\ptpusd.dll
HKCR,CLSID\{B5EE90B0-D5C5-11D2-82D5-00C04F8EC183}\InProcServer32,ThreadingModel,,"Both"
HKCR,CLSID\{65aab96d-71b5-44d1-ab9e-488f730e7870},,,"PIMA15740 USB Transport"
HKCR,CLSID\{65aab96d-71b5-44d1-ab9e-488f730e7870}\InProcServer32,,,%11%\ptpusb.dll
HKCR,CLSID\{65aab96d-71b5-44d1-ab9e-488f730e7870}\InProcServer32,ThreadingModel,,"Both"
[STI.PTPUSBDeviceData]
Model=PIMA15740
Server=local
UI DLL=sti.dll
UI Class ID={4DB1AD10-3391-11D2-9A33-00C04FA36145}
TransportCLSID={65aab96d-71b5-44d1-ab9e-488f730e7870}
[STI.PTPUSBDeviceEvents]
Connected=%DCConnected%,{A28BBADE-64B6-11d2-A231-00C04FA31809},*
Disconnected=%DCDisconnected%,{143E4E83-6497-11d2-A231-00C04FA31809},*

[jds]

Giant2011, on 15 April 2012 - 07:45 AM, said:

HP-scannersoftware v3.00 was already installed. Later when I bought my Fuji camera I installed first wia11.exe and then
Finepixviewer 5.4.11E. And then mtp12 to experiment. But I understand that can be removed. When I want to transfer a
a picture from my camera Quickdcf2.exe in the finepixviewer directory. And then finepixviewer is started automatically.
In this directory there is another file called ptpbridge.exe. I think that this program is started by quickdfw.exe in the backbround
to build a bridge to the camera using the ptp driver.

Well, as the Finepix software installs its own PTP driver, I suspect your camera would work this way withouth installing WIA. If WIA really is working, you should be able to access it via the "Scanner and Camera Wizard" (in Start/Programs/Accessories).

PROBLEMCHYLD, on 30 April 2012 - 07:51 PM, said:

jds, on 12 April 2012 - 03:05 AM, said:

Well, I added my Fujifilm camera's USB ID, etc. to the INF file, so basically this invoked the same 'PTP' section as for the "Generic" case. The driver installed fine, asking for the location of a DLL or two, after which the camera appeared in the Device Manager as an Imaging Device, and reported as "working properly". It also showed up in 'Scanners & Cameras'.

Joe.

When you tested, did you have WPDUSB9X.SYS on the system? It seems like the two DLL files has gotten us a step closer.
We can probably just use your combined MTPPTP.INF files with the two DLL files and go from there

PTPUSB.DLL 4.90.3000.0
PTPUSD.DLL 4.90.3000.0

Well, unfortunately, I can't test this stuff at the moment. I've since restored my system from Ghost backups and am WIA-free once again. Perhaps later, when my wife regains her patience (it's her Fujifilm camera, mine's a Panasonic and works via mass storage).

Joe.

[PROBLEMCHYLD]

I haven't given up on this yet.
I believe we can get this thing working with some patience, testers, devices, and each other.
I'm looking into borrowing some devices to test. I'll keep you guys posted.

[cybertheque]

I just purchased a Canon Rebel T3i DSLR (600D) and wanted to control it with PTP on Windows 2000; I had decided to try migrating the PTP dlls from XP and give it a go but instead discovered a PTP driver from Canon (ostensibly for the EOS 5D) which is written for WIndows 2000 and Windows 98 and worked well for me on Win2k to manage the T3i. Here is a short list of how to install it:

1. Download Canon PTP driver for EOS 5D here:

http://canoncanada.c...%2Fwindows-2000

2. unzip the (exe) archive to a target dir

3. unpack (extract /e) 'data1.cab' to a different target dir

4. edit the included '.INF' file to add the T3i/600D
(make any obvious needed changes)

5. plug in the camera to the usb port and complete the
install using the edited '.INF' file

6. control the camera using the EOS Utility
(version 2.10.2.0)

Note: when I first plugged in the camera, the 'select imaging utility' dialog popped up once
just like in WIA under XP -- just ignore it if you don't want to make any association and
it won't nag you.

[PROBLEMCHYLD]

cybertheque, on 25 November 2012 - 03:28 PM, said:

I just purchased a Canon Rebel T3i DSLR (600D) and wanted to control it with PTP on Windows 2000; I had decided to try migrating the PTP dlls from XP and give it a go but instead discovered a PTP driver from Canon (ostensibly for the EOS 5D) which is written for WIndows 2000 and Windows 98 and worked well for me on Win2k to manage the T3i. Here is a short list of how to install it:

1. Download Canon PTP driver for EOS 5D here:

http://canoncanada.c...%2Fwindows-2000

2. unzip the (exe) archive to a target dir

3. unpack (extract /e) 'data1.cab' to a different target dir

4. edit the included '.INF' file to add the T3i/600D
(make any obvious needed changes)

5. plug in the camera to the usb port and complete the
install using the edited '.INF' file

6. control the camera using the EOS Utility
(version 2.10.2.0)

Note: when I first plugged in the camera, the 'select imaging utility' dialog popped up once
just like in WIA under XP -- just ignore it if you don't want to make any association and
it won't nag you.

Thank you for your feedback. We are trying to avoid downloading multple drivers. We are trying to use the microsoft drivers to work with all devices instead of using many different drivers for individual devices

This post has been edited by PROBLEMCHYLD: 27 November 2012 - 10:14 AM