After hours, well.. days now, I figured out a lot by my own now: 1. OnePiece XP Embedded Post-SP3 International True AddOn v1.0.2 seems not compatible in any way. It caused several problems even without XP2ESD. I also don't know what "NOTE: Embedded pack changing original system requirements" means. Can you explain more about please? What is original system? Hardware? ISO? How to make it run? 2. Script seems not working properly with spaces in name of folder path. Actual this is easy avoidable by setting paths in strings, in batch it is "C:\Folder\Another folder". Also it easy reaches it maximal characters allowed in folder names. In my XP-VM I needed to put it to something like C:\XP2ESD to make it run. I would add this as important information in the thread. 3. For the VM also was need to allow more virtual RAM for the machine, since it starts a VM with 512mb by default. So better using a machine with at least 1024mb then. Watching out these, it finally worked. Other side questions: 1. I could not figure to add a "pause" in the progress before making the ISO for VM, any ideas there? 2. Because: I would like make a Lite (nLite Preset) and add some cosmetics to: XPize+Sevenmizer, how to make this? 3. Can I make it run with Win11 ISO? Would like to have the WIM beside other Windows 11 in installer setup. Relate to a new name for future AIO release, how about NT2ESD? Or something like Windows Modern Installer Converter WMIC or WIM/ESD-Maker. Anyway I'm done for now. Cheers.
I still do not understand how to get this to work on a Dell Optiplex 3070. Attempting to use Windows XP Pro 64bit w/ SP2
Is v1.7 planned to release soon? It seems like the new version was promised to come out months ago, and the scope of the update looks like it's getting bigger each week. Asking because I believe the next version fixes some issues I have with v1.6.2 (which were already posted by a few others here)
Work is still in progress. Real testing discovered real issues.. But progress is not frozen, it goes up, but just a bit slowly. I spend many days on extender to bring some other / new / useless functions for various drivers. My goal is to fix issues I found. But no worry we are getting closer, when I finish some things around drivers, then I will move to "BootStack" for POWIS, then we are done. I have tested many combinations for multiboot deploying for XP-11 in CSM... Too much to write, just wait for release
Good news, I have added few more ported drivers and seems like issues on my testing machine are gone. Even some of these newly ported drivers doesn’t support new HWIDs, its fine to have them. Because I really wanted to bring something new, I must touch NTOSKRN8 Extender. I need to compare changes as during this testing I have touched existing code aswell. Maybe Thats why I was able to port ACPItime.sys from Windows 8. List of all ported drivers right now: x86 Code: AMD_SATA_1.2.001.0337 AMD_SATA_1.2.001.0402 AMD_SD+MMC_1.0.0.0106 AMD_USB3_1.1.0.0145 Generic_ACPITime_6.2.9200.16384 Generic_AHCI_1.0.0.0 Generic_AHCI_1.0.0.585 Generic_AHCI_6.2.7989.0 Generic_AHCI_6.2.9200.20652 Generic_AHCI_6.3.0.1 Generic_Disk_5.2.3790.4171 Generic_HID_6.2.9200.16384 Generic_MSAHCI_6.1.7601.26057 Generic_NVMe_1.3.1014.00 Generic_NVMe_1.5.1200.00 Generic_NVMe_6.1.7601.23403 Generic_NVMe_10.4.49.0 Generic_SD+MMC_6.2.8056.0 Generic_Touchpad_6.2.9200.16384 Generic_UASP_1.0.0.51 Generic_UASP_6.1.7600.4002 Generic_UASP_6.2.9200.16384 Generic_USB2_5.2.3790.5203 Generic_USB2_6.1.7601.24138 Generic_USB3_6.1.7800.0 Generic_USB3x_6.2.9200.21180 Generic_USBMassStorage_5.2.3790.5829 Generic_USBMassStorage_6.2.9200.23486 Generic_USBParent_6.2.9200.22279 Generic_VGA_6.1.7600.16385 IaNVMe_4.4.0.1003 IRST_16.8.2.1002 RSTe_4.7.0.1119 Samsung_NVMe_3.3.0.2003 TPM_6.1.7601.24564 WinUSB_6.2.9200.16384 x64 Code: AMD_SATA_1.2.001.0337 AMD_SATA_1.2.001.0402 AMD_SD+MMC_1.0.0.0106 AMD_USB3_1.1.0.0145 Generic_ACPITime_6.2.9200.16384 Generic_AHCI_1.0.0.0 Generic_AHCI_1.0.0.585 Generic_AHCI_6.2.7989.0 Generic_AHCI_6.2.9200.20652 Generic_AHCI_6.3.0.1 Generic_HID_6.2.9200.16384 Generic_MSAHCI_6.1.7601.26057 Generic_NVMe_1.3.1014.00 Generic_NVMe_1.5.1200.00 Generic_NVMe_6.1.7601.23403 Generic_NVMe_10.4.49.0 Generic_SD+MMC_6.2.8056.0 Generic_Touchpad_6.2.9200.16384 Generic_UASP_1.0.0.51 Generic_UASP_6.1.7600.4002 Generic_UASP_6.2.9200.16384 Generic_USB2_5.2.3790.5203 Generic_USB2_6.1.7601.24138 Generic_USB3_6.1.7800.0 Generic_USB3x_6.2.9200.21180 Generic_USBMassStorage_5.2.3790.5829 Generic_USBMassStorage_6.2.9200.23486 Generic_USBParent_6.2.9200.22279 Generic_VGA_6.1.7600.16385 IaNVMe_4.4.0.1003 IRST_16.8.3.1003 IRST_18.36.3.1019 RSTe_4.7.0.1119 Samsung_NVMe_3.3.0.2003 TPM_6.1.7600.16385 WinUSB_6.2.9200.16384
According to previously changed things I think I have adapted all of used scripts. Just PAE patch remaining for adapting. Then finally build “BootStack” to enable full MultiBoot support. Its insane how much I must touch again due improvements and bug fixing Edit: Now I have tested 3 different machines, one stick Unattended until desktop. Current mechanism seems really good.
So, I tried this out, making a UEFI-bootable XP 64-bit ISO, but when I attempt to load the XP 64-bit iso, I get "A required device isn't connected or can't be accessed 0xc0000007". This happens with the pure ISO in Virtual Box, and on real hardware after burning it to a USB device and enabling UEFI mode on that hardware. The real hardware I tested is as follows. Lenovo IdeaPad 3 with Intel Tiger Lake and no Legacy Mode. Acer Aspire E1-531 with Intel Sandy Bridge with Legacy Mode disabled (and this laptop does support XP). Idk what I did wrong as I followed the guide correctly. I don't think this has anything to do with ACPI, SATA, or USB, otherwise, a BSOD for either NON_ACPI_COMPLIANT_BIOS A5 or INACCESSIBLE_BOOT_DEVICE 7B would occur, and not the Windows Boot Manager black screen error. Hopefully, someone can help me out here. Also, is NVMe and USB3 included, or is that separate. If it's separate, where do I find the appropriate files for those to use with XP2ESD. I want to try booting XP 64-bit on my Lenovo IdeaPad 3 with Intel Tiger Lake.
Upcoming version comes with 2 safe nLite presets. You can add your own, just for removals. For example when is enable this option you will receive number images based on your presets. One full image and lite ones. XPize / SevernMIzer are installers, you can safely use then in RunOnceEx. In upcoming version is really improved this process which support configs for each installer. Yes, new version can be used as AIO builder and installer. Multiboot supported. I'm currently building ISO like 60GBs. Last days I have tested various multiboot scenarios and I fixed and improved whole process for all systems. There few things which must be done before release. 1) Add few more options for DriverPacks into POWIS. Setup Mode - Hybrid, Media, Disk. Process options - Auto, Manual + ReIndex. Will see how much time I need for this, hopefully only few hours. 2) Add process to build "bootstack". There is maybe another option how to do it. This is needed to allow installing modern Windows in any order. For example: Installing 11 then 7 mean, you can't boot 11 due 7 bootmgr. I would like to add process to automaticallly extract these files from ISO / Update. It's still under construction There are also many other things and maybe many forgotten. But make this tool public is priority. Delay is mostly caused by testing and bugfixing and polishing...
@Scr4tch There are no benefits in merging different Windows builds into one WIM expect 5.1 and 5.2 as they share some of files. Best is what I did for new version, merge same builds into different ESD / WIM / SWM automaticaly on provided images. Why not use XPize from RunOnceEx? You will always have latest system files when you use updated image. I mean you can then switch your Transformatiom Pack on each install on the fly. I have collection of them for XP and 2003 aswell.
The benefit for me is, there is just one ISO file in the end, that has all the builds I want, not several different (with mostly 80% same content) etc. So there is one ISO, I boot and can install then by choice: Win7, Win10, Win11, would be nice to have there WinXP as well, will test in a few. Because it would be the same as just start the exe by my own with few clicks, when I have desktop access. Would like to have everything finished when copying image content on disk is done. Like re-copying a backup image, but with freshest content from installers. Both just a personal preference, I love efficiency.
Install by my own or run it silenced, is the same for me. My goal is to have a ready desktop, since installing (copy the image on disk) is done. Does OnePiece XP Embedded Post-SP3 International True AddOn v1.0.2 require any special version? (like maybe only on embedded applicable?) I tried and still trying several things I get only problems with that package...
Have you tried with OnePiece XP Post-SP3 AIO International Update Packs? AFAIK it should be used with Post-SP3 UpdatePacks.
On XP x64 (from XP2ESD Build) on UEFI Class 3, with UefiSeven + Vbemp or FlashBoot + vgapnp.sys/vpa.sys (the problem is present regardless of using XP/7 generic vga drivers), my modern browser's framebuffer freezes automatically at the modern browser's startup but the browser still works (Mozilla, mypal, chrome, etc), this problem doesn't exist on Internet Explorer 8... I need to show things above the window to change the framebuffer (like opening the start menu etc). I can't use modern browsers this way on XP. This is why I was suggesting backporting basicdisplay.sys for XP using the source code that George King found (because being limited to only one screen resolution doesn't allow some applications to run). @George King This is an issue you should know, that's why I announced it!
Did you apply the hal.dll patch ? Here all is working fine, Uefi Class3, Vbemp + Uefiseven patched 1920 + Winload.efi patched 1920. 360 browsers + mypal 68 + Serpent 52 Without this patch, specially for Gecko type browsers, mouse scrooling isen't working due to lot of QueryPerformanceCounter Api callings.
Give me the hal.dll patch in a private message, please (I used the uefiseven patched 1920 and winload.efi patched 1920).
Yea beside of it, but with it alone its missing updates: 1. OnePiece XP Post-SP3 AIO International Update Packs FINAL v1.1.0 = Updates from ~Mai 2008 till ~April 2014 2. OnePiece XP Embedded Post-SP3 International True AddOn v1.0.2 = Updates from ~April 2014 till ~April 2019. So this pack includes security updates from 5 years. That is why I want to include it either. ((but some information saying it has updates 2009 till 2021? idk.. Im missing information, what is probably the source of problems, maybe it needs to integrate at the very first? Will try out soon I guess...)) But yea.. I facing problems when I integrate it. This is my current state: But with XP2ESD it seems it removes all the MCE and TPC stuff.. idk. Also I wish I could "integrate" XPize v5.6 and Sevenmizer v2.2.1 in the iso (modifying the installer files) Right now I do manually before script building the image for VM, but that is not optimal, a lot get overwritten etc. Also, just netfr40 causing problems? So maybe the answer is: Code: nLite: add post-sp3-emb add netfr11-updated add mce-updated add tpc-updated add tpc-fix add post-sp3 RVMI: rem netfr40 nLite: add netfr10-updated make iso (important, ISO label has to be official xp pro: f.e.: GRTMPVOL_EN) but maybe the updated mce + tpc packages already has the post-sp3-updates? sooooooo.... Code: nLite: add post-sp3-emb add post-sp3 add netfr11-updated add mce-updated add tpc-updated add tpc-fix RVMI: rem netfr40 nLite: add netfr10-updated make iso (important, ISO label has to be official xp pro: f.e.: GRTMPVOL_EN) Needs to test soon... If I would have all the information, I would love to create and publicize a "freestyle"-addon. (Maximum updated, maximum extended, one file, everything will be done with it.)