Universal HDD Image files for XP and Windows 7, Boot VHD Image files with Grub4dos Menu on HDD or USB
*** IMG_XP package ***
Make XP and Win7 Universal Image files booting with Grub4dos Menu on HDD or USB
================================================================================
Download - IMG_XP_85 - mirror
In Win7 OS Set User Account Control Off and Reboot
1. VHD_XP_Create.exe - Make VHD file and Install XP in VHD by using Grub4dos Boot Menu on HDD
First Prepare XP Setup ISO file with integrated UpdatePack and DriverPacks as described below in Section 2
and Copy XP Setup ISO file to the root of internal harddisk drive of your computer.
-
0. Run IMG_XP.exe and Extract to simple path on your Local Harddisk - gives folder IMG_XP
1. Use IMX_XP\makebt\imdiskinst.exe to Install ImDisk driver (if not present)
- Imdisk is used by USB_XP_Fix.exe to mount VHD and HDD Image files in a virtual drive
2. Run VHD_XP_Create.exe to create XP-1.vhd and Grub4dos Boot Menu for Install of XP in VHD
- Boot Drive - FAT32 or NTFS - can be USB-stick so that there are no changes needed in the Windows installation on the internal harddisk
- System Drive - NTFS - where VHD file is created e.g your internal harddisk drive
- XP Setup ISO file - located on internal harddisk drive so that fast loading into RAM is enabled
3. Reboot and in Grub4dos menu select Start XP Setup on XP-1.vhd - WinVBlock driver
- XP-1.vhd has already NTFS compressed format, so you should NOT format at Setup, just keep settings
- Format XP-1.img inside XP Setup cannot be used, it results in corrupt message
4. After Reboot select Continue XP Setup and then Reboot to Start XP from Image XP-1.vhd
5. Reduce size and improve settings as usual and Install missing Drivers but NOT the specific large Video driver
Reduce size to get rid of pagefile.sys and hiberfil.sys via:
- right click My Computer > select Properties > Advanced > Change Virtual memory > select No pagefile and Set
- right click on Desktop > Screen Protection > Energy > Uncheck Sleep settings to get rid of hiberfil.sys
- Set System Restore and Windows Update Off and delete 350 MB of dllcache folder via cmd SFC /purgecache (or Run PURGE_DLLCACHE.BAT)
- For Universal XP don't Install the Video driver. You can Uninstall the Video driver so that you still have high resolution on any hardware.
- Set Screen Resolution to 1024 x 768 useful on all monitors (right click on Desktop)
6. USBoot DriveGuard driver is probably unneeded to prevent BSOD 7B since recent USB_XP_Fix.exe will Fix XP and Install waitbt.sys driver.
Skip this step Or Install USBoot DriveGuard driver ubdrvgd.sys to prevent BSOD 7B in booting from USB
- Download USBoot from http://usboot.org/tiki-index.php
- Extract the package, right click on ubdrvgd.inf, click on Install
- the XP boot message - DriveGuard Initialization failed - has No effect, the driver works OK
- More Info http://reboot.pro/9830/page__st__800#entry160006
- DriveGuard driver ubdrvgd.sys is installed as LowerFilters between the main driver and the hardware
7. Connect USB-HDD where you want to use XP Image, so that USB-HDD settings are known in XP registry, and Reboot
8. Reboot with other OS and copy XP-1.vhd to bootable USB-drive and create entry in Grub4dos menu.lst
- BOOT_USB.exe can be used to make USB-drive bootable with Grub4dos Menu
- BOOT_IMG.exe can be used to make Grub4dos Boot Menu on existing bootable drives
9. Run USB_XP_Fix.exe and Select your XP-1.vhd file on USB-drive and click GO
10. Reboot from USB on the same computer and Select Boot XP Image - XP-1.vhd - WinVBlock FILEDISK
11. Reboot from USB on other computers and Select Boot XP Image - XP-1.vhd - WinVBlock FILEDISK - to make Universal
When booting on other unknown machine, then XP will auto adjust itself in about 3 min and install the required drivers.
In this learning process, the registry gets extra info on how to boot on that machine and will use it next time and so XP becomes Universal.
This process requires that you have the WINDOWS\DriverPacks folder of 135 MB available with Chipset + Processor + MassStorage + LAN drivers
and that DevicePath in the registry was properly set by the Keep The Drivers Option KTD (see below and in Picture).
If you have Installed XP in VHD on AMD machine and then boot XP Image file first time on Intel machine,
then intelppm Service will have Start=1 value, which will give BSOD 7 E when booting again on AMD machine.
This problem can be overcome by running the intelppm_Start3.reg registry tweak from POST_FIX folder.
In that case intelppm Service will get Start=3 and everything will be OK all the time for AMD and Intel.
Thanks to Sha0 for making WinVBlock driver - http://reboot.pro/8168/
Thanks to cdob for making usb_xp_init.cmd - http://www.911cd.net/forums//index.php?sho...22473&st=37
Thanks to sara - pmedia for her tutorial - http://reboot.pro/13731/
More Info on direct Install of XP by using grub4dos menu and WinVBlock or FiraDisk driver:
cdob - Install XP from a ISO file No RAM disk - http://www.msfn.org/board/topic/149675-ins...rom-a-iso-file/
Doodoo - http://reboot.pro/13856/page__p__122385#entry122385
sara - pnedia - http://reboot.pro/13731/
wimb - http://www.911cd.net/forums//index.php?showtopic=23553
karyonix - http://reboot.pro/8804/page__st__400__p__121737#entry121737
karyonix - http://reboot.pro/13967/
In case of a hidden boot partition containing Boot folder and file bootmgr of Windows 7,
then Grub4dos Boot menu for Install of XP in VHD can be made by using USB-Stick as Target Boot Drive.
Grub4dos Menu for Install of XP in VHD by using XP Setup ISO file and WinVBlock driver
After Install of XP then you need to fix XP-1.vhd for booting from USB-drive by using USB_XP_Fix.exe
The fix will prevent BSOD 7B and will help to allow the XP VHD to boot on various hardware and so become Universal.
menu.lst on USB drive
title XP-2.vhd - WinVBlock FILEDISK - 2000 MB
# Sector-mapped disk
map /XP-2.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
title XP-2.vhd - WinVBlock RAMDISK - 2000 MB
# Sector-mapped disk
map --mem /XP-2.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
================================================================================
Wait4UFD driver Enables Direct Install of XP in VHD on USB
Advantage of Direct Install of XP is that one does not need to make changes in the booting of the local harddisk,
where changes might be unwanted or difficult as in the case of a hidden Boot Manager partition e.g. Windows 7
First XP Setup ISO file was prepared as described in Section 2 here
DPsBase.exe was used to Integrate DriverPacks Chipset + Processor + MassStorage + LAN + WLAN
(settings Disc - Method 2 - GuiRunOnce - Enable KTD for the DriverPacks I will Select C+P+M+L)
http://reboot.pro/topic/18107-integratedrv...it/#entry167235
1. IntegrateDrv was used to integrate Wait4UFD driver in the XP Setup Source directory containing folder i386
2. ImgBurn was used to make new XP Setup ISO file, that was copied to NTFS formatted active partition of USB-harddisk
3. VHD_XP_Create.exe was used to make 2 GB NTFS VHD on USB and to make Grub4dos Menu for WinVBlock driver
4. Boot with Grub4dos Menu from USB and Install XP in VHD using Start TXT-mode / Continue GUI-mode / Boot Windows XP VHD
5. After Install of XP then Run USB_XP_Fix.exe and Select your XP-1.vhd file on USB-drive and click GO
to make XP Universal for booting from USB connected to any computer.
================================================================================
2. How to prepare XP Setup Source ? - Prepare XP Setup ISO file with integrated UpdatePack and DriverPacks
Take care that your XPSOURCE Folder is located on your Harddisk in a simple Path without SPACES.
Copy the Content of your Windows XP Setup CD to your XPSOURCE Folder on Harddisk
First Integrate ServicePack SP3 in your XP-SP2 Source (don't use here nLite).
http://www.helpwithwindows.com/WindowsXP/S...ice_Pack_3.html
Download from - http://www.microsoft.com/download/en/detai...ng=en&id=24
In Command Window use for English version and XPSOURCE folder on drive E:
Siginet's RyanVM Integrator 1.6 can then be used to Integrate Windows UpdatePacks in the XP-Source.
http://integrator.siginetsoftware.com/index.php?download
Download preferred version RVM Integrator 1.6.1 Beta 2.1 - http://www.mediafire.com/?ynajonymmnz
Windows XP UpdatePacks and Addons:
Onepiece XP Post-SP3 AIO Update Pack FINAL - http://www.ryanvm.net/forum/viewtopic.php?t=6438
Onepiece XP Post-SP3 AIO International Update Packs FINAL - http://www.ryanvm.net/forum/viewtopic.php?t=10445
Dutch Update Pack - http://www.ryanvm.net/forum/viewtopic.php?t=8428
RyanVM Forum - http://www.ryanvm.net/forum/
For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE DriverPack Massstorage with TXT Mode Enabled.
http://driverpacks.net/downloads
In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated which appear in the
XP Setup BootFolder $WIN_NT$.~BT on Install-Drive and can prevent a lot of XP Install Boot Problems.
Use DPsBase.exe to Integrate DriverPacks Chipset + Processor + MassStorage + LAN + WLAN DriverPacks
which will then be located in OEM Folder in your XPSOURCE folder.
(settings Disc - Method 2 - GuiRunOnce - Enable KTD for the DriverPacks I will Select)
Always first use RyanVM Integrator and then use DPsBase to Improve your XP-Source
DPsBase makes presetup.cmd in folder I386 and changes the I386\winnt.sif file for use of DriverPacks
presetup.cmd in folder I386 will start decompression of DriverPacks located in OEM folder
at the beginning of GUI-mode of XP Setup, which does NOT take to much time for the 5 DriverPacks
You should select to Keep The Drivers for Chipset + Processor + MassStorage + LAN
Then WINDOWS\DriverPacks is about 135 MB which is acceptable and provides a lot of extra driver support
which is useful to make XP Universal and adapt easily to very different hardware.
In that case the DevicePath is set accordingly in key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
so that XP can automatically make use of these drivers for adjusting to New Hardware
When you don't use nLite, you can copy the supplied $OEM$ folder to your XP Source folder
Change $OEM$ folder to your needs for UserAccounts and Registry Tweaks and Adding Drivers
CMDLINES.TXT is used for making UserAccounts and install of Registry Tweaks at T-12
Info see: http://unattended.msfn.org/unattended.xp/
Use DriverForge.v4.5.4.exe to Install from C:\Drivers at T-9 of GUI XP Setup (just for the last Reboot).
DriverForge.v4.5.4.exe was made by kickarse http://www.msfn.org/board/index.php?showtopic=110783
At end of TXT-mode XP Setup the folder $OEM$\$1\Drivers is copied to C:\Drivers
and $OEM$\$1\Install\DriverForge.v4.5.4.exe is copied to C:\Install
For Auto Use of DriverForge at T-9 add uncompressed driver folders in $OEM$\$1\Drivers
and Uncomment two rules by removing ; in winnt.sif file copied from winnt_sif to your I386 folder
This is very useful for Install of your well known Audio and Video driver during GUI-mode of XP Setup.
[SetupParams]
UserExecute = "%SystemDrive%\INSTALL\SetupPar.cmd"
Next alinea is not needed when DriverPacks are integrated as described above but given here as useful info.
PnP Drivers specified in winnt.sif can be added to $OEM$\$1\Drivers
http://unattended.msfn.org/unattended.xp/view/web/34/
TEXTMODE Drivers defined in winnt.sif and located in $OEM$\TEXTMODE folder of the XP Source
can be used instead of using F6 floppy for MassStorage Drivers.
The content of the $OEM$\TEXTMODE folder is copied to XP Setup BootFolder $WIN_NT$.~BT\$OEM$
See cdob and allanf in http://reboot.pro/topic/5306-install-xp-fr...ge-8#entry63133
Smart Driver Backup 2.12 of Jaque is very useful to Backup your drivers before install of XP
http://www.911cd.net/forums//index.php?showtopic=20555
================================================================================
How to make XP Setup ISO File ?
- Use BBIE (see below) or Isobuster to Extract Boot Image bootsect.bin from Original bootable XP Setup CD
bbie will make image1.bin that you can copy as bootsect.bin to XP Setup source folder
- Reduce Size of XP Setup Source folder (if needed to fit on CD then remove folders LANG WIN9XMIG WIN9XUPG)
- Use ImgBurn and bootsect.bin to make Bootable CD
1. Remove 3 folders LANG WIN9XMIG WIN9XUPG - reduction in size = 135 MB
2. Run ImgBurn - Portable Tool in PStart Menu - IMG_XP\MULTI\PStart\Progs\ImgBurn
- Select Write files/folders to disc
- Output - Select Image File
- Browse Source folder and Select your XP Setup Source folder
- Browse Destination file - Give Name e.g. XP-Setup.iso
- Labels ISO 9660 - Give Name e.g. XP-Setup
- Advanced Restrictions - ISO9660 - Select Level X and DOS CharSet with 4x Checkbox On (allow ...)
- Bootable Disc - Make Image bootable - Checkbox On - Browse Boot Image - Select bootsect.bin file
- Bootable Disc - Emulation Type = None
Load Segment = 07C0
Sectors to Load = 4
BOOT_USB\makebt>bbie M:\XP3_1201.iso
BBIE - Bart's Boot Image Extractor v1.0, © 2001, Bart Lagerweij
http://www.nu2.nu
will make BOOT_USB\makebt\image1.bin that you can rename as bootsect.bin
================================================================================
POST_FIX Tools for XP - Readme
You can use DriverForge.v4.5.4.exe to Install any missing driver (e.g. video audio or WLAN)
by selecting Path to Uncompressed Driver Files e.g. S:\D
In that case DevicePath in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
is set to what DriverForge needs.
It means that any previous settings are lost e.g. for making use of the KTP C:\WINDOWS\DriverPacks store.
If you have selected in DPsBase.exe to Keep The Drivers by using KTP Option,
then after using DriverForge you need to run DevicePath_Reset_KTP.reg to Reset DevicePath to the KTD settings.
================================================================================
If you have Installed XP on AMD machine and then boot XP Image file on Intel machine,
then intelppm Service will have Start=1 value, which will give BSOD 7 E when booting on AMD machine.
This problem can be overcome by running the intelppm_Start3.reg registry tweak.
In that case intelppm Service will get Start=3 and everything will be OK for AMD and Intel.
================================================================================
Post Install Add DriverPacks to XP:
1. Boot with Universal XP Image file
2. Extract 3 DriverPacks to C:\ e.g. Chipset + CPU + MassStorage - will give C:\D folder
3. Use R-mouse to Open command prompt at C:\POST_FIX and run command
DevicePath in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
is set to subfolders of C:\D
================================================================================
Portable Windows HD Image files booting from USB
================================================================================
The Apps VHD_XP_Compact.exe and VHD_W7_Compact.exe of IMG_XP package
can be used to make Portable Windows VHD Image files booting with Grub4dos Menu on HDD or USB
These Virtual Harddisk VHD files require WinVBlock or FiraDisk driver to boot them as FILEDISK or as RAMDISK
The Ultimate Windows 7 VHD files make use of Microsoft VHD HBA driver which allows to boot them as FILEDISK
Target Boot Drive can be FAT32 or NTFS USB-drive used only for Boot files so that booting of internal harrddisk is NOT changed.
Target System Drive must be NTFS and is the drive where the VHD file is created and this can be your internal harddisk drive.
Booting from USB on computers with UEFI-firmware requires that the Boot Drive has FAT32 format.
Possible Scenario's
- Boot with Grub4dos Menu on NTFS or FAT32 USB-Stick with VHD located on NTFS Drive of Internal Harddisk
- Boot with Portable USB-harddisk and launch VHD located on NTFS System Drive of USB-Harddisk
Booting VHD files from Grub4dos Menu as FILEDISK or as RAMDISK requires to Install in Source VHD either FiraDisk Or WinVBlock driver.
Additinally Installed Programs and Drivers and Settings are remembered in FILEDISK just like in normal Windows OS.
Loading the VHD into RAMDISK is much faster when the VHD file is located on the internal NTFS harddisk drive.
Source can be drive where Windows is installed or full XP VHD file Or Windows 7 VHD file
In case of using existing Installed XP as source, it is handy to first create a NEW user in XP,
so that this NEW user folder is small in size e.g. only contains very few Documents and Pictures.
Also Install either WinVBlock or FiraDisk driver:
- Install WinVBlock driver see - IMG_XP\Help_Info\WinVBlock_Install.txt
- Install FiraDisk driver with R-mouse on firadisk.inf in IMG_XP\makebt\firadisk-driver- folder
Reduce size and connect USB-harddisk as described in point 5 and 6 given above
to get rid of pagefile.sys and hiberfil.sys and to get USB-HDD settings are known in XP registry
After booting with other OS e.g. Portable 7 PE, then you can run VHD_XP_Compact.exe and Select the NEW user
to make XP Image file that can boot from grub4dos menu on HDD or USB
Mini XP = OS Size 200 MB - including WLAN + Audio + Printer + 7-Zip + ImDisk and all installed drivers
Port XP = OS Size 600 MB - extra system32 complete + Windows Media Player - Multimedia support
In case of Mini XP then external VLC portable player can be used for MultiMedia support
Advised size of XP Image file is 1.2 GB and for Windows 7 VHD file is 2.0 GB.
==
Grub4dos Menu for Win7-1.vhd and using FiraDisk driver
================================================================================
3. Boot Win7 VHD Image file from USB
- Direct Install Windows 7 in a VHD file on local harddisk created by WinNTSetup2_x86.exe with Ctrl + Shift + V
- Copy Win7 VHD file to USB and use USB_W7_Fix.exe to fix for booting from USB-drive
- Make Boot Manager menu on USB for Win7 VHD Image file
Thanks to JFX for creating the very handy WinNTSetup2 tool to Install Windows 2k/XP/2003/Vista/7 x86/x64
Info in folder IMG_XP\WinNTSetup2_x86_x64 and here http://www.msfn.org/board/topic/149612-winntsetup-v2/
WARNING: Boot menu of your computer and your USB-drive will change needed for booting with Win7 VHD file.
WinNTSetup2_x86.exe will create or change Boot Manager menu (folder Boot and file bootmgr)
Details of Procedure to create Win7 VHD file for booting from USB-drive
1. Boot with Windows 7 or 7PE
2. Use R-mouse menu to Mount Windows 7 Setup ISO file in ImDisk virtual drive (if needed first Install imdiskinst.exe)
3. Run WinNTSetup2_x86.exe and use Ctrl + Shift + V to create Win7 VHD file on local Harddisk (or use Disk Management)
4. In WinNTSetup2_x86.exe adjust Windows 7 Tweaks and Select install.wim and Bootdrive and your attached Win7 VHD
Select all System-Only Tweaks except Turn OFF USB and select other tweaks that you like
Select Checkbox to Mount Installation drive as C:
5. Use Setup to prepare Win7 VHD file and Boot drive menu and Reboot to Start Install of Windows 7
6. Reboot 2x with Win7 VHD to finish Install of Windows 7 in VHD
7. Set System Restore and UserAccount Control Off and Reduce Size
e.g. Change settings to get rid of pagefile.sys and hiberfil.sys
No pagefile.sys - Run as Administrator in cmd window: sysdm.cpl
and Change Advanced Performance Virtual memory Settings - Set to use No paging file
No hiberfil.sys - Run as Administrator in cmd window: powercfg.exe -H off
- Install missing Drivers but NOT the specific large Video driver
8. Install anything you need like ImDisk and 7Zip and connect your USB-harddisk to Update registry
Use Computer Properties and Set System Protection for Win7 VHD drive Off and Reboot Win7 VHD
9. Reboot with Windows 7 or 7 PE
10. Copy Win7 VHD to bootable USB-drive and use Disk Management to Attach Win 7 VHD located on USB
11. Open cmd prompt and create Boot Manager menu on USB-drive by running
where N: is your attached Win7 VHD and P: is your USB-drive
12. In Disk Management Detach Win7 VHD
13. If your USB-drive was NOT formatted in Windows 7 OS, then you need to fix the Bootsector of USB-drive P: with
14. Run USB_W7_Fix.exe of IMG_XP package to fix the registry of Win7 VHD file on USB
15. Reboot with Win7 VHD from USB
Instead of points 9-14 you can make use of VHD_W7_Compact.exe to make Portable Windows 7 VHD file of 2 GB booting from USB-harddisk.
Procedure for booting with 2 GB Portable Windows 7 VHD file on USB-harddisk
Step 1. - Direct Install Windows 7 in a 10 GB VHD file on local harddisk and created by WinNTSetup2_x86.exe with Ctrl + Shift + V
Step 2. - Run VHD_W7_Compact.exe to Copy Win7 VHD content in 10 min to New VHD file of Reduced Size on USB-harddisk
Step 3. - Reboot with 2 GB Win7 VHD file from USB
On Running VHD_W7_Compact.exe you need to Select your User Folder in folder Users of the Win7 VHD Source file
The program takes care of Attach and Detach of VHD files by using diskpart.exe of your Windows 7 or 7 PE Operating System.
The program is suitable for 32-bits Windows 7 and was tested with en-US Ultimate version,
but may work with other distributions as well.
VHD_W7_Compact.exe - makes 2.0 GB Win7 VHD file for booting from USB-harddisk
================================================================================
4. Universal Image Create and Restore - Details
- Win_Restore.exe for Restore on USB drive takes care of:
USB Services get "Group"="Boot Bus Extender" and Start=0 to prevent BSOD 7B
UsbBootWatcher.exe and UsbBootWatcher.conf are copied to USB-HDD\WINDOWS\system32 directory.
Thanks to marv and cdob for describing effect of Driver Group and Start value to prevent BSOD 7B in booting XP from USB.
http://www.911cd.net/forums//index.php?showtopic=22473
IMG_XP\makebt\registry_tweaks\HKLM_systemdst_USB_XP.reg - Added to SYSTEM registry for Restore on USB drive
IMG_XP\makebt\registry_tweaks\HKLM_systemdst_BOOT_HDD.reg - Added to SYSTEM registry for Restore on HDD drive
In all cases of Restore the DiskSignature 4 bytes in MBR at hex offset 1B8 must be taken into account:
Value of \DosDevices\C: in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices on Target Drive is set according to DiskSignature.
All other values in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices on Target Drive are deleted.
More Info on DiskSignature http://thestarman.pcministry.com/asm/mbr/index.html
User can add extra registry tweaks
to HKLM_systemdst_Add.reg or HKLM_softwaredst_Add.reg in IMG_XP\makebt\registry_tweaks folder,
which will be added in Restore to the WINDOWS\system32\config\SYSTEM and the SOFTWARE registry files on Target drive.
IMG_XP\makebt\registry_tweaks\HKLM_systemdst_Add_XP.reg - used by HKLM System CheckBox
IMG_XP\makebt\registry_tweaks\HKLM_softwaredst_Add.reg - used by HKLM Software CheckBox
Windows Registry Editor Version 5.00
;------------------------------------------------------------------------------------------------------------
; SuppressNewHWUI - Suppress popup of Wizard New Hardware found, so that Universal OS can continue recognizing New Hardware
;------------------------------------------------------------------------------------------------------------
[HKEY_LOCAL_MACHINE\softwaredst\Policies\Microsoft\Windows\DeviceInstall\Settings]
"SuppressNewHWUI"=dword:00000001
;------------------------------------------------------------------------------------------------------------
; Diable SystemRestore
;------------------------------------------------------------------------------------------------------------
[HKEY_LOCAL_MACHINE\softwaredst\Microsoft\Windows Nt\CurrentVersion\SystemRestore]
"DisableSR"=dword:00000001
;------------------------------------------------------------------------------------------------------------
; Disable Automatic Windows Updates - Notify Only, No download
;------------------------------------------------------------------------------------------------------------
; [HKEY_LOCAL_MACHINE\softwaredst\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
; "AUOptions"=dword:00000002
;------------------------------------------------------------------------------------------------------------
; Win7 Search drivers via WindowsUpdate - Auto Install of some missing drivers
[HKEY_LOCAL_MACHINE\softwaredst\Microsoft\Windows\CurrentVersion\Device Metadata]
"PreventDeviceMetadataFromNetwork"=dword:00000000
[HKEY_LOCAL_MACHINE\softwaredst\Microsoft\Windows\CurrentVersion\DriverSearching]
"SearchOrderConfig"=dword:00000001
; Disable WindowsUpdate
[HKEY_LOCAL_MACHINE\softwaredst\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
"AUOptions"=dword:00000001
After Install of Windows 7 on system with BIOS SATA = IDE Controller, then the msahci Service has Start = 3.
Subsequent booting from USB-HD with msahci Start=3 on system with BIOS SATA = AHCI controller results in BSOD 7B.
The msahci tweak to set Start = 0 has been added to HKLM_systemdst_iaStor.reg used by Add iaStor - AHCI CheckBox.
This is needed to prevent BSOD 7B in Restore of Windows 7 for support of BIOS with SATA = AHCI controller setting.
http://support.microsoft.com/kb/922976/en-us
Adding iaStor driver prevents BSOD 7B on booting from USB-HDD on other computer systems.
Copy iaStor.sys to C:\WINDOWS\system32\drivers and iaStor.inf + iaAHCI.inf to C:\WINDOWS\inf
Copy iaStor.cat + iaAHCI.cat to your CatRoot folder C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
download the latest version of the Intel Matrix Storage Manager from http://downloadcenter.intel.com/Product_Fi...01&lang=eng
More Info on adding iaStor driver to SYSTEM registry - http://forums.pcper.com/showthread.php?t=444831
http://www.msfn.org/board/enable-ahci-inte...xp-t109450.html
Win_Restore.exe has Add iaStor - AHCI CheckBox to take care of the above and
IMG_XP\makebt\registry_tweaks\HKLM_systemdst_iaStor.reg registry tweak is added to the WINDOWS\system32\config\SYSTEM registry file on Target drive
so that HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase contains the required PCI device values.
IMG_XP\makebt\registry_tweaks\HKLM_systemdst_iaStor.reg - used by Add iaStor - AHCI CheckBox
Besides the already existing option to Add iaStor Driver, there is additional possibility to add other drivers
by dropping them previously in the corresponding IMG_XP\makebt\drivers folder.
Registry Tweaks used for Win7 instead of those for XP are
HKLM_systemdst_Add_W7.reg and HKLM_systemdst_USB_W7.reg
Additionally for Install of Windows 7 on USB-HDD primary partition with DriveLetter U:
On booting from USB this USB-HDD partition will automatically get drive letter C:
http://www.multibootersno.no.genius/cloning.html
For making correct Windows 7 entry in BCD store of BOOTMGR menu it is essential that Windows 7 was set as the default option.
================================================================================
5. Solutions to prevent BSOD 7B - Run USB_XP_Fix.exe
It is often possible to prevent BSOD 7B without using any delay driver like waitbt.sys or DriveGuard ubdrvgd.sys driver.
USB_XP_Fix.exe was improved such that the CriticalDeviceDatabase registry has all entries for IDE Controller and USB Controller Services
and that all IDE and USB Controller drivers if missing are extracted previously from the XP driver.cab file.
The CriticalDeviceDatabase registry of Windows 7 has much more entries as compared to XP.
IDE ATA\ATAPI Controller has ClassGuid={4D36E96A-E325-11CE-BFC1-08002BE10318} with entries in mshdc.inf
USB Controller has ClassGUID={36FC9E60-C465-11CF-8056-444553540000} with entries in usbport.inf and usbstor.inf and usb.inf
CriticalDeviceDatabase registry of XP is now improved and comparable with Windows 7 by adding
all entries for Control Class {4D36E96A-E325-11CE-BFC1-08002BE10318} and {36FC9E60-C465-11CF-8056-444553540000}
These CDDB entries arre added in folder makebt\registry_tweaks in files HKLM_systemdst_Add_XP.reg and HKLM_systemdst_USB_XP.reg
To be Universal for a lot of hardware it is also necessary to have the WINDOWS\DriverPacks folder available with Chipset + Processor + MassStorage drivers.
In that way you provide support for another important Controller Class, the SCSI- en RAID-controllers
Class=SCSIAdapter has ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
So there are two measures that make XP behave more like Windows 7 and will allow booting on all hardware:
1. improved CriticalDeviceDatabase registry with IDE Controller and USB Controller entries
combined with the built in IDE Controller drivers made readily available (unpacked from driver.cab)
2. WINDOWS\DriverPacks store with subfolder M (MassStorage) for support for SCSI- en RAID-controllers
USB_XP_Fix.exe has Checkboxes to add Intel iaStor.sys driver and AMD ahcix86.sys AHCI driver with their CriticalDeviceDatabase entries
Intel iaStor.sys is IDE Controller (iaAHCI.inf for Intel AHCI Controller) with entries ending on cc_0106
iaStor.sys can be RAID Controller (iaStor.inf for Intel RAID Controller) with entries ending on cc_0104
In general one can say that missing (or slow access to) Controller drivers are the reason for BSOD 7B
IDE ATA\ATAPI Controller has ClassGuid={4D36E96A-E325-11CE-BFC1-08002BE10318} with entries in mshdc.inf
USB Controller has ClassGUID={36FC9E60-C465-11CF-8056-444553540000} with entries in usbport.inf and usbstor.inf and usb.inf
SCSI- en RAID-controllers has ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318} mainly supported via MassStorage DriverPack
In case of any boot problem, then always run SaveHwids.exe and post the Hwids of your machine,
so that we can try to solve the boot problem by adding CriticalDeviceDatabase registry entries combined with suitable drivers.
If you did not use the advised Keep The Drivers Option KTD when integrating DriverPacks in your XP Setup Source with DPsBase.exe
then you can later add to your Image the WINDOWS\DriverPacks folder with subfolders C and CPU and M of extracted DriverPacks.
Also after using DriverForge then any previous settings are lost e.g. for making use of the KTP C:\WINDOWS\DriverPacks store.
After booting with XP Image you can run POST_FIX\DevicePath_Reset_KTP.reg to Reset DevicePath to the KTD settings
Additionally the Environment value of KTD must be set as C:\WINDOWS\DriverPacks by using KTD_C_WIN_DP.reg
Alternatively you can use this method:
Post Install Add DriverPacks:
1. Boot with Universal XP Image file
2. Extract 3 DriverPacks to C:\ e.g. Chipset + CPU + MassStorage - will give C:\D folder
3. Use R-mouse to Open command prompt at C:\POST_FIX and run command
DevicePath in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
is set to subfolders of C:\D
USBoot DriveGuard driver is probably unneeded to prevent BSOD 7B since recent USB_XP_Fix.exe will Fix XP and Install waitbt.sys driver.
If you still have problem then Install USBoot DriveGuard driver ubdrvgd.sys to prevent BSOD 7B in booting from USB
- Download USBoot from http://usboot.org/tiki-index.php
- Extract the package, right click on ubdrvgd.inf, click on Install
- the XP boot message - DriveGuard Initialization failed - has No effect, the driver works OK
- More Info http://reboot.pro/9830/page__st__800#entry160006
- DriveGuard driver ubdrvgd.sys is installed as LowerFilters between the main driver and the hardware
================================================================================
6. Universal XP - Support in boot.ini menu for Multiple Hal and Kernel
The boot.ini menu of XP can be used to select on the fly which hal and kernel file will be used for booting.
In this way one can support booting with the same Universal Image file on computers having quite different hardware.
http://www.vernalex.com/guides/sysprep/hal.shtml
http://www.etherboot.org/wiki/appnotes/port_winnt_sanboot
The method described above is improved and used in VHD_XP_Compact.exe and Win_Restore.exe
Default XP boots by boot.ini entry LAST CONFIG with the files hal.dll and ntoskrnl.exe and ntkrnlpa.exe
The boot.ini switches /hal and /kernel will copy the in boot.ini named switchfiles and on the fly overwrite hal.dll and ntoskrnl.exe
At the same time the kernel name (max=6 letters) plus pa .exe file is used to overwrite ntkrnlpa.exe
A set of 7 hal files and 4 kernel files in folder halkern is generated from the XP Setup Source provided by user.
The hal and kernel files are extracted in priority from sp3.cab or sp2.cab or driver.cab (used by RVM Integrator) e.g. as
In folder halkern we rename:
In this way folder halkern contains 7 hal and 4 kernel files:
VHD_XP_Compact.exe and Win_Restore.exe will copy the files of the halkern folder to Image folder WINDOWS\system32
Multiprocessor = MP and Uniprocessor = UP
boot.ini file with Multiple Hal and Kernel for making Universal XP
================================================================================
- Win_Restore.exe can be used to Restore XP or Win7 from VHD to HDD-partition.
For Restore of Win7 from VHD you need to run Win_Restore.exe in Win 7/8/7PE OS
so that bcdboot.exe can be used to generate Boot Manager Menu required to boot Win 7 from HDD-partition.
- BOOT_IMG makes GRUB4DOS Menu on Target Boot Drive for selected VHD File on NTFS Target System Drive (copy occurs if needed).
- IMG_XP_Update.exe is used after booting with XP Image file from RAMDISK, to Update the Image file that you just booted from.
Boot with full XP Image file in RAMDISK and Update Drivers using DriverForge with Drivers folder that you supply.
Then run IMG_XP_Update.exe to improve full XP Image file in 1 minute with drivers for New Hardware.
- Most computers nowadays are ACPI Multiprocessor PC and we can use the corresponding HAL.
If you need for XP to support old computers using a different HAL then you can use Add Hal and Kernel files and
let modify by IMG_XP programs your boot.ini as described in Section 6.
http://www.vernalex.com/guides/sysprep/hal.shtml
http://www.etherboot.org/wiki/appnotes/port_winnt_sanboot
In general ImDisk must be installed in XP or Win 7/8 by using previously the provided imdiskinst.exe file.
ImDisk is used to mount VHD Image file in a virtual drive.
To Install ImDisk driver on Vista and Windows 7/8 you need to turn off UAC, User Account Control
http://www.ltr-data.se/opencode.html
The 64-bit FiraDisk driver requires in x64 Win7 to set testsigning switched on.
Open Command Prompt as Administrator:
Reboot to activate this.
http://msdn.microsoft.com/en-us/library/dd419910.aspx
Thanks to karyonix, more Info see:
FiraDisk - http://reboot.pro/index.php?showtopic=8804
Install FiraDisk driver in XP with R-mouse on firadisk.inf in IMG_XP\makebt\firadisk-driver- folder
Forum FiraDisk - http://reboot.pro/index.php?showforum=94
Windows 7 - http://reboot.pro/index.php?showforum=77
Windows 7 on USB-HDD - http://reboot.pro/index.php?showtopic=9196
Thanks to jaclaz for pointing me to strarc.exe of Olof Lagerkvist ,
which is used in IMG_XP_Update.exe to Update the XP Image File on HDD after booting from RAMDISK.
Updating Registry and Drivers in Image file is done in only 5 sec, a Total Update of the Image requires 1 min.
___________________________________________
Need More Detail ? contact me !!
I sell a lot of stuff, program. knowledge, etc.. at a small cost.
I will guide you step by step, personally.
My Paypal Account is : ksw.industries@gmail.com
Don't know how to send money ? Click here for detail about Paypal account.
http://xyberpast.blogspot.com/2014/05/how-to-get-my-program.html
Don't have money? OK! Here is another way to get the program.
how to get my program - Free of charge
*** IMG_XP package ***
Make XP and Win7 Universal Image files booting with Grub4dos Menu on HDD or USB
================================================================================
Download - IMG_XP_85 - mirror
In Win7 OS Set User Account Control Off and Reboot
1. VHD_XP_Create.exe - Make VHD file and Install XP in VHD by using Grub4dos Boot Menu on HDD
First Prepare XP Setup ISO file with integrated UpdatePack and DriverPacks as described below in Section 2
and Copy XP Setup ISO file to the root of internal harddisk drive of your computer.
-
 Reduced 35%
406 x 462 (23.51K)
|
0. Run IMG_XP.exe and Extract to simple path on your Local Harddisk - gives folder IMG_XP
1. Use IMX_XP\makebt\imdiskinst.exe to Install ImDisk driver (if not present)
- Imdisk is used by USB_XP_Fix.exe to mount VHD and HDD Image files in a virtual drive
2. Run VHD_XP_Create.exe to create XP-1.vhd and Grub4dos Boot Menu for Install of XP in VHD
- Boot Drive - FAT32 or NTFS - can be USB-stick so that there are no changes needed in the Windows installation on the internal harddisk
- System Drive - NTFS - where VHD file is created e.g your internal harddisk drive
- XP Setup ISO file - located on internal harddisk drive so that fast loading into RAM is enabled
3. Reboot and in Grub4dos menu select Start XP Setup on XP-1.vhd - WinVBlock driver
- XP-1.vhd has already NTFS compressed format, so you should NOT format at Setup, just keep settings
- Format XP-1.img inside XP Setup cannot be used, it results in corrupt message
4. After Reboot select Continue XP Setup and then Reboot to Start XP from Image XP-1.vhd
5. Reduce size and improve settings as usual and Install missing Drivers but NOT the specific large Video driver
Reduce size to get rid of pagefile.sys and hiberfil.sys via:
- right click My Computer > select Properties > Advanced > Change Virtual memory > select No pagefile and Set
- right click on Desktop > Screen Protection > Energy > Uncheck Sleep settings to get rid of hiberfil.sys
- Set System Restore and Windows Update Off and delete 350 MB of dllcache folder via cmd SFC /purgecache (or Run PURGE_DLLCACHE.BAT)
- For Universal XP don't Install the Video driver. You can Uninstall the Video driver so that you still have high resolution on any hardware.
- Set Screen Resolution to 1024 x 768 useful on all monitors (right click on Desktop)
6. USBoot DriveGuard driver is probably unneeded to prevent BSOD 7B since recent USB_XP_Fix.exe will Fix XP and Install waitbt.sys driver.
Skip this step Or Install USBoot DriveGuard driver ubdrvgd.sys to prevent BSOD 7B in booting from USB
- Download USBoot from http://usboot.org/tiki-index.php
- Extract the package, right click on ubdrvgd.inf, click on Install
- the XP boot message - DriveGuard Initialization failed - has No effect, the driver works OK
- More Info http://reboot.pro/9830/page__st__800#entry160006
- DriveGuard driver ubdrvgd.sys is installed as LowerFilters between the main driver and the hardware
7. Connect USB-HDD where you want to use XP Image, so that USB-HDD settings are known in XP registry, and Reboot
8. Reboot with other OS and copy XP-1.vhd to bootable USB-drive and create entry in Grub4dos menu.lst
- BOOT_USB.exe can be used to make USB-drive bootable with Grub4dos Menu
- BOOT_IMG.exe can be used to make Grub4dos Boot Menu on existing bootable drives
9. Run USB_XP_Fix.exe and Select your XP-1.vhd file on USB-drive and click GO
10. Reboot from USB on the same computer and Select Boot XP Image - XP-1.vhd - WinVBlock FILEDISK
11. Reboot from USB on other computers and Select Boot XP Image - XP-1.vhd - WinVBlock FILEDISK - to make Universal
When booting on other unknown machine, then XP will auto adjust itself in about 3 min and install the required drivers.
In this learning process, the registry gets extra info on how to boot on that machine and will use it next time and so XP becomes Universal.
This process requires that you have the WINDOWS\DriverPacks folder of 135 MB available with Chipset + Processor + MassStorage + LAN drivers
and that DevicePath in the registry was properly set by the Keep The Drivers Option KTD (see below and in Picture).
If you have Installed XP in VHD on AMD machine and then boot XP Image file first time on Intel machine,
then intelppm Service will have Start=1 value, which will give BSOD 7 E when booting again on AMD machine.
This problem can be overcome by running the intelppm_Start3.reg registry tweak from POST_FIX folder.
In that case intelppm Service will get Start=3 and everything will be OK all the time for AMD and Intel.
Thanks to Sha0 for making WinVBlock driver - http://reboot.pro/8168/
Thanks to cdob for making usb_xp_init.cmd - http://www.911cd.net/forums//index.php?sho...22473&st=37
Thanks to sara - pmedia for her tutorial - http://reboot.pro/13731/
More Info on direct Install of XP by using grub4dos menu and WinVBlock or FiraDisk driver:
cdob - Install XP from a ISO file No RAM disk - http://www.msfn.org/board/topic/149675-ins...rom-a-iso-file/
Doodoo - http://reboot.pro/13856/page__p__122385#entry122385
sara - pnedia - http://reboot.pro/13731/
wimb - http://www.911cd.net/forums//index.php?showtopic=23553
karyonix - http://reboot.pro/8804/page__st__400__p__121737#entry121737
karyonix - http://reboot.pro/13967/
In case of a hidden boot partition containing Boot folder and file bootmgr of Windows 7,
then Grub4dos Boot menu for Install of XP in VHD can be made by using USB-Stick as Target Boot Drive.
Grub4dos Menu for Install of XP in VHD by using XP Setup ISO file and WinVBlock driver
CODE
title Continue GUI-mode XP Setup on XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP3_1210W.iso
map --mem /XP3_1210W.iso (0xff)
find --set-root --ignore-floppies /XP-1.vhd
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)
map /XP-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
title Start - TXT-mode XP Setup on XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP3_1210W.iso
map --mem /XP3_1210W.iso (0xff)
find --set-root --ignore-floppies /XP-1.vhd
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)
map /XP-1.vhd (hd0)
map --hook
chainloader (0xff)
title Boot Windows XP from Image - XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP-1.vhd
map /XP-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
find --set-root --ignore-floppies /XP3_1210W.iso
map --mem /XP3_1210W.iso (0xff)
find --set-root --ignore-floppies /XP-1.vhd
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)
map /XP-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
title Start - TXT-mode XP Setup on XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP3_1210W.iso
map --mem /XP3_1210W.iso (0xff)
find --set-root --ignore-floppies /XP-1.vhd
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)
map /XP-1.vhd (hd0)
map --hook
chainloader (0xff)
title Boot Windows XP from Image - XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP-1.vhd
map /XP-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
After Install of XP then you need to fix XP-1.vhd for booting from USB-drive by using USB_XP_Fix.exe
The fix will prevent BSOD 7B and will help to allow the XP VHD to boot on various hardware and so become Universal.
menu.lst on USB drive
CODE
title XP-2.vhd - WinVBlock FILEDISK - 2000 MB
# Sector-mapped disk
map /XP-2.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
title XP-2.vhd - WinVBlock RAMDISK - 2000 MB
# Sector-mapped disk
map --mem /XP-2.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr
================================================================================
Wait4UFD driver Enables Direct Install of XP in VHD on USB
Advantage of Direct Install of XP is that one does not need to make changes in the booting of the local harddisk,
where changes might be unwanted or difficult as in the case of a hidden Boot Manager partition e.g. Windows 7
First XP Setup ISO file was prepared as described in Section 2 here
DPsBase.exe was used to Integrate DriverPacks Chipset + Processor + MassStorage + LAN + WLAN
(settings Disc - Method 2 - GuiRunOnce - Enable KTD for the DriverPacks I will Select C+P+M+L)
http://reboot.pro/topic/18107-integratedrv...it/#entry167235
1. IntegrateDrv was used to integrate Wait4UFD driver in the XP Setup Source directory containing folder i386
2. ImgBurn was used to make new XP Setup ISO file, that was copied to NTFS formatted active partition of USB-harddisk
3. VHD_XP_Create.exe was used to make 2 GB NTFS VHD on USB and to make Grub4dos Menu for WinVBlock driver
4. Boot with Grub4dos Menu from USB and Install XP in VHD using Start TXT-mode / Continue GUI-mode / Boot Windows XP VHD
5. After Install of XP then Run USB_XP_Fix.exe and Select your XP-1.vhd file on USB-drive and click GO
to make XP Universal for booting from USB connected to any computer.
================================================================================
2. How to prepare XP Setup Source ? - Prepare XP Setup ISO file with integrated UpdatePack and DriverPacks
Take care that your XPSOURCE Folder is located on your Harddisk in a simple Path without SPACES.
Copy the Content of your Windows XP Setup CD to your XPSOURCE Folder on Harddisk
First Integrate ServicePack SP3 in your XP-SP2 Source (don't use here nLite).
http://www.helpwithwindows.com/WindowsXP/S...ice_Pack_3.html
Download from - http://www.microsoft.com/download/en/detai...ng=en&id=24
In Command Window use for English version and XPSOURCE folder on drive E:
CODE
WindowsXP-KB936929-SP3-x86-ENU.exe /integrate:E:\XPSOURCE
Siginet's RyanVM Integrator 1.6 can then be used to Integrate Windows UpdatePacks in the XP-Source.
http://integrator.siginetsoftware.com/index.php?download
Download preferred version RVM Integrator 1.6.1 Beta 2.1 - http://www.mediafire.com/?ynajonymmnz
Windows XP UpdatePacks and Addons:
Onepiece XP Post-SP3 AIO Update Pack FINAL - http://www.ryanvm.net/forum/viewtopic.php?t=6438
Onepiece XP Post-SP3 AIO International Update Packs FINAL - http://www.ryanvm.net/forum/viewtopic.php?t=10445
Dutch Update Pack - http://www.ryanvm.net/forum/viewtopic.php?t=8428
RyanVM Forum - http://www.ryanvm.net/forum/
For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE DriverPack Massstorage with TXT Mode Enabled.
http://driverpacks.net/downloads
In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated which appear in the
XP Setup BootFolder $WIN_NT$.~BT on Install-Drive and can prevent a lot of XP Install Boot Problems.
Use DPsBase.exe to Integrate DriverPacks Chipset + Processor + MassStorage + LAN + WLAN DriverPacks
which will then be located in OEM Folder in your XPSOURCE folder.
(settings Disc - Method 2 - GuiRunOnce - Enable KTD for the DriverPacks I will Select)
Always first use RyanVM Integrator and then use DPsBase to Improve your XP-Source
DPsBase makes presetup.cmd in folder I386 and changes the I386\winnt.sif file for use of DriverPacks
presetup.cmd in folder I386 will start decompression of DriverPacks located in OEM folder
at the beginning of GUI-mode of XP Setup, which does NOT take to much time for the 5 DriverPacks
You should select to Keep The Drivers for Chipset + Processor + MassStorage + LAN
Then WINDOWS\DriverPacks is about 135 MB which is acceptable and provides a lot of extra driver support
which is useful to make XP Universal and adapt easily to very different hardware.
In that case the DevicePath is set accordingly in key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
so that XP can automatically make use of these drivers for adjusting to New Hardware
When you don't use nLite, you can copy the supplied $OEM$ folder to your XP Source folder
Change $OEM$ folder to your needs for UserAccounts and Registry Tweaks and Adding Drivers
CMDLINES.TXT is used for making UserAccounts and install of Registry Tweaks at T-12
Info see: http://unattended.msfn.org/unattended.xp/
Use DriverForge.v4.5.4.exe to Install from C:\Drivers at T-9 of GUI XP Setup (just for the last Reboot).
DriverForge.v4.5.4.exe was made by kickarse http://www.msfn.org/board/index.php?showtopic=110783
At end of TXT-mode XP Setup the folder $OEM$\$1\Drivers is copied to C:\Drivers
and $OEM$\$1\Install\DriverForge.v4.5.4.exe is copied to C:\Install
For Auto Use of DriverForge at T-9 add uncompressed driver folders in $OEM$\$1\Drivers
and Uncomment two rules by removing ; in winnt.sif file copied from winnt_sif to your I386 folder
This is very useful for Install of your well known Audio and Video driver during GUI-mode of XP Setup.
[SetupParams]
UserExecute = "%SystemDrive%\INSTALL\SetupPar.cmd"
Next alinea is not needed when DriverPacks are integrated as described above but given here as useful info.
PnP Drivers specified in winnt.sif can be added to $OEM$\$1\Drivers
http://unattended.msfn.org/unattended.xp/view/web/34/
TEXTMODE Drivers defined in winnt.sif and located in $OEM$\TEXTMODE folder of the XP Source
can be used instead of using F6 floppy for MassStorage Drivers.
The content of the $OEM$\TEXTMODE folder is copied to XP Setup BootFolder $WIN_NT$.~BT\$OEM$
See cdob and allanf in http://reboot.pro/topic/5306-install-xp-fr...ge-8#entry63133
Smart Driver Backup 2.12 of Jaque is very useful to Backup your drivers before install of XP
http://www.911cd.net/forums//index.php?showtopic=20555
================================================================================
How to make XP Setup ISO File ?
- Use BBIE (see below) or Isobuster to Extract Boot Image bootsect.bin from Original bootable XP Setup CD
bbie will make image1.bin that you can copy as bootsect.bin to XP Setup source folder
- Reduce Size of XP Setup Source folder (if needed to fit on CD then remove folders LANG WIN9XMIG WIN9XUPG)
- Use ImgBurn and bootsect.bin to make Bootable CD
1. Remove 3 folders LANG WIN9XMIG WIN9XUPG - reduction in size = 135 MB
2. Run ImgBurn - Portable Tool in PStart Menu - IMG_XP\MULTI\PStart\Progs\ImgBurn
- Select Write files/folders to disc
- Output - Select Image File
- Browse Source folder and Select your XP Setup Source folder
- Browse Destination file - Give Name e.g. XP-Setup.iso
- Labels ISO 9660 - Give Name e.g. XP-Setup
- Advanced Restrictions - ISO9660 - Select Level X and DOS CharSet with 4x Checkbox On (allow ...)
- Bootable Disc - Make Image bootable - Checkbox On - Browse Boot Image - Select bootsect.bin file
- Bootable Disc - Emulation Type = None
Load Segment = 07C0
Sectors to Load = 4
BOOT_USB\makebt>bbie M:\XP3_1201.iso
BBIE - Bart's Boot Image Extractor v1.0, © 2001, Bart Lagerweij
http://www.nu2.nu
will make BOOT_USB\makebt\image1.bin that you can rename as bootsect.bin
================================================================================
POST_FIX Tools for XP - Readme
You can use DriverForge.v4.5.4.exe to Install any missing driver (e.g. video audio or WLAN)
by selecting Path to Uncompressed Driver Files e.g. S:\D
In that case DevicePath in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
is set to what DriverForge needs.
It means that any previous settings are lost e.g. for making use of the KTP C:\WINDOWS\DriverPacks store.
If you have selected in DPsBase.exe to Keep The Drivers by using KTP Option,
then after using DriverForge you need to run DevicePath_Reset_KTP.reg to Reset DevicePath to the KTD settings.
================================================================================
If you have Installed XP on AMD machine and then boot XP Image file on Intel machine,
then intelppm Service will have Start=1 value, which will give BSOD 7 E when booting on AMD machine.
This problem can be overcome by running the intelppm_Start3.reg registry tweak.
In that case intelppm Service will get Start=3 and everything will be OK for AMD and Intel.
================================================================================
Post Install Add DriverPacks to XP:
1. Boot with Universal XP Image file
2. Extract 3 DriverPacks to C:\ e.g. Chipset + CPU + MassStorage - will give C:\D folder
3. Use R-mouse to Open command prompt at C:\POST_FIX and run command
CODE
DevPath.exe %SystemDrive%\D
DevicePath in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
is set to subfolders of C:\D
================================================================================
Portable Windows HD Image files booting from USB
================================================================================
The Apps VHD_XP_Compact.exe and VHD_W7_Compact.exe of IMG_XP package
can be used to make Portable Windows VHD Image files booting with Grub4dos Menu on HDD or USB
These Virtual Harddisk VHD files require WinVBlock or FiraDisk driver to boot them as FILEDISK or as RAMDISK
The Ultimate Windows 7 VHD files make use of Microsoft VHD HBA driver which allows to boot them as FILEDISK
Target Boot Drive can be FAT32 or NTFS USB-drive used only for Boot files so that booting of internal harrddisk is NOT changed.
Target System Drive must be NTFS and is the drive where the VHD file is created and this can be your internal harddisk drive.
Booting from USB on computers with UEFI-firmware requires that the Boot Drive has FAT32 format.
Possible Scenario's
- Boot with Grub4dos Menu on NTFS or FAT32 USB-Stick with VHD located on NTFS Drive of Internal Harddisk
- Boot with Portable USB-harddisk and launch VHD located on NTFS System Drive of USB-Harddisk
Booting VHD files from Grub4dos Menu as FILEDISK or as RAMDISK requires to Install in Source VHD either FiraDisk Or WinVBlock driver.
Additinally Installed Programs and Drivers and Settings are remembered in FILEDISK just like in normal Windows OS.
Loading the VHD into RAMDISK is much faster when the VHD file is located on the internal NTFS harddisk drive.
Source can be drive where Windows is installed or full XP VHD file Or Windows 7 VHD file
In case of using existing Installed XP as source, it is handy to first create a NEW user in XP,
so that this NEW user folder is small in size e.g. only contains very few Documents and Pictures.
Also Install either WinVBlock or FiraDisk driver:
- Install WinVBlock driver see - IMG_XP\Help_Info\WinVBlock_Install.txt
- Install FiraDisk driver with R-mouse on firadisk.inf in IMG_XP\makebt\firadisk-driver- folder
Reduce size and connect USB-harddisk as described in point 5 and 6 given above
to get rid of pagefile.sys and hiberfil.sys and to get USB-HDD settings are known in XP registry
After booting with other OS e.g. Portable 7 PE, then you can run VHD_XP_Compact.exe and Select the NEW user
to make XP Image file that can boot from grub4dos menu on HDD or USB
Mini XP = OS Size 200 MB - including WLAN + Audio + Printer + 7-Zip + ImDisk and all installed drivers
Port XP = OS Size 600 MB - extra system32 complete + Windows Media Player - Multimedia support
In case of Mini XP then external VLC portable player can be used for MultiMedia support
Advised size of XP Image file is 1.2 GB and for Windows 7 VHD file is 2.0 GB.
Reduced 42%
406 x 512 (26.99K)
|
Reduced 40%
406 x 494 (14.71K)
|
Grub4dos Menu for Win7-1.vhd and using FiraDisk driver
CODE
title Port Win7-1.vhd - FiraDisk FILEDISK - 2.0 GB
map --heads=2 --sectors-per-track=18 --mem (md)0x800+4 (99)
map /Win7-1.vhd (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=disk,vmem=find:/Win7-1.vhd,boot;\n\0
rootnoverify (hd0,0)
chainloader /bootmgr
map --status
pause Press any key . . .
title Port Win7-1.vhd - FiraDisk RAMDISK - 2.0 GB
find --set-root --ignore-floppies /Win7-1.vhd
map --mem /Win7-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr
map --heads=2 --sectors-per-track=18 --mem (md)0x800+4 (99)
map /Win7-1.vhd (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=disk,vmem=find:/Win7-1.vhd,boot;\n\0
rootnoverify (hd0,0)
chainloader /bootmgr
map --status
pause Press any key . . .
title Port Win7-1.vhd - FiraDisk RAMDISK - 2.0 GB
find --set-root --ignore-floppies /Win7-1.vhd
map --mem /Win7-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr
================================================================================
3. Boot Win7 VHD Image file from USB
- Direct Install Windows 7 in a VHD file on local harddisk created by WinNTSetup2_x86.exe with Ctrl + Shift + V
- Copy Win7 VHD file to USB and use USB_W7_Fix.exe to fix for booting from USB-drive
- Make Boot Manager menu on USB for Win7 VHD Image file
Thanks to JFX for creating the very handy WinNTSetup2 tool to Install Windows 2k/XP/2003/Vista/7 x86/x64
Info in folder IMG_XP\WinNTSetup2_x86_x64 and here http://www.msfn.org/board/topic/149612-winntsetup-v2/
WARNING: Boot menu of your computer and your USB-drive will change needed for booting with Win7 VHD file.
WinNTSetup2_x86.exe will create or change Boot Manager menu (folder Boot and file bootmgr)
Details of Procedure to create Win7 VHD file for booting from USB-drive
1. Boot with Windows 7 or 7PE
2. Use R-mouse menu to Mount Windows 7 Setup ISO file in ImDisk virtual drive (if needed first Install imdiskinst.exe)
3. Run WinNTSetup2_x86.exe and use Ctrl + Shift + V to create Win7 VHD file on local Harddisk (or use Disk Management)
4. In WinNTSetup2_x86.exe adjust Windows 7 Tweaks and Select install.wim and Bootdrive and your attached Win7 VHD
Select all System-Only Tweaks except Turn OFF USB and select other tweaks that you like
Select Checkbox to Mount Installation drive as C:
5. Use Setup to prepare Win7 VHD file and Boot drive menu and Reboot to Start Install of Windows 7
6. Reboot 2x with Win7 VHD to finish Install of Windows 7 in VHD
7. Set System Restore and UserAccount Control Off and Reduce Size
e.g. Change settings to get rid of pagefile.sys and hiberfil.sys
No pagefile.sys - Run as Administrator in cmd window: sysdm.cpl
and Change Advanced Performance Virtual memory Settings - Set to use No paging file
No hiberfil.sys - Run as Administrator in cmd window: powercfg.exe -H off
- Install missing Drivers but NOT the specific large Video driver
8. Install anything you need like ImDisk and 7Zip and connect your USB-harddisk to Update registry
Use Computer Properties and Set System Protection for Win7 VHD drive Off and Reboot Win7 VHD
9. Reboot with Windows 7 or 7 PE
10. Copy Win7 VHD to bootable USB-drive and use Disk Management to Attach Win 7 VHD located on USB
11. Open cmd prompt and create Boot Manager menu on USB-drive by running
CODE
bcdboot N:\Windows /s P:
where N: is your attached Win7 VHD and P: is your USB-drive
12. In Disk Management Detach Win7 VHD
13. If your USB-drive was NOT formatted in Windows 7 OS, then you need to fix the Bootsector of USB-drive P: with
CODE
bootsect.exe /nt60 P: /force
14. Run USB_W7_Fix.exe of IMG_XP package to fix the registry of Win7 VHD file on USB
15. Reboot with Win7 VHD from USB
Instead of points 9-14 you can make use of VHD_W7_Compact.exe to make Portable Windows 7 VHD file of 2 GB booting from USB-harddisk.
Procedure for booting with 2 GB Portable Windows 7 VHD file on USB-harddisk
Step 1. - Direct Install Windows 7 in a 10 GB VHD file on local harddisk and created by WinNTSetup2_x86.exe with Ctrl + Shift + V
Step 2. - Run VHD_W7_Compact.exe to Copy Win7 VHD content in 10 min to New VHD file of Reduced Size on USB-harddisk
Step 3. - Reboot with 2 GB Win7 VHD file from USB
On Running VHD_W7_Compact.exe you need to Select your User Folder in folder Users of the Win7 VHD Source file
The program takes care of Attach and Detach of VHD files by using diskpart.exe of your Windows 7 or 7 PE Operating System.
The program is suitable for 32-bits Windows 7 and was tested with en-US Ultimate version,
but may work with other distributions as well.
VHD_W7_Compact.exe - makes 2.0 GB Win7 VHD file for booting from USB-harddisk
================================================================================
4. Universal Image Create and Restore - Details
- Win_Restore.exe for Restore on USB drive takes care of:
USB Services get "Group"="Boot Bus Extender" and Start=0 to prevent BSOD 7B
UsbBootWatcher.exe and UsbBootWatcher.conf are copied to USB-HDD\WINDOWS\system32 directory.
Thanks to marv and cdob for describing effect of Driver Group and Start value to prevent BSOD 7B in booting XP from USB.
http://www.911cd.net/forums//index.php?showtopic=22473
IMG_XP\makebt\registry_tweaks\HKLM_systemdst_USB_XP.reg - Added to SYSTEM registry for Restore on USB drive
IMG_XP\makebt\registry_tweaks\HKLM_systemdst_BOOT_HDD.reg - Added to SYSTEM registry for Restore on HDD drive
In all cases of Restore the DiskSignature 4 bytes in MBR at hex offset 1B8 must be taken into account:
Value of \DosDevices\C: in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices on Target Drive is set according to DiskSignature.
All other values in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices on Target Drive are deleted.
More Info on DiskSignature http://thestarman.pcministry.com/asm/mbr/index.html
User can add extra registry tweaks
to HKLM_systemdst_Add.reg or HKLM_softwaredst_Add.reg in IMG_XP\makebt\registry_tweaks folder,
which will be added in Restore to the WINDOWS\system32\config\SYSTEM and the SOFTWARE registry files on Target drive.
IMG_XP\makebt\registry_tweaks\HKLM_systemdst_Add_XP.reg - used by HKLM System CheckBox
IMG_XP\makebt\registry_tweaks\HKLM_softwaredst_Add.reg - used by HKLM Software CheckBox
CODE
Windows Registry Editor Version 5.00
;------------------------------------------------------------------------------------------------------------
; SuppressNewHWUI - Suppress popup of Wizard New Hardware found, so that Universal OS can continue recognizing New Hardware
;------------------------------------------------------------------------------------------------------------
[HKEY_LOCAL_MACHINE\softwaredst\Policies\Microsoft\Windows\DeviceInstall\Settings]
"SuppressNewHWUI"=dword:00000001
;------------------------------------------------------------------------------------------------------------
; Diable SystemRestore
;------------------------------------------------------------------------------------------------------------
[HKEY_LOCAL_MACHINE\softwaredst\Microsoft\Windows Nt\CurrentVersion\SystemRestore]
"DisableSR"=dword:00000001
;------------------------------------------------------------------------------------------------------------
; Disable Automatic Windows Updates - Notify Only, No download
;------------------------------------------------------------------------------------------------------------
; [HKEY_LOCAL_MACHINE\softwaredst\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
; "AUOptions"=dword:00000002
;------------------------------------------------------------------------------------------------------------
; Win7 Search drivers via WindowsUpdate - Auto Install of some missing drivers
[HKEY_LOCAL_MACHINE\softwaredst\Microsoft\Windows\CurrentVersion\Device Metadata]
"PreventDeviceMetadataFromNetwork"=dword:00000000
[HKEY_LOCAL_MACHINE\softwaredst\Microsoft\Windows\CurrentVersion\DriverSearching]
"SearchOrderConfig"=dword:00000001
; Disable WindowsUpdate
[HKEY_LOCAL_MACHINE\softwaredst\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
"AUOptions"=dword:00000001
After Install of Windows 7 on system with BIOS SATA = IDE Controller, then the msahci Service has Start = 3.
Subsequent booting from USB-HD with msahci Start=3 on system with BIOS SATA = AHCI controller results in BSOD 7B.
The msahci tweak to set Start = 0 has been added to HKLM_systemdst_iaStor.reg used by Add iaStor - AHCI CheckBox.
This is needed to prevent BSOD 7B in Restore of Windows 7 for support of BIOS with SATA = AHCI controller setting.
http://support.microsoft.com/kb/922976/en-us
Adding iaStor driver prevents BSOD 7B on booting from USB-HDD on other computer systems.
Copy iaStor.sys to C:\WINDOWS\system32\drivers and iaStor.inf + iaAHCI.inf to C:\WINDOWS\inf
Copy iaStor.cat + iaAHCI.cat to your CatRoot folder C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
download the latest version of the Intel Matrix Storage Manager from http://downloadcenter.intel.com/Product_Fi...01&lang=eng
More Info on adding iaStor driver to SYSTEM registry - http://forums.pcper.com/showthread.php?t=444831
http://www.msfn.org/board/enable-ahci-inte...xp-t109450.html
Win_Restore.exe has Add iaStor - AHCI CheckBox to take care of the above and
IMG_XP\makebt\registry_tweaks\HKLM_systemdst_iaStor.reg registry tweak is added to the WINDOWS\system32\config\SYSTEM registry file on Target drive
so that HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase contains the required PCI device values.
IMG_XP\makebt\registry_tweaks\HKLM_systemdst_iaStor.reg - used by Add iaStor - AHCI CheckBox
Besides the already existing option to Add iaStor Driver, there is additional possibility to add other drivers
by dropping them previously in the corresponding IMG_XP\makebt\drivers folder.
Registry Tweaks used for Win7 instead of those for XP are
HKLM_systemdst_Add_W7.reg and HKLM_systemdst_USB_W7.reg
Additionally for Install of Windows 7 on USB-HDD primary partition with DriveLetter U:
CODE
bcdedit /store U:\Boot\BCD /set {bootmgr} device partition=U:
bcdedit /store U:\Boot\BCD /set {default} device partition=U:
bcdedit /store U:\Boot\BCD /set {default} osdevice partition=U:
bcdedit /store U:\Boot\BCD /set {default} detecthal on
bcdedit /store U:\Boot\BCD /set {default} device partition=U:
bcdedit /store U:\Boot\BCD /set {default} osdevice partition=U:
bcdedit /store U:\Boot\BCD /set {default} detecthal on
On booting from USB this USB-HDD partition will automatically get drive letter C:
http://www.multibootersno.no.genius/cloning.html
For making correct Windows 7 entry in BCD store of BOOTMGR menu it is essential that Windows 7 was set as the default option.
================================================================================
5. Solutions to prevent BSOD 7B - Run USB_XP_Fix.exe
It is often possible to prevent BSOD 7B without using any delay driver like waitbt.sys or DriveGuard ubdrvgd.sys driver.
USB_XP_Fix.exe was improved such that the CriticalDeviceDatabase registry has all entries for IDE Controller and USB Controller Services
and that all IDE and USB Controller drivers if missing are extracted previously from the XP driver.cab file.
The CriticalDeviceDatabase registry of Windows 7 has much more entries as compared to XP.
IDE ATA\ATAPI Controller has ClassGuid={4D36E96A-E325-11CE-BFC1-08002BE10318} with entries in mshdc.inf
USB Controller has ClassGUID={36FC9E60-C465-11CF-8056-444553540000} with entries in usbport.inf and usbstor.inf and usb.inf
CriticalDeviceDatabase registry of XP is now improved and comparable with Windows 7 by adding
all entries for Control Class {4D36E96A-E325-11CE-BFC1-08002BE10318} and {36FC9E60-C465-11CF-8056-444553540000}
These CDDB entries arre added in folder makebt\registry_tweaks in files HKLM_systemdst_Add_XP.reg and HKLM_systemdst_USB_XP.reg
To be Universal for a lot of hardware it is also necessary to have the WINDOWS\DriverPacks folder available with Chipset + Processor + MassStorage drivers.
In that way you provide support for another important Controller Class, the SCSI- en RAID-controllers
Class=SCSIAdapter has ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
So there are two measures that make XP behave more like Windows 7 and will allow booting on all hardware:
1. improved CriticalDeviceDatabase registry with IDE Controller and USB Controller entries
combined with the built in IDE Controller drivers made readily available (unpacked from driver.cab)
2. WINDOWS\DriverPacks store with subfolder M (MassStorage) for support for SCSI- en RAID-controllers
USB_XP_Fix.exe has Checkboxes to add Intel iaStor.sys driver and AMD ahcix86.sys AHCI driver with their CriticalDeviceDatabase entries
Intel iaStor.sys is IDE Controller (iaAHCI.inf for Intel AHCI Controller) with entries ending on cc_0106
iaStor.sys can be RAID Controller (iaStor.inf for Intel RAID Controller) with entries ending on cc_0104
In general one can say that missing (or slow access to) Controller drivers are the reason for BSOD 7B
IDE ATA\ATAPI Controller has ClassGuid={4D36E96A-E325-11CE-BFC1-08002BE10318} with entries in mshdc.inf
USB Controller has ClassGUID={36FC9E60-C465-11CF-8056-444553540000} with entries in usbport.inf and usbstor.inf and usb.inf
SCSI- en RAID-controllers has ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318} mainly supported via MassStorage DriverPack
In case of any boot problem, then always run SaveHwids.exe and post the Hwids of your machine,
so that we can try to solve the boot problem by adding CriticalDeviceDatabase registry entries combined with suitable drivers.
If you did not use the advised Keep The Drivers Option KTD when integrating DriverPacks in your XP Setup Source with DPsBase.exe
then you can later add to your Image the WINDOWS\DriverPacks folder with subfolders C and CPU and M of extracted DriverPacks.
Also after using DriverForge then any previous settings are lost e.g. for making use of the KTP C:\WINDOWS\DriverPacks store.
After booting with XP Image you can run POST_FIX\DevicePath_Reset_KTP.reg to Reset DevicePath to the KTD settings
Additionally the Environment value of KTD must be set as C:\WINDOWS\DriverPacks by using KTD_C_WIN_DP.reg
Alternatively you can use this method:
Post Install Add DriverPacks:
1. Boot with Universal XP Image file
2. Extract 3 DriverPacks to C:\ e.g. Chipset + CPU + MassStorage - will give C:\D folder
3. Use R-mouse to Open command prompt at C:\POST_FIX and run command
CODE
DevPath.exe %SystemDrive%\D
DevicePath in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
is set to subfolders of C:\D
USBoot DriveGuard driver is probably unneeded to prevent BSOD 7B since recent USB_XP_Fix.exe will Fix XP and Install waitbt.sys driver.
If you still have problem then Install USBoot DriveGuard driver ubdrvgd.sys to prevent BSOD 7B in booting from USB
- Download USBoot from http://usboot.org/tiki-index.php
- Extract the package, right click on ubdrvgd.inf, click on Install
- the XP boot message - DriveGuard Initialization failed - has No effect, the driver works OK
- More Info http://reboot.pro/9830/page__st__800#entry160006
- DriveGuard driver ubdrvgd.sys is installed as LowerFilters between the main driver and the hardware
================================================================================
6. Universal XP - Support in boot.ini menu for Multiple Hal and Kernel
The boot.ini menu of XP can be used to select on the fly which hal and kernel file will be used for booting.
In this way one can support booting with the same Universal Image file on computers having quite different hardware.
http://www.vernalex.com/guides/sysprep/hal.shtml
http://www.etherboot.org/wiki/appnotes/port_winnt_sanboot
The method described above is improved and used in VHD_XP_Compact.exe and Win_Restore.exe
Default XP boots by boot.ini entry LAST CONFIG with the files hal.dll and ntoskrnl.exe and ntkrnlpa.exe
The boot.ini switches /hal and /kernel will copy the in boot.ini named switchfiles and on the fly overwrite hal.dll and ntoskrnl.exe
At the same time the kernel name (max=6 letters) plus pa .exe file is used to overwrite ntkrnlpa.exe
A set of 7 hal files and 4 kernel files in folder halkern is generated from the XP Setup Source provided by user.
The hal and kernel files are extracted in priority from sp3.cab or sp2.cab or driver.cab (used by RVM Integrator) e.g. as
CODE
D:\XPSOURCE\I386>expand driver.cab -f:hal*.dll D:\IMG_XP\makebt\halkern\
D:\XPSOURCE\I386>expand driver.cab -f:nt*.exe D:\IMG_XP\makebt\halkern\
D:\XPSOURCE\I386>expand driver.cab -f:nt*.exe D:\IMG_XP\makebt\halkern\
In folder halkern we rename:
CODE
D:\IMG_XP\makebt\halkern>ren hal.dll halstan.dll
D:\IMG_XP\makebt\halkern>ren ntoskrnl.exe ntkrup.exe
D:\IMG_XP\makebt\halkern>ren ntkrnlpa.exe ntkruppa.exe
D:\IMG_XP\makebt\halkern>ren ntkrnlmp.exe ntkrmp.exe
D:\IMG_XP\makebt\halkern>ren ntkrpamp.exe ntkrmppa.exe
D:\IMG_XP\makebt\halkern>ren ntoskrnl.exe ntkrup.exe
D:\IMG_XP\makebt\halkern>ren ntkrnlpa.exe ntkruppa.exe
D:\IMG_XP\makebt\halkern>ren ntkrnlmp.exe ntkrmp.exe
D:\IMG_XP\makebt\halkern>ren ntkrpamp.exe ntkrmppa.exe
In this way folder halkern contains 7 hal and 4 kernel files:
CODE
halmacpi.dll
halaacpi.dll
halacpi.dll
halmps.dll
halapic.dll
halstan.dll
halsp.dll
ntkrmp.exe
ntkrmppa.exe
ntkrup.exe
ntkruppa.exe
halaacpi.dll
halacpi.dll
halmps.dll
halapic.dll
halstan.dll
halsp.dll
ntkrmp.exe
ntkrmppa.exe
ntkrup.exe
ntkruppa.exe
VHD_XP_Compact.exe and Win_Restore.exe will copy the files of the halkern folder to Image folder WINDOWS\system32
Multiprocessor = MP and Uniprocessor = UP
boot.ini file with Multiple Hal and Kernel for making Universal XP
CODE
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="LAST CONFIG - XP Pro (Last Configuration)" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="MP HALMACPI - XP Pro (ACPI Multiprocessor PC) for multi-core, hyperthreading" /noexecute=optin /fastdetect /kernel=ntkrmp.exe /hal=halmacpi.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="UP HALAACPI - XP Pro (ACPI Uniprocessor PC) for single-core, no hyperthreading" /noexecute=optin /fastdetect /kernel=ntkrup.exe /hal=halaacpi.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="UP HALACPI - XP Pro (ACPI PC) for most compatability on ACPI computers" /noexecute=optin /fastdetect /kernel=ntkrup.exe /hal=halacpi.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="MP HALMPS - XP Pro (MPS Multiprocessor PC) for multi-core Xeons" /noexecute=optin /fastdetect /kernel=ntkrmp.exe /hal=halmps.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="UP HALAPIC - XP Pro (MPS Uniprocessor PC) for single-core Xeons" /noexecute=optin /fastdetect /kernel=ntkrup.exe /hal=halapic.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="UP HALSTAN - XP Pro (Standard PC) for old non-ACPI computers" /noexecute=optin /fastdetect /kernel=ntkrup.exe /hal=halstan.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="MP HALSP - XP Pro (Compaq SystemPro Multiprocessor PC)" /noexecute=optin /fastdetect /kernel=ntkrmp.exe /hal=halsp.dll
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="LAST CONFIG - XP Pro (Last Configuration)" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="MP HALMACPI - XP Pro (ACPI Multiprocessor PC) for multi-core, hyperthreading" /noexecute=optin /fastdetect /kernel=ntkrmp.exe /hal=halmacpi.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="UP HALAACPI - XP Pro (ACPI Uniprocessor PC) for single-core, no hyperthreading" /noexecute=optin /fastdetect /kernel=ntkrup.exe /hal=halaacpi.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="UP HALACPI - XP Pro (ACPI PC) for most compatability on ACPI computers" /noexecute=optin /fastdetect /kernel=ntkrup.exe /hal=halacpi.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="MP HALMPS - XP Pro (MPS Multiprocessor PC) for multi-core Xeons" /noexecute=optin /fastdetect /kernel=ntkrmp.exe /hal=halmps.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="UP HALAPIC - XP Pro (MPS Uniprocessor PC) for single-core Xeons" /noexecute=optin /fastdetect /kernel=ntkrup.exe /hal=halapic.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="UP HALSTAN - XP Pro (Standard PC) for old non-ACPI computers" /noexecute=optin /fastdetect /kernel=ntkrup.exe /hal=halstan.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="MP HALSP - XP Pro (Compaq SystemPro Multiprocessor PC)" /noexecute=optin /fastdetect /kernel=ntkrmp.exe /hal=halsp.dll
================================================================================
- Win_Restore.exe can be used to Restore XP or Win7 from VHD to HDD-partition.
For Restore of Win7 from VHD you need to run Win_Restore.exe in Win 7/8/7PE OS
so that bcdboot.exe can be used to generate Boot Manager Menu required to boot Win 7 from HDD-partition.
- BOOT_IMG makes GRUB4DOS Menu on Target Boot Drive for selected VHD File on NTFS Target System Drive (copy occurs if needed).
- IMG_XP_Update.exe is used after booting with XP Image file from RAMDISK, to Update the Image file that you just booted from.
Boot with full XP Image file in RAMDISK and Update Drivers using DriverForge with Drivers folder that you supply.
Then run IMG_XP_Update.exe to improve full XP Image file in 1 minute with drivers for New Hardware.
- Most computers nowadays are ACPI Multiprocessor PC and we can use the corresponding HAL.
If you need for XP to support old computers using a different HAL then you can use Add Hal and Kernel files and
let modify by IMG_XP programs your boot.ini as described in Section 6.
http://www.vernalex.com/guides/sysprep/hal.shtml
http://www.etherboot.org/wiki/appnotes/port_winnt_sanboot
In general ImDisk must be installed in XP or Win 7/8 by using previously the provided imdiskinst.exe file.
ImDisk is used to mount VHD Image file in a virtual drive.
To Install ImDisk driver on Vista and Windows 7/8 you need to turn off UAC, User Account Control
http://www.ltr-data.se/opencode.html
The 64-bit FiraDisk driver requires in x64 Win7 to set testsigning switched on.
Open Command Prompt as Administrator:
CODE
bcdedit /set testsigning on
Reboot to activate this.
http://msdn.microsoft.com/en-us/library/dd419910.aspx
Thanks to karyonix, more Info see:
FiraDisk - http://reboot.pro/index.php?showtopic=8804
Install FiraDisk driver in XP with R-mouse on firadisk.inf in IMG_XP\makebt\firadisk-driver- folder
Forum FiraDisk - http://reboot.pro/index.php?showforum=94
Windows 7 - http://reboot.pro/index.php?showforum=77
Windows 7 on USB-HDD - http://reboot.pro/index.php?showtopic=9196
Thanks to jaclaz for pointing me to strarc.exe of Olof Lagerkvist ,
which is used in IMG_XP_Update.exe to Update the XP Image File on HDD after booting from RAMDISK.
Updating Registry and Drivers in Image file is done in only 5 sec, a Total Update of the Image requires 1 min.
___________________________________________
Need More Detail ? contact me !!
I sell a lot of stuff, program. knowledge, etc.. at a small cost.
I will guide you step by step, personally.
My Paypal Account is : ksw.industries@gmail.com
Don't know how to send money ? Click here for detail about Paypal account.
http://xyberpast.blogspot.com/2014/05/how-to-get-my-program.html
Don't have money? OK! Here is another way to get the program.
how to get my program - Free of charge
No comments:
Post a Comment