@Gelip, use LISTDISK for grabbing data only for now. Diskpart is 100% useles in this case as you need to run gazilions scripts and command to collect not exact values. Use listdisk to get rid of diskpart for displaying. Speed is visible in my tests. Use bootice for mounting and handling partition settings, just need to use partition-1 (not sure if real values are based from zero, but MS structure starts from 1 when counting physical partitions). Your mounvol command wont work in many cases (tested in past) P.S. We are not talking about only EFI partition. We call it boot partition which in MBR can be NTFS or FAT32 used for BIOS or UEFI boot. In GPT only FAT32 due UEFI boot. And we need to cover original boot methods first (My newly developed setup.cmd currently works fine with tons of scenarios, using tools mix it's much smaller because we don't need to handle with diskpart anymore, Also works with unattended without any ussue ).
No, bootice also uses other disk and partition numbers - probably the same as diskpart so still listdisk is useless for me What cases - give an example other than I wrote (two or more EFI partitions) mountvol /s works only on the GPT disk when there is an EFI partition on it
@Gelip Read again this, thats reality. Code: https://forums.mydigitallife.net/threads/tool-xp2esd-create-modern-windows-xp-installer-v1-6-2.82935/page-148#post-1823547 And again, as you told mountvol is useless when it works only in GPT disk.
Hey, I just started using this tool but it seems to hang after step 4 of making the ISO, mine has been running about an hour and hasn't gotten past that point. Do I have something missing or should I try to deploy the tool on something older instead of Windows 11
Code: REM Change default console width to 95 reg add "HKLM\TEMPDEFAULT\Console\%%SystemRoot%%_system32_cmd.exe" /v "ScreenBufferSize" /t REG_DWORD /d "19660895" /f >nul reg add "HKLM\TEMPDEFAULT\Console\%%SystemRoot%%_system32_cmd.exe" /v "WindowSize" /t REG_DWORD /d "1638495" /f >nul
So an update to my previous query, I moved the location where I was running the project and I managed to get it to create the virtual machine; however, I seem to be doing something wrong I suppose because the VM has been running for 6 hours straight just doing the first part of the install. i9-9900k 32GB of ram running from an SSD Windows 11 750 Ti (dont ask why, just temporary anyway) I feel like my vm shouldnt be having these issues, especially since its running at less than 11% of my cpu and using 520mb of ram at the moment. Any advice to speed this up would be amazing.
Hey George King If Its no too much to ask can i test it as well i really be grateful to be your beta tester on something i have been trying to do for years (Installing Win XP on modern hardware)
@George King On the first page, you should replace the link to Snappy (sdi-tool) to Snappy Origin (snappy-driver-installer). The former's download page links to malware/unauthorized version of Snappy. There's apparently some sort of drama going on how the original site was hijacked from the original author. Also, this is off-topic I guess, but is there something wrong with the "Ramsey XP" besides the whole copyright infringement thing... Installing via XP2ESD seems like a bit of a hassle. I just want to revisit old XP games on a modern-ish system that is not officially supported.
When times come, first post will be rewritten. Well using “Integral edition” is different method a lot. We are deploying Syspreped images in same way like all modern Windows. Instead installing.
OT listdisk on some of my pc === HP w7pro x64 240gb Failed to open 00000000002AF080, Error: 5 === HP w7pro x64 500gb Failed to open 00000000001EEBC0, Error: 5 === HP w10home x64 Failed to open 000000ABB2DEF0D0, Error: 5 Failed to open 000000ABB2DEF0D0, Error: 5