PROBLEMCHYLD

Quite agree. I've been using KernelEx for ages, and never had a moment's problem with it. It enables me to run Opera and Java 6 and Flash 10. Whether its files should be included in a future version of the service pack is debatable. I would say not. I certainly would have no problem with KernelEx being included as an optional extra install though. I wasn't saying KernelEx wasn't good. What I was saying at the same time it allows certain apps to runit also breaks some at the sametime. KEX is great for you, but it doesn't suit my needs. No offense intended.

I agree. Maybe if KernelEx comes more stable in the future, I'll consider it. ATM is not going to happen.Its an great addon, but when I wanted to run certain programs KEX couldn't do it. So I have no use for it. This is not a (PROBLEM) for me. I love working on the SP. As long as the Lord give my breath, I will work on it until its finished.

Windows 2003 Resource Kits contains these newer files IVIEWERS.DLL 2.1.0.59 OLEVIEW.EXE 2.1.0.59 VFI.EXE 4.99.8.2301 (AKA FILEWISE.EXE)

This might be great for people who don't like bloated software. Of course one will have to create batch files to automate the process. From Windows 2003 Resouce Kit: Microsoft CD ISO Burn Utility CDBURN.EXE 5.2.3790.0 (Commandline Tool) Microsoft DVD Burn Utility DVDBURN.EXE 5.2.3790.0 (Commandline Tool)

It would be great to combine all 3 packages into 1.

This is what I'll be adding to SP 3.2I like to ask everyone that uses SP 3.x, please test files that doesn't require KernelEx. Even if they work I will not add them. I was going to create a option and add KernelEx files, due to lack of interest, its water under the bridge now. About the Mdac files, it requires (some) testing connections to an SQL Server etc.... I don't use MDAC, so I'm not able to test the newer files. I know the older files work because no one has reported any problems in the many years of use. Sure, I place it in the folder. You can delete it once you copy it.

Thanks for testing.VBSCRIPT.DLL 5.8.6001.23141 breaks VBscript files on my system. So I won't be adding it. When you tested these files, did you test without KernelEX?. I know that it will allow newer files to work.

I am testing these files atm. ASYCFILT.DLL 2.40.4534.0 Windows 2000 Service Pack 4 OLEAUT32.DLL 2.40.4532.0 Windows 2000 Service Pack 4 RICHED20.DLL 5.30.23.1231 XPSP3 Hotfix SETUPAPI.DLL 5.0.2183.1 Windows 2000 Service Pack 4 If someone can test these other files, we can speed the process up. MSJET40.DLL 4.0.9514.0 T2EMBED.DLL 5.0.2195.7349 MSADCE.DLL 2.81.3010.0 MSADO15.DLL 2.81.1145.0 MSADOMD.DLL 2.81.1145.0 MSADOX.DLL 2.81.1145.0 MSJRO.DLL 2.81.1145.0 ODBCBCP.DLL 2000.85.3009.0 SQLOLEDB.DLL 2000.85.1128.0 2000.85.3006.0 SQLSRV32.DLL 2000.85.1128.0 2000.85.3009.0

@ maximus-decim To get the Casio USB devices to work, you need these two files. USBDSC1.SYS 4.10.0.1998 USBDSC2.VXD 4.0.0.950 You can find the two files in a package googling casio usb_win.exe All you have to do is add the code below to your USBSTOR.INF. You can remove QV2KUX.SYS 1.0.0.2000. Thanks again for the update. [Manufacturer] %Casio.Mfg%=Casio [Casio] %USB\VID_07CF&PID_1001.DeviceDesc%=USBDSC1,USB\VID_07CF&PID_1001 [USBDSC1.AddReg] HKR,,DevLoader,,*NTKERN HKR,,NTMPDriver,,USBDSC1.SYS HKLM,"System\Currentcontrolset\Services\usbdsc1\Parameters","Install",0x10001,77 HKLM,"System\Currentcontrolset\Services\usbdsc1\Parameters","DiskMakeFirstInstallDelay",0x10001,3000 HKLM,"System\Currentcontrolset\Services\usbdsc1\Parameters","DiskMakeOtherDelay",0x10001,300 [Strings] Casio.Mfg="Casio" USB\VID_07cf&PID_1001.DeviceDesc="USB-CASIO DIGITAL CAMERA"

Service Pack installs everything except for these updates DirectX 9 Internet Explorer NET Framework Windows Image Acquisition 1.1 (WIA) Windows Media Player (WMP)

Thanks. Now I need the remaining 6 files above.

I'm looking for a an old update that has these files MSADCO.DLL 2.81.1145.0 MSADO20.TLB 2.81.1145.0 MSADO21.TLB 2.81.1145.0 MSADO25.TLB 2.81.1145.0 MSADO26.TLB 2.81.1145.0 MSADO27.TLB 2.81.1145.0

Good tools you suggested Do you think its possible for someone to create a batch/vbscript to delete the universal serial bus controllers tree in device manager?

There is a typo in USB2.INF. [WMVARE] %PCI\VEN_15AD&DEV_0770.DeviceDesc%=EHCI,PCI\VEN_15AD&DEV_0770It should read [VMWARE] %PCI\VEN_15AD&DEV_0770.DeviceDesc%=EHCI,PCI\VEN_15AD&DEV_0770I have already fixed the issuse for SP3. Thanks for the update

Was these files tested? If not, I'm going to have to test each one separately.I have started working on the Windows 2000 Server files set. I can put it on hold for now and wait until you release your package. I know for a fact that some of the Script 5.X files won't work. MDGx had some of the files in his old packages of Script 5.X. From another topic: I'm not a gamer so this one is hard for me to test.

If anyone know of a tool to remove all usb devices, I will add it for everyone convenience.Then it won't be a 100 more (Do I Remove All USB DEVICES).

I can use a test build right about now, if you have one ready.

submix8c That really help me. I've been analyzing the inf files, and everything looks good.

I'm about to start stripping down fdv 2000 Server fileset. I'm going to need some help. What I mean by strip, is that I will be removing everything that is (NOT) server related. No NOTEPAD No WORDPAD No CALCULATOR etc..... The fileset will install only system core files + server files. Nothing more, nothing less. Things like defrag/chkdsk will be left, because they are system tools. Now here's an example in LAYOUT.INF iexplore.hlp = 1,,,,,,,21,0,0 I know the 21 means the help directory, but what does the other numbers mean?

New topic

Thanks

I hope people are reading what you guys wrote. It’s repetitious, so maybe you guys can deal with it. How many times one must say (REMOVE ALL)? I thought USB devices can only be loaded in Safe Mode through USB Legacy Support if the BIOS supports it?Not everyone have this option. So we should focus on the majority (atm).

You guys can direct all USB related questions to members Tihiy, MDGx, and maximus-decim. They are the founders of the USB packages. You can ask them why all devices should be removed. I followed their instructions and gave them to you. The next version of the Service Pack will (NOT) have any usb support. Enjoy

I can't download the file. It says Our service is currently unavailable in your country. Sorry about that.

There wouldn't be any confusion if people followed instructions. The instructions specifically says REMOVE ALL DEVICES.Not some, not a couple, but ALL. Why are peolpe following NUSB instructions? The heck if I know. They should be following the Service Pack instructions. If my one year old daughter can understand All when asked to pick up her toys, then any adult should be able to do it also.