GreenMachine

I believe the WUA files have been updated (7.0.6000.374 -> 7.0.6000.381), but the standalone installer (windowsupdateagent30-x86.exe) has not yet been updated. windowsupdateagent30-x86.exe can be used to integrate those files into the installation. I suspect that will follow shortly.

Over the years here at MSFN, there has been much work, discussion and collaboration devoted to the slipstreaming of hotfixes and updates to allow our members to easily create an up-to-date Windows Installation. Though these topics may have seemed "dead" to the higher powers, I would consider them completed. I, personally, have not invested more time into XPCREATE because it is working just fine: a finished product. In addition to the product itself, the disscussions that led to the solving of many problems was invaluable in itself. Additionally, I found myself looking at other posts in the Members Contributed Projects Forums that have helped me with other issues, most notably as of late the Hotstream Project. Alas, much to my dismay, and surprise, those forums are gone now. Has bandwidth and disk space become so scarce and valuable? Has work done just a few years ago become so irrelevent? I am not sure what the reason, but I do want to take a moment to express my disappointment, and sadness, that even as a two time "Supreme Sponsor" more than half of my posts have been deemed unwanted and are now gone, while more "worthwile" topics, like how to import registry settings, or remove shortcuts, or circumvent WGA nags are beat into the ground ... Is it a case of "Different Strokes For Different Folks", or simply "GreenMachine Being GreenMachine"?

The Greatest Need? Well, Gosh ... I think the greatest need is to spark some life back into these forum members. Things got boring. There seem to be too many sheep and not enough shepards. The days of members delving and disecting seem to be long gone. My greatest need, though I have not spent much time on it yet, is to figure out how to make a Type I Hotfix. Basicaly a packed cab with the small self-extracting module tacked on. Specifically, it is for re-packing the IE7 installation (which is simply a Type I Hotfix) with the latest updates included. The reason for this is that I install IE7 from SVCPACK.INF during the installation, but cannot install the updates until after the reboot, as IE7 does not replace IE6 until that point. So, Old Chap, there is a request! Or, we could just call eachother names for old times sake ...

Working fine now ... could be the last bit of sleep is gone from my eyes! Thanks, Martin L! That makes the "sponsor" thingy really worth it! (Hint Hint ... )

Now that I am a little more awake ... I do NOT see the ads at the top of the page, just beween the 1st and 2nd post. Maybe that is the way it is supposed to be .... Hiya IcemanND!

Just to let you know, I am still seeing the ads between the 1st and 2nd post here. Also, though I needed to log on for access yesterday, I still saw lots of "guest" users. Not the case today. No complaining, just trying to help you debug! Good Luck!

I have updated XPCREATE to fix the few bugs reported. I have also updaetd the Flash integration to work with version 7.X, 8.X and 9.X. Please download the latest version of XPCREATE, 01 JULY 2006, from the link in the first post of this thread. @Mann: I am not sure where you got that TXTSETUP.SIF information above, but it does not look XPCREATE generated to me. In fact, I never got around to integrating the nVidia drivers, as I never had the hardware to test. Is that TXTSETUP info tried and tested? @BaTLeZone: Hotfix KB917734 updates WMP.DLL to that version. @Tinywoods: You should be good with any Flash version now. ... Allez les Bleus ...

Oh no ... A bug. I hate when that happens. I see where the SATA integration goes astray, but I have not yet figured out the log file part. I will post a fix ASAP, probably tomorrow. For the moment, if you compressed your drivers, e.g. iastor.sy_, it will probaly work ... To be continued ...

@BaTLeZone: I think you forgot the 2KSETUP this time. It is attached to my first post, which I updated to include the KB numbers for these three problem hotfixes. @Mann: Attach LOGFILES.CAB from the NEWFILES directory to your next post, and I can help you further.

OK, Who let the Cat (The Wraith) outta the bag? I guess classes are out, and you have a little too much free time ... Sunny and warm on the Riviera, bet you cannot say that down under! Good to see you around, Wraith!

"CDTYPE=DVD" ... What was I thinking ... Should have been something like MEDIA=DVD ... That switch only tells XPCREATE which burning software to use: either CDBURN, or DVDBURN, both courtesy of Microsoft. There is, however, NO DIFFERENCE in the way the ISO is created. I do believe the key for NERO is selecting DVD from the list as mentioned above. I suppose I will consider adding a MAKEISO, MAKECD and MAKEDVD script to allow these tasks to be performed individually.

