Aaron

You really should proof-read the command you're using as I've spotted two mistakes: $systemdrive% and a blank line space which breaks the command used. Here's the fixed command: start /wait %systemdrive%\Install\Graphics\PhotoShop\Setup.exe -s -f1"%systemdrive%\Install\Graphics\PhotoShop\setup.iss"

This is a list of all the critical hotfixes you need for Windows XP Professional SP1 32-bit. Recommended Updates are excluded from this list as they are not always needed for every system, whereas the Critical Updates should be installed for every system. This list will be updated regularly and old ones removed when a newer hotfix supersedes it. Looking for the Office 2003 Updates list? Click here -------------------------------------------------- Type 1 Hotfixes (Switches to use: Click here) Q819696 (23rd July 2003) Unchecked Buffer in DirectX Could Enable System Compromise Download - 800KB Note: This is for DirectX 8.1 on Windows XP, you do not have to download/install this if you plan to install DirectX 9.0c. Q823182 (14th October 2003) Vulnerability in Authenticode Verification Could Allow Remote Code Execution Download - 424 KB Q824105 (3rd September 2003) Flaw in NetBIOS Could Lead to Information Disclosure Download - 339 KB Q824141 (29th September 2003) Buffer Overrun in the ListBox and in the ComboBox Control Could Allow Code Execution Download - 2.12 MB Q825119 (14th September 2003) Buffer Overrun in Windows Help and Support Center Could Lead to System Compromise Download - 299 KB Q826939 (14th September 2003) Update Rollup 1 for Windows XP Download - 9 MB Q828026 (10th February 2004) Update for Windows Media Player URL Script Command Behavior Download - 2.77 MB Q828035 (29th October 2003) Buffer Overrun in Messenger Service Could Allow Code Execution Download - 358 KB Q828741 (12th April 2004) Cumulative Update for Microsoft RPC/DCOM Download - 3.2 MB Q833987 (14th September 2004) Buffer overrun in JPEG processing (GDI+) could allow code execution Download - 1389KB Q835732 (12th April 2004) Security Update for Microsoft Windows Download - 2.6 MB Q837001 (12th April 2004) Vulnerability in the Microsoft Jet Database Engine Could Allow Code Execution Download - 2.9 MB Q839645 (13th July 2004) Vulnerability in Windows Shell Could Allow Remote Code Execution Download - 3.81 MB Q840315 (13th July 2004) Vulnerability in HTML Help Could Allow Code Execution Download - 375 KB Q840374 (11th May 2004) Vulnerability in Help and Support Center Could Allow Remote Code Execution Download - 854 KB Q841873 (13th July 2004) Vulnerability in Task Scheduler Could Allow Code Execution Download - 882 KB Q842773 (13th July 2004) Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP 5.1 Download - 635 KB Q883357 (13th August 2004) Your backup program may fail or incorrectly exclude some files from your backup in Windows XP Download - 320KB -------------------------------------------------- Type 2 Hotfixes (Switches to use: /Q:A /R:N) Q814078 Also known as JS56NEN.exe (19th March 2003) Flaw in Windows Script Engine May Allow Code to Run Download - 361 KB Q816093 Flaw in the Microsoft VM Could Enable System Compromise WindowsUpdate Corporate (Search for 816093) Note: This is the MSJava 3810 Update, only download if you use SP1 and not SP1a. - 5.07 MB Q823353 (13th July 2004) Cumulative Security Update for Outlook Express (July 2004) Download 1.90 MB Q867801 (30th July 2004) *NEW* Cumulative Security Update for Internet Explorer 6 SP1 Download - 2.77 MB Q870669 (2nd July 2004) Critical Update for Microsoft Data Access Components - Disable ADODB.Stream object from Internet Explorer Download 104 KB -------------------------------------------------- MDAC - Requires different switch. Do not use this syntax directly in svcpack.inf. You can create a batch file to call out that syntax from svcpack.inf, or do it from GuiRunOnce: As outlined in the Technet article, install using: xxx_Q832483_MDAC_X86.EXE /C:"dahotfix.exe /q /n" /q where xxx is your language version. Q832483 (13th January 2004) Buffer overrun in an MDAC function could allow code execution Download - 1.99 MB -------------------------------------------------- NOT SVCPACK.INF SUPPORTED - Anything shown below must not be processed by svcpack. Instead, these should be installed on first logon to process silent unattended installations of these updates. Q817787 (Switch: /Q:A /R:N) (6th May 2003) Flaw in Windows Media Player Skins Downloading Could Allow Code Execution Download - 360 KB Note: This is for Windows Media Player 8 on Windows XP, you do not have to install this if you plan to install Windows Media Player 9. Q817778 (Switch: Same as "type 1" switches) (23rd July 2003) Advanced Networking Pack for Windows XP - 1.21 MB -------------------------------------------------- Extras (Switches to use: varies) These files can also be installed using svcpack.inf: DirectX 9.0c redist (Extract, and use /silent on dxsetup.exe) *NEW* WMP9 and MM2 Bundle (no switch needed) Tip: Make sure Q828026 is queued up after WMP9 in svcpack.inf. -------------------------------------------------- Updates 21st September 2004 - 2 new Type 1 updates added (833987 and 883357), both can be installed via svcpack.inf. 30th July 2004 - New Cumulative update for Internet Explorer released (867801), this replaces the last cumulative update (832894) and all the ones before that. We stress that you remove all old IE cumulative updates from svcpack.inf to avoid issues. 27th July 2004 - DirectX 9.0c is released, and is listed under Extras. The switch /silent can be used on dxsetup.exe. The DirectX 9.0b Security Update (Q839643) has been removed from the list, this is superceded by DirectX 9.0c which contains all past fixes, so you can remove this from your svcpack.inf file. 13th July 2004 - Good news, all 5 updates marked *NEW* (4 in Type1, and 1 in Type2) can be installed via svcpack.inf without any difficulty. Remove Q837009.exe from both svcpack.inf and your svcpack folder as this is superseded by the newer OE Update. 2nd July 2004 - New Critical Update workaround for Internet Explorer to protect against the Download.Ject exploit. KB870669 under Type 2 Hotfixes. I haven't had time to test this thoroughly, but install this after any MDAC patches you plan to install. 13th June 2004 - DirectX update added Q839643, make sure you download the correct hotfix by reading the notes in brackets in this list. 11th May 2004 - 1 new Windows XP Update today: Q840374 - Vulnerability in Help and Support Center Could Allow Remote Code Execution. You may also want to re-download Q837001, as it's been re-released.

