Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Spheris

  1. that is a little harder to do it really is a manual sort job but well worth the results
  2. as long as you make sure the cat files are in the svcpack dir and accounted in the svcpack inf should be a flawless and seamless slipstream
  3. home and pro hotfixes are not strictly compatible from the IIS perspective, which is why there is a separate folder and file sort in the current service packs to differentiate them steer away from pro only hotfixes as they do insert files not fully compatible with home and vice versa
  4. Second addendum: to use this hotfix prep. the files must be named to numeric order, ie js56.exe will be invalid and out of sequence if written by a later hotfix and qchain will NOT update to sequential order. so look in the extracted exe for the q number and rename to those numbers to make the sort list to use with the files use the command line dir <driveletter\folder> *.* >filelist.txt to generate the correct sort order to paste to the inf file have fun
  5. Preinstalling HotfixesThis procedure describes how to preinstall hotfixes for Windows XP. This process differs slightly from the implementation for Windows 2000. To preinstall hotfixes for Windows XP Rename the hotfix package to a suitable 8.3 file name. Setup does not recognize long file names. For example: REN Q308387_WXP_SP1_X86_JPN.EXE Q308387.EXE Make a temporary directory to hold the extracted contents of the hotfix package. The files within the package will replace the original files in the i386 folder: MD C:\TEMP Extract the files from the hotfix package. For example: Q308387.EXE /x Enter C:\TEMP for the name of the directory. Open \Opktools\Lang\JPN\SKU\Pro\x86\i386\DOSNET.INF with Notepad and add this information to the file: [OptionalSrcDirs] svcpack Delete the svpack.in_ and original file(s) that the hotfix is replacing. For example: DEL SVCPACK.IN_, DEL AUTOLFN.EX_ Copy the replacement file from the temporary directory to the i386 folder: For example: COPY C:\TEMP\AUTOLFN.EXE C:\Opktools\Lang\JPN\SKU\Pro\x86\i386\AUTOLFN.EXE Create a SVCPACK folder in \Opktools\Lang\JPN\SKU\Pro\x86\i386. Create a new \Opktools\Lang\JPN\SKU\Pro\x86\i386\SVCPACK.INF with this content: For example: [Version] Signature = $Windows NT$ BuildNumber = 2600 MajorVersion = 5 MinorVersion = 1 [setupData] CatalogSubDir = i386\svcpack [ProductCatalogsToInstall] sp1.cat [setupHotfixesToRun] Q308387.exe /q /n /z Copy SP1.CAT from C:\TEMP\UPDATE to the C:\Opktools\Lang\JPN\SKU\Pro\x86\i386\SVCPACK folder: For example: COPY C:\TEMP\UPDATE\SP1.CAT C:\Opktools\Lang\JPN\SKU\Pro\x86\i386\SVCPACK\SP1.CAT Copy Q308387.EXE to the C:\Opktools\Lang\JPN\SKU\Pro\x86\i386\SVCPACK folder: For example: COPY Q308387.EXE C:\Opktools\Lang\JPN\SKU\Pro\x86\i386\SVCPACK\Q308387.EXE There is a addendum to this that only requires the actual hotfix packages placed in the SVCPACK folder without the extract and placing in the dll/sys/etc files in the i386 root conversely the files can be extracted and placed in the folder root and their older counterparts removed with only the cat files required to remain in the SVCPACK folder with resolves the space problems for those without dvr drives who want all the update files NOTE: the current sp2 rollup (build 1228) is an official internal build and can be used with the kernal rollup to make a validated sp2 build of xp extract the applicable files from the kernal rollup and integrate with the sp2 package, before doing the slipstream and should bring you upto current build status of 4/29/03 for sp2 there are no logged conditions or caveats on this particular build 1228 for sp2
  6. A fair assement, but I'm curious as to how many people are actually using ipsec to lock their machines down, negating the use of the "security" hotfixes being necessary at all. Thanks very much for the reply and if you can give me some feedback on your own use of ipsec when you have time
  7. using the tgtsoft patch, you have about a 70/30 chance of installing the uxtheme.dll the sfc_os is a signed file however and cannot be circumvented for those with the sp2 1228 build and the kernal roll up hotfix you can add the current hotfix listing and the kernal rollup packages and have a current non debug sp2 build or wait for sp2 3/4 in q1 2005 as the delay is for integration of additional security and compatibility with future winos versions
  8. None taken, you should see what we do to each other over at the msdn-technet boards But seriously, wanted a show of hands on which seems more important the security hotfixes (that can be taken care of by judicious use of the manual and ipsec configuration) or the functional fixes -ie bugfixes for kernal/usb etc et al the debate started last wednesday with the blaster hotfix being worthless by some accounts over at msdn and I wanted to throw this one out to the people on the ground to get an opinion
  9. First casualty of the day I see~ The question is simple, sec fixes, which can be done alternately with locking down a workstation Or chasing one file or another down endlessly - versus actual function fixes. devil270975, don't be an a**. If you don't get the question - ask to clarify. Flaming doesn't really get you anywhere with me
  10. Here's the deal, we do a disc to MS specs I'll provide the engineering docs and etc - but lets get a little creative license going too but I would like a discussion before we get rolling on the pros and cons of security fixes versus functionality fixes as a priority seems the sec fixes size versus the actual bug fixing is getting a little out of hand in sight of general laziness going on with taking the time to lock a system down I'd like some other opinions from admins and general users on the state of the never ending hotfix saga
  11. Alright will post a complete list guide for the MS-OPK guide version of the automated discs give me a day or two to put it all together as the documentation and options are pretty extensive but a good bit more stable in builds that need to work the first time round
  12. Use CDIMAGE 2.47 and any burner software that supports DVD-R Myself I use the CDBURN and DVDBURN apps from the reskit with no problems Including Nero, though I don't recommend it for practical reasons I'm sure some people have very good luck with it, but some of the reports of conflicts and burnouts I've read over the last year tell a very sad story for most people. Your own mileage will vary of course
  13. The actual listing is at http://warp2search.net applicable for post sp-1 and for post IE/OE sp-1. The fixes are available with corresponding links and applicable download sites though not officially approved by MS, they are allowed as a redirection to the correct MS sites and not deep linked There are 5 non released updates in the downloads section as well - THESE ARE HOTFIXES RELEASED TO OEMS only and not strictly for public use - however, they are listed in the sp2 log and are valid for current issues with current and advancing technology (i.e.: HT issues, usb2 etc) cheers
  14. For the sblive, if using the current asio enabled drivers or a variant, edit the iss file its your best bet at having the complete support dlls loading as it has an existing wow16 problem in their installshield implementation, a hotfix is available for it but does not help at install time
  15. Mortis, I'll have a correct $OEM$ folder order for you this evening. You're right the folder sort isnt lending to pre installs as intended and dell etc have made MS aware of it. There is a workaround but I'll have to get it from someone else here.
  16. Not advisable to remove the UPG dir, can work for clean installs but does break upgrade and or repair support~
  17. He is correct, sysoc.inf must be edited to enable removal of a core component and oe/ie are core components, no matter what the pr dept at ms would like to say to the contrary
  18. The command lines text method does indeed support hotfixing with accompanying switches using the win32 api rather than the wow api and is about 15-30% faster overall and more robust than the batch script as far as stress on memory starved systems I also have a concurrent list of applicable fixes (i ignore the security fixes by and large - pointless race and am a better programmer and more conscious admin than to leave myself a** out as these flaws seem to indicate for a lot of these people who do not lock their systems down) at any rate - here we go [Commands] ".\SVCPACK\Q282010.EXE -U -Q -N -Z" ".\SVCPACK\Q322011.EXE -U -Q -N -Z" ".\SVCPACK\Q323255.EXE -U -Q -N -Z" ".\SVCPACK\Q327696.EXE -U -Q -N -Z" ".\SVCPACK\Q327979.EXE -U -Q -N -Z" ".\SVCPACK\Q328310.EXE -U -Q -N -Z" ".\SVCPACK\Q329048.EXE -U -Q -N -Z" ".\SVCPACK\Q329115.EXE -U -Q -N -Z" ".\SVCPACK\Q329170.EXE -U -Q -N -Z" ".\SVCPACK\Q329256.EXE -U -Q -N -Z" ".\SVCPACK\Q329390.EXE -U -Q -N -Z" ".\SVCPACK\Q329441.EXE -U -Q -N -Z" ".\SVCPACK\Q329604.EXE -U -Q -N -Z" ".\SVCPACK\Q329623.EXE -U -Q -N -Z" ".\SVCPACK\Q329692.EXE -U -Q -N -Z" ".\SVCPACK\Q329834.EXE -U -Q -N -Z" ".\SVCPACK\Q330512.EXE -U -Q -N -Z" ".\SVCPACK\Q330909.EXE -U -Q -N -Z" ".\SVCPACK\Q331953.EXE -U -Q -N -Z" ".\SVCPACK\Q331958.EXE -U -Q -N -Z" ".\SVCPACK\Q810032.EXE -U -Q -N -Z" ".\SVCPACK\Q810243.EXE -U -Q -N -Z" ".\SVCPACK\Q810272.EXE -U -Q -N -Z" ".\SVCPACK\Q810400.EXE -U -Q -N -Z" ".\SVCPACK\Q810565.EXE -U -Q -N -Z" ".\SVCPACK\Q810577.EXE -U -Q -N -Z" ".\SVCPACK\Q810833.EXE -U -Q -N -Z" ".\SVCPACK\Q811630.EXE -U -Q -N -Z" ".\SVCPACK\Q812035.EXE -U -Q -N -Z" ".\SVCPACK\Q812415.EXE -U -Q -N -Z" ".\SVCPACK\Q814033.EXE -U -Q -N -Z" ".\SVCPACK\Q814995.EXE -U -Q -N -Z" ".\SVCPACK\Q815021.EXE -U -Q -N -Z" ".\SVCPACK\Q815485.EXE -U -Q -N -Z" ".\SVCPACK\Q816073.EXE -U -Q -N -Z" ".\SVCPACK\Q817606.EXE -U -Q -N -Z" ".\SVCPACK\Q820128.EXE -U -Q -N -Z" ".\SVCPACK\Q820291.EXE -U -Q -N -Z" ".\SVCPACK\Q821253.EXE -U -Q -N -Z" ".\SVCPACK\Q821557.EXE -U -Q -N -Z" ".\SVCPACK\Q821581.EXE -U -Q -N -Z" ".\SVCPACK\Q822603.EXE -U -Q -N -Z" ".\SVCPACK\Q823559.EXE -U -Q -N -Z" ".\SVCPACK\Q823980.EXE -U -Q -N -Z" ".\SVCPACK\QCHAIN.EXE ".\CMDLINES.CMD" Syntax must match -m is superceded by -u for xp unattended cheers
  19. you read the inf file and as long as there are no conditional branch dir listed in the copy part of the inf you're golden
  20. http://www.microsoft.com/technet/treeview/...ity/current.asp This is the current and as far as I know the only hotfix bulletin site MS maintained and gives a clear and concise chronology of released hotfixes Cheers
  21. To preinstall a mass-storage device In the \$OEM$ subfolder of the configuration set, create the \Textmode subfolder. Copy the files from the disks supplied by the device vendor to the \Textmode subfolder. These files normally include: Driver.sys Driver.dll Driver.inf Driver.cat Txtsetup.oem where Driver is the driver name. Notes You must also copy the driver files to the location you specified in the OemPnPDriversPath entry in the answer file(s). For example: OemPnPDriversPath = drivers\storage Some drivers, such as SCSI miniport drivers, may not include a .dll file. A catalog file (Driver.cat) must be included with mass-storage device drivers if it is listed in Txtsetup.oem. For more information about catalog files, see Using Signed Drivers. Also see the Microsoft Windows Driver Development Kit (DDK), which you can read in the MSDN Library (http://msdn.microsoft.com/library/): Select Windows Development, and then select Driver Development Kit. In the Unattend.txt file, create a [MassStorageDrivers] section, and then type any driver entries in that section. For example, a possible entry in the [MassStorageDrivers] section is: "Adaptec 2940..." = "OEM" Obtain the information for this section from the [sCSI] section of the Txtsetup.oem file provided by the hardware manufacturer. Note You must use signed drivers. Unsigned drivers are not installed during an unattended installation. In the Unattend.txt file, create an [OEMBootFiles] section, and in it type a list of the files in the \$OEM$\Textmode folder. For example: [OEMBootFiles] Driver.sys Driver.dll Driver.inf Driver.cat Txtsetup.oem where Driver is the driver name. Important Add driver entries only to the [MassStorageDrivers] and [OEMBootFiles] sections for bootable mass-storage devices. Do not include secondary mass-storage devices. Instead, add the drivers for secondary mass-storage devices to the folder specified by the OemPnPDriversPath entry in your unattended Setup answer file. Including drivers for non-bootable mass-storage devices in the [MassStorageDrivers] or [OEMBootFiles] sections causes an error during Setup. If your mass-storage device is a Plug and Play device, verify that a Hardware Identification section and the name of the catalog file for the driver (Driver.cat) exist in the Txtsetup.oem file. For more information, see the Microsoft Windows Driver Development Kit in the MSDN Library (http://msdn.microsoft.com/library/): Select Windows Development, and then select Driver Development Kit. If the Hardware Identification section does not exist, you must add [HardwareIds.scsi.yyyyy] to the Txtsetup.oem file and verify that the following information is included: id = "xxxxx" , "yyyyy" where xxxxx represents the device ID, and yyyyy represents the service associated with the device. For example, to preinstall the Symc810 driver, which has a device ID of PCI\VEN_1000&DEV_0001, verify that your Txtsetup.oem file contains the following additional section: [HardwareIds.scsi.symc810] id = "PCI\VEN_1000&DEV_0001","symc810" You must remove drive and path references from Txtsetup.oem. For example, instead of this text, use the NTFS or FAT32 examples that follow: [disks] d1 = "Windows XP Driver Set v1.00", \w2kdsk1, \win2000\smy810\ For NTFS installations, use this text: [disks] d1 = "Windows XP Driver Set v1.00", \w2kdsk1, \ Note the trailing slash at the end of the line. For FAT32 installations, use this text: [disks] d1 = "Windows XP Driver Set v1.00", w2kdsk1, . Note the lack of a backslash; also note the trailing period at the end of the line. Note The MSDInst.exe tool enables you to add mass-storage device drivers to an offline image. For details, see the white paper entitled Using the Mass Storage Device Installation Tool (MSDInst.exe) on the Windows OPK CD. Selecting and Loading the Correct Mass-Storage Driver If you are including new or updated drivers for mass-storage devices, you must add the new driver to both of these folders: \$OEM$\Textmode The location specified in the OemPnPDriversPath entry in the Unattend.txt file. For example: \$OEM$\$1\Pnpdrvrs\storage Loading Mass-Storage Drivers During Text-mode Setup If the driver for the mass-storage device is included with Windows XP, the Windows XP driver is chosen before any drivers in \$OEM$\Textmode. However, the driver you place in \$OEM$\Textmode is the first driver chosen during text-mode Setup only if: The driver that ships with Windows XP does not boot. The driver does not ship with Windows XP. Loading Mass-Storage Drivers During GUI-Mode Setup Windows XP loads an updated or new driver during GUI-mode Setup if the following criteria are met. If you are loading an updated mass-storage device driver for one that ships with Windows XP: The correct mass-storage driver is provided in the location specified by OemPnPDriversPath. The driver is signed and is a more recent version than the one provided with Windows XP. If you are loading a new mass-storage device driver that did not ship with Windows XP: The driver is new (not included with Windows XP), signed, and installs properly during text-mode Setup. For information about how Windows chooses the best driver during Plug and Play detection, see How Windows Selects a Particular Device Driver.
  22. [Commands] "rundll32 setupapi,InstallHinfSection DefaultInstall 128 .\*.INF" all files must reside in the base $OEM$ folder
  • Create New...