Unfortunatly, adding .NET Framework II to the install also put my ISO over the CD size, albeit just barely. I have written a few script to delete the unneeded CMPNTS, VALUEADD and SUPPORT directories from the local copy of the source files, and will include them in the next update. Even then, there is no room for additional software, and anything more than a bare install almost requires a DVD. As for the SATA drivers, I have assembled what I think is a working collection of drivers, and will also be posting that in the next few days, if you would like to try again. Exactly which SATA devices are you using? Do you have a link to the download? As for nLite ... be careful that neither nLite nor XPCREATE overwite files modified by the other. XPCREATE only modifies SVCPACK.INF, DOSNET.INF, and TXTSETUP.SIF if SATA drivers are included. I, of course, think that XPCREATE should be run first ... That way I can blame the other guy!

Look for the simple answer ... A directive file (or DDF, Diamond Directive FIle) is not intended to compress individual files. Your stated goal is not to see the DOS box flash. Simply direct MAKECAB output to NUL ... The following code compresses everything in DIR1 into DIR2 discretly: FOR /F "USEBACKQ" %%I IN (`DIR /A-D /B DIR1\*.* 2^>NUL`) DO ( MAKECAB /D CompressionMemory=21 /D CompressionType=LZX /L DIR2 DIR1\%%I > NUL ) Or to see what is happening: FOR /F "USEBACKQ" %%I IN (`DIR /A-D /B DIR1\*.* 2^>NUL`) DO ( ECHO Compressing %%I MAKECAB /D CompressionMemory=21 /D CompressionType=LZX /L DIR2 DIR1\%%I > NUL )

Don't get desperate: Stay LeveL-headed! Though my issue and solution with Server 2003 is not exactly the same as yours, perhaps it will help you in tracking down the problem. In my case, I change the Administrator name from Adminitrator to 2K3Admin. I am not sure why you want to install from your newly created account instead of the built-in administrators account, but that is your business ... Installing everything as the built-in administrator (now renamed), is my preference. Pre SP1, I would enter the new name in to the registry as you did, set the autologon, and that would be fine. HOWEVER ... Post SP1 I noticed that Windows could not auto logon the administrator. This was due to the fact that sometime between the point I set the default name to 2K3Admin (the last thing I did at the T-13 stage), and reboot time, that value had been changed back to Administrator. Here is where I do not understand how your setup has Server2003 in the logon box, but so be it. Further investigation showed that in fact setup did change the name value back to Administrator value back, and probably the autologon flag as well. To get to the point ... I created a stand alone package that would change these values back one last time, and called it from SetupParams, which runs at T-9. @ECHO OFF REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /V "AltDefaultUserName" /T REG_SZ /D "2003Server" /F REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /V "AutoAdminLogon" /T REG_SZ /D "1" /F REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /V "DefaultPassword" /T REG_SZ /D "" /F REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /V "DefaultUserName" /T REG_SZ /D "2003Server" /F REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /V "ForceAutoLogon" /T REG_SZ /D "1" /F This should be enough to get your started in your troubleshooting. Another thing I would be interested in is a compare of of slipstreamed SP1 and beta SP1. You say this used to work. Compare the two side by side, and you will have what it takes to better analyze the situation. Good luck!

After coming across a link to the .NET Framework 2.0 from SVCPACK.INF Solution on the infamous RyanVM Web Site, I decided to revamp XPCREATE to include that functionality. I have also made a few other updates. This release produces Windows 2000, Windows XP and Windows Server 2003 versions that are up to date for both High Priority and Optional updates on Windows Update Site. All updates are controlled via SVCPACK.INF, and a WINNT.SIF file is NOT required. As usual, no Microsoft binaries are modified. The only files modifed are DOSNET.INF and SVCPACK.INF, as well as TXTSETUP.SIF in the case of SATA integration. For download and update information, please see THIS POST

