PROBLEMCHYLD

Thanks. Here's two more that might come in handy in the future.WdfVersionUnbind WdfVersionBind

@ jaclaz Do the drivers you listed work with any bluetooth or are they specific to its own devices. I do like dencorso approach using the microsoft files. I hope someone will take on this task, so we all can benefit.

After running WDMCHECK for XNACC.SYS 6.0.5435.0 which can be found here http://www.microsoft.com/download/en/details.aspx?id=4190 I get the following error WDMCHECK caused an invalid page fault in module WDMCHECK.EXE at 017f:00401d83. Registers: EAX=0040ba6e CS=017f EIP=00401d83 EFLGS=00010202 EBX=00000000 SS=0187 ESP=0063fbb8 EBP=0063fbc4 ECX=0063fbf4 DS=0187 ESI=0040909d FS=2c37 EDX=3c883c78 ES=0187 EDI=00000000 GS=0000 Bytes at CS:EIP: 8a 27 47 38 c4 74 f2 2c 41 3c 1a 1a c9 80 e1 20 Stack dump: 00000000 00409050 00000000 8350f0d8 00401530 00000000 0040909c 0063fe38 00000000 00000000 00530000 00000001 00760e90 00408108 00000010 004080f0

Yes, but since I'm using NUSB/USB 2.0 stack, words from the wise. I would suggest people do it just to be safe. It would only need to be done once. There's no need to repeat these steps once you have done them unless you are witnessing the USBEHCI.SYS bug.

Like you and others, you people are too lazy to read the LICENSE and README txt files. If you have read the txt files you would know that, I'm using EXPLORER.EXE from http://www.mdgx.com/files/EXPLOR98.EXE which either MDGx or erpude8 change the icon not me. You would know if you read the LICENSE and README txt files that the WinME icons has been there way before I started to update the Service Pack. If you read the LICENSE and README txt files you would know you USE AT YOUR OWN RISK! What's buggy about the Service Pack? As far as I'm concern you could have buggy software installed that was not caused by the Service Pack. Remember you always have the option of (NOT) installing the Service Pack. REMEMBER TO BACK UP! That's sounds like a problem only you can fix. Changes mean improvement, give or take.Please list the bugs and unstabilities that you may have come across. As far as I know if there are any bugs, I do my best to fix them immediately. I WILL TRY MY BEST, BUT I KNOW I CAN'T MAKE EVERYBODY HAPPY!

Your sed file is the same as mine except mines is english.

I don't understand what you mean

It means that I need install all components of SP3 except USB component? No what it means is that USB install as a part of main updates. After installation of main updates follow the instructions in the USB 2.0 notice.

Would it be too much trouble to add Second Edition to the images, and fix the start menu bmp.

Updated Please read the USB 2.0 NOTICE

Thanks

It looks nice but the text in the new image is too big. Can you make them smaller?

I trust you know more than me about the USB stuff. I will follow you lead. Just give me the instructions, and we are golden.

Maybe a good idea to update USBCDC.INF. gerislamico also found this was not the problem but USBEHCI.SYS was the cause (this post). I will probably put back the WinXP of USBSER.SYS version since this was not the actual cause. Please note the Service Pack is set to load WDMSTUB.SYS automatically so we don't have problems in the future.

yes

I have two Dell latitudes C600/C610. I would like to disable the pointing stick/ball etc.... I can disable the pointing stick/ball in the BIOS, but it also disables the touchpad which I DO NOT want to do. I would to accomplish this without using a third party app.

The file works on most systems, so what I will do since only a few are having this problem, I will note and add the USBEHCI.SYS v.5.00.2195.6882.I also like the start menu banner, can you send it to me. Nice video btw. Thanks again.

I'll test both versions USBSER.SYS 5.0.2195.6655 + 5.0.2195.7006. The one that works best will be suitable for SP3. Thanks

Module has no missing import links after running wdmcheck. It may be safe to use this version. I will test it. If all goes well it will be in the next update.

Updated

I will fix the USB problem soon. Thanks

Updated

Just as loblo said, technically SP3 didn't cause the problems you have encountered. since you have done everything manually you are at fault. I really can't help you on this one because 1. I don't know the exact changes you made. 2. I don't have a french version of windows. I'm sorry that I can't help you.

The KernelEx option is looking good so far.

I was NOT one of the four. LOL