With CDmage you find the information needed to properly burn the CD with Windows XP.
drivers on a fresh XP: motherboard, network card, video card etc.. Here, depending on how you want to Shut generic CD, you can include drivers for most common components. It’s time to populate this directory with the files, according to the rules set out above. Once completed this operation, we must return to the answer file winnt. SIF is containing your search for new ways installer. Using Notepad, open the map file and the [Unattended] section, add or modify the following parameters:
UnattendMode = ProvideDefault
OemPreinstall = Yes
OemSkipEula = Yes
NoWaitAfterTextMode = l
NoWaitAfterGUIMode = l
TargetPath = \ WINDOWS
DriverSigningPolicy = Ignore
OemPnPDriversPath = Drivers \
Driver 1, Drivers \ driver2;
Drivers \ driver3; … Drivers \ drivern
where driverl, 2, n are directories containing the drivers. DriverSigningPolicy is very important parameter is set to Ignore, because not all drivers are WHQL certified also name directories must be on same line with OemPnPDriversPath parameter.
A different problem arises when there is a controller in the system SCSI/SATA/RAI1). For this kind of components of the Windows Setup  opportunity as the beginning of the operation to load the driver for that component (key F6). With controller driver archive, and create this one directory $ OEM $ \ $ l \ Drivers and decom-press files. SYS file (the driver itself) to copy the folder 1386. Also in this directory is the file “txtsetup.sif” (which they make her a backup). Using Notepad site is added to section [SourceDisksFiles] registration “nume.sys = l” “” _x, 4, l ‘where name is replaced with name SYS file just copied. Using the driver INF file, it found code component that we install. It has a shape similar to the following examples: “PCI \ VEN_105 A & DEV_3375″ or “PCI \ VEN_1095 & DEV_3112 & SUBSYS_61121095″. If there are several such codes in the file INF copy them to a temporary file. Back then in txtsetup.sif and Section | HardwareIdsDatabase] add codes and file name rule as SYS “Code -” name “.” Continuing, the section [SCSI.Load] add the line “name = nume.sys, 4″ and a final amendment to the section [SCSI] add the line “name-” long description of the controller “.” Save the file under the same name and, after the operation, upgrade and OemPnPDriversPath line in winnt.sif file.
Integrating Windows updates
Lately, Microsoft has accustomed us a monthly pace of the updates for XP. But a visit to Windows Update is a nightmare for a newly installed system. And usually delete update process after running these updates kits.
At windowsupdate.microsoft.com / cata log you access to all updates for Microsoft operating systems and the collection of drivers licenses. There can be chosen updates it needs a fresh install and on which was applied Service Pack 1.
Microsoft tells us is how to integrate these hotfixes sites in our package, the directory 1386 to create a subdirectory “svcpack.” Open file “dosnet.inf” and add the following lines:
[OptionalSrcDirs] svcpack
Copy updates using the 8.3 format (where xxxxxx Qxxxxxx rename them is the number present in the original name of the file). in a temporary directory extract the contents of the updates (preferably, each in its own directory). Copy the I386 \ svcpack form Qxxxxxx.cat CAT all files that you find in the temporary directory. If the same file exists on several updates, should be kept at the newest version. For each of the hotfix files in order to be found you have to delete correspondent in 1386. Then copy any files and subdirectories in 1386. For each of the copied files have their name checked dosnet.inf presence under section [Files] and, in case that there be added a line as “Mr., file_name ‘\
After this verification can delete the file “svcpack.in_” and create a text document named svcpack.inf. It will have the following structure:
We have integrated a service Fack, drivers and hotfix’s. It remains installed with Windows and some applications. For this we turn to winnt.sif file. Using batch scripts, the first running of Windows can be run a number of installation programs. We will not deepen the problem, but we enunciate the principle of operation. Windows setup will search site at some point during the installation file found in the directory SOEMS Cmdlines.txt. in it, under Section [Commands], may be brought on behalf of different batch files. in these files can be included controls to applications installed by Windows and the programs available on CD in the directory SOEMS.
For Baking
To test the installation that I just “created” a need to reconstruct the Windows CD’s. This operation will first make an image of the original CD using Windows’ application CDRWin. Using this image in the application Cdmage, we can extract the correct information needed to create our CD. first extract boot image file. To do this, choose CDmage Ed / t -> Date Tnick PropertiesÅi in the dialogue that follows, we choose Boot record. Clicking the Save button boot image is moment to save the file needed. The same dialogue extract and the remaining information required for proper combustion. They can be found in ISO 9660 Descriptor tab. We are almost done. in one of the versions of Nero Rom Buming create a new bootable CD project. through the steps of defining the properties of the CD: the Boot tab CDmage will use the saved file, activate the advanced options (Enable Expert Settings) and emulation type (Type otEmulation) choose No Emuhtion for parameter Load segment of sectors introduce 07C0 hex value and the number of sectors to load (Number ofhxided sectors) value 4. the next tab – ISO – we check / choose options ISO LEVEL I, Mode /, ISO 9660, Joliet and all checkboxes to Relax ISO restrictions sites. If you noted the values of ISO 9660 Descriptor Cdmage, you will not have trouble completing the fields tab feet. After completing the following store data tab Original files and, eventually, sign out the CD. It remains only to add your files and directories in C: \ XPTEST \ XPCD the project and burn to CD. Good luck!