ahhh, its all becoming crystal clear now All the hotfixes installed perfectly, except for mdac, (have to create the directories like webmedic said.) I will work on making a guide on this (with images) to explain everything. The script will just be for hotfixes only (winnt.sif and raid drivers removed), and will link to webmedic's webspace for users who have a RAID setup and want the RAID and Hotfix combination script, as I can't test this myself. First, I will instruct the user to extract to the root drive to avoid problems with folders that may contain spaces. Then, dump all the critical updates into '1', and the following in '2': August Cumulative Update for Internet Explorer April Cumulative Update for Outlook Express JScript 5.6 MSJava 3810 Update Hotfix for Media Player 8 for XP (assuming the user will not install WMP9 at a later time) Catalog Database Corruption Update (817287) And in '3': MDAC hotfix (Not forgetting to create $oem$\$1\install\system\hotfix3 and $oem$\$1\install\tmp and moving Q823718_.EXE file to the hotfix3 folder.) Followed by extracting the sp1.cab into /files/sp1 and then run do.cmd. Lastly, copy everything to your i386 directory (which should have been slipstreamed with SP1 previously). Last question: 1. Does it matter what filenames are used for each of the hotfixes? Or should they all be renamed to Q######.exe?

Change OemPreinstall=No to Yes so the contents of your $OEM$ folder are copied to the hard drive during Windows XP Setup.

That was the log file from my first attempt, the 2nd one is here I'll check your file listings with mine, and move the folder to the root as you suggested. Here goes attempt no.3

I think I'll leave this alone for a while, there's a lot I don't know what I'm actually supposed to do, or what kind of hotfixes are supposed to be in the folders. It still errors out with invalid command syntax for the IE and OE cumulative updates in folder 2. The log file was also making references to C:\install\system\ C:\install\tmp even though I never created those, nor do I have any idea what they're for.

