PROBLEMCHYLD

I will fix it in 3.1 Thank you

VIA Controllers TEST files Unplug all USB devices Install Main Updates Place the 2 inf files in Windows\inf directory Place the VSBHUB20.SYS in WINDOWS\SYSTEM32\DRIVERS Remove all USB controllers/devices in safe mode. Reboot!

Virtual Private Network works fine on my system. I hope you figure it out.

I think I may have the VIA controllers fix. I have the files ready. Please don't ask for the files if you are NOT going to test them. We have a size limit here at MSFN. I have to upload them somewhere else. Make sure you have a VIA Chipset. You don't need to do a clean install, but you will need to install main updates again (for testing purposes). Then navigate to safe mode, replace some files, remove all usb controllers and REBOOT! If we get the VIA controllers working, I shouldn't have any problems getting the others to work. Thank you Lonecrusader, Drugwash, dencorso. B)

The file is a part of (UPNP) Universal Plug and Play + (ICS) Internet Connection Sharing. It is optional. If you doNOT have UPNP devices then you don't need this option installed. Each option has a small description explaining its contents Its not possible. You either have to choose between the ones in the SP or the originals

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},*

You probably would have to ask maximus-decim about that. B)

Edit: Misunderstood the question..

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" ;

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

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

@ egrabrych Glad everything working.

The file inside the hotfix is Apmbatt.sys 4.10.0.2224

Great job Can't wait to test it

I admit I didn't read it.... But I had to add it manually a couple of days ago because VLC wouldn't run. You didn't need to install it, main updates does that for you. But since you have ignored the fineprint on the homepageI wouldn't complain about anything if I was you. It will p*** some people off

I see you haven't read or didn't understand the Service Pack home page. 2.0 RC1: - NEW: 1 new hot-fix. - ADDED: Web Folders update. - UPDATED: HTML update.. - UPDATED: UNICOWS.DLL. - UPDATED: MS VC++ runtime files. - FIXED: All reported problems. - FIXED: Uninstallation problems.

I'm in no rush. I think I will wait til tomasz86 releases his SP for Windows 2000, so I can dig in it and maybe get some newer files for our Win98 systems

If you take care of this issue I can take care of this one

You are correct Mr. I'm always testing newer files. Just cause they work on my system doesn't mean they will work on others. Kinda like the VIA contoller issue. Hopefully I can fix it.

Somebody was wrong. I don't want to point fingers. I use USBPORT.SYS 5.0.2195.6941 in U9SESP3 and I have no problems A lot of people have downloaded the SP and this file must not be problematic.

What is your chipset? Its seems to be moving faster than earlier.

If you have some free time, can you please edit the VIA inf for me? You guys seem to know more about the USB stuff and how it works.Thank you How is this possible, to be able to have two of the same files with different versions? This should be fix once you go to safe mode to handle the USB issue. Is it possible to patch USBHUB20.SYS 5.0.2195.6891 so that it can load VIA controllers?

Then it shouldn't be a problem for me. I will add the VIA controllers.Thanks LoneCrusader

Thanks dencorso What I will do is come up with something for VIA controllers. In the meantime I'll leave it out. I can't test the VIA stuff but if someone is more familiar with them and have it working please post some documentation so I can add it to the USB 2.0 NOTICE. Thanks

Thanks Drugwash I think the only file I need is USBHUB20.SYS 4.90.3000.11. I will place it in the SP3.CAB as VSBHUB20.SYS. If people are using VIA chipsets, then all they would have to do while already in safe mode is delete USBHUB20.SYS 5.0.2195.6891 and rename VSBHUB20.SYS to USBHUB20.SYS. That should take care all of the USB issues. Can anyone confirm this?