That's not the issue - I just don't need a Retail/FPP trial. AFAIK, the OEMBIOS changer does not work on Retail installations - only OEM or VLK.
Upcoming update will change DriverPacks setup to use Snappy Driver Installer as this seems much better and also we can use newer DriverPacks and also only Finnish language is missing. This can bring better user experience. And I have also added new option into config.ini to acpi.sys replacement inside install.wim. This can help users to install it into new hardware too. This switch will be disabled by default. It's time to test it on my Asus K53SV
Hi again! I managed to make english modern windows installer. But with norwegian it failes with intergrating OnePiece_Windows_XP_Post-SP3_UpdatePack_v1.0.9_FINAL_NOR.7z. It intergrates all other stuff but skips this. Why? I tried downloading the updatepack again, but same result. I imported manualy onepiece update pack into nlite. Does the automatic intergration fail because of language problem?
Great! And are you sure you have Norwegian source? If yes, unpack UpdatePack, then edit entries.ini and remove ForceLang=*** attribute. Then repack it and keep file name. Now it should work. EDIT: Please attach PRODSPEC.INI from your setup media
Its from Norwegian VL Sp3 install media. When I edited entries.ini, the onepiece packs integrated normally. Thank you so much for the tip.
@WindowsMyStyle Can you confirm you really used untouched ISO? Does exist sp3.cab inside your Windows\Driver Cache\i386? Just read again first post, nothing from updates folder is required, but recommended..
@WindowsMyStyle I send you PM, lets find why it doesn't work for you. Anybody else encountered same problem with ntoskrnl.exe is missing?
Im not sure if these lines in unattended sif file will help AutoUpdate = Off MU = Off ;Microsoft Update
Can you grab boot.ini from deployed unbootable Windows so we can see if there is corectly set partition? That is only idea accoring to mentioned article. Also I have only one HDD (SSD) with two partitions. I will prepare video from installing on my Asus K53SV EDIT: Must be caused by bad boot.ini I forgot it’s set to disk(0). Will investigate into disk number detection EDIT2: For VMware BSOD - its expected as we have old driver. Massstorage DriverPack should be revised by someone EDIT3: I’m working on better rdisk and partition detection from target volume. Hope this solve it
@WindowsMyStyle I was able to reproduce same errors as you. I have improved boot.ini writing. So should be fixed in upcoming 1.4. I need only finish dispart MUI patches to get english output in all languages.
It will be a coincidence the problem is not mine but of all PCs in the world! if I had tried only one PC ... but between yesterday and today I will have tried dozens of them !!! all the same problems !!! Maybe it is better to send me the changes in private first ...because it seems to be the only one who does serious tests ... useless to release yet another unusable version.
Current boot.ini was incorectly writen, It works only in some specific scenario - Only one HDD with installed Windows on first partition as I incorrectly set partition number as volume number. And HDD aka rdisk was static on disk 0. I have improved both of them so all is dynamic now. Yes, will send prerelease to you soon
ok I understand the problem ... inside the install.wim / esd file the boot.ini file looks like this: Code: [boot loader] timeout=15 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /noexecute=alwaysoff /detecthal multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="1.Standart PC" /fastdetect /noexecute=alwaysoff /hal=halstd.dll /kernel=ntkrnlst.exe multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="2.ACPI PC" /fastdetect /noexecute=alwaysoff /hal=halacpi.dll /kernel=ntkrnlst.exe multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="3.ACPI Uniprocessor PC" /fastdetect /noexecute=alwaysoff /hal=halaacpi.dll /kernel=ntkrnlst.exe multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="4.ACPI Multiprocessor PC" /fastdetect /noexecute=alwaysoff /hal=halmacpi.dll /kernel=ntkrnlmp.exe multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="5.Uniprocessor PC with MPS" /fastdetect /noexecute=alwaysoff /hal=halapic.dll /kernel=ntkrnlst.exe multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="6.Multiprocessor PC with MPS" /fastdetect /noexecute=alwaysoff /hal=halmps.dll /kernel=ntkrnlmp.exe multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Safe mode boot" /fastdetect /noexecute=alwaysoff /safeboot:minimal /sos /bootlog /noguiboot but on first reboot after installation it is like this: Code: [boot loader] timeout=15 default=multi(0)disk(0)rdisk(0)partition(0)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(0)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /noexecute=alwaysoff /detecthal multi(0)disk(0)rdisk(0)partition(0)\WINDOWS="1.Standart PC" /fastdetect /noexecute=alwaysoff /hal=halstd.dll /kernel=ntkrnlst.exe multi(0)disk(0)rdisk(0)partition(0)\WINDOWS="2.ACPI PC" /fastdetect /noexecute=alwaysoff /hal=halacpi.dll /kernel=ntkrnlst.exe multi(0)disk(0)rdisk(0)partition(0)\WINDOWS="3.ACPI Uniprocessor PC" /fastdetect /noexecute=alwaysoff /hal=halaacpi.dll /kernel=ntkrnlst.exe multi(0)disk(0)rdisk(0)partition(0)\WINDOWS="4.ACPI Multiprocessor PC" /fastdetect /noexecute=alwaysoff /hal=halmacpi.dll /kernel=ntkrnlmp.exe multi(0)disk(0)rdisk(0)partition(0)\WINDOWS="5.Uniprocessor PC with MPS" /fastdetect /noexecute=alwaysoff /hal=halapic.dll /kernel=ntkrnlst.exe multi(0)disk(0)rdisk(0)partition(0)\WINDOWS="6.Multiprocessor PC with MPS" /fastdetect /noexecute=alwaysoff /hal=halmps.dll /kernel=ntkrnlmp.exe multi(0)disk(0)rdisk(0)partition(0)\WINDOWS="Safe mode boot" /fastdetect /noexecute=alwaysoff /safeboot:minimal /sos /bootlog /noguiboot with a Windows Live I put the first version back and it started immediately ... as you can see the problem was not mine
@WindowsMyStyle Language bug is solved in upcoming version. I added new part to read default setup language from extracted XP source. So this is fixed. These menus are driven by MyFactory.. If you are speaking about everything in "auto-sysprep" folder. I don't care, this part is only adapted from another project, right? Also SysPrep is no logner used in upcoming 1.4. Only turning into OOBE using registry keys. You can always create your own SysPrep image, for this purpose is here CaptureVHD.cmd Maybe you didn't catch main purpose of this tool. It's Convert Windows XP into modern installer. If you want to modify image, you can always do everything in offline source. And as I write in first post, any ideas how to improve are welcome. EDIT: Please also share mentioned thousand of bugs for review