cdob

This behaviour reminds to XP setupldr.bin and 512 mb size RAM disk. There is a max ram disk size limit. There may be another limit at Windows 7 bootmgr, never tried a huge boot.wim so far. Idea: use a newer bootmgr instead. Not tested.

How do you build the mult_iso image? Customize_Info.txt: Put in folder MULTI\images your Boot Image files (.iso or .img) to make MultiBoot CD/DVD In case of CD=YES then Make_PE3 programs will copy 7pe_x86.iso or 7pe_amd64.iso to folder MULTI\images Graphics drivers are big. Watch the ISO file size. Booting may fail at low RAM. The booted Make_PE3 offers 'Driverpacks from folder'. This launches Dpinst to load drivers. Expand graphics drivers to USB drive. Boot the PE and load the drivers. A Intel 4 Series is active, no reboot required. No idea about a unknown nividia hardware and driver. The behaviour may be different at different hardware. Specific used hardware and drivers. Try this too.

Dpinst can serach sub-directories also. It's supported in Make_PE3 already

I doubt always, very often it's disk 0. A user may change UEFI boot order: current running windows disk 0, second disk 1 The user changes the boot order: next boot is not from previous windows disk Possible execeptions Kansas chity shuffle http://www.911cd.net/forums//index.php?showtopic=21242 Machines with chipset storage and addional esata, msata or m.2 connector Imagine at two disk: given one EFI system partiton. You add a file this single EFI system partiton. The end user boot another OS next, creates a second EFI system partiton at the second hard disk. And boots from second hard disk next. Your file is missing at active EFI system partiton I don't understand the requirements still. Machinbe booted at BIOS? Machinbe booted at BIOS? What about EFI NVRAM settings? Remember, if you boot from UEFI, then mountvol solves your basic issue. Given the end user keeps the UEFI disk order. A real world simplification: If a disk 0 contains a EIF system, then use this. Ignore strange cases. By the way: At booted PE may reset SystemSetupInProgress settings, e.g. printer support

@echo offFOR /L %%a IN (1,1,9) DO (echo sel disk 0echo sel par %%aecho det par ) | diskpart.exe | find.exe /I "c12a7328-f81f-11d2-ba4b-00a0c93ec93b" && ( echo disk 0 partition %%a (echo sel disk 0 echo sel par %%a echo assign letter=S ) | diskpart.exe)Should work in most cases, will fail at strange machines or configurations.There is no general way.

Mountvol does support /s parameter, if you boot at UEFI mode. This includes Windows 10. Mountvol dosn't support /s parameter, if you boot at BIOS mode. How do you boot the machine?

How many disks do you use at one machine? Did you boot windows from this UEFI disk? mountvol.exe S: /S. Did you like to support another disk, not booted from this one? The specs request a EFI system partition GUID C12A7328-F81F-11D2-BA4B-00A0C93EC93B https://en.wikipedia.org/wiki/EFI_system_partition There may be two hard disks with this GUID at one machine.

Did you used XP boot loader before? Did you used grub4dos boot loader before? Which boot loader do you use now? To add XP to windows 7 boot loader, open a elevated command prompt bcdedit.exe /create {ntldr}bcdedit.exe /set {ntldr} device partition=D:bcdedit.exe /set {ntldr} path \ntldrbcdedit.exe /set {ntldr} description "Windows XP"bcdedit.exe /displayorder {ntldr} /addlastD: is a example, use your XP (system) drive letter instead. This is the \ntldr drive.You may have to open disk management and assign a drive letter first.

That's the 64 bit driver. Do you use a 32 bit XP? http://www.msfn.org/board/topic/107504-integration-of-intels-sata-ahci-and-raid-drivers/ http://www.win-raid.com/t22f23-Guide-Integration-of-Intels-AHCI-RAID-drivers-into-a-Windows-XP-W-k-W-k-CD.html

Yes, a single boot base is impossible at a x86 and x64 UEFI environment. The second approach uses a single wim or esd to install for x86 and x64. You don't have to copy esd twice, feel free to create a hardlink at the hard disk. I'm using individual ISO for every type too.

How do you like to use the AIO ISO?Do you like to burn the ISO to a optiocal media? Any IOS size limitations? single layer DVD, dual layer DVD, blu ray Do you use a virtual CD drive inside a USB hdd? Which boot environments should be supported? x86 BIOS, x64 BIOS, x86 UEFI, x64 UEFI, secure boot Do you like to boot from the media? Do you like to mount the ISO image at running windows and upgrade the current running windows? A one size all solution may be impossible. A x86 AIO ISO and a second x64 AIO ISO may be another approach. Try a x86_x64 AIO ISO: Use the Media Creation Tool x86_x64 ISO file as reference. The Media Creation Tool creates a \boot\bcd file references a file \x86\sources\boot.wim and another file \x64\sources\boot.wim. boot.wim x86 setup.exe supports a folder \x86\sources\ boot.wim x64 setup.exe supports a folder \x64\sources\ Ideas: Extract the ISO archive file. Create one x86 install.wim or install.esd. Export all single x68 win 10 images to this wim file. Create another file x64 install.wim or install.esd: Run dism.exe to export all single x64 win 10 images to this wim file. Replace the two existing x86\sources\install.esd and \x64\sources\install.esd files. Create a new ISO image running oscdimg.exe. https://technet.microsoft.com/en-us/library/hh824847.aspx Another idea: run dism.exe to export all single x86 and x64 win 10 images to one install.wim file. Copy this file to x86\sources\install.wim and \x64\sources\install.wim Use oscdimg.exe -o to encode duplicate files only once. dism.exe /Export-Image /compress:recovery /SourceImageFile:D:\x86\sources\install.esd /sourceIndex:1 /DestinationImageFile:install.esddism.exe /Export-Image /compress:recovery /SourceImageFile:D:\x64\sources\install.esd /sourceIndex:1 /DestinationImageFile:install.esddism.exe /Export-Image /compress:max /SourceImageFile:D:\x86\sources\install.esd /sourceIndex:1 /DestinationImageFile:install.wimdism.exe /Export-Image /compress:max /SourceImageFile:D:\x64\sources\install.esd /sourceIndex:1 /DestinationImageFile:install.wimdism.exe /Get-ImageInfo /ImageFile:install.wim /Index:1dism.exe /Get-ImageInfo /ImageFile:install.wim /Index:2path %ProgramFiles(x86)%\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\%PROCESSOR_ARCHITECTURE%;%path%oscdimg\Oscdimg.exe -bootdata:2#p0,e,bAIO\boot\Etfsboot.com#pEF,e,bAIO\x64\efi\microsoft\boot\Efisys.bin -o -u2 -udfver102 Win10_AIO.iso AIO