XPCREATE 2006 I am in the process of wrapping up XPCREATE 2006, and have put up a test version for downloading. (Link at bottom of post.) There have been very few functional changes, as I feel the XPCREATE has achieved it's goals in terms of design: slipstream the latest hotfixes, and produce a distribution CD that reports zero updates available, in both the High Priority and Optional sections of Windows Update. The main changes are: 1) Duplicate versions of the same file in different hotfixes are now compared by file version number, and not date. While this has no effect on the current set of hotfixes for Windows XP, it does effect a couple of files on WIndows 2000 installations. 2) SATA Driver Integration has been completly redesigned. The complete sections relating to SCSI drivers in TXTSETUP.SIF are now rewritten, avoiding both doubles in file names, and PCI Hardware IDs. Several drivers, e.g. Silicon Image SATA, and Promise Ultra and FastTrack, have been known to "share" PCI IDs. XPCREATE will now only keep one of the conflicting IDs. While this may not be the optimal solution, it should reduce driver conflict issues. 3) Support for .NET Framework 2.0 is now included. A work-around discussed by a certain Aaron of Microsoft has been implemented, wherein changes are made to the registry before and after the .NET installation. This works on Windows 2000 as well as XP and Server 2003. 4) An extensive build report can now be generated. This Summary Report readily shows the hotfixes integrated, the files included in these hotfixes, the version numbers of these files, a matrix cross referencing files and hotfixes, SATA integration information, and more. As this report does add five to ten minutes to the XPCREATE process, it is not active by default. Before any error reporting, XPCREATE should be run using this option: LOGCREATE=YES in XPCREATE.INI ================================================================================ ======================= XPCREATE Summary and Log Report ======================== ================================================================================ = = = XPCREATED on 15/06/2006 Windows Version : XPP = = Started at 19:56:13 Service Pack : 2 = = Finished at 20:25:29 = = = = HF1 Hotfixes : 50 CF1 Hotfixes : 2 = = HF2 Hotfixes : 0 CF2 Hotfixes : 0 = = = = .NET 1.1 Framework : YES Windows Media Player : YES = = .NET 2.0 Framework : YES DirectX 9 : NO = = Windows Update Agent : YES Shockwave Flash Player : YES = = = = Mass Storage Drivers : 0 Double File Messages : 13 = = MSD Warning Messages : 0 = = = ================================================================================ ================================================================================ ================================================================================ Slipstreamed Files and Hotfixes Matrix ================================================================================ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |B| |8|8|8|8|8|8|8|8|8|8|8|9|9|9|9|9|9|9|9|9|9|9|9|9|9|9|9|9|9|9|9|9|9|9|9|A| |9|9|9|9|9|9|9|9|9|9|9|0|0|0|0|0|0|0|0|0|0|0|1|1|1|1|1|1|1|1|1|1|1|1|1|S| |0|3|6|6|6|6|8|9|9|9|9|0|1|1|1|2|4|4|5|8|8|8|0|1|1|1|1|1|2|4|6|7|7|7|8|E| |0|7|3|4|4|4|7|5|5|5|5|7|0|1|2|4|7|9|4|5|5|9|4|2|5|5|5|9|9|3|2|3|7|9|4|C| |4|5|5|2|2|2|1|8|8|8|9|2|1|9|1|0|0|4|1|1|3|8|3|8|6|6|6|2|1|8|8|4|3|5|3|S| |6|6|8|2|4|8|5|7|8|9|1|5|7|0|4|0|6|2|4|9|1|1|7|0|2|4|7|7|9|9|1|4|4|3|9|P| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | admin.dll | | | | | | | | | | | | | | | | | | | | | |X| | | | | | | | | | | | | | | agentdpv.dll |X| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | author.dll | | | | | | | | | | | | | | | | | | | | | |X| | | | | | | | | | | | | | | axaltocm.dll | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |X| basecsp.dll | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |X| bcsprsrc.dll | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |X| browseui.dll | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |X| | | | | | catsrv.dll | | | | | | | | | | | | | | | |X| | | | | | | | | | | | | | | | | | | | | catsrvut.dll | | | | | | | | | | | | | | | |X| | | | | | | | | | | | | | | | | | | | | cdosys.dll | | | | | | | | | | | | |X| | | | | | | | | | | | | | | | | | | | | | | | cfgwiz.exe | | | | | | | | | | | | | | | | | | | | | |X| | | | | | | | | | | | | | | clbcatex.dll | | | | | | | | | | | | | | | |X| | | | | | | | | | | | | | | | | | | | | clbcatq.dll | | | | | | | | | | | | | | | |X| | | | | | | | | | | | | | | | | | | | | colbact.dll | | | | | | | | | | | | | | | |X| | | | | | | | | | | | | | | | | | | | | comadmin.dll | | | | | | | | | | | | | | | |X| | | | | | | | | | | | | | | | | | | | | 5) The Hotfix Downloading Functionality is making a comeback. However, I do not plan on keeping a list available for download. You may either use a local file, or use a custom HTTP URL. 6) As requested, the first run of XPCREATE once again creates the directory structure. After this version is released, I will update the documentation. Until then, the basic steps remain unchanged. On the XPCREATE Web Site, the Current Hotfixes and What Goes Where Pages are up to date. Known Issues: Windows XP 1) The files WMP.DLL and MSSCP.DLL are correctly installed during setup, but overwritten during system reboot. These files correspond to hotfixes KB917734 and KB902344. The attached code can be saved as XPSETUP.CMD (or a name of your choice), and placed in the SVC-CMD directory. This will schedule a RunOnce task to copy the backed up version of these files over the incorrect versions when the first user logs on. Note that this user must have administrator privileges. Known Issues: Windows 2000 1) As above, the file QUARTZ.DLL, from hotfix KB904706 , must be restored to the correct version. The attached batch file, 2KSETUP.CMD.TXT, will do this. This file must be saved with the .CMD extension, e.g. 2KSETUP.CMD, and placed in the SVD-CMD directory. 2) The hotfix 832483 is reported as missing if not installed. However, installing 832483 prevents the subsequent MDAC update to install before a reboot. Installing in the reverse order results in 832483 not being able to be installed at any point. Most importantly, this update (832483) only contains files that are superceeded by other versions, and adds no registry information, other than the "installed" flags. The following batch file, saved as indicated above, will set these values in the regsitry. I suspect that Microsoft will straighten out this glitch before long, but for now this work around is without side effects. 3) The .NET 2.0 installations reports the following error in the setuperr.log file: Error: Setup failed to install the .NET Framework Migration Package package (version 2.0) on your system. Software which depends on this package may not function properly. Contact your system administrator. I have not yet determined the consequences of this message, but Windows Update does report .NET 2.0 as needing to be installed. 4) The following error, concerning a DirectX file, also apears in setuperr.log: Error: Setup detected that the system file named [c:\windows\system32\drivers\msdv.sys] 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. I am not sure why the .CAT file is not found, but it is present. Feel fere to post comments or questions! XPCREATE Download : HERE XPPSETUP.CMD.TXT 2KSSETUP.CMD.TXT

