[core] don't analyse boot records of deleted partition

* Also revert a472e96e87 as this is creating
  unwanted detection issues as per #1239. We'll try to devise a better way
  to avoid intempestive refreshes later on.
This commit is contained in:
Pete Batard 2018-11-28 11:12:54 +00:00
parent c0526b3e8b
commit 4cd308a1c0
No known key found for this signature in database
GPG key ID: 38E0CF5E69EDD671
3 changed files with 6 additions and 15 deletions

View file

@ -1831,9 +1831,6 @@ DWORD WINAPI FormatThread(void* param)
if (!zero_drive && !write_as_image) {
PrintInfoDebug(0, MSG_226);
AnalyzeMBR(hPhysicalDrive, "Drive", FALSE);
if ((hLogicalVolume != NULL) && (hLogicalVolume != INVALID_HANDLE_VALUE)) {
AnalyzePBR(hLogicalVolume);
}
UpdateProgress(OP_ANALYZE_MBR, -1.0f);
}
@ -1842,7 +1839,7 @@ DWORD WINAPI FormatThread(void* param)
goto out;
}
// Zap any existing partitions. This helps prevent access errors.
// Zap partition records. This helps prevent access errors.
// Note, Microsoft's way of cleaning partitions (IOCTL_DISK_CREATE_DISK, which is what we apply
// in InitializeDisk) is *NOT ENOUGH* to reset a disk and can render it inoperable for partitioning
// or formatting under Windows. See https://github.com/pbatard/rufus/issues/759 for details.