referring to #30 I implemented some logic in order to determine the actual DiskID for the system disk and the USB stick to be used in the appropriate diskpart scripts. Previously those values have been hard coded.
Behaviour
The logic assumes, that the DeviceID property from diskpart and from Get-PhysicalDevice PowerShell cmdlet are the same. In my test scenarios this has been the case.
When there is only one physical disk detected which is connected via USB and one device which is not USB, the corresponding DiskIDs are mapped automatically.
In case there is more than one disk, the user has to choose where Windows should be installed. However due to a lack of devices with more than one internal disk I was not able to test this part of the script.
tabs-not-spaces
commented
3 years ago
Hello,
referring to #30 I implemented some logic in order to determine the actual DiskID for the system disk and the USB stick to be used in the appropriate diskpart scripts. Previously those values have been hard coded.
Behaviour The logic assumes, that the DeviceID property from diskpart and from Get-PhysicalDevice PowerShell cmdlet are the same. In my test scenarios this has been the case.
When there is only one physical disk detected which is connected via USB and one device which is not USB, the corresponding DiskIDs are mapped automatically.
In case there is more than one disk, the user has to choose where Windows should be installed. However due to a lack of devices with more than one internal disk I was not able to test this part of the script.