Come on ... The problem is not deleting the Links folder: that is easy with a batch file, or simply using delete in the explorer. Your problem is that the Links folder will be re-created next time you open the Internet Explorer. Why, you may ask ... Because IE is configured to show the Links Folder, thus creates it if missing. Right click on an IE toolbar, and uncheck the Links item. Delete the Links folder, and it does not came back. At least not on my box, your actual mileage may vary ...

Here is an untested modified sniplet of the file I use to accomplish this. Must be run AFTER setup has completed, e.g. GUIRunOnce from WINNT.SIF. MAKEDIRS.CMD

That link will work, but be suer to select NO when asked to install the ActiveX, and click on the "alternate method" link on the ensuing page.

I wish I was that good! It's hard enough for me to know what I am really thinking ... For XP, you could try the GenuineCheck.exe program, made for those who do not want to install the ActiveX used on the web pages. I don't have a link, but if you do not have the ActiveX on your machine (remove it if you do), and try to download something like Windows Defender, you will have the choice to use the "Alternate" authentification method. This will allow you to download GenuineCheck.exe. From there, I am not sure about doing it remotely, but it requires no installation. Perhaps using some tool to run on a remote registry? Give it a try, and post your findings!

1) It depends on how you use it. From CMDLINES.TXT you could put it directly in the $OEM directory. From SVCPACK.INF, it would go in the SVCPACK directory. From GUIRunOnce it can go anywhere, as long as your call to it reflects the correct location. 2) You can call it at about anyponit. I use SVCPACK.INF. 3) SETCD will work fine, if you want K, L, M and N as drive letters. Otherwise, SETCD, followed by one to four new drive letters, each with the ":" after the drive letter. See the Unattended Guide for adding CMD files to CMDLINES.TXT, SVCPACK.INF or GUIRunOnce.

