homiebrah

Search this forum. The answer is there. As well as a way to make it point to a local file, which some of us, myself included, use. GM has enough these days than to worry about than 12 patches that come out about every 6 days.

But it is used for 2K, 2K3, and XP SP1a. The DX9 folder is to be used in the next release of XPCreate.

Here are the registry entries for the "patches" that will show up on WU, but not do anything other than remove certain items. If you are running AV and spy/ad/malware blockers, they should provide enough protection.

just curious then, why did the hotfixes thread in the unattended forum listed this: "REG ADD "HKLM\SOFTWARE\Microsoft\GdiDetectionTool" /v "GDITool" /t REG_DWORD /d "00000001" /f" Your registry entry is different from that. Also when entering the /Q command that you mentioned, should I leave a space after the filename to enter it or tie it in together? Yes, add a space after the filename before adding the /Q. The REG ADD was addressed in the post above. EDIT: I ran an image last night in VMWare just using the registry key for the Malware Removal Tool. I did not install the software, and WindowsUpdate reported it as installed. Based on the MS article, the program will install, look for the specific malware, remove it, then remove itself. It will make an entry in the registry. That's it. So, 890830 can be addressed in the same fashion as the GDI+ tool by using the registry to tell WU that the patch/program is installed. Registry Key for Malware Removal Tool: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RemovalTools\MRT "Version"="805647C6-E5ED-4F07-9E21-327592D40E83"

Yup. Took me all of 1.26657 times the square root of pie to get it from a site. The avatar is still a work in progress.

Done in Fireworks. Took about 30 seconds to create.

RyanVM has his UpdatePack which does the same thing, as well as incorporating several hotfixes and additional files into the i386 directory. UpdatePack

890830 is not the GDITool you are referring to. That is covered as the following registry entry: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\GdiDetectionTool] "GDITool"=dword:00000001 Incorporate that into the registry with any reg tweaks. All the GDI+ Tool does is take you to a MS site to start the tool. The program I am referring to is the Malware Removal Tool.

Easiest way to to find out is to install 03 with no patches and run it through Windows Update. Note what it finds and use this board to determine the placement. That's what I do from time to time.

SVC-MSX maybe? Haven't tested it out yet.

lol I'm not sure if I understand that last sentence of yours. Just dump the patch in the svc-exe folder then? Download the patch. From the Run line, type in iexpress and hit Enter. 1. Click Next. 2. Click Next. 3. Type in a package title. 4. Click Next. 5. Click Next. 6. Click Next. 7. Click Add and navigate to the location you saved the patch. 8. Click the down arrow in the Install Program box. Select the patch. Then, at the end of the patch name, enter /Q. 9. Click Next. 10. Click Next. 11. Click Next. 12. Specify a location to the save the new file. I would use SVC-EXE. Check both boxes and click Yes. 13. Click Next. 14. Select No Restart and click Next. 15. Select Don't Save and click Next. 16. Click Next. The program will create the new file and save it in the location you specified. Click Finish when it is complete.

Sorry, got 890830 mixed up with another one. I iexpress 890830 up and put it in SVC-EXE.

Game's over, Pats win...time for the goods.

Gonna be some updatin' goin' on this week. MS is planning on release some more "pearls of patching" wisdom on the heathens.

The HFLISTS file has been removed from the XPCREATE.ini file. Try this thread out. http://www.msfn.org/board/index.php?showtopic=35566

873374 is the GDI+ Detection Tool, and will simply take you to another website once it is run. Add the registry key identified in that thread into your registry tweaks. 890830 works fine in SVC-HF1.

So, if the Pats lose, do we still get the new version of XPC?

I use a program called Metapad, which is just one single file. I renamed it notepad.exe and compressed it to notepad.ex_. Using XPCREATE, it gets merged into the i386 during the process. I get the following error in setuperr.log: Error: Setup detected that the system file named [c:\windows\system32\notepad.exe] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. However, when the OS is reloaded and the final reboot is done, I have a suitable replacement for notepad. No problems, and no WFP trying to restore it back to the original notepad.

Although I can understand a few of the benefits of installing programs on a separate partition, it would still be useless to do so, IMHO. Reason being is that if Progs are on D, and the OS is on C, what happens when the OS becomes corrupt and a reinstall is needed? The OS does not know the Progs are on D, and accessing them would not work, since the registry entries for them do not exist, nor the registering of .dll's, .ocx's, etc. I could see this as a logical setup. OS on C, Profiles on D, and the swap file on E.

No worries there, GM. I'm hooked. Iexpress works wonders when developing SMS packages for release to nearly 5,200 clients.

This is what I have done with XPCREATE. 1. Ran XPCREATE the first time create the required folders. You will have several, with some like SVC-XXX and so on. 2. Created a Root folder and copy the contents of an original XP Pro CD, with NO SERVICE PACK applied. 3. Extraced SP2 and renamed setupapi.dll in the \update folder. 4. Ran update with the /integrate switch. For example, mine would look like: d:\xp\sp2\i386\update\update.exe /integrate:d:\xpcreate\sp2\root 5. Once that was done, my root was now at SP2, and was done within Windows 2000. XPCREATE will try to slip the SP without renaming the .dll file, which, like I said, GM would consider (hopefully) with the next release of XPC. It creates less problems to get the root folder at the proper SP level, then let XPCREATE do the rest.

Yes, there is a workaround. Extract the service pack files and go into the Update folder. Rename setupapi.dll to oldsetupapi.dll, or something else, and then run update.exe. It will allow you to slip the SP on Win2K boxes. This is to be done outside of XPCREATE. It was brought to GM's attention for consideration with the next release of XPCREATE.

If you really wanted XPCREATE to hook it up, wrap the installer into iexpress and place it in SVC-EXE. If MP10 is in SVC-WMP, it should work with no issues.

832483 goes into SVC-DAH.