@George King I am also interested in testing new Quibble on Bios without any CSM, just UEFI class 3 Dietmar
Noted In upcoming version there will be simple checkbox when installer booted under UEFI to install Quibble, if this checkbox will be unchecked standard known UEFI support will be installed. Great is Quibble can support all Windows versions to 10 22H2. I hope with new version it will be easy to deploy and then easy for everyone to reports bugs and push development forward EDIT: I hope we can see in future booting x86 XP installed on NTFS GPT disk on x64 UEFI using Quibble.
little bug report: DP_GPU_XP.7z give you you bad VMware graphic driver(forced to use 800x600 4bit-color), however don't install that driverpack(use stock XP driver) or reinstall VMWare Tool in VMware menu does work. my VMware version: 15.2.5, XP hardware ID: PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD BTW, WTF is WPI folder
my guess it's something like: Work in Progress Saturday evening is a good time for an XP2ESD build: Code: Started on Sat 04/08/2023 at 17:58:48.19 Auto-Sysprep progress: 1 / 1 [1] Extracting en_windows_xp_professional_n_with_service_pack_3_x86_cd_vl_x14-78118.iso Windows XP Professional N Volume License (en-US) SP3 v5.1.2600.5512 [2] Integrating UpdatePack [3] Adding Auto-Sysprep [4] Building ISO [5] Installing into VirtualBox [6] Extracting VHD Windows XP Professional N Volume License (en-US) SP3 v5.1.2600.6532 [7] Capturing image [8] Exporting image Started on Sat 04/08/2023 at 18:29:51.41 Windows XP Modern Installer [1] Extracting 19041.1.191206-1406.VB_RELEASE_CLIENTEDUCATION-EDUCATIONN_VOL_X86FRE_EN-US.iso [2] Building setup structure Building bootloader Adding DriverPacks support Adding Office folder Adding Setup folder Adding Themes Adding Fonts Adding Wallpapers [3] Upgrading setup engine Integrating setup drivers [5] Modifying setup launch [6] Cleaning boot.wim [7] Compressing boot.wim "C:\XP2ESD_v1.6.2\_output\sources\boot.wim" original size: 337216 KiB Using LZX compression with 12 threads Archiving file data: 812 MiB of 812 MiB (100%) done Calculating integrity table for WIM: 327 MiB of 327 MiB (100%) done "C:\XP2ESD_v1.6.2\_output\sources\boot.wim" optimized size: 334856 KiB Space saved: 2359 KiB [8] Updating install.wim 1. Windows XP Professional N Volume License (en-US) x86 Integrating drivers License files check Applying RunOnceEx icon patch Applying RunOnceEx dialog patch Adding patched ACPI.sys Repacking sp3.cab [9] Compressing install.esd Using LZMS compression with 12 threads Archiving file data: 2172 MiB of 2172 MiB (100%) done [10] Final customization [11] Building bootable ISO Finished on Sat 04/08/2023 at 18:39:45.54 Process finished, press any key to exit...
Partially true, but you're mixing up processor generations and chipset revisions. Ivy Bridge CPUs are backward compatible with Cougar Point chipset-powered mobos (like the H61 ones mentioned by you) only after necessary microcode updates (and in some cases, the ME firmware - both usually bundled as a BIOS update). Of course you will need a third-party chip from one of the aforementioned vendors on such boards to get the USB 3.0 functionality. However, the origin post of this discussion is about the MacBook Pro (13-inch, Mid 2012), which features the Panther Point chipset, hence it does support USB 3.0 out of the box.
Yes, speaking about users who upgraded (which were/are a not irrelevant share of IVY bridge owners. But there were a lot of brand new systems sold brand new with new CPUs while using the "old" chipsets, which obviously come with all the relevant updates out of the box. I guess price and / or overproduction of the part mattered (and still matters today). I started my post saying that my MAC knowledge is close to zero for a reason, like I'm sused to do whenever I share a guess and not a 100% sure fact.
During testing I found new and never reported bugs in POWIS Launcher. Great is I was able to find cause, bad is fixing require touching code on many places.. I hope next release will be without serious bugs in POWIS Laucher EDIT: POWIS Launcher seems almost fixed! Some polishing must be done to provide 100% translation support
Regarding bug fixing, can I help you re-write the BootPartition option? The only problem (if BootPartition=Yes) is that the BCD is unaltered from the windows xp setup, you didn't do the changes in the BCD after copying the BCD again from ISO to BootPartition, that was the problem (You also forgot to make it copy the EFI BCD files to the boot partition in UEFI mode as well). I know that Myfactory works if the Windows XP partition is set to C: by setting the Boot Partition to hidden, so that's not part of the problem. Try to copy the BCD code you have done for UEFI mode (the one that worked without BootPartition set to Yes) on the section with boot partition set to Yes and change the paths inside BCD. I know I have told you this so many times and I am sorry for bringing this up again but this problem needed to be fixed in the future.
@UsefulAGKHelper I'm pretty sure you understand that I'm not going to react to your message in public again.
Just to let you know, for now, using Quibble to boot XP, Vista, and 7 does require CSM, it won't boot those operating systems without it, so that wouldn't be an option in my case. Also, have you improved XP on Server 2008 Beta 3 EFI files?
Yes, improvements are done also in this part. Newly patched bootloader, correct partitions are now created during setup, etc. Last time (more than 6 months back) I tried it my testings machine, I was able to boot from UEFI based Windows 7 installer, and install XP x64 without any other touch. Of course it needs to be tested and probably improved, I don't remember everything from my findings
Last night I was performed huge testing in WinPE with POWIS Launcher. I was gaming with various combinatios and crazy clicking on everything to see how It goes. I think I fixed last logical bugs and added almost all to be translatable. As various strings was added. I will created standalone topic for POWIS / RunOnceEx translation to make it clear for all translators. Btw, now POWIS Launcher handle installer exit codes, so you can for example choose XP2ESD setup and then decide to cancel it using X button, then you are returned to POWIS Launcher and you can start again from scratch. Main goal was to support multiboot installation from single WinPE boot. Now it should be possible to deploy for example Windows 10 + 7 + XP in one session (Noreboot must be checked for deploying 10 + 7, XP must be deployed as last one - this is current design).
anyone possibly knows how to deal with a broken user's profile? Administrator logs-in fine. tried to create new user, but issue insists. sfc /scannow is my last resort before re-installing. this is on a classic HDD. Edit: I ended up shamefully re-installing
@Alexandros C. Couloumbis have you used UpdatePacks in XP2ESD process? My personal recommendation is do not use Legacy Update as UpdatePacks handle all newest file version, including request only hotfixes. There exist one update, which was never leaked and is lost in time.