My two cents worth ... (Sorry for the cut and paste, Yzöwl, but you said it so clear ...) This changes the first four CD / DVD Drive letters to those of your choice. To run it enter: SETCD K: L: M: N: where K: L: M: and N: are the drive letters you require, and SETCD is the name of the batch file. I have commented it for you to understand how it works, since I will not be making requested changes to it. SETCD.CMD: @ECHO OFF SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION SET LOGFILE=%SYSTEMROOT%\XPCSETUP.TXT SET LOGLINE=------------------------------------------------------------------------------- ECHO %LOGLINE% >> %LOGFILE% ECHO -- %TIME:~0,8% -- Starting SETCD >> %LOGFILE% ECHO %LOGLINE% >> %LOGFILE% :: This version of SETCD is for Windows XP SP2. :: It will change the CD Drive Letters, the Installation Source value, :: and create a System Variable INSTALLCD, used for subsequent applications. :: Find out which CD is listed as Install Source FOR /F "TOKENS=3" %%I IN ('REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "SourcePath" ^| FINDSTR "SourcePath"') DO SET INSTCD=%%~dI :: Get any passed parameters SET NEWCDROM1=%1 SET NEWCDROM2=%2 SET NEWCDROM3=%3 SET NEWCDROM4=%4 :: If we were not passed new drive letters, use these: IF "%NEWCDROM1%"=="" SET NEWCDROM1=K: IF "%NEWCDROM2%"=="" SET NEWCDROM2=L: IF "%NEWCDROM3%"=="" SET NEWCDROM3=M: IF "%NEWCDROM4%"=="" SET NEWCDROM4=N: ECHO %LOGLINE% >> %LOGFILE% ECHO SETCD Log File >> %LOGFILE% ECHO. >> %LOGFILE% ECHO Install CD = %INSTCD% >> %LOGFILE% ECHO. >> %LOGFILE% ECHO NEWCDROM1 = %NEWCDROM1% >> %LOGFILE% ECHO NEWCDROM2 = %NEWCDROM2% >> %LOGFILE% ECHO NEWCDROM3 = %NEWCDROM3% >> %LOGFILE% ECHO NEWCDROM4 = %NEWCDROM4% >> %LOGFILE% ECHO. >> %LOGFILE% ECHO DOS Devices as per Registry: >> %LOGFILE% ECHO. >> %LOGFILE% REG QUERY HKLM\SYSTEM\MountedDevices | FINDSTR "DosDevices" >> %LOGFILE% SET NEWINSTCD= SET CDCOUNT=0 :: Loop throgh list of DOS Devices: FOR /F "TOKENS=1,2,3 DELIMS= " %%A IN ('REG QUERY HKLM\SYSTEM\MountedDevices ^| FINDSTR "DosDevices"') DO ( SET RAWRESULT=%%A SET RESULT=!RAWRESULT:~26,18! :: CDs are encoded as "5C003F003F005C0049" IF "!RESULT!"=="5C003F003F005C0049" ( SET DLETTER=!RAWRESULT:~12,2! SET /A CDCOUNT=!CDCOUNT!+1 :: Get current drive letters into CDROMn variables. IF "!CDCOUNT!"=="1" SET CDROM1=!DLETTER! IF "!CDCOUNT!"=="2" SET CDROM2=!DLETTER! IF "!CDCOUNT!"=="3" SET CDROM3=!DLETTER! IF "!CDCOUNT!"=="4" SET CDROM4=!DLETTER! ) ) ECHO. >> %LOGFILE% ECHO CDs found: %CDCOUNT% >> %LOGFILE% ECHO. >> %LOGFILE% ECHO CDROM1 = %CDROM1% >> %LOGFILE% ECHO CDROM2 = %CDROM2% >> %LOGFILE% ECHO CDROM3 = %CDROM3% >> %LOGFILE% ECHO CDROM4 = %CDROM4% >> %LOGFILE% ECHO. >> %LOGFILE% :: Got through CDs found above :: If we are changing the Install CD letter, update the NEWINSTCD variable :: Get the Volume Info for each drive, which we need to mount the Volume to new letter. :: SUBST the old drive letter to new drive, in order to finish installation. :: Do that for all possible drives (0-4) IF "%CDROM1%"=="" GOTO NOMORECDS IF "%CDROM1%"=="%INSTCD%" SET NEWINSTCD=%NEWCDROM1% ECHO Changing %CDROM1% to %NEWCDROM1% >> %LOGFILE% FOR /F "TOKENS=1 DELIMS= " %%A IN ('MOUNTVOL %CDROM1% /L') DO SET VOLINFO=%%A MOUNTVOL %CDROM1% /D MOUNTVOL %NEWCDROM1% %VOLINFO% SUBST %CDROM1% %NEWCDROM1%\ IF "%CDROM2%"=="" GOTO NOMORECDS IF "%CDROM2%"=="%INSTCD%" SET NEWINSTCD=%NEWCDROM2% ECHO Changing %CDROM2% to %NEWCDROM2% >> %LOGFILE% FOR /F "TOKENS=1 DELIMS= " %%A IN ('MOUNTVOL %CDROM2% /L') DO SET VOLINFO=%%A MOUNTVOL %CDROM2% /D MOUNTVOL %NEWCDROM2% %VOLINFO% SUBST %CDROM2% %NEWCDROM2%\ IF "%CDROM3%"=="" GOTO NOMORECDS IF "%CDROM3%"=="%INSTCD%" SET NEWINSTCD=%NEWCDROM3% ECHO Changing %CDROM3% to %NEWCDROM3% >> %LOGFILE% FOR /F "TOKENS=1 DELIMS= " %%A IN ('MOUNTVOL %CDROM3% /L') DO SET VOLINFO=%%A MOUNTVOL %CDROM3% /D MOUNTVOL %NEWCDROM3% %VOLINFO% SUBST %CDROM3% %NEWCDROM3%\ IF "%CDROM4%"=="" GOTO NOMORECDS IF "%CDROM4%"=="%INSTCD%" SET NEWINSTCD=%NEWCDROM4% ECHO Changing %CDROM4% to %NEWCDROM4% >> %LOGFILE% FOR /F "TOKENS=1 DELIMS= " %%A IN ('MOUNTVOL %CDROM4% /L') DO SET VOLINFO=%%A MOUNTVOL %CDROM4% /D MOUNTVOL %NEWCDROM4% %VOLINFO% SUBST %CDROM4% %NEWCDROM4%\ :NOMORECDS :: If we have a New Install CD, update the registry for the Install Source. :: Also create a system wide Environment Variable that will tell us the Install CD Drive Letter. IF NOT "%NEWINSTCD%"=="" ( ECHO. >> %LOGFILE% ECHO Updating SourcePath to %NEWINSTCD%\I386 >> %LOGFILE% ECHO Creating INSTALLCD Variable = %NEWINSTCD% >> %LOGFILE% REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /V "SourcePath" /T REG_SZ /D %NEWINSTCD%\I386 /F REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /V INSTALLCD /T REG_SZ /D %NEWINSTCD% /F ) ECHO %LOGLINE% >> %LOGFILE% ECHO -- %TIME:~0,8% -- Finished SETCD >> %LOGFILE% ECHO %LOGLINE% >> %LOGFILE% This will change the drive letters to that which you specify, or K:, L: M: and N: by default if no drive letter is passed. The drive letter is changed immediatly, without the need for a reboot. During the Windows Installation, if this is run before setup finishes, this has the adverse effect that the Install CD cannot be found. For this reason, the existing drive letter is also "kept", using a DOS SUBST command. Additionaly, this will update the Windows Registry to reflect the new drive letter in the "Install Source" registry value. Finally, it will create an system variable called INSTALLCD, that can be used to identify the Intall CD Drive in BATCH files at a later date (after the next reboot). This script runs silently, and uses the logfile XPCSETUP.TXT that will be found in the %SYSTEMROOT% directory, usually C:\Windows. This SETCD.CMD file has been working just fine for me for quite a while, so I, like Yzöwl, will not be making requested changes to it. For information, this does not work for me in Windows 2003 Server: I have a slightly modified verstion for that OS.

No, the SWFLASH.INF is not compatable, and, as I pointed out, the flash.ocx has a different name. You could just rename and cab the flash.ocx. Flash would play, but the browser would still try to update because the version info in the registry would not reflect the version of the OCX. Furthermore, the other files in the downloaded cab are not used by Windows Setup.

- Rename the new flash from the downloaded cab (flash8.ocx) to flash.ocx, and cab it to flash.oc_. - Get the new version number from the .inf in the downloaded cab (8.??.??) - Expand the SWFLASH.IN_ file from I386, update the version number, and cab it to swflash.in_ - Replace SWFLASH.IN_ and FLASH.OC_ in I386 with the newly cabbed versions. - Forget about FLASH.IN_, as it is not for Macromedia Flash.

****! Why couldn't they have done that for the Advanced Networking Pack (877778?) last time!