Edition / SKU is not important in these inputs. I just tested that link and it works without issues here.
I think he wants to know if / when there will be a new release ........ and at what stage its at ......... and what problems there are to be solved before a new release .
In first place trying to support all supported In-place upgrade scenarios from Windows XP and Windows Server 2003 to themselves, and in second place to have a starting point to implement those not officially supported (e.g. client to server, x86 to amd64, ...)
Well I have been away from this project for few weeks due lack of time in real work. But I can tell 1.6.3 is cancelled and it became 1.7 as changelog is bigger than 1.6 release I have few unresolved bugs reported by users with testing ISO, but I'm close to solve all of them. From big things that must be done there is only one - fix all RES for 38 languages for great polished UI in installer Also 2003 UpdatePacks are almost ready, @MilkChan greatly contributed in this way. When I build all languages we need to retest them again to be sure they are OK as there is really huge amount of manual work on each language. But we are close to have 2003 packs as FINAL
In XP2ESD's setup.cmd file, the boot partition can be successfully hidden much easier with Bootice inside XP2ESD's boot.wim (in boot.wim's \Windows\system32 directory): Code: if /i "%BootPartition%" == "Yes" ( bootice /DEVICE=U: /partitions /hide /quiet >nul ) Ensure that this is added after all the changes In the U: partition to avoid errors.
OK i was able to create the WinXP_AIO_ESD.iso When i boot the usb iso made with rufus (mbr/bios) on physical Zotac pc N2087 bay trail i get this message: setup cant detect esd/wim/swm file in source folder of setup media.(missing driver) Instead if using w7+w10 iso should i use w8+w10 iso or just w10 iso ?
Hi George, About in-place upgrade paths, it is a question of completeness in engineering. Or said in other words how to finish the engineering job without being stopped by marketing /sales short term objectives curated from any sustainability awareness. This still could be fixed, at least for NT 5.1/5.2 and ReactOS could be the delivery vehicle within a few years. Backporting key technologies like DISM provider architecture could help. About legacyupdate.net it is somehow the same spirit according to sustainability, where forbidden planned obsolescence and right to repair are basic concepts/values. If Windows Update is dead, long life to legacyupdate.net and why not to integrate it with UpdatePacks (I mean using a common package management technology for both offline and online updates management)?
I've got an usb bootable working XP cant remeber on wich PC i made it but on newer hardware it will crash, i had no problem till now to boot win7 from usb even on new hardware
I want to do the same on XP , win7 x64 for me boots fine from usb, maybe win8 and win10 but i dislike.
In place upgrades fixed broken installations for two decades (in pre vista OS, also unbootable OSes can be fixed), still works in 2023. No, absolutely not. Each time you format instead of fix is a surrender, and a lost chance to learn something new.