Log.txt Virtual PC's finished, but somehow my graphics display got corrupted and set to 8bit. IE won't start either

OK, I had to do a bit of guesswork and using some of the instructions that GreenMachine put into a script he made available for download yesterday. Created XPCD Folder, and placed the contents of the XP CD into there, as well as webmedic's hotfix folder. All the critical updates into folder 1 and the IE/OE Cumulative update, MDAC hotfix, msjava 3810 update and the WMP8 for XP update (assuming the user doesn't install wmp9): Although when the do.cmd script processed folder 2, it error'ed 5 times. Its now running setup in Virtual PC so I'll see how it goes. You might want to prevent the script from copying over winnt.sif as this could overwrite someone else's custom winnt.sif file.

Ah I see, but they're ok with the script which puts the hotfixes into svcpack? I don't want to put anything on the site which MS wouldn't approve of.

Any chance of instructions on how to use this? Does this also contain MassStorageDrivers? Basically when I update the site with the new hotfix script I want to keep things seperately otherwise readers might get confused. Or would this be too complicated to do since some files are shared (e.g. dosnet.inf)?

According to Spheris, it can't be slipstreamed into the Windows XP CD.

You can't get MSN Messenger 6 smaller than 1.44mb. But you can use WinZip or WinRAR and split the setup file into 1.44mb parts, so you can carry them on 3-4 floppies and put it back together again at work.

I have wondered that too, every Microsoft documentation shows it differently with uppercasing or lowercasing, quotation marks or spaces. The only way to find out is to try them out yourself. It shouldn't take too long if you leave your OEM install out of it.

An unofficial pack which I wouldn't use, personally I would wait until MS release the Security Rollup Package on the 24th. Could we have a look at the two batch files though?

No Crack/serial requests. Please read the MSFN Forum Rules Topic Closed

Yeah you're right, its gone down to 8mins now. I'll run qfecheck and windowsupdate afterwards to see the results.

heh, it seems XP Setup has stalled at Registering Components (13mins), lots of hdd activity but not making any progress at all for the last 10mins. I'll wait for webmedic's scripts Edit: On a side note, how would one add a new hotfix to I386 when do.cmd has already been ran? Would the whole process have to be repeated on a clean unmodified i386 directory?

hmm I ran do.cmd when your XPSETUP folder was on the Desktop. Anyhow, Virtual PC is running so I'll see how it goes.

found the script in a download you provided at http://board.MSFN.org/index.php?showtopic=...=8341&st=60&hl= so I'm trying this out now

hehe, where's webmedic's script? Is it in the "How to install Hotfixes and Raid correctly" thread? Last time I looked, it looked like a batch file that runs switches on the hotfix files in 3 seperate folders, so it isn't exactly integrated into the i386 folder. (Correct me if I'm wrong, I might have looked at it the wrong way)

I've been doing the The Combination Installation this evening (which uses svcpack), and that was a very nasty peice of work. Very very tedious and time consuming, with mistakes very easy to make and difficult to trace. I spent 2-3 hours doing it and after finishing installation, Windows XP wouldn't boot, leaving a black screen. I won't be adding this to the guide as most users won't like this. Anyway webmedic, you said earlier you made a script to automate all this, so I'm interested to see what you've done. Although it must have been a difficult script to make to create the svcpack.inf and all the .cat and .exe lines in svcpack.inf and then replacing all the files in the i386 directory with updated versions?

When you create a CD that's designed for multiple computers, you should start with the chipset drivers, lets say for example, VIA, Intel and nForce. They can take up 000, 001 and 002. Next would be Nvidia, ATI and Matrox, which would take 003, 004 and 005 in that order repectively. For a PC that has an Intel Motherboard and an ATI graphics card, Windows XP Setup will install first from 001 then 004 after. Spheris will probably tell you more

Good idea GreenMachine, I could give Debugging its own dedicated page on the site

Remember guys, please give the link to what you're talking about. It would take me hours to go through each single thread on 56k

Disable any firewalls, enable ICS on the PC connected to the Internet and make sure the network card is assigned with the IP of 192.168.0.1. On the other PC, make sure TCP/IP options are set to automatically assign an IP address, that's all there is to it. Troubleshooting: ping your other PC using computer name, and vice versa. Any response?