Integration side effects not UpdatePack bugs : setuperr. Please note that in some rare configurations the integration of this addon could cause issues, so we don't suggest to use it. Post by harkaz » Sat Sep 14, pm Thanks for the tip, bphlpt, I'll check this later.
Is this normal? Currently working hard on the "Battery unsigned" problem. I'm making progress: I have been able to reproduce the problem I faced with the original patch with the new one I applied yesterday.
I'm confident I'll find the solution. Can someone help me debug it to find its region in EXE? Note: This is the region which, if changed, causes all catalogs not to be recognised correctly. This seems to be independent of battery, however.
Post by harkaz » Sun Sep 15, am Making progress: With a second patch, I managed to completely remove Messenger its catalog was manually removed by me in syssetup. So it seems that this patch is required for some changes in syssetup. Now, the final step is removing the "Battery unsigned issue".
Post by harkaz » Sun Sep 15, pm Fixed the "Battery unsigned" issue, will perfrom some additional checks before giving you the essential details. How to properly patch syssetup. Grab the original XP SP3 syssetup. Using a hex editor, like XVI32, open the dll file. Go to address offset 33B7B. Replace 74 with EB. Save changes to syssetup. Using modifype -c command or a similar tool fix the PE checksum.
To get rid of the "Battery unsigned" issue, you have to perform this additional step: Open the syssetup. Delete or comment the line with the battery. Save changes. Use the new syssetup. Known side-effects: Setuperr. In addition, SFC does not protect syssetup. However, SFC does not report any problems after Windows installation. Waiting for your comments after testing the new patch. Time to return to my SP4 project.
Post by Atarixl » Mon Sep 16, pm Thanks harkaz, nice to read your "adventures" every day. I still tested them with nLite and Dutch XP, but of course? Well, it kinda worked, but there were 2 errors. So I hope you'll tell us how we can build the SP4 when the time's right, from your last posts, I'm sure you will succeed! DLL patch steps Integrates with RyanVM Integrator 1. Last edited by 5eraph on Tue Sep 17, am, edited 4 times in total. Post by harkaz » Tue Sep 17, am Thanks Atarixl. I'm working on MSN Explorer I haven't tested the removed Messenger yet.
Is it working as it should? Post by 5eraph » Tue Sep 17, am Tested and working as intended following steps 7 and 8 of your patching guide. Details added to my previous post. Post by harkaz » Tue Sep 17, pm A new challenge: While installing the service pack testing now this error message appears: Setup cannot copy the file syssetup. Let's see what's going on here Let's see if Gurgelmeyer has done sth on that The error GetCatVersion: Failed to retrieve version information from Probably patching it is not needed UPDATE 2: The error message: "A component's fil soes not match the information peresent in the verification manifest" seems to be related with update.
It is probably related with modified syssetup. Issue seems to have been fixed with a second patch I applied. Note that Gurgelmeyer's update. Messenger removed. The only thing I need to add for removal are the start menu messenger entries. After that, I'll test slipstreaming to SP3 installation media. Is there an automated way to keep the update.
Post by harkaz » Thu Sep 19, am Some instructions to create a self extracting executable. Extract the sfx from the KB for example package for the desired language: In the update package of the desired language, using a hex editor, search for MSCF string. This the self-extracting "header for EXE file. The update. Any argument parsed to the sfx executable will be parsed to the update.
Using a hex editor, open the sp4. Go to the hex editor section. Change 20 to 60 and save changes. Optionally, add a manifest to require elevation each time the SP4 package is run. Post by tomasz86 » Thu Sep 19, pm harkaz Good luck with the project but I think you're spending a lot of time on things which have already been done Same instructions as the ones above were already posted by WildBill 3 years ago here , and here you can also find my automated version.
As for Gurgelmeyer and USP5 - he didn't modify any signed system files so no additional patching was necessary except for the installer. Post by harkaz » Thu Sep 19, pm Thanks! This was the source of theseinstructions, and thank you for mentioning it!
I posted it in this thread so that everything is one place. Now, I have an additional problem with update. No catalog file installs after SP4 installation completes. Windows Preinstallation Environment images based on Windows 10 and later use an italic Segoe UI font by default as a result of missing resources. A custom Windows PE image can be created with the following instructions, provided that a set of tools from Microsoft are installed.
To create a WinPE image, the following steps have to be performed:. Windows Preinstallation Environment based on Windows Longhorn build Windows Preinstallation Environment based on Windows Vista build Windows Preinstallation Environment based on Windows 8 build Automatically add customized Internet Explorer branding, including a search page, custom toolbar buttons, a custom home page, as well as additional customized Favorites and Help and Support pages.
Automatically copy and execute Sysrep. Automatically start Audit mode. In addition, if you do network installations, you do not need to open all CDs from the 3pack because the source files are copied from one CD one each for Home Edition or Professional to your technician computer only once.
You should ship the remaining unopened packs with each new computer that you preinstall by using the configuration set you built. While a network-based process is the recommended approach, it is possible to perform a CD-based preinstallation without a network. For information on this process, refer to Appendix A. Overview of the Preinstallation Process Before you begin, set up one of the following configurations listed in order of preference.
A technician computer that contains one network adapter, plus a network router or a server running Windows Server that is configured as a DHCP server.
In addition, you need a master computer that also contains one network adapter. This option gives you the maximum preinstallation flexibility. A technician computer that contains two network adapters or a network adapter and a modem. Your technician computer must be running Windows XP. A technician computer that contains one network adapter, plus a crossover cable to connect to a master computer that also contains one network adapter.
You can preinstall Windows without using a network; however, you lose considerable flexibility in doing so. As discussed elsewhere in this document, not using DHCP makes your preinstallation process more complex. Selecting this check box copies a modified version of the Winbom. Restore the image over the network to the destination computers. Or copy the image from the technician computer onto the destination computers. Note Alternatively, you can burn a CD containing the image and imaging software, and use this CD to start and configure the destination computers.
Build Build an an image image of of the the installation installation and and store store itit on on the the technician technician computer computer Deploy Deploy image image from from the the technician technician computer computer onto onto the the destination destination computer s computer s.
Set up the new hardware and software, and identify any applications that you want to install. If the CD does not start automatically, double-click Setup. Only one version of the OPK tools and documentation can be installed on a technician computer. Run Opk. This is the autorun file, which automatically starts when you insert the CD. The preferred method is to use Setup Manager.
When you use this method, your existing configuration sets still work. Run Setup Manager. Save the configuration set and complete Setup Manager as you normally would. The first time you upgrade the OPK toolkit, the OPK installation program automatically detects and upgrades the set of tools in the corresponding language. Sharing the OPKTools and Application Folders Make sure that your OPKTools folder and any folders containing applications that you want to install are shared and that you have created appropriate user accounts to access them.
To share a folder, right-click it, click Sharing and Security, and then click Share this folder. After you run Setup Manager and create your first configuration set, you can share the OPKTools folder if you have not already done so.
Type a new user name and password that you will use during the application preinstallation phase. On the Name the new account page, type a name, and then click Next. On the Pick an account type page, select Computer administrator, and then click Create Account. Important For the preinstallation to work properly, you must share the OPKTools and application folders, and then create user accounts for accessing them. For example, use the user name opkuser and a password for the OPKTools folder; and use the user name appuser and a password for the applications folder.
To start Setup Manager 1. Double-click the Setupmgr. The first page of Setup Manager will appear. However, the functionality is the same. On the first page of Setup Manager, you can prepare the automated preinstallation of Windows XP on your destination computers the computers that you will sell to your customer.
Setup Manager will save the settings that you choose in a configuration set. To avoid seeing this page the next time you run Setup Manager, select the Skip this page next time check box. When you are ready to continue, click Next.
Configuration Set On this page, create a new configuration set, or edit or copy an existing one. Because this is your first time running Setup Manager, you can choose to create a new configuration set. To modify an existing configuration set 1. Click Edit or copy an existing configuration set. In the Existing configuration sets list, click the configuration set that you want to use, and then click Next.
If you select this option, you must download the source files and run Windows Setup. Completing this type of installation does not reseal the computer. The computer restarts into Audit mode.
Reseal when finished: Based on the above installation mode, this mode automatically reseals the computer without enabling further customization. To enable further customization after restart, select Factory. To restart into the default end-user experience either Windows Welcome or Mini-Setup, depending on the version of Windows that you install , select End user.
Copy files only: This installation mode provides you access to the command prompt after the file-copying portion of Setup finishes and before first-boot processing occurs.
You have the option of disk duplication and other customization. By default, auditing is not set in this mode. Resealing is the last step in the preinstallation process. It prepares the computer for delivery to the end user and sets the computer to start into either Windows Welcome or Mini-Setup depending upon the Windows product that you install.
You are required to reseal the computer before delivering it to the end user. Location of Settings The settings from this page are saved in this location: Winbom. To specify the target product 1. In the Products list, select the product that you want to install, and then click Next. Setup Manager will copy the product files to your computer. When the destination computer runs Windows XP, branding information appears automatically in Control Panel, on the General tab of the System Properties dialog box.
To specify your branding information 1. In the Manufacturer box, type your manufacturer name. This is required information. In the Model box, type the model of the computer. This is optional information. In the Provide information on how your customers can get support box, type how the end user can obtain support. Spell all items exactly the way you want the text to appear in the product.
Include telephone numbers and hours of operation for your technical support group. Include information for several countries or regions with a common language and different support information.
Do not list Microsoft in the support information section—you are responsible for supporting Windows XP on all computers that your company ships.
Localize the required [Support Information] section in Oeminfo. Microsoft includes only an English U. Do not include any information, such as the version number of the Windows XP operating system that could change when the end user upgrades to the next version.
Do not include any information in the [Support Information] section that does not directly pertain to support. Location of Settings The settings from this page are saved in this location: Oeminfo.
This Product Key will be set to blank when you reseal the computer for final shipment to the customer. Notes The Product Key setting is saved in the unattended installation file if you use Unattend. Preinstalled Applications Use this page to define entries that start application setup programs or. The steps that you complete to preinstall other programs will differ depending on the program. To specify the programs to start during auditing 1. On the Preinstalled Applications page, click Add.
The Add an Application dialog box will appear. In the Add an Application dialog box, in the Display name box, type the name of the application as you want it to appear in the user interface. If you want to specify a Universal Naming Convention UNC path, click Browse to find the location of the Windows Setup program in a folder on a mapped network drive or a local folder that is shared. This command line sets up that program to run during auditing. The Standard installation mode automatically invokes auditing during the Windows XP preinstallation.
Click Advanced if you want to specify the type of setup program, restart the computer after installing, or select staging options.
Staging an application: If you want to install a particular application on most of your computers, consider including a staged version of the application in the master installation. To stage an application means to make all the files available locally. When an application is staged on the hard drive, the application setup program is required only to make the relevant changes in the registry, eliminating time-consuming copying of files.
On the Preinstalled Applications screen, you can also edit the preload parameters by selecting the item on the list and then clicking Edit. You can also change the order in which the setup programs run by selecting an item and clicking the arrow buttons to the right of the list to move that item. To specify network access credentials for this configuration set only 1. Select the Specify credentials for connection to network resources in Factory mode check box.
Type the password in the Password and Confirm password boxes. Important Type the user name and password that you created earlier for the application preinstallation phase for example, appuser.
Specifying credentials for this configuration set does not change the credentials specified in the distribution share settings. If you do not specify credentials for this configuration set, Setup Manager uses those specified in the distribution share settings. You can view or change the distribution share settings by clicking the Tools menu, and then clicking Distribution Share. To set up the installation of Plus!
You will see this only if you look at the Winbom. Make sure that all of your folders are shared and that the user account that you created has access to the shares. Important If you assign a static IP address, applications are not preinstalled, even though they are specified in the Winbom. On this page, specify the logo file that you want to use. To specify a custom logo for System Properties 1. Create a bitmap file named Oemlogo. The bitmap must be x pixels in size.
Specify the path and file name for the logo bitmap. It is strongly recommended that you test your logo bitmap on the computer models and monitors that you ship to ensure that the logo appears the way you want. Setup Manager saves the Oemlogo. Windows Setup copies the. Branding Opportunities On this page, customize the Windows Welcome screen with your own branding. To customize Windows Welcome 1.
Type your company name in the Company Name box exactly as you want it to appear on the Welcome and Finish pages. Select the Add the following OEM logo to Windows Welcome check box, and then click Browse to specify the path and file name of the graphic file that you want to display.
Your logo will appear in the upper-right corner of the Windows Welcome pages. Note It is recommended that you prepare the logo graphic before you run Setup Manager. Other requirements are noted in the table below. Location of logo display. If the image is larger than the specified dimension, Windows Welcome crops any additional pixels on the right-hand side or bottom of the image. Location of Settings The settings from this page are saved in this location: Oobeinfo.
System Settings On this page, choose the default settings for language, region, keyboard, and time zone. These settings are based on the language version of Windows XP that you install. Whether you use the defaults or other selections, you can select whether to enable the user to change the settings that you specified.
Some countries, regions, or locales may have more than one common language or multiple time zones, and some languages are used in more than one locale, country, or region. If you clear the Allow end user to change language, region, and keyboard settings or Allow end user to change time zone setting check boxes, then the pages for these settings do not display in Windows Welcome when the end user first runs Windows XP Home Edition or Windows XP Professional.
If you do not configure a specific time zone setting, the default time zone in Windows is set equal to the default for the language that Setup Manager is localized in. If you want the end user to specify a time zone, select the Allow end user to change time zone setting check box. Note If you use this page to change regional settings, you will not see the prepopulated settings when you run Sysprep in Audit mode.
However, when the end user completes Windows Welcome, the settings will be correctly prepopulated. Mouse Tutorial On this page, specify a custom mouse tutorial during Windows Welcome.
0コメント