boot.wim is mapped as X: by default. This default can be changed, can be anoher letter.As long as you use default boot.wim: its X: Yes, I did understood "installed OS".How many systems do you like to support. Any multi boot machines with several windows? A "special tag file" offers a secure approach: create a file yourself: \windows\special_tag_file.txt This file is once at hard disk, and you can find this windows installation. Or use a default existing file, e.g. \Windows\Media\tada.wav This file is missing in boot.wim, won't exist at ramdisk. Be aware, this may match several locations at a multi windows installation And this will fail, if the default file is deleted. for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\Windows\Media\tada.wav set win_dir=%%i:\Windowsecho Windows folder at %win_dir%Another one: assume a existing file \WINDOWS\system32\config\system This is located at x: too, exclude x: from search for %%i in (C D E F G H I J K L M N O P Q R S T U V W Y Z) do if exist %%i:\WINDOWS\system32\config\system set win_dir=%%i:\Windowsecho Windows folder at %win_dir%

Mount the file \sources\boot.wimAdd a file <boot.wim>\Windows\system32\Winpeshl.ini [LaunchApps]%SystemRoot%\setup.cmdAdd a file <boot.wim>\Windows\setup.cmdUnmount the file boot.wim. Create a new ISO file. http://www.robvanderwoude.com/userinput.php#W2K rem Windows 7 and up http://technet.microsoft.com/library/dd744592.aspxWpeutil.exe WaitForRemovableStorageWpeutil.exe UpdateBootInfoset PEBootRamdiskSourceDrive=for /f "tokens=1-3 delims== " %%a in ('reg.exe query "HKLM\SYSTEM\CurrentControlSet\Control" /v "PEBootRamdiskSourceDrive" 2^>nul') do ( if %%a.==PEBootRamdiskSourceDrive. @set PEBootRamdiskSourceDrive=%%~dc)if Defined PEBootRamdiskSourceDrive ( echo PEBootRamdiskSourceDrive %PEBootRamdiskSourceDrive%) That's simple: %SYSTEMDRIVE% is x:, the ramdisk Search for a special tag file at hard disk to detect the local windows partition.

Boot Win7, open a elevated command prompt and run bcdedit. Copy and paste the text output. And post the message.

The manufacturer documentation lists: https://technet.microsoft.com/en-us/library/dn502540.aspx Slmgr.vbs Options for Volume Activation Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2 The slmgr command and documentation shows the same activation duration for a retail version: permanent

Should be a retail without a timebomb.To view the activation time, run: cscript.exe slmgr.vbscscript.exe slmgr.vbs /xpr

Yes, that's correct. First textmode part uses BIOS interrupts: windows drivers are read from mapped disk. Next windows drivers are activated and no more BIOS interrupts used: No boot drive: BSOD 0x7b. Well, BSOD 0x7b can refer to different issues. Missing boot drive, missing target drive. As for USB: it's about drivers and timing (BIOS may initialize USB at boot, USB disk firmware may go to sleep temporarily at boot) A firadisk memdisk and no internal disk, different BIOS. It works and BSOD 0x7b. Try both: firadisk and winvblk

The 32 bit ramdisk driver does work. The 64 bit ramdisk driver fails: BSOD 0x7b. The driver hasn't been tested thoroughly at XP 64 bit.

0x10 reallocaed sectors and zero currrent pending sectors. I would interpred this as a warning, not a error message so far. Keep an eye on it Validate S.M.A.R.T. data: use your ears: any strange noises at hdd usage? does the system freezes temporarily without a reason? make a write test: transfer speed matches previous speed still? Which data are stored? mission critical? system / user data without a backup?

It's called anytime upgrade: the files are at hard disk already. Compare dism.exe /Get-TargetEditions Yes, you may disagree with the manufacturer.

basebrd.dll is a good catch. Yes, this is not hardlinked so far. hardlink this file. And other, not hardlinked files too. The previous mentioned approach shrinks about ten percent.

The hell is doubled nowadays: some programs adds msvcp*.dll to the program directory. Version manifest refers to WinSxS directory https://msdn.microsoft.com/en-us/library/windows/desktop/bb773175.aspx There can be different comctl32.dll file versions at WinSxS. Explorer.exe refers winsxs\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0* comctl32.dll Can you name a example?

Did you set at WinNTSetup: Enable native USB Boot of Windows 7 ? Which hardware do you use? Do you use a USB2.0 port?

Use a Window 10 boot.wim and a Windows 7 install.wim.

There is a iastor example http://www.msfn.org/board/topic/119748-howto-integrate-raid-drivers-into-txtsetupsif/#entry782204 However read TXTSETUP.OEM and adjust the [HardwareIdsdatabase] section: include all HardwareID from used TXTSETUP